On Thu, 06 Dec 2007 10:12:27 Kallin Nagelberg wrote: > You can always wrap certain sets of dependencies up in another POM with > 'pom' packaging type to keep the dependencies aspect of your pom isolated > from whatever else you're having it do. yes this is the way to do it... however i use jars as that way i get the pom and pom.properties in unpacked aggregations which is very handy for figuring out whats actually deployed on various environments
this has more significant uses in terms of the closest first resolution mechanism this gives an easy way to force particular versions and exclusions... for example i have replaced commons logging with slf4j... but lots of things depend on commons-logging so i put exclusions in my compositions... another good example could be ehcache and hibernate... they have circular depedencies... so i use the composites to exclude each other and enforce particular versions of things > > One thing I wish the pom had was a way to perform composition from common > components instead of having to use inheritance. Rigid inheritance > hierarchies are more difficult to maintain than delegation IMHO. For i only have 2 deep hierachies the parent of all for distribution managment and then group parents... all repository definitions are in settings.xml to avoid the chicken and egg of parent resolution the thing i would like most would be to promote/demote released artifacts in the repository... i wonder if archiva does this... that way you can easily use ranges and remove a broken artifact from the resolution graph... -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
