>1) Is their a better way to meet the requirements? This is a very common use of classifiers. It's probably the best way to handle what you want.
>2) Are classifiers stable in a multi-project build? Yes. >3) Are classifiers well supported by Maven's plugins? Yes. >4) What is the minimum Maven version that should be used when creating >artifacts with classifiers? 2.0, been there since "day one" >5) What is the minimum Maven version that should be used when depending >on an artifact containing a classifier? Same as above. >5) For projects dependent on an artifact with classifiers, can the >artifact be calculated by Maven? No, unless you are using a property as mentioned elsewhere in the thread. >6) What are the pitfalls or disadvantages? The only thing to note is that the main artifact can't have a classifier...so you should pick one (ie jdk5) to be the normal non-classifier artifact and have jdk14 be the "attached" classifier. This all assumes you can easily create both artifacts during the same build (retrotranslating and attaching is possible to do, there are examples in the Nexus-Indexer and also Maven-Artifact 3.0) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
