Sorry, same thing as before. I was in changes mode, but I really meant release.
> -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, 3 May 2004 3:53 PM > To: 'Maven Developers List' > Subject: RE: Little glitches in rc2 release process > > > Brett, > > What's the relationship with the changes plugin? > > Thanks > -Vincent > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: 03 May 2004 01:20 > > To: 'Maven Developers List' > > Subject: RE: Little glitches in rc2 release process > > > > File a bug against the changes plugin. > > > > > -----Original Message----- > > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > > Sent: Monday, 3 May 2004 12:10 AM > > > To: 'Maven Developers List' > > > Subject: RE: Little glitches in rc2 release process > > > > > > > > > Here's another one: > > > > > > - The <versions> element has been moved to the end of the > > > project.xml which is not the correct place (it should be after > > > <repository> > > > > > > Thanks > > > -Vincent > > > > > > > -----Original Message----- > > > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > > > Sent: 01 May 2004 12:25 > > > > To: 'Maven Developers List' > > > > Subject: Little glitches in rc2 release process > > > > > > > > Hi Brett, > > > > > > > > I think I've found some little glitches in the release process > we've > > > used > > > > for rc2. This is just a heads up so that we can improve the > process > > > for > > > > rc3. > > > > > > > > - in several plugins there are wrong <version> tags. > Here's what I > > > > typically find: > > > > > > > > <version> > > > > <id>1.1</id> > > > > <name>1.1</name> > > > > <tag>HEAD</tag> > > > > </version> > > > > <version> > > > > <id>1.1</id> > > > > <name>1.1</name> > > > > <tag>MAVEN_ASPECTWERKZ_1_1</tag> > > > > </version> > > > > > > > > Whereas it should be: > > > > > > > > <version> > > > > <id>1.1</id> > > > > <name>1.1</name> > > > > <tag>MAVEN_ASPECTWERKZ_1_1</tag> > > > > </version> > > > > <version> > > > > <id>1.2</id> > > > > <name>1.2</name> > > > > <tag>HEAD</tag> > > > > </version> > > > > > > > > - It's missing the download link for the new version in > > > navigation.xml. > > > > For example, for the 1.1 release of aspectwerkz plugin: > > > > > > > > <menu name="Downloads"> > > > > <item name="AspectWerkz plugin 1.0" > > > > > > > href="http://www.ibiblio.org/maven/maven/plugins/maven-aspectw > > > erkz-plugi > > > n- > > > > 1.0.jar"/> > > > > </menu> > > > > > > > > whereas it should have been: > > > > > > > > <menu name="Downloads"> > > > > <item name="AspectWerkz plugin 1.0" > > > > > > > href="http://www.ibiblio.org/maven/maven/plugins/maven-aspectw > > > erkz-plugi > > > n- > > > > 1.0.jar"/> > > > > <item name="AspectWerkz plugin 1.1" > > > > > > > href="http://www.ibiblio.org/maven/maven/plugins/maven-aspectw > > > erkz-plugi > > > n- > > > > 1.1.jar"/> > > > > </menu> > > > > > > > > - Sometimes, the new versions have not been created in the JIRA > > > project. > > > > Say I'm releasing version 1.1. We need to add a new 1.2 > version to > > > that > > > > JIRA project. > > > > > > > > - Of course, I really don't like the modifications to > changes.xml > > > where > > > > the lines are not wrapped and all <action> are on one line. It > makes > > > it > > > > very difficult to read :-) It has also wrecked all my careful > > > indentations > > > > that I had set over the past 2 years on all the plugins I was > > > managing... > > > > :-( > > > > > > > > Thanks > > > > -Vincent > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] >
