Best practice for creating & distributing a projects install bina ries?

[Dave Comeau <DC...@xenos.com>]

Hi all,

I'm learning Maven so we can replace our product's current build system with
a Maven based one.

The current process involves pulling the source code from a SCM server
(based on a specified checkpoint label), going through the typical build
process yada yada, and then creating a series of Install Shield based
installers for the various platforms that we support (Windows, several
Unixes, etc).

I have not come across any documentation (yet) that discusses this stage.
The default Maven lifecycle seems to take the project through to the point
where the artifacts are deployed to a repository.  Is there a best practice
for what happens to them from that point on?  Or is this out of the scope of
Maven?

In our current corporate business processes, we need to generate
installation binaries very frequently (unfortunately).  So it's ideal that
this function be integrated into the same build process somehow.

I look forward to any suggestions,

Thanks
DaveC

Re: Best practice for creating & distributing a projects install bina ries?

[dan tran <da...@gmail.com>]

In your final build module ( assume you are using multiprojects build here)
use a combination of maven-dependency-plugin and maven-assembly-plugin
to prepare a file system foot print that your InstallShield can work on (
invoke thru maven-antrun-plugin).
Once all the installers are ready, use build-helper-maven-plugin to attach
the installer(s) to maven so that
they can be deployed thru deploy phase.

There are discussions about getting maven-assembly-plugin to support
InstallerShield/InstallAnywhere type,
but they not taking shape yet.

Hope it helps

-D

On 4/26/06, Dave Comeau <DC...@xenos.com> wrote:
>
>
> Hi all,
>
> I'm learning Maven so we can replace our product's current build system
> with
> a Maven based one.
>
> The current process involves pulling the source code from a SCM server
> (based on a specified checkpoint label), going through the typical build
> process yada yada, and then creating a series of Install Shield based
> installers for the various platforms that we support (Windows, several
> Unixes, etc).
>
> I have not come across any documentation (yet) that discusses this stage.
> The default Maven lifecycle seems to take the project through to the point
> where the artifacts are deployed to a repository.  Is there a best
> practice
> for what happens to them from that point on?  Or is this out of the scope
> of
> Maven?
>
> In our current corporate business processes, we need to generate
> installation binaries very frequently (unfortunately).  So it's ideal that
> this function be integrated into the same build process somehow.
>
> I look forward to any suggestions,
>
> Thanks
> DaveC
>
>
>