On Fri, Mar 29, 2013 at 09:50PM, Stack wrote: > On Fri, Mar 29, 2013 at 9:22 PM, Konstantin Boudnik <[email protected]> wrote: > > > I also would rather abstain from classifiers approach despite this > > particular > > usecase to be their original intention (see a good discussion here > > http://is.gd/PH1FPU). I found them particularly painful in Ivy > > environment, > > but it might be "somebody else problem" ;) > > > > > I tried again to make it wor*k. Maven won (again). I concede.* > * > * > *It is plain that the assembly can't find artifacts w/ the classifier > appended. Messing w/ moduleSets and dependencySets in the assembly spec. I > can get the jars w/ classifier to show up -- and not their dependencies -- > or it just fails, w/ above noted error, or dependencySets go erratic and > start picking up random includes.*
Yup, classifiers - at least in my experience are good for adding extra bits to a main artifact, e.g. sources, javadocs, etc. Managing versions is better be done with well... versions. And if you end up messing with the dependencies like that above - most likely it will cause more PITA and/or 'dll hells' down the road. Cos > > May be version strings isn't that bad an idea after all? All other things > > being equal of course :/ > > > > This is what I am thinking now. > > Thanks, > St.Ack
signature.asc
Description: Digital signature
