activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: maven build upgrade?
Date Sat, 20 Jun 2009 08:37:57 GMT
I opened  and  
committed some changes that do most of what I have in mind.

To see what a release would include run with -Papache-release.

Your settings.xml will need something like this:

<gpg.passphrase>...your gpg passphrase.......</gpg.passphrase>

It looks like actually deploying a trunk snapshot using mvn clean  
deploy -Papache-release is going to have to wait for nexus access for  
activemq.  See

Let me know if the inability to deploy snapshots turns into too much  
of a problem.  I had the wrong impression that deploying snapshots did  
not require per-project permissions, only deploying releases and I  
don't like to deploy uncommitted work.

david jencks

On Jun 17, 2009, at 4:09 PM, David Jencks wrote:

> The build is getting a little out of date.  I'd like to update the  
> parent to apache pom 6 and make some related changes to use the most  
> up to date maven build recommendations.  This will make it a lot  
> easier to produce release candidates that follow the apparent  
> details of apache release policy.  It will also deploy snapshots and  
> releases to the apache nexus instance which is much much much easier  
> to use than the file based repo.
> Also there's some stuff to produce source distros more or less  
> automatically.
> If we agree on this I'll file a jira as a sub-issue of

> , we also need a vote apparently.  We can update the pom and start  
> pushing snapshots immediately.
> One other advantage of nexus is that we can use unique timestamped  
> snapshots rather than non-unique "SNAPSHOT" snapshots which can  
> reduce internal maven confusion a bit.
> I'm primarily thinking of trunk here, I might be able to work on  
> other active branches a bit if I know what they are :-)
> thanks
> david jencks

View raw message