[
https://issues.apache.org/jira/browse/LUCENE-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5322:
-------------------------------
Attachment: LUCENE-5322.lucene-javadoc-url.fix.patch
{{ant nightly-smoke}} failed on branch_4x because of a permgen OOM:
https://builds.apache.org/job/Lucene-Solr-SmokeRelease-4.x/125/
I chatted with [~thetaphi] on #lucene-dev IRC, and he thinks the issue is that
groovy is being resolved more than once, in order to define
{{lucene.javadoc.url}}, and it should only be done once.
This patch fixes the problem: {{\-dist\-maven}} in {{solr/build.xml}} now
depends on {{define-lucene-javadoc-url}}, and passes
{{uptodate.and.compiled.properties}}, which includes {{lucene.javadoc.url}},
down the call chain.
Committing shortly.
> Clean up / simplify Maven-related Ant targets
> ---------------------------------------------
>
> Key: LUCENE-5322
> URL: https://issues.apache.org/jira/browse/LUCENE-5322
> Project: Lucene - Core
> Issue Type: Task
> Components: general/build
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Minor
> Fix For: 4.6, 5.0
>
> Attachments: LUCENE-5322.lucene-javadoc-url.fix.patch,
> LUCENE-5322.patch, LUCENE-5322.validate-maven-artifacts.patch
>
>
> Many Maven-related Ant targets are public when they don't need to be, e.g.
> dist-maven and filter-pom-templates, m2-deploy-lucene-parent-pom, etc.
> The arrangement of these targets could be simplified if the directories that
> have public entry points were minimized.
> generate-maven-artifacts should be runnable from the top level and from
> lucene/ and solr/.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
