*Sent:* Saturday, September 24, 2011 3:12 AM
>
> *To:* [email protected]
> *Subject:* Re: Prettify JS and CSS exceluded from Javadocs
>
> ** **
>
> Hi Steve,
>
> As I noted before, jarring prettify won't solve the problem entirely, as
> the references i
Hi Shai,
Sure, that sounds fine to me.
Steve
From: Shai Erera [mailto:[email protected]]
Sent: Saturday, September 24, 2011 3:12 AM
To: [email protected]
Subject: Re: Prettify JS and CSS exceluded from Javadocs
Hi Steve,
As I noted before, jarring prettify won't solve the problem ent
Hi Steve,
As I noted before, jarring prettify won't solve the problem entirely, as the
references in the HTML will point to an incorrect location.
Why don't we just package prettify.js in the jar like we do with
stylesheet+prettify.css? We only need this .js as we only write in Java ...
It's a t
The patch I gave for lucene/contrib-build.xml's "javadocs" target was wrong (I
placed the tag outside of the jarify invocation). Here's a fixed
patch:
Index: lucene/contrib/contrib-build.xml
===
--- lucene/contrib/contrib-build.xm
Hi Shai,
On 9/22/2011 at 4:09 AM, Shai Erera wrote:
> I looked into how to include the prettify directory with the .jar, and
> the only way I found is to copy the prettify dir to @destDir/prettify
> in "invoke-javadoc" macro. The reason is that when "jarify" is called
> later, it takes only a baseD
ld be included in the .jar
>
> ** **
>
> It’s possible that I messed this up in the packaging work I’ve done
> recently, but if so, it was not intentional.
>
> ** **
>
> Steve
>
> ** **
>
> *From:* Shai Erera [mailto:[email protected]]
> *Sent:* Wed
@lucene.apache.org
Subject: Prettify JS and CSS exceluded from Javadocs
Hi
I noticed that our build does not include the prettify JS and CSS with
Javadocs, unless the javadocs are created for the release. For example, if you
open any of the *javadocs.jar files (core or contrib), you'll see that the
pre
Hi
I noticed that our build does not include the prettify JS and CSS with
Javadocs, unless the javadocs are created for the release. For example, if
you open any of the *javadocs.jar files (core or contrib), you'll see that
the prettify files are missing. Therefore, documentation which relies on i
