I figured it out, it seem to be a source control problem. I already had the tag mortgageware-1.0.0, I thought if I re-created the tag during my deployment testing, it would simply overwrite the previous tag in subversion, however that is not the case. If I explicitly delete the tag from subversion, then re-run the release, everything works correctly.
Thanks, Todd On 2/23/07, Todd Nine <[EMAIL PROTECTED]> wrote:
I Remy, Thanks for the reply. I had to link it to a phase explicitly to get it to deploy the zip when performing an install or release. I have tried removing the specific lifecycle execution, but this does not alleviate the issue. Thanks, Todd On 2/23/07, Rémy Sanlaville <[EMAIL PROTECTED]> wrote: > > Hi Todd, > > I'm not sure but it's perhaps because you link the maven-assembly-plugin > to > a phase. > Generally it's better to avoid this[1]. > > Try this instead: > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <configuration> > <descriptors> > <descriptor> > src/assemble/bin.xml > </descriptor> > </descriptors> > </configuration> > </plugin> > > and > mvn clean package assemby:assembly > > An other solution is to declare your maven-assembly-plugin configuration > in > a profile. > > Not sure it will resolved your problem, but you can try. > > Rémy > > > [1] > http://www.nabble.com/Attaching-an-assembly-to-a-multi-module-project-tf2608001s177.html#a7277887 > >
