I tried the unpack-dependencies but that didn't make a difference, still doesn't work as described.
On Tue, Apr 3, 2012 at 3:34 PM, Ryan Wexler <[email protected]> wrote: > That blog post seemed very self explanatory, but it didn't work. > > What I am getting from the blog is that if you bind a plugin to the > "generate-resources" phase, then you can filter on the resulting files in > project build directory. > > I did this, but no luck. The only difference between what I am doing and > what the blog does is that the blog is using "unpack-dependencies" goal > while I am simply using the "unpack" goal. I assume that shouldn't matter. > > When you turn on filtering on a resource directory, does it apply > recursively? > > > On Tue, Apr 3, 2012 at 2:32 PM, Wayne Fay <[email protected]> wrote: > >> > I am using the maven-dependency-plugin unpack goal to unpack the >> > "client-generic" dependency into these other projects. Is there a way >> to >> > apply resource filtering for the unpack goal so I can filter this >> property >> > on the configuration file that is in the dependency? >> >> You should find complete directions in this Sonatype blog post written >> by Brian Fox: >> >> http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/ >> >> Wayne >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
