You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jesper <ma...@plakto.com> on 2008/04/10 15:04:46 UTC
Recommended production release procedure?
Hi,
I'm maven'izing a large enterprise project (from ant) and am looking
for any recommendations on how to do releases to non-maven environments.
After doing the maven build (multi-module) and producing all the
artifacts in the repository, I need to deploy them to different
environments.
I may have 20 jars from 20 modules, 1 war and script files/webstart jnlp
files, etc (binaries), all these need to go into a certain directory
structure on the environments, eg. the war in the webapps directory, all
the libs in a lib directory without any poms and maven versioning data
in the filenames or the classpath will need to constantly be updated.
Currently, my thinking is to use the assembly plugin to group the jars,
create jars of the binaries so they can be deployed.
The deploy plugin seem to be to deploy to a another maven repository
which isn't really what I want to do.
So my question is whether there is a plugin suitable for this, or do I
need to break it up into more steps, eg. copy to a remote machine,
unpack the binaries, etc.
What are everyone experience with this, perhaps others have a different
way of achieving this..
Thanks
Jesper
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Recommended production release procedure?
Posted by jesper <je...@plakto.com>.
Yes, I'm using the assembly plugin to create the structure, where the
missing link for me is to deploy to other environments outside a maven
repository as explained below.
I'll add a shell script for now to do the final steps (eg. unpacking)
after the assembly built jar has been transferred to the other environments.
Jesper
Chris Helck wrote:
> I don't think Maven was meant to solve application deployment issues.
> The whole field of installers & deployment is very complex. Sometimes
> you need to install certain files as root, install cron/timer jobs, stop
> and restart services, create directory structures, and so on.
>
> I have been able to use Maven to create installable artifacts -- I had a
> Maven1 plugin that would invoke InstallShield. In Maven2 I replaced
> InstallShield with a Python script. There are various plugins for other
> installers. I'm sure that this is not the right way to do things, but
> for us, right now, it works.
>
> That said the assembly plugin is very nice. You could use it to define a
> simple zip file with a structure like:
> bin
> etc
> jars
> wars
>
> This zip file would then feed into some deployment tool/process which
> would do the messy stuff. I would like a way to create a self-extracting
> zip file using the assembly plugin, but I've never had time to
> investigate. This would make it easy to do simple linux installs. The
> self extracting archive would unpack everything then execute the file
> ./bin/install, which (hopefully) does the right things.
>
> Regards,
> Christopher Helck
>
>
> -----Original Message-----
> From: Jesper [mailto:mavenuserlist@plakto.com]
> Sent: Thursday, April 10, 2008 9:05 AM
> To: users@maven.apache.org
> Subject: Recommended production release procedure?
>
> Hi,
> I'm maven'izing a large enterprise project (from ant) and am looking
> for any recommendations on how to do releases to non-maven environments.
>
> After doing the maven build (multi-module) and producing all the
> artifacts in the repository, I need to deploy them to different
> environments.
>
> I may have 20 jars from 20 modules, 1 war and script files/webstart jnlp
> files, etc (binaries), all these need to go into a certain directory
> structure on the environments, eg. the war in the webapps directory, all
> the libs in a lib directory without any poms and maven versioning data
> in the filenames or the classpath will need to constantly be updated.
>
> Currently, my thinking is to use the assembly plugin to group the jars,
> create jars of the binaries so they can be deployed.
>
> The deploy plugin seem to be to deploy to a another maven repository
> which isn't really what I want to do.
> So my question is whether there is a plugin suitable for this, or do I
> need to break it up into more steps, eg. copy to a remote machine,
> unpack the binaries, etc.
>
> What are everyone experience with this, perhaps others have a different
> way of achieving this..
> Thanks
> Jesper
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> **********************************************************************
> This communication and all information (including, but not limited to,
> market prices/levels and data) contained therein (the "Information") is
> for informational purposes only, is confidential, may be legally
> privileged and is the intellectual property of ICAP plc and its affiliates
> ("ICAP") or third parties. No confidentiality or privilege is waived or
> lost by any mistransmission. The Information is not, and should not
> be construed as, an offer, bid or solicitation in relation to any
> financial instrument or as an official confirmation of any transaction.
> The Information is not warranted, including, but not limited, as to
> completeness, timeliness or accuracy and is subject to change
> without notice. ICAP assumes no liability for use or misuse of the
> Information. All representations and warranties are expressly
> disclaimed. The Information does not necessarily reflect the views of
> ICAP. Access to the Information by anyone else other than the
> recipient is unauthorized and any disclosure, copying, distribution or
> any action taken or omitted to be taken in reliance on it is prohibited. If
> you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and
> notify the sender.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Recommended production release procedure?
Posted by Chris Helck <Ch...@us.icap.com>.
I don't think Maven was meant to solve application deployment issues.
The whole field of installers & deployment is very complex. Sometimes
you need to install certain files as root, install cron/timer jobs, stop
and restart services, create directory structures, and so on.
I have been able to use Maven to create installable artifacts -- I had a
Maven1 plugin that would invoke InstallShield. In Maven2 I replaced
InstallShield with a Python script. There are various plugins for other
installers. I'm sure that this is not the right way to do things, but
for us, right now, it works.
That said the assembly plugin is very nice. You could use it to define a
simple zip file with a structure like:
bin
etc
jars
wars
This zip file would then feed into some deployment tool/process which
would do the messy stuff. I would like a way to create a self-extracting
zip file using the assembly plugin, but I've never had time to
investigate. This would make it easy to do simple linux installs. The
self extracting archive would unpack everything then execute the file
./bin/install, which (hopefully) does the right things.
Regards,
Christopher Helck
-----Original Message-----
From: Jesper [mailto:mavenuserlist@plakto.com]
Sent: Thursday, April 10, 2008 9:05 AM
To: users@maven.apache.org
Subject: Recommended production release procedure?
Hi,
I'm maven'izing a large enterprise project (from ant) and am looking
for any recommendations on how to do releases to non-maven environments.
After doing the maven build (multi-module) and producing all the
artifacts in the repository, I need to deploy them to different
environments.
I may have 20 jars from 20 modules, 1 war and script files/webstart jnlp
files, etc (binaries), all these need to go into a certain directory
structure on the environments, eg. the war in the webapps directory, all
the libs in a lib directory without any poms and maven versioning data
in the filenames or the classpath will need to constantly be updated.
Currently, my thinking is to use the assembly plugin to group the jars,
create jars of the binaries so they can be deployed.
The deploy plugin seem to be to deploy to a another maven repository
which isn't really what I want to do.
So my question is whether there is a plugin suitable for this, or do I
need to break it up into more steps, eg. copy to a remote machine,
unpack the binaries, etc.
What are everyone experience with this, perhaps others have a different
way of achieving this..
Thanks
Jesper
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
**********************************************************************
This communication and all information (including, but not limited to,
market prices/levels and data) contained therein (the "Information") is
for informational purposes only, is confidential, may be legally
privileged and is the intellectual property of ICAP plc and its affiliates
("ICAP") or third parties. No confidentiality or privilege is waived or
lost by any mistransmission. The Information is not, and should not
be construed as, an offer, bid or solicitation in relation to any
financial instrument or as an official confirmation of any transaction.
The Information is not warranted, including, but not limited, as to
completeness, timeliness or accuracy and is subject to change
without notice. ICAP assumes no liability for use or misuse of the
Information. All representations and warranties are expressly
disclaimed. The Information does not necessarily reflect the views of
ICAP. Access to the Information by anyone else other than the
recipient is unauthorized and any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it is prohibited. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and
notify the sender.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org