[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jedit-devel
Subject:    Re: [ jEdit-devel ] AntFarm updated
From:       Alan Ezust <alan.ezust () gmail ! com>
Date:       2020-11-11 14:59:25
Message-ID: CALy5K9rgJwB419pJUNA=-tgmDAe+6=QCEOxY_PtKyYp-97Y+zA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Mon, Nov 9, 2020 at 7:04 PM orbitalair <orbitalair@gmail.com> wrote:

>
> Thanks Alan.
>
> xsltproc does work.  IF i manually copy the build-support/users-guide.xls
> to AntFarm/build/docs.
>
> I made all sorts of relative and absolute path settings for user-doc.xsl=
> in the build.properties file.  No go.  IIRC setting an absolute path/file
> for this caused a nullpointer crash when executing doc-xsltproc ant task.
>

> It will work if I copy the file.  Its one of a couple of annoyances.
>
> The other is this; why is the docs and extras folders flattened in the jar
> file?  all the doc/ files go into the root.
> Kinda of annoying in AntPlugin where there are a lot of doc/ files in
> there.
>

I agree, this decision was made a long time ago by someone else, I think it
was the developer of the common build scripts.


>
> Finally, should the javadocs be included in the jars as a good practice?
> I dont see where Jedit can access them, but I might have missed it.
> (I see where some help files include them, but they are too tiny to
> actually read.)
>

That is my fault and it seemed like a good idea at the time, but I agree it
is not necessary now.
If someone wants to modify the build-support files to stop generating and
including javadocs, I have no objection to that.

[Attachment #5 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Mon, Nov 9, 2020 at 7:04 PM orbitalair &lt;<a \
href="mailto:orbitalair@gmail.com">orbitalair@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div><br></div><div>Thanks Alan.</div><div><br></div><div>xsltproc does \
work.   IF i manually copy the build-support/users-guide.xls to \
AntFarm/build/docs.</div><div><br></div><div>I made all sorts of relative and \
absolute path settings for user-doc.xsl= in the build.properties file.   No go.   \
IIRC setting an absolute path/file for this caused a nullpointer crash when executing \
doc-xsltproc ant task. <br></div></div></blockquote><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>It will work if \
I copy the file.   Its one of a couple of annoyances.</div><div><br></div><div>The \
other is this; why is the docs and extras folders flattened in the jar file?   all \
the doc/ files go into the root.</div><div>Kinda of annoying in AntPlugin where there \
are a lot of doc/ files in there.</div></div></blockquote><div><br></div><div>I \
agree, this decision was made a long time ago by someone else, I think it was the \
developer of the common build scripts. <br></div><div>  </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Finally, should \
the javadocs be included in the jars as a good practice?</div><div>I dont see where \
Jedit can access them, but I might have missed it.</div><div>(I see where some help \
files include them, but they are too tiny to actually \
read.)<br></div></div></blockquote><div><br></div><div>That is my fault and it seemed \
like a good idea at the time, but I agree it is not necessary now. <br></div><div>If \
someone wants to modify the build-support files to stop generating and including \
javadocs, I have no objection to that.</div><div><br></div><br></div></div>





-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel


[prev in list] [next in list] [prev in thread] [next in thread]