[
https://issues.apache.org/jira/browse/LUCENE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13221922#comment-13221922
]
Steven Rowe commented on LUCENE-3825:
-------------------------------------
bq. Not that it's especially my business, but how did the snapshots get pushed
historically to nexus if you didn't have access to nexus?
I found the following comment on SOLR-586 that described the process by which
Maven snapshots made it into the Apache snapshot repository:
[https://issues.apache.org/jira/browse/SOLR-586?focusedCommentId=12623985&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12623985].
> Please push maven snapshots to repositories.apache.org again
> ------------------------------------------------------------
>
> Key: LUCENE-3825
> URL: https://issues.apache.org/jira/browse/LUCENE-3825
> Project: Lucene - Java
> Issue Type: Improvement
> Components: general/build
> Affects Versions: 4.0
> Reporter: Benson Margulies
> Assignee: Steven Rowe
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3825-add-scm-to-poms-trunk.patch
>
>
> Once upon a time, snapshots of the lucene trunk went into the snapshot repo
> at repositories.apache.org. No longer. Instead, they just sit at:
> https://builds.apache.org//job/Lucene-Solr-Maven-trunk/lastSuccessfulBuild/artifact/maven_artifacts/
> Unfortunately, Jenkins makes a rather mediocre maven repo. the
> maven-wagon-plugin can't copy it and Nexus can't proxy it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
