IMHO we should use the project version (for example 2.3.1-SNAPSHOT). In this way * the release plugin is able to assign the right value; * we can keep up to date the snapshot version of the website simply running mvn site-deploy everytime we change something (f.i.: http://struts.apache.org/2.3.1-SNAPSHOT).
Once and for all, we should make clear what should contain the 2.x directory (maybe writing into the docs). IMHO it should be a symlink, but it is very annoying keep that link up to date for every release of Struts. Furthermore we should consider the opportunity to have a 3.x (or 2.5.x) directory. Twitter :http://www.twitter.com/m_cucchiara G+ :https://plus.google.com/107903711540963855921 Linkedin :http://www.linkedin.com/in/mauriziocucchiara Maurizio Cucchiara On 14 December 2011 14:27, Łukasz Lenart <[email protected]>wrote: > Hi, > > I'm finishing the release of new Struts 2 version but I have a problem > with updating Struts 2 site. It wasn't updated during Maven release > process and think it's because of that > > <distributionManagement> > <site> > <id>apache-site</id> > <url>scp://people.apache.org/www/struts.apache.org/2.x/</url> > </site> > </distributionManagement> > > 2.x is a valid folder for 2.3.1, should it be changed to > ${project.version} ? > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > Warszawa JUG conference - Confitura http://confitura.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
