On 7 Sep 07, at 3:52 PM 7 Sep 07, John Casey wrote:
I thought we'd agreed awhile back to do this, but apparently that's
not the case.
For big features sure. I wasn't adding any new features. I'm getting
rid of the ton of crap lying around to prepare for more people being
able to understand 2.1.
When I updated from Subversion today, I got a nasty surprise. Lo
and behold, it would not bootstrap! I didn't find much discussion
on the dev list about a massive reorganization (none, in fact),
The issues for refactoring the major components has been in JIRA for
a long time. Yes, I am additionally cleaning things up, no one else
has touched the trunk in any significant way in the last couple
months so I see myself as pretty much alone (unfortunately at this
point).
and the number of commits makes it pretty difficult to parse out
exactly where things went wrong. Suffice it to say that I'm doing
all of my build/plugin work today based on 2.1-SNAPSHOT artifacts,
not on a trunk build.
Can we please, please, PLEASE start using feature friggin branches??
I'm fixing bugs, trying to get plugins to work and improving error
reporting and generally push all configuration to the front-end so
that it can be explained.
It's not so difficult to merge them in when you're done, and I'm
willing to help anyone who has trouble.
If I attempt any large features I will definitely use a branch. All
the features I have implemented I have not pushed into trunk.
-john
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
