Hi Rolf, I think you might be looking for the Shade plugin.
If you add this to your POM the dependecies will be added when you package your project. If I'm not mistaken they are unpacked and then included in the final JAR, but I'm not sure. <project> > ... > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-shade-plugin</artifactId> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>shade</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > </build> > ... > </project> > > /Roland On Mon, Feb 23, 2009 at 10:20 AM, Jon Georg Berentsen < [email protected]> wrote: > Could you elaborate a bit more? > Are these three artifact dependencies to your project or something you > build? > > Jon > > > "I'd like to distribute a desktop utility > > utility.jar > lib/lib1.jar > lib/lib2.jar > lib/... > > where the MANIFEST.MF contains the line > > classpath = lib/lib1.jar lib/lib2.jar ... > > > included libs are listed as dependencies or transient dependencies as > specified in pom.xml." > > > Is such a thing possible? > With or without writing a plugin? > > Please be patient, I'm new to maven. > I read a lot. Maybe at the wrong place. > I included <addClasspath>true</addClasspath> to maven-jar-plugin > configuration, without luck to change manifest.mf > > Any help welcome. > > Rolf > > --------------------------------------------------------------------- > 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] > >
