[ 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.patch Patch. Targets that don't need to be public are made private. Each of the three versions of generate-maven-artifacts makes sure that resolve, -unpack-(lucene and or solr)-tgz, and -filter-pom-templates is called. Then recursive non-public -dist-maven doesn't have to worry about these things being done. This patch also fixes the problem introduced by LUCENE-5217 with resolve not being called before get-maven-poms and filter-pom-templates. I'll commit this to trunk shortly, then to branch_4x after LUCENE-5217 has been committed to branch_4x, in a few days. > 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.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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org