maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kalle Korhonen <>
Subject Re: dumb quetsion . . .
Date Mon, 07 Dec 2009 18:57:43 GMT
There cannot be a single answer to this since applications,
application packages and use cases are different. If you are building
webapplications and updating your own site, Maven cargo plugin is very
effective (google this list for examples, lots of them). If you are
developing a client-side application, you want to probably package
everything up into a single file (zip, exe, installer package etc.)
and make it available to your customers one way or another. In one
instance, I used the assembly plugin and deployed that assembly
together with Maven site and linked to the file from the index page.


On Mon, Dec 7, 2009 at 10:43 AM, ChadDavis <> wrote:
> I'm been starting to use Maven for some of my projects.  One thing
> that I've not been able to clear up is how the dependencies get
> deployed to my deployment environment.  For development, I sometimes
> use the assembly plugin's ability to generate a single Jar with all
> dependencies included, or I use the jetty plugin to run web apps, and
> this knows about all of the maven managed dependencies inherently.
> But what is the best way to deploy and run my app in a production setting?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message