Please forget about my last post. I have had, for some copy/paste reason, the following lines in my .pom: <dependency> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.1</version> </dependency>
which caused all these maven-specific libs to be added to the target. Sorry. Best regards, Frank maven_newbie99 wrote: > > Hi jieryn, > > I could achieve what I want using your link (ueberjar). Many thanks. > > The only thing I don't understand is why so many maven-specific libraries > are included in my taret? For eample: > mavenmodel, mavenmonitor, mavenpluginapi, mavenpluginregistry, ... > plexusarchiver, plexuscontainerdefault, ... > junit > > and many more. It's a total of 77 libraries of which only ~10 are really > used in my project. > > What do I need to change in order to get rid of these libraries in the > target? > > I appreciate any help. > > Frank > > > > jieryn wrote: >> >> Hi Frank, >> >> On Wed, Nov 4, 2009 at 7:09 AM, maven_newbie99 <[email protected]> wrote: >>> >>> second: is it possible not to include the whole dependent JARs but only >>> those classes within my dependencies that I really use in my code? >> >> Try http://mojo.codehaus.org/minijar-maven-plugin/ >> >> -- >> There are 10 types of people in this world, those >> that can read binary and those that can not. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > -- View this message in context: http://old.nabble.com/Creating-a-JAR-with-dependencies-tp26195103p26197274.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
