[
https://issues.apache.org/jira/browse/SOLR-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061325#comment-13061325
]
Benson Margulies commented on SOLR-2634:
----------------------------------------
So, if you apply the patch, folks like me can trivially deliver snapshots to
repo managers that use password authentication.
You can deliver to the Apache snapshot repo by changing your jenkins job to
look like:
ant generate-maven-artifacts
-Dm2.repository.url=https://repository.apache.org/content/repositories/snapshots/
-Dm2.repository.username="whoever" -Dm2.repository.password="whatever"
There is some scheme on the jenkins instance for these credentials, I can
research it for you.
My elders and betters at d...@maven.apache.org tell me that the thing that you
have is really not a good idea from either a Jenkins or a Maven standpoint.
Following my recipe here will change nothing about the publicity/policy issues,
it will retain some old snapshots which might be useful, and it will generally
work better.
> Publish nightly snapshots, please
> ---------------------------------
>
> Key: SOLR-2634
> URL: https://issues.apache.org/jira/browse/SOLR-2634
> Project: Solr
> Issue Type: Improvement
> Components: Build
> Affects Versions: 3.4
> Reporter: Benson Margulies
> Assignee: Steven Rowe
> Attachments: SOLR-2634.patch, SOLR-2634.patch
>
>
> If you added 'mvn deploy' to the jenkins job, the nightly snapshots would
> push to repository.apache.org as snapshots, where maven could get them
> without having to manually download and deploy them. Please?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
