[
https://issues.apache.org/jira/browse/BUILDR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416426#comment-13416426
]
Damian Monogue edited comment on BUILDR-642 at 7/17/12 6:24 PM:
----------------------------------------------------------------
We use ~/.buildr/buildr.rb for this, in combination with the buildr
environment. For release builds we pass -e release, and for nonrelease builds
we pass -e integration . Then in ~/.buildr/buildr.rb we case Buildr.environment
and set repositories.release_to accordingly.
ETA: this is less of a hassle for us than those invoking manually because we
using a continuous integration server to run nearly all of our builds. I do
still agree that being able to set a release url and a snapshot url separately
would be quite handy
was (Author: dmonogue):
We use ~/.buildr/buildr.rb for this, in combination with the buildr
environment. For release builds we pass -e release, and for nonrelease builds
we pass -e integration . Then in ~/.buildr/buildr.rb we case Buildr.environment
and set repositories.release_to accordingly.
> individual repositories for snapshots and releases
> --------------------------------------------------
>
> Key: BUILDR-642
> URL: https://issues.apache.org/jira/browse/BUILDR-642
> Project: Buildr
> Issue Type: Improvement
> Reporter: Michael Nielsen
>
> We use nexus for maven artifacts. Like other repository managers it require
> snapshots in one place and releases in another.
> My understanding is that buildr use the same URL for both upload (snapshots)
> and release:
> repositories.release_to[:url]
> Release simply calls upload in a separate process. What would be nice is to
> have individual variables for release and upload:
> repositories.release_to[:url]
> repositories.upload_to[:url]
> including username and password.
--
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
