I think this approach makes a lot of sense. It's a problem I've run
into in the C/C++ world, too, where any number of compiler options
may be supplied during a given build, not to mention target
architecture and operating systems. I had been thinking for the past
year or so that we should g
ne-
De : Shane Isbell [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 9 août 2007 22:22
À : Maven Developers List
Objet : Re: Expanding Classifier Support
I have put the proposal here:
http://docs.codehaus.org/display/MAVENUSER/Expanded+Classifier+Support
Thanks,
Shane
On 8/9/07, Jason van Zyl
ndeed, the
aforementioned issues didn't get much attention the first time.
Regards,
Cédric
-Message d'origine-
De : Shane Isbell [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 9 août 2007 22:22
À : Maven Developers List
Objet : Re: Expanding Classifier Support
I have put the
I have put the proposal here:
http://docs.codehaus.org/display/MAVENUSER/Expanded+Classifier+Support
Thanks,
Shane
On 8/9/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> Put the proposal in here with the others:
>
> http://docs.codehaus.org/display/MAVEN/Home
>
> This one in particular is the
Put the proposal in here with the others:
http://docs.codehaus.org/display/MAVEN/Home
This one in particular is the pattern I would like to shoot for:
http://docs.codehaus.org/display/MAVEN/Decoupling+of+Maven+Artifact
Akin to "The Pattern Language" way of describing problems and solutions.
I
I have a concern, as I am sure other do, that NMaven may drift too far apart
from Maven; I would like to start raising some the issues that may impact
Maven on the general dev list so that solutions can be considered for
2.1+versions of Maven. One important issue is classifiers. In a
typical Mave
