On Tue, Sep 9, 2008 at 3:25 PM, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> The one shortcoming of this is, if there are libs listed inside this > "lib list" pom, you'd get them any way. I see a set of excludes, but > that could get really long (say there are 30 shared libs, but we're only > interested in three). Is a matching "include" coming to match the > "exclude" statement in the dependency bits? That would make life so > much easier... (Except for the single inheritance problem,) this seems roughly equivalent to using dependencyManagement further up the pom hierarchy, and declaring the dependency in the project (leaving out the version). Can you mix the two ideas, have a set of "lib list" poms, each of which declares several dependencies that are usually used together, with a common parent that uses dependency management to control the version? Are each of these 30 things completely independent or could you use transitive dependencies to cut down the number of things you must declare? -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
