[
https://issues.apache.org/jira/browse/LUCENE-5322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13819327#comment-13819327
]
Steve Rowe edited comment on LUCENE-5322 at 11/11/13 8:19 PM:
--------------------------------------------------------------
Currently {{validate-maven-artifacts}} invokes {{filter-pom-templates}} once
per POM, which is way too much; also, {{validate-maven-artifacts}} depends on
{{generate-maven-artifacts}}, even though it only needs the filtered POMs, and
not the built artifacts.
This patch fixes both issues.
Committing shortly.
was (Author: steve_rowe):
Currently {{validate-maven-artifacts}} invokes {{filter-pom-templates}} once
per POM, which is way too much; also, {{validate-maven-artifacts}} depends on
{{generate-maven-artifacts}}, even though it only needs to filtered POMs, and
not the built artifacts.
This patch fixes both issues.
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.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
