[
https://issues.apache.org/jira/browse/SOLR-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140564#comment-16140564
]
Steve Rowe commented on SOLR-11181:
-----------------------------------
bq. Was the patch ok?
Yes, the patch was ok.
The problem isn't with {{generate-maven-artifacts}}, but rather with
{{validate-maven-artifacts}}. Both these targets are run by Jenkins via the
{{jenkins-maven-nightly}} target.
The problem is that {{validate-maven-artifacts}} first removes all Lucene/Solr
artifacts from the local Maven repository, and then attempts to resolve each
artifact's dependencies from the local repository by disabling remote
resolution. Apparently because of the re-ordering of the {{artifact:deploy}}
and {{artifact:install}} tasks (as a result of your patch), (some?) depended-on
artifacts are no longer populated in the local repository.
Since {{validate-maven-artifacts}} needs only {{artifact:install}}, and not
{{artifact:deploy}}, I'm thinking we could add an {{m2-install}} macro to be
used instead. I'm not yet sure how {{m2-deploy}} is called via
{{validate-maven-artifacts}} though.
bq. Anything I can do to help?
If you're up for it, you could a) investigate whether
{{generate-maven-artifacts}} currently does any local repository installation
(if not, that's a problem); and/or b) look into the feasibility of, and
possibly implement, my above {{m2-install}} idea.
> Deploying Maven artifacts (generate-maven-artifacts) pushes the same
> artifacts multiple times
> ---------------------------------------------------------------------------------------------
>
> Key: SOLR-11181
> URL: https://issues.apache.org/jira/browse/SOLR-11181
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build
> Affects Versions: 6.6, master (8.0), 7.1
> Reporter: Lynn Monson
> Assignee: Steve Rowe
> Priority: Minor
> Fix For: master (8.0), 7.1
>
> Attachments: SOLR-11181.patch, SOLR-11181.patch
>
>
> When following the instructions in the README.maven file, and watching the
> wire traffic, the build system issues HTTP PUT operations for the same
> artifacts multiple times. For example, issuing this command:
> ant -Dm2.repository.id=my-repo-id \
> -Dm2.repository.url=http://example.org/my/repo \
> generate-maven-artifacts
> from the lucene/ directory will generate redundant puts. For example:
> PUT
> /<path>/org/apache/lucene/lucene-core/<version>/lucene-core-4.10.4-fs.31-sources.jar
>
> PUT
> /<path>/org/apache/lucene/lucene-core/<version>/lucene-core-4.10.4-fs.31-sources.jar.sha1
>
> PUT
> /<path>/org/apache/lucene/lucene-core/<version>/lucene-core-4.10.4-fs.31-sources.jar.md5
> ...
> PUT
> /<path>/org/apache/lucene/lucene-core/<version>/lucene-core-4.10.4-fs.31-sources.jar
>
> ...
> The maven repo I am using does not allow the second PUT and, hence, the build
> fails.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
