I think that to be clear moving forward, the information (and, I
suppose, background) should probably focus on creating a formal,
*written* spec for every major piece - separate ones for lifecycle
management, project building, artifact resolution, etc...*not*
describing what we're currently in the process of changing.
To a certain extent, I'm guilty of doing this backward with the build
planning. I did document the new system as I implemented it on a branch,
and we all talked about it (at least, as much as I could get people to)
before I merged it to the trunk. However, having a document that
describes the rough design of the system - not the specific
implementation details - would be good to contribute to the overall
architecture documentation. I can convert the documentation I do have to
any format we settle on for this.
IMO, we've jumped the gun many, many times here, skipping straight from
a loose (and rather poor) consensus on what needs to be done, *past* the
formal design tasks, and into a frenzy of nearly blind implementation. I
think this is what has gotten us very much in trouble in the 2.0.x code,
and it has resulted in a large part of what needs to be fixed/redesigned
now for 2.1.
While we're at it, I really think we need to start talking about calling
this code on trunk Maven 3.0, since it's going to incorporate rewrites
of all the major subsystems:
- artifact resolution (mercury and Oleg's new SAT-solver based code)
- project building (Shane's cleanroom implementation for example)
- lifecycle management (my own build planning code represents a rewrite
of the lion's share of what it takes to orchestrate the lifecycle)
- plugin manager (refactoring around class-realm management is just the
tip of the iceberg with the work that needs to be done here)
These are all hotspots in our code, where single classes weigh in at or
above 1500 lines, and have been targeted specifically in other threads
as required refactorings pre-2.1. Leaving aside APIs (which from the
consumer's point of view is just a series of interfaces and thin
implementations), this *is* Maven. If we rewrite these parts, we're
talking about third-generation code, not a revision of the second
generation.
-john
Jason van Zyl wrote:
We should be focusing on the release candidate in the short term.
As far as 2.1 discussions so productive discussion will happen 1) unless
people have the necessary background, and 2) are given enough time to
prepare.
I have no time until next week for a couple hour discussion, and people
don't have enough information. I will send out another email to setup
some decent planning.
On 4-Aug-08, at 3:36 PM, Brett Porter wrote:
Hi,
As I shift back to looking at 2.1-alpha-1 regressions in JIRA and the
changes on trunk so far, I was hoping we could have a once off meeting
in IRC to gather up who's working on what, where we are going next,
and where we stand for a release. I don't want to waste a bunch of
time working on issues that get done by other work.
I see Jason has started collating notes for what's changed so far and
other ongoing work. They can probably be a starting point for
discussion. I can capture anything that comes out of it and bring it
back to the list for those who can't make it at the time and we can
take it from there.
I was thinking we could shoot for roughly Thursday 11am PDT [1],
though if interest skews it towards another time that's fine.
So, who is interested?
Cheers,
Brett
[1]
http://timeanddate.com/worldclock/fixedtime.html?year=2008&month=8&day=7&hour=18&min=0&sec=0
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
