Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer;
  b=YFKspBjgUXR+K0KLU+t1PIyfVIwLqGT33gg55rvJvbJsqxQZFJ+bIDBmM+b+9PVra+k9CDgJXf32dC5Y3aDX1nIFyqE0d/8FaWGsqZibcvqLiWWVE/DU1CLdwicSK7dQVuzlQ9XOujN99u32Lki5tvmNw/ZLCODr9E3O7TnRsKE=
  ;
Message-Id: <8C45BDB2-FAB2-4623-9FBB-8D02AEB93300@yahoo.com>
From: David Jencks <david_jencks@yahoo.com>
To: dev@activemq.apache.org
In-Reply-To: <E71E0484-1093-4AF1-891A-1F9A42BBCAFA@yahoo.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: maven build upgrade?
Date: Sat, 20 Jun 2009 01:37:57 -0700
References: <E71E0484-1093-4AF1-891A-1F9A42BBCAFA@yahoo.com>

I opened https://issues.apache.org/activemq/browse/AMQ-2297  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:

<profile>
<id>apache-release</id>
<properties>
<gpg.passphrase>...your gpg passphrase.......</gpg.passphrase>
</properties>
</profile>

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 https://issues.apache.org/jira/browse/INFRA-2103

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.

thanks
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 https://issues.apache.org/jira/browse/INFRA-1896 
> , 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