Gertjan van Oosten schrieb:
As quoted from Simon Kitching <[EMAIL PROTECTED]>:
If you do want to use the sandbox
jar, you should deploy a copy into your own maven repo.
In trying to build 1.1.7 myself, I noticed that
http://svn.apache.org/repos/asf/myfaces/tomahawk/tags/1_1_7/site/pom.xml
still refers to tomahawk-project-1.1.7-SNAPSHOT
Hmm..a side-effect of the release process.
In order to use mvn release-plugin without deploying sandbox, it was
commented out in the pom (see the top-level pom in the tagged dir). So
then the plugin did not update the sandbox pom version number.
No big deal in my opinion, and I think it should probably just be left
like this. Building a fixed version of the sandbox using the dir tagged
as part of the earlier tomahawk release is not going to be very common.
And if someone does want to do it, then the pom version number issue is
reasonably obvious and easy to modify. And if you're deploying the jar
into your own mvn repo, then presumably you are installing it using a
custom version id like "1.1.7-mycomp", so you'd need to customise the
pom anyway.
Alternatively, we could remove the sandbox subdir from the tagdir. There
is absolutely *no* testing of sandbox against tomahawk as part of the
tomahawk release process, so the state of sandbox at the time a tomahawk
release was made is really not very relevant. But IMO the easiest option
is probably the best here: just leaving things as they are.
Regards,
Simon
