I am deploying a maven application with 4 different packages (4
assemblies). Each are the same except for one jar (SWT) that is
native. I have had to resort to 4 different executions of maven to
package them, one execution per profile. This is so that I can change
the classpath per execution to pull in the correct SWT jar and have
the jar plugin add it to the jar classpath manifest. I then am using
the assembly plugin to generate tar.bz2 or zip files with my batch
file or shell scripts as well as all the dependent jars.

This is working except I don't know how to get release:perform to
work. I would like to have the scenario where I could generate the 4
assemblies, tie in a plugin to upload the assemblies all during the
release, so that the are generated with the correct version number. It
seems, correct me if I am wrong, that my working copy is not updated
to the releasing build until during release:perform. The problem is
that I cannot create the 4 assemblies with one maven target.

How can I accomplish this? Do I have to create my own custom plugin?

Overview:

Prepare the release
Generate the 4 assemblies each with a jar with a different classpath /
dependencies using the release tag
Release the 4 assemblies on the tag and upload them using ssh to my server
Deploy the new site using the same tag
Resume work on the new tag

Advice is greatly appreciated.

-Andrew

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to