Could have sworn I tested that. In any case, apologies for the bad info.

I think it would be reasonably easy to create a custom release plugin that 
worked in the way you're describing.

----- Original Message -----
From: Todd Thiessen <[EMAIL PROTECTED]>
To: Maven Users List <users@maven.apache.org>
Sent: Thu Dec 04 11:18:59 2008
Subject: RE: Limitation of the release plugin?

Not so. Doing a working copy with uncommited changes actually does work
with SVN 1.5.4.

But it may be not supported in other SCMs. That I can understand. The
term "working copy" does normally include uncommited files though.

---
Todd Thiessen
 

> -----Original Message-----
> From: Edelson, Justin [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, December 04, 2008 11:09 AM
> To: users@maven.apache.org
> Subject: Re: Limitation of the release plugin?
> 
> Copying a working copy with uncommitted changes. It's part 
> the SCM-406 issue. 
> 
> ----- Original Message -----
> From: Todd Thiessen <[EMAIL PROTECTED]>
> To: Maven Users List <users@maven.apache.org>
> Sent: Thu Dec 04 10:57:19 2008
> Subject: RE: Limitation of the release plugin?
> 
> What won't?
> 
> ---
> Todd Thiessen
>  
> 
> > -----Original Message-----
> > From: Edelson, Justin [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, December 04, 2008 10:55 AM
> > To: users@maven.apache.org
> > Subject: Re: Limitation of the release plugin?
> > 
> > And it won't work on SVN 1.5.x
> > 
> > ----- Original Message -----
> > From: Brian E. Fox <[EMAIL PROTECTED]>
> > To: Maven Users List <users@maven.apache.org>
> > Sent: Thu Dec 04 10:53:03 2008
> > Subject: RE: Limitation of the release plugin?
> > 
> > Yeah but it sounds like you're thinking in svn terms only. 
> > This might not work for all scms.
> > 
> > -----Original Message-----
> > From: Todd Thiessen [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, December 04, 2008 7:45 AM
> > To: Maven Users List
> > Subject: RE: Limitation of the release plugin?
> > 
> > My suggestion though is to not commit at all. Just do a 
> working copy.
> > So no commit to tags would be required.
> > 
> > ---
> > Todd Thiessen
> >  
> > 
> > > -----Original Message-----
> > > From: Brian E. Fox [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, December 04, 2008 10:42 AM
> > > To: Maven Users List
> > > Subject: RE: Limitation of the release plugin?
> > > 
> > > Many scm's don't let you commit changes to tags, which is why it 
> > > commits to trunk first and then tags.
> > > 
> > > -----Original Message-----
> > > From: Todd Thiessen [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, December 04, 2008 6:18 AM
> > > To: Maven Users List
> > > Subject: RE: Limitation of the release plugin?
> > > 
> > > Have anyone considered changing the release plugin such
> > that it does
> > > not commit the changes to the POM which removes SNAPSHOT from the 
> > > version?
> > > The only negative I can see is that you don't see a 
> history of this 
> > > change in your trunk.  But this shouldn't matter since you
> > have a copy
> > > of this POM in your tags.  In fact, this makes more sense to me 
> > > anyway.
> > > I don't like seeing a released version of my POM in my
> > trunk history.
> > > 
> > > So to be clear, the steps would be changed to this (roughly):
> > > 
> > > 1. Make changes to the POM in your working copy to remove 
> "SNAPSHOT"
> > > from the version and make changes to your SCM entries to
> > point to your
> > > tags instead of your trunk. (Same) 2. DO NOT commit this
> > change back
> > > to trunk. (Different).
> > > 3. Do an svn copy of your working directory to your tags,
> > just as it
> > > does today. (Same) 4. ... continue as normal
> > > 
> > > Are there any negatives to this that I have overlooked?
> > > 
> > > ---
> > > Todd Thiessen
> > > 
> > > 
> > > 
> > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > 
> > > 
> > > 
> > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > 
> > > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to