> I agree, however I don't want to create 100 poms. > That just isn't manageable, especially since they all need similar > assemply > logic.
That's where project inheritance is truly useful. You can put all the common logic in one parent pom, and have your tiddlers all define only local things (e.g. just the artifactId, and a reference to the parent). I don't have 100 dependencies to manage this way, but I do have 20 (and climbing). It's pretty sweet when you get your head round it. One thing I find very useful is to be able to specify the extra meta data (url, name, description) for the artifacts that I am installing / deploying - it makes the dependency report of my main project much more readable. -- View this message in context: http://www.nabble.com/Optional-Goals---Dependencies-tf2081628.html#a5799178 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
