2009/12/17 Wes Wannemacher <w...@wantii.com>: > When I was checking this, it reminded me of something I have been > meaning to ask. If you look at the tag name that Lukasz used - > "struts2-archetype-starter-2.1.8.1" But, somewhere in our docs, we use > a tag name like this - "STRUTS2_ARCHETYPE_STARTER_2_1_8_1" which you > can see here - > > https://svn.apache.org/repos/asf/struts/struts2/tags/ > > The tag name that Lukasz used is what the release plugin defaults > to... Is there a reason we don't use it? I'm all about sticking to > defaults (since it tends to make the documentation easier), so I am > wondering if there is a reason, other than "that's the way we always > did it"
Yes, quite stupid ;-( I tried to use name like that STRUTS_ARCHETYPE_STARTER_2.1.8.1 and it didn't work - I just missed that underscores between numbers in the example - so I looked here [1] and noticed that there are already tags with suggested names, so I went forward. I thought the instruction is specific for project and not for archetypes - I think I was too stressful ;-) Next time I will do it better! [1] https://svn.apache.org/repos/asf/struts/maven/tags/ Regards -- Lukasz http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
