Hello Brett, It seems that the shade plugin just takes the packaging type of the pom.xml to create the shaded artifact. For eg, If i use the shade plugin in a pom that generates a war file, the shaded artifact is also a war file. Is there a way to specify I want a shaded jar file instead of a shaded war file. ? I was not able to find any parameter that lets me specify the packaging type.
Thanks, Anand On Sun, Oct 11, 2009 at 3:15 PM, Brett Porter <[email protected]> wrote: > You can do this with either the assembly plugin or the shade plugin. You > might find the latter easier to work with since instead of an additional > descriptor it will build an aggregated JAR and you can include/exclude > patterns of classes from the plugin configuration. An example is here: > http://www.packtpub.com/article/useful-maven-plugins-part1 > > Cheers, > Brett > > > On 12/10/2009, at 9:04 AM, anand sridhar wrote: > > Hi, Im pretty sure my issue is a common scenario across maven projects. >> Here is my scenario - >> >> I have a web maven project with a number of dependencies. My project >> demands >> the user of an applet that has a number of dependencies. So, In addition >> to >> building my project, I also need to build my applet jar and package inside >> the webapp. >> >> Now, the applet jar file is made up of several project specific classes >> and >> also third party library classes. For eg, the applet jar has functionality >> to generate PDF , so i need to package iText related classes as well. >> Because of size concerns, I cannot package all classes from all applet >> dependencies. >> >> The question I have is how can i create an applet jar with selective >> classes >> from my application, my third party libraries etc. >> >> I have been doing this with the help of ant tasks by calling ant targets >> as >> part of package phase. >> >> Is there a better way of accomplishing this. ? For eg, a maven plugin to a >> similar job. ? >> >> Thanks, >> Anand >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
