You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/03/15 07:00:32 UTC
[jira] Closed: (CONTINUUM-609) Continuum deployment repository
[ http://jira.codehaus.org/browse/CONTINUUM-609?page=all ]
Brett Porter closed CONTINUUM-609:
----------------------------------
Resolution: Fixed
> Continuum deployment repository
> -------------------------------
>
> Key: CONTINUUM-609
> URL: http://jira.codehaus.org/browse/CONTINUUM-609
> Project: Continuum
> Type: Improvement
> Components: Core system
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 1.0.3
>
> Original Estimate: 3 hours
> Time Spent: 2 hours, 30 minutes
> Remaining: 0 minutes
>
> What I was thinking of was having Continuum be configured to have a
> repository that is the default location for deploying JARs to and that
> can be served up without requiring an additional web server. This would
> make configuration of a "snapshot repository" much simpler.
> I'm thinking this wouldn't be required in the POM at all - that even
> though the goals are "clean install", that Continuum would deploy to
> this repository itself after the build completed successfully. Using
> "deploy" wouldn't be desirable because you might accidentally wind up
> deploying a release which is probably not what you want.
> I was thinking this is purely a deployment repository, so would not be the "local repository" for continuum at all.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira