I don't think I can do that easily since that would require rebuilding and redeploying the modified projects as the new packaging type. Maybe I could fetch all of the dependency POMs with something like go-offline and modify them in my local repository? Yuck. I hope there is a nicer way, but I'll consider this if there are no alternatives.
I'm thinking that modifying the existing dependency plugin tree builder code might be a better solution. Wayne Fay wrote: > >> at various levels are war type projects. The dependency plugin appears >> to >> stop at war projects as if they have no dependencies of their own. Does >> anyone have suggestions as to how I can build a full dependency tree, > > Could you temporarily change the packaging to "jar" for those war > projects, just to get past the issue so you could complete your > analysis, and then change them back? > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://old.nabble.com/Dependency-analysis-through-wars-tp28672012p28672240.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
