Pierre-Arnaud Marcelot schrieb: > +1 too, of course. > > Let's unify this between projects. > > I think we can simply drop the current 'tags' folder and then move 'releases' to 'tags'.
I think so too. But there's another problem we need to solve for the next release. Look at the <scm> section of the to poms [1][2] [2] is the one I was keen to release. It contains the tagged URL whereas [1] contains the trunk as URL. Maybe this is an issue of the release process of studio? Regards Felix [1] https://svn.apache.org/repos/asf/directory/studio/releases/1.2.0/pom.xml [2] https://svn.apache.org/repos/asf/directory/studio/tags/1.0.0/pom.xml > > Regards, > Pierre-Arnaud > > On Wed, Sep 17, 2008 at 1:17 PM, Emmanuel Lecharny <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > So far, we don't have a 'release' element?. All we have is 'branches', 'tags', and 'trunk' (+ trunk-with-dependencies...) > > It would be good to stick to this convention. > So +1 to move to 'tags' instead of 'relase' for studio. > > > Felix Knecht wrote: > > Before doing wrong I think to remember we decided to have no longer a > releases tree beside the trunk/tags/branches but > putting release tags to tags tree. For studio this is not yet the case > (see diff needed to patch). > > Index: pom.xml > =================================================================== > --- pom.xml (revision 696222) > +++ pom.xml (working copy) > @@ -1025,7 +1025,7 @@ > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <configuration> > - > <tagBase>https://svn.apache.org/repos/asf/directory/studio/releases/</tagBase> > + > <tagBase>https://svn.apache.org/repos/asf/directory/studio/tags/</tagBase> > </configuration> > </plugin> > <plugin> > > Regards > Felix > > PS: > At least this saves me from the studio/sutdio-plugin tagging problem > ATM ;-) > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com <http://www.iktek.com> > directory.apache.org <http://directory.apache.org>
