maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: update
Date Sun, 08 Aug 2004 12:18:08 GMT
Personally I prefer maven-jar-plugin-2.x. I don't particularly like m2 as a name (and it does
conflict with 
an existing product - Opera's mail client).

The only m1 plugins that have reached 2 are aspectj and the app/web server ones I think. They
can go 
one major version up if they even get written inside maven (but I imagine they are mojos,
which is not 
going to be maven-x-plugin anyway I would think). This makes sense, because mojos should still
work in 
m1 I think (or could be made to by providing an m1 wrapper specific to the plugin, even if
the jelly 
wrapper doesn't support them natively). So v2.x of a plugin is just its evolution.

I'm -0 on the m2 name, +1 on maven-2.x


Quoting Jason van Zyl <>:

> Howdy,
> Yes I'm taking a while and I'm at a point where I'm ready to check stuff
> in but I wanted to float a couple notions about naming.
> I would like to prevent any sort of collisions with m1 plugins and m2
> plugins but right now it is very possible that m1 plugins might
> eventually go to something like:
> maven-jar-plugin-2.x.jar 
> So I was wondering what folks thought about something like:
> m2-jar-plugin-1.x.jar
> To keep any possible collision from happening.
> I was also thinking because m2 is basically a rewrite that "m2" be used
> for in the artifact ids, so something like:
> m2-core
> instead of 
> maven-core
> I'm all ears, I don't particularly care what the naming scheme is I just
> want to continue down the path of m1 and m2 co-existing peacefully.
> -- 
> jvz.
> Jason van Zyl
> happiness is like a butterfly: the more you chase it, the more it will
> elude you, but if you turn your attention to other things, it will come
> and sit softly on your shoulder ...
>  -- Thoreau 

View raw message