maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ron Wheeler <>
Subject Re: Can't specify distributionManagement in settings.xml
Date Wed, 06 Oct 2010 19:17:28 GMT
  On 06/10/2010 2:42 PM, Siegmann Daniel, NY wrote:
> Phillip,
> Nexus supports deployment via HTTP. Probably other repo managers do too.
> Using Maven in a corporate setting without having a repository manager
> is like working in a team without a version control system. You could do
> it but you're going to suffer.
It makes Maven so much easier to understand and gives you lots of nice 
features for managing and controlling your use of dependent libraries 
besides a good visual interface into your own artifacts:
For example:
  browse Maven Central proxy in your repo to find the right artifactId 
and groupId and latest versions for third party stuff.
  upload a third party package that is not distributed through Maven 
Central so that your team gets it without adding anything to their 
  add a new repo for a special package without touching everyone's 
settings.xml just by adding it to your central proxy definition.
  quickly find the latest version of a library that is available just by 
looking in the index of your repo's proxy.
  developers can delete their own local Maven cache without having a 
huge penalty since the repo has a copy of everything that you have on 
your workstation and only gets new things from the Internet, once.

Much better sense of being in control of Maven artifacts.


> ~Daniel
> -----Original Message-----
> From: Phillip Hellewell []
> Sent: Wednesday, October 06, 2010 11:55 AM
> To: Maven Users List
> Subject: Re: Can't specify distributionManagement in settings.xml
> On Wed, Oct 6, 2010 at 9:28 AM, Anders Hammar<>  wrote:
>> Please, please, please have a look at a repo manager. It has these
> type of
>> features. That's why it's called a manager.
> I'm sure a repo manager can do fancy things with multiple repositories
> for downloading, and I am already working on getting Nexus set up
> today.  But I don't see how a repo manager will solve my problem with
> deployment.  You can't deploy with the HTTP protocol, can you?  It has
> to be something like scp://, ftp://, or file://.  Are there repo
> manageres that interject somehow in the deployment phase.
> Since the<distributionManagement>  can only specify two kinds of
> repositories, snapshot and normal (release), I am thinking that I need
> to decide that (from a deployment perspective at least) there are only
> two repositories, so I should probably combine my idea of a "staging"
> repository with the snapshot repository.
> But I'll still need to copy between repositories (copy a non-snapshot
> artifact from the snapshot repository to the release repository), so
> if stage:copy is not the best way to do this, I'm hoping to find that
> this is something Nexus or another repo manager can do easily.
> Phillip
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message