Will do, I won't have time to post the issue until this Friday.
On 4/11/06, dan tran <[EMAIL PROTECTED]> wrote: > > please post both logs for beta3 and beta4-snapshot > > On 4/11/06, dan tran <[EMAIL PROTECTED]> wrote: > > > > JIRA is needed, please post a complete log with -X turn on. > > > > -D > > > > > > On 4/11/06, Todd Nine <[EMAIL PROTECTED]> wrote: > > > > > > I tried the latest snapshot 2.0-beta-4-snapshot(built from svn) as > your > > > recommended, but I had the same issue, so I rolled back to > 2.0-beta3since > > > it was released. > > > > > > Todd > > > > > > On 4/11/06, dan tran <[EMAIL PROTECTED]> wrote: > > > > > > > > we have not had a new beta for release plugin for a long time, > perhaps > > > a > > > > the > > > > snapshot would solve this issue? > > > > > > > > -D > > > > > > > > > > > > On 4/11/06, Todd Nine <[EMAIL PROTECTED]> wrote: > > > > > > > > > > This definitely seems like a bug, I'm glad someone else has seen > > > this > > > > > behavior, now we can compare the system configuration of two > > > independent > > > > > users. Here is my configuration, can you please let me know your > > > > > configuration so we can determine the common problem and report a > > > bug? > > > > > > > > > > OS: Windows 2k > > > > > Java Version: 1.4.2_09 or 1.5.0_04 > > > > > Maven 2.0.2 > > > > > org.apache.maven.plugins.maven-release-plugin version: 2.0-beta3 > > > > > CVS executable : cvs.exe , part of the Tortoise CVS package > > > > > SSH executable: plink > > > > > Key manager :pageant > > > > > > > > > > > > > > > Thanks, > > > > > Todd > > > > > > > > > > > > > > > > > > > > On 4/11/06, Gelkand < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > Hi! > > > > > > > > > > > > I am using maven-2.0.4 (on WindowsXP, CVS on Solaris) and have > > > exactly > > > > > the > > > > > > same problem during release:prepare of a multiproject build. The > > > child > > > > > > poms > > > > > > were updated and checked in, the master pom is updated (and so > > > locally > > > > > > changed), but not checked in before tagging the source tree. > This > > > > leads > > > > > > during tagging to the failure with the message ... pom.xml is > > > locally > > > > > > modified .... Seems to be a bug ... > > > > > > > > > > > > As a workaround, i manually checked the master pom into CVS, > > > performs > > > > > > again > > > > > > the release:prepare(which successfully uses the before created > > > > > > release.properties) and the tagging is successfull, (At the end > > > the > > > > > master > > > > > > pom with the new snapshot version number is again not checked > into > > > > CVS, > > > > > > just > > > > > > the child poms with the new snapshot version numbers are checked > > > into > > > > > CVS, > > > > > > i > > > > > > do not know if this is a feature or a bug) > > > > > > > > > > > > Greetings, Gelkand > > > > > > -- > > > > > > View this message in context: > > > > > > > > > > > > > > > > http://www.nabble.com/Question-about-release-plugin-on-pom-archtype-t1403232.html#a3867837 > > > > > > > > > Sent from the Maven - Users forum at Nabble.com< > http://nabble.com/> > > > . > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
