[
https://issues.apache.org/jira/browse/LUCENE-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412203#comment-16412203
]
Steve Rowe commented on LUCENE-3543:
------------------------------------
Also, {{ant validate-maven-artifacts}} depends on {{-install-maven-artifacts}},
which will use the {{-SNAPSHOT}} suffix when populating the local repository.
Maybe we could make {{-install-maven-artifacts}} callable from the cmdline by
removing its leading dash?
> Add previous versions to maven-metadata.xml files generated by 'ant
> generate-maven-artifacts'
> ---------------------------------------------------------------------------------------------
>
> Key: LUCENE-3543
> URL: https://issues.apache.org/jira/browse/LUCENE-3543
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/build
> Affects Versions: 3.4, 4.0-ALPHA
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Major
>
> The {{generate-maven-artifacts}} target generates one {{maven-metadata.xml}}
> file per artifact. In a repository, these files should contain a list of all
> previous releases along with the current release, but because Maven Ant Tasks
> doesn't have access to these versions, it does not include them in the files
> it produces.
> Two possible solutions:
> # download Maven central's versions of the files prior to running
> {{generate-maven-artifacts}} and pre-populate the target local repository; or
> # post-process the files to include the previous versions - this would
> require some form of access to the previously released versions for each
> artifact being published
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
