If I recall there are problems using the 'assembly' goal inline with
the full build cycle. I'd still recommend using 'attached'.
And, I think if you really want all of the artifacts to have the same
version that includes the rev, then you need to release with that
version... no easy way around. I don't think the addition of the tag
is a bad thing... if you want you can clean out old tags, to just
leave them.
--jason
On Aug 26, 2006, at 2:44 PM, David Blevins wrote:
On Aug 26, 2006, at 2:23 PM, Jason Dillon wrote:
If you use 'attached', you should be able to hook yo the assembly
plugin to the default build cycle.
I added "<phase>package</phase>" to the "<execution>" and that
seems to work.
Now I'm off on a tangent trying to figure out an elegant way to
squirt out occasional builds with the svn revision in the version
number, 3.0-${SVN_REVISION}. I can get the svn revision easily
enough, but changing version numbers is a mess as you know (stupid
hardcoded parent pom version number).
Any ideas? Is there some way to do this with the release plugin,
but without the tags? Or maybe a snapshot deploy, but with svn
number instead of the date?
-David
--jason
On Aug 26, 2006, at 1:30 PM, David Blevins wrote:
On Mar 8, 2006, at 11:14 AM, David Blevins wrote:
On Mar 8, 2006, at 3:04 AM, Gianny Damour wrote:
- Having any assembly run with the build as in 'mvn install' it
causes everything to build twice
I think that this is this very annoying bug http://
jira.codehaus.org/browse/MASSEMBLY-37. Also, it seems that
fileSets defined in assembly descriptors are resolved based on
the directory from which Maven is executed.
Oh man, that bug has been open for two months!
Looks like this bug was closed in May. Going to see if I can't
update the build to make the assemblies by default.
-David
