[
https://issues.apache.org/jira/browse/LUCENE-3543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16412023#comment-16412023
]
David Smiley commented on LUCENE-3543:
--------------------------------------
I see something that is either this issue (sorta) or should perhaps be a new
issue. At least it matches the description loosely.
{{ant generate-maven-artifacts}} will indeed populate my local repo with the
artifacts. But the layout when it's a SNAPSHOT is wrong (or seems to be). In
particular, the saved files should have the form
{{solr-test-framework-7.4.0-SNAPSHOT.jar}} but instead I see
{{solr-test-framework-7.4.0-20180323.173533-1.jar}}. As a result, even though
the artifacts are plainly there and in my local repo, they are not there in a
way that allows them to be resolved. I think the way they are saved now makes
sense for a remote style path (e.g. to be served by a webserver as a remote
repo), but not local which doesn't follow the same rules exactly.
I was really pulling my hair out for awhile. I even went so far as to get
Maven's sources (particularly the "maven-resolver") so I could use a debugger
in another program to see why the heck Maven itself wouldn't resolve the
artifacts. AFAICT it didn't care at all about the maven-metadata-local.xml file
(that would have pointed to the "7.4.0-20180323.173533-1") and instead it
insisted the file is named simply with the SNAPSHOT suffix in the obvious way.
> 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]
