Hi Ron, thanks for your help, I honestly forgot to have a look at the assembly plugin, very appreciated!!! Have a nice weekend, Simo
http://people.apache.org/~simonetripodi/ On Sat, Feb 6, 2010 at 3:54 PM, Ron Wheeler <[email protected]> wrote: > Simone Tripodi wrote: >> >> Hi all guys, >> I've been developing a multi-module project where one module is the >> 'commons' stuff and the other modules are dependent from the first >> one; when producing artifacts, I want to include the 'commons' >> dependency in the final jar, so I started using the shade plugin, and >> declared the 'commons' dependency scope as 'provided', but sadly >> noticed that dependencies which scope is 'provided' are not included >> even if specified in the shade configuration. >> Do you know if there is any other way/best practice that could help me, >> please? >> Thanks in advance, best regards! >> Simo >> >> http://people.apache.org/~simonetripodi/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> > > I am not sure why you need shade but it sounds like jar-with-dependencies is > for. > http://maven.apache.org/plugins/maven-assembly-plugin/usage.html > > In your library, your dependencies are all declared as compile so that they > get included into the library jar. > > In your client POMs, your shared library is declared as "provided" if you > want to provide it separately > or "compile" if you want it included in your > client jar that is created with "jar-with-dependencies". > > > I hope that this helps and does match what you are trying to achieve. > > Ron > > --------------------------------------------------------------------- > 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]
