On 16 Feb 07, at 1:12 AM 16 Feb 07, Eric Brown wrote:
My project's decided to continue using maven and patch it as
necessary to fix bugs in maven that we're no longer willing to live
with. I tried for an hour or two to get my project to build under
2.1, but gave up and figured it was under too much active
development anyway. What is the time frame for 2.1 anyway? (3-
months, 6-months, 2-years?)
It has actually been working just fine other then a problem
introduced a few days ago which I haven't fixed yet. Wagon extensions
don't work but other then that several of us have been using it and
it's being used in production at a client of mine and is also working
fine there.
But I'm noticing that several of the bugs I have to patch in 2.0.5
are actually scheduled for 2.1 and some discuss architectural
issues of maven that I'm not quite familiar with yet. Thus my
question...
These are the bugs I'm in the process of patching (on my project's
fork of 2.0.5):
MNG-1994 Execution order of child plugins is arbitrary if
inheritance is involved. (Somebody should close this. It is fixed
in 2.0.5.)
Someone just mentioned that this wasn't fixed on the list yesterday,
if there is no test project then it's not confirmed.
MNG-1412 Dependency sorting in classpath. I updated the patch for
this already.
Does it have tests?
MNG-624 Every module must contain version info.
MNG-2653 Using ${version} for subproject dependencies doesn't work.
MNG-1949 Plugin dependencies in inherited plugins are ignored.
John's comments a bit confusing to me.
MNG-2823 Too many useless warning messages trying to download
artifacts from all repositories.
Cheers,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
