mark_in_gr wrote: > > > > What would be the most efficient way to format my executable jar > application, though? >
Depends on your apps requirements. I think unpacked leads to less of a burden on host filesystem. jar-with-dependencies is easiest to configure, for sure. Using the maven assembly plugin's jar-with-dependencies, I can bundle up all the jar's dependencies in unpacked form in one jar file and easily distribute the app that way. However, is this the most practical approach as opposed to including ONLY my internal application dependencies(classes our organization has written) within the jar along w/manifest classpath references to external dependencies in a lib directory relative to the location of the executable jar? I think the answer to this question depends on your application's deployment requirements. Maven doesn't enforce one or the other. It would be less work in maven configuration if you can choose the former. I understand the concept and relationships between the maven package phase(which builds artifacts to a developer's local file system target directory), install phase(copying the target artifacts to the local repository) and finally the deploy phase(which takes the local repo artifact and sends it to a specified location based on a given transfer protocol). However, is this concept only applicable to artifacts which are meant to be components to be shared, or full fledged applications as well? Full fledged applications. The full fledged application known as maven is an example. Check out its source code and look into the module 'maven-core'. You will find use of the assembly plugin to build the maven application. And if the later is true, how does one structure the executable jar application in regards to it's external dependencies so it may be used in an automated build and testing process? You can create an application jar using some combination of the assembly and dependency plugins. The assembly plugin may do all for you, but maybe the dependency plugin could be useful in your situation. Note that the documentation on the maven web page for the assembly plugin refers to 2.2-SNAPSHOT, not 2.1 release. Regards, John -- View this message in context: http://www.nabble.com/Best-Practice-for-Deploying-an-Application-w-Dependencies-tf3366937s177.html#a9374201 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
