Re: [vote] Release maven-deploy-plugin 2.2.1

[John Casey <ca...@gmail.com>]

Yes, you're right Mike. I've changed the subject accordingly...

Brett, what I meant was that Maven cannot use a custom pluginRepository
location given in a settings profile if there isn't a pom.xml running the
build. While I know we have the apache.snapshots repository location
available for normal artifact resolution, I'm pretty sure it's not available
for plugin resolution. So, I'm not sure how you can use the deployed plugin
snapshot via deploy:deploy-file. There is a bug filed against MNG for this,
scheduled for 2.0.5.

-john

On 6/6/06, Mike Perham <Mi...@webifysolutions.com> wrote:
>
> John, is this going to be 2.3 or 2.2.1?  If it's just bugfixes,
> shouldn't it be 2.2.1?
>
> -----Original Message-----
> From: John Casey [mailto:casey.john.d@gmail.com]
> Sent: Monday, June 05, 2006 11:56 PM
> To: Maven Developers List
> Subject: Re: [vote] Release maven-deploy-plugin 2.3
>
> BTW, the test snapshot for this release is 2.2.1-20060606.044331-3, on
>
> http://cvs.apache.org/maven-snasphot-repository
>
> Though you may have trouble trying to use the deploy-file mojo from
> there.
> The SVN revId is: 411999.
>
> -john
>
> On 6/6/06, John Casey <ca...@gmail.com> wrote:
> >
> > Hi,
> >
> > I've noticed that some people have had trouble with a few bugs in the
> > current release of the maven-deploy-plugin, including:
> >
> > * POM and artifact build numbers are out of sync when using
> -DpomFile=...
> > * Repository layout is not configurable
> >
> > I've checked, and both of these problems have been fixed.
> > Additionally, I've gone over the documentation for this plugin, and it
>
> > all looks to be in pretty good shape, including the parameter
> > javadocs. Though it would be a small release, I believe that these two
> bugfixes warrant a fresh release.
> > The only outstanding bug marked for 2.3 is MDEPLOY-28, which depends
> > on a fix in maven-wagon...I don't believe this issue should hold up
> > the release of 2.3.
> >
> > I'd like to open up the vote for 72 hours. Please cast your +1/+0/-1.
> >
> > Here's my +1.
> >
> > Thanks,
> >
> > john
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: [vote] Release maven-deploy-plugin 2.2.1

[Brett Porter <br...@apache.org>]

Hi John,

Can you reset the versions in JIRA and call this vote again?

(yes, I know I have a vote from mid-may on the WAR plugin still hanging 
out there. I found more issues to fix and hope to get to it this week).

- Brett

John Casey wrote:
> Yes, you're right Mike. I've changed the subject accordingly...
> 
> Brett, what I meant was that Maven cannot use a custom pluginRepository
> location given in a settings profile if there isn't a pom.xml running the
> build. While I know we have the apache.snapshots repository location
> available for normal artifact resolution, I'm pretty sure it's not 
> available
> for plugin resolution. So, I'm not sure how you can use the deployed plugin
> snapshot via deploy:deploy-file. There is a bug filed against MNG for this,
> scheduled for 2.0.5.
> 
> -john
> 
> On 6/6/06, Mike Perham <Mi...@webifysolutions.com> wrote:
>>
>> John, is this going to be 2.3 or 2.2.1?  If it's just bugfixes,
>> shouldn't it be 2.2.1?
>>
>> -----Original Message-----
>> From: John Casey [mailto:casey.john.d@gmail.com]
>> Sent: Monday, June 05, 2006 11:56 PM
>> To: Maven Developers List
>> Subject: Re: [vote] Release maven-deploy-plugin 2.3
>>
>> BTW, the test snapshot for this release is 2.2.1-20060606.044331-3, on
>>
>> http://cvs.apache.org/maven-snasphot-repository
>>
>> Though you may have trouble trying to use the deploy-file mojo from
>> there.
>> The SVN revId is: 411999.
>>
>> -john
>>
>> On 6/6/06, John Casey <ca...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > I've noticed that some people have had trouble with a few bugs in the
>> > current release of the maven-deploy-plugin, including:
>> >
>> > * POM and artifact build numbers are out of sync when using
>> -DpomFile=...
>> > * Repository layout is not configurable
>> >
>> > I've checked, and both of these problems have been fixed.
>> > Additionally, I've gone over the documentation for this plugin, and it
>>
>> > all looks to be in pretty good shape, including the parameter
>> > javadocs. Though it would be a small release, I believe that these two
>> bugfixes warrant a fresh release.
>> > The only outstanding bug marked for 2.3 is MDEPLOY-28, which depends
>> > on a fix in maven-wagon...I don't believe this issue should hold up
>> > the release of 2.3.
>> >
>> > I'd like to open up the vote for 72 hours. Please cast your +1/+0/-1.
>> >
>> > Here's my +1.
>> >
>> > Thanks,
>> >
>> > john
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
> 


-- 
Brett Porter <br...@apache.org>
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org