the correct solution is to mark all its dependencies as <scope>provided</scope>
otherwise if you try your suggestion you will have issues with the preparation goals when you run release:prepare -Stephen On 20 August 2010 13:47, Benson Margulies <[email protected]> wrote: > I have a zip file built with the assembly plugin. I list it as a > dependency in a project so that I can in turn include it in another > assembly. > > I got a surprise. mvn dependency:tree shows that it has dependencies > -- all the dependencies of its parent. > > This is particularly sideways since it was carefully shaded to avoid > dependencies. > > I think that the solution to my problem is to use dependency:copy on > the artifactId and <fileSet> in the second assembly instead of a > dependencySet, but I thought I would note this for posterity. > > --------------------------------------------------------------------- > 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]
