so you create a 'FAT' jar, as i understand. this can be very troublesome.
think about a scenario where you need to update one of the dependencies, and its being used in a lot of application jars. you will need to update all the applications jars On Tue, Jan 19, 2010 at 12:25 PM, Johannes Schneider <[email protected] > wrote: > On 01/18/2010 07:28 PM, eyal edri wrote: > >> i'm interested in how people do deploy their apps, even if it's not >> directly >> connected to maven. >> > > I create a runnable jar (with all dependencies) or a war (for web > applications). That is deployed to the repository. > That can be downloaded with a one liner using wget. > > So I think you shouldn't "install" or do any fancy work on you production > server but just download the latest artifact/jar/war/whatever. > > > Johannes > > > >> maybe i'm biased from our current status, where we use YUM&RPM to install >> our perl code on servers. >> >> On Mon, Jan 18, 2010 at 8:25 PM, Wayne Fay<[email protected]> wrote: >> >> i can't understand how the project goes from being the in repository to >>>> being installed and running on the production server. >>>> >>> >>> This is outside the domain of Maven. From the website: "Apache Maven >>> is a software project management and comprehension tool. Based on the >>> concept of a project object model (POM), Maven can manage a project's >>> build, reporting and documentation from a central piece of >>> information." >>> >>> Where does it say "Maven will also help you deploy/install your end >>> product into your production environment"? >>> >>> How does Ant or another Java build tool support your use case? >>> >>> Wayne >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >>> >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Eyal Edri
