Mailing List Archive: Lucene: Java-Dev

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs

Index | Next | Previous | View Threaded

jira at apache

Nov 13, 2007, 9:22 PM

Post #1 of 10 (371 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542322 ]

Michael Busch commented on LUCENE-1051:
---------------------------------------

I'm planning to commit this tomorrow... any objections? Did anyone look at the preview yet?

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 13, 2007, 11:41 PM

Post #2 of 10 (339 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542356 ]

Paul Elschot commented on LUCENE-1051:
--------------------------------------

This has been somewhere far down on my todo list for quite a while, so I was going to try the patch, but a committed version would certainly be easier. In case you prefer someone else to try this before committing, could you wait a (short) week?

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 4:52 AM

Post #3 of 10 (336 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542444 ]

Grant Ingersoll commented on LUCENE-1051:
-----------------------------------------

Looks good. I think we need to put GData in before committing.

Also, I don't know ANT well enough, but is there anyway to have it automatically do the contrib packages without having to explicitly specify it? Just one less thing to remember to add when adding new contrib packages. If it's not a quick fix, don't worry about.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 10:23 AM

Post #4 of 10 (335 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542527 ]

Michael Busch commented on LUCENE-1051:
---------------------------------------

{quote}
Looks good. I think we need to put GData in before committing.
{quote}

GData has build files that don't extend common-build.xml, so there's always extra work that needs to be done when we add a new feature to our build (like maven artifacts or these javadocs improvements). It doesn't seem that Simon is still around, but we should decide on how we're going to maintain gdata. I'll open a new issue for that and not put GData in this patch.

{quote}
Also, I don't know ANT well enough, but is there anyway to have it automatically do the contrib packages without having to explicitly specify it? Just one less thing to remember to add when adding new contrib packages. If it's not a quick fix, don't worry about.
{quote}

Hmm, not sure how to do that. There's a TODO comment in the build file for a long time. I think I'll commit this patch and we can simplify that in the future if someone knows who to do this with Ant.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 10:40 AM

Post #5 of 10 (336 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542536 ]

Doug Cutting commented on LUCENE-1051:
--------------------------------------

> we should decide on how we're going to maintain gdata

Are many folks using Lucene's gdata server? If no one is using it, and it's not maintained, then it should probably be dropped from trunk. If someone decides to start maintaining it later, then they could update it and re-add it to trunk.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 10:40 AM

Post #6 of 10 (335 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542537 ]

Paul Elschot commented on LUCENE-1051:
--------------------------------------

The take2 patch works fine for me. Also this works fine:
ant -Djavadoc.access=private javadocs-core
but it generates two minor javadoc warnings.

Grant:
ant javadocs generates everything combined and everything seperately,
and ant javadocs-contrib works as expected.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 10:44 AM

Post #7 of 10 (336 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542538 ]

Hoss Man commented on LUCENE-1051:
----------------------------------

the note about keeping the contrib list uptodate with the group list should also mention keeping the list in site.xml uptodate.

we could probably make that site.xml list autogenerated by the javadoc target, but that would require someone with ant fu and forrest fu thinking about it carefully ... in the meantime a reminder note would be handy.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 10:50 AM

Post #8 of 10 (334 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542542 ]

Michael Busch commented on LUCENE-1051:
---------------------------------------

{quote}
Are many folks using Lucene's gdata server? If no one is using it, and it's not maintained, then it should probably be dropped from trunk. If someone decides to start maintaining it later, then they could update it and re-add it to trunk.
{quote}

+1

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 14, 2007, 10:52 AM

Post #9 of 10 (336 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542543 ]

Michael Busch commented on LUCENE-1051:
---------------------------------------

{quote}
The take2 patch works fine for me.
{quote}

Thanks for trying! I will commit then...

{quote}
the note about keeping the contrib list uptodate with the group list should also mention keeping the list in site.xml uptodate.
{quote

Agreed. I'll update the comment.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

jira at apache

Nov 16, 2007, 11:29 AM

Post #10 of 10 (336 views)
Permalink

[jira] Commented: (LUCENE-1051) Separate javadocs for core and contribs [In reply to]

[ https://issues.apache.org/jira/browse/LUCENE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543179 ]

Grant Ingersoll commented on LUCENE-1051:
-----------------------------------------

OK, this should be up live on the site now. I still have to check into why the site isn't being copied properly. Will do when I get back from ApacheCon.

> Separate javadocs for core and contribs
> ---------------------------------------
>
> Key: LUCENE-1051
> URL: https://issues.apache.org/jira/browse/LUCENE-1051
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Javadocs
> Reporter: Michael Busch
> Assignee: Michael Busch
> Priority: Minor
> Fix For: 2.3
>
> Attachments: lucene-1051-take2.patch, lucene-1051.patch
>
>
> A while ago we had a discussion on java-dev about separating the javadocs
> for the contrib modules instead of having only one big javadoc containing
> the core and contrib classes.
> This patch:
> * Adds new targets to build.xml:
> ** "javadocs-all" Generates Javadocs for the core, demo, and contrib
> classes
> ** "javadocs-core" Generates Javadocs for the core classes
> ** "javadocs-demo" Generates Javadocs for the demo classes
> ** "javadocs-contrib" Using contrib-crawl it generates the Javadocs for
> all contrib modules, except "similarity" (currently empty) and gdata.
> * Adds submenues to the Javadocs link on the Lucene site with links to
> the different javadocs
> * Includes the javadocs in the maven artifacts
> Remarks:
> - I removed the ant target "javadocs-internal", because I didn't want to
> add corresponding targets for all new javadocs target. Instead I
> defined a new property "javadoc.access", so now
> "ant -Djavadoc.access=package" can be used in combination with any of
> the javadocs targets. Is this ok?
> - I didn't include gdata (yet) because it uses build files that don't
> extend Lucenes standard build files.
>
> Here's a preview:
> http://people.apache.org/~buschmi/site-preview/index.html
> Please let me know what you think about these changes!

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads