2011/11/8 David Jencks <david_jen...@yahoo.com>: > I've run into this problem in 3 or 4 situations and the only practical > solution is to individually list the dependencies with the extra info in the > plugin configurations. I don't really understand the mindset that only the > information needed for some bits of well-known maven can be associated with > dependencies, and all other uses should just duplicate large swathes of maven > configuration to be able to add a couple bits of info per dependency. My > impression is that aether takes a more inclusive view of dependency > properties.
So is this something we could implement in Maven (easily)? Carsten > > thanks > david jencks > > On Nov 8, 2011, at 9:00 AM, Brett Porter wrote: > >> >> On 08/11/2011, at 8:15 AM, Carsten Ziegeler wrote: >> >>> Yes, we were using that approach for years now and it turned out to be >>> too error prone as you have to keep the plugin configuration and the >>> dependency list in sync. It doesn't sound like a hard task first, but >>> in our case it caused trouble many times. That's why we would like to >>> have a single point of information. >> >> So, wildcards or excludes lists don't help with the sync task? There's no >> convention that can be applied (e.g. all dependencies of a certain type, or >> the same group ID as the project)? >> >> How would you handle transitive dependencies? >> >> - Brett >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- Carsten Ziegeler cziege...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
