[
https://issues.apache.org/jira/browse/LUCENE-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412178#comment-16412178
]
Steve Rowe commented on LUCENE-3543:
------------------------------------
The maven ant tasks project, which Lucene/Solr uses to install/deploy maven
artifacts, has been defunct for a while. I'm kinda surprised it mostly still
works :). I've been thinking we'll have to switch to something Ivy-based
(assuming the build system remains as Ant) in the relatively near future.
Here's a patch that appears to fix the problem for me (info source:
[http://maven.apache.org/ant-tasks/reference.html#install]) - just add
{{uniqueVersion="false"}} to the {{<artifact:deploy>}} tag in the {{m2-deploy}}
macro in {{common-build.xml}}:
{noformat}diff --git a/lucene/common-build.xml b/lucene/common-build.xml
index 86e4288..408dd1d 100644
--- a/lucene/common-build.xml
+++ b/lucene/common-build.xml
@@ -640,7 +640,7 @@
<artifact:install-provider artifactId="wagon-ssh" version="1.0-beta-7"/>
<parent-poms/>
<artifact:pom id="maven.project" file="@{pom.xml}"/>
- <artifact:deploy file="@{jar.file}">
+ <artifact:deploy file="@{jar.file}" uniqueVersion="false">
<artifact-attachments/>
<remoteRepository id="${m2.repository.id}" url="${m2.repository.url}">
<credentials/>
{noformat}
> 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]
