On Sep 7, 2009, at 6:19 PM, Brett Porter wrote:
On 05/09/2009, at 6:25 AM, Brian Fox wrote:
Just my 2 cents as a Maven evangelist in a big private company.
Even if
Maven is around for years now, basic endusers just start to get
accustomed to pom.xml and Maven philosophy (really! people are far
slowest to change than in OpenSource project team).
Please, please don't mess everything. Small additions are fine,
but I think a new format is a bad idea even if it is optional. One
of advantage of Maven is standardization across all our projects.
If there are several format allowed, some projects will start
using new one when others are still using the former and it will
lead to a total mess.
That's my main concern as well to be honest.
Agreed - though I think it's the "optional" part that is bad.
Taking all the learnings and improving the format and making that
the default should be a possibility. I'd want something very
familiar, easy to recognise - the model is still the same, but the
format might be different. Developers can learn those changes and
their group can still standardise on one format, one version of
Maven. The repository format can be standardised across versions and
doesn't need to match (see other thread). Tools is the biggest
problem - that's where "optional" hurts most. They can adapt and
migrate but widening the options they need to work with other than
for a finite set of versions of Maven is unreasonable.
Since we are on the topic of the pom format....
At one point the pom was going to be "redone" so that it wasn't going
to be completely compatible. Later, I think the decision was made to
keep it compatible. At one point there was support for having
different pom formats but I'm not really sure what the state of that is.
This has been a rather long thread so I may have missed it but can
someone please summarize the current state?
Also, I brought up a long, long time ago changes I wanted to see made
in artifact resolution. It was recommended that that be held off until
a later beta phase. I still would like to see those changes
introduced as I still consider the way maven does artifact resolution
solely by version number to be inadequate. While maven 3 would still
be able to process pom's with this information added, maven 2 would
not. If we decide to make these kinds of changes it would be great to
add something to 2.x to allow it to ignore the extra info.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org