Well, the problem currently is if you define a pom that declares a number of dependencies (e.g: the ones you need for the flex framework), and some of these have custom scopes (e.g: RSL or external), those scopes are stripped when you include that pom in your project. (IIRC, anything custom just gets converted into 'runtime')
e.g: https://issues.sonatype.org/browse/FLEXMOJOS-153 I asked about it last month: http://maven.40175.n5.nabble.com/custom-scopes-eaten-when-dependency-is-transitive-td4888586.html That means that unfortunately I'm having to specify every one of about 15 dependencies manually in every project (in the exact correct order, but that's a different non-maven issue! :-) ) Sure, being able to provide default, or regex-specified values to groups of artifacts can be nice - but it's not always easy to get right, an sometimes the information is granular enough that you want to be able to specify it for each individual artifact. For flex, if the dependency is an RSL, for each one I can specify not just the application domain, but the deployment path, policy file URL(s) and force-load attributes. It's just feels more natural (to me) to keep that with the dependency statement rather than referenced via the coordinate in some other place in the POM. On Tue, Nov 8, 2011 at 5:00 PM, Brett Porter <br...@apache.org> 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 > >
