Ok, thanks for the suggestions. Yes, I'm building it separately with
assembly:assembly. The separate module idea sounds good too.
Wendy Smoak wrote:
On Thu, Oct 23, 2008 at 6:26 PM, Rusty Wright <[EMAIL PROTECTED]> wrote:
My parent pom has 3 modules, one produces a jar of common utility code for
the other two, the other two are jar files that will be run from a shell
script via cron.
For our people who will be deploying this on the production and qa machines
I want to provide them with two zip files, which I will have checked into
subversion as a tag. They'll check each one out, unzip it, which contains
the shell script and the crontab entries (which they can double-check in
case they change).
I have an assembly file which makes the zip files of the jar file and its
dependencies, the shell script, and the file with the crontab entries.
The part I don't understand is putting the zip file into subversion; I'm
thinking that I ought to use the release plugin but it seems to me that it's
going to want to just do my jar file.
Are you building the assembly separately? If so, use one of the goals
that "attaches" it so that it happens during a normal build. You may
want to put the assembly in a separate module, if it's not there
already.
Then you can use the release plugin to tag and deploy all of your
artifacts, including the assembly. Normally, released artifacts go
into a remote repository, not into Subversion.
Given that they can be recreated from the tag, do you still have to
check them in? If so, and want to do it as part of the build, take a
look at maven-scm-plugin, which can be convinced to do this.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
