None of these has been fleshed out into any sort of formal design,
right? I want to be clear about this: what I'm proposing is not a
feature-complete release of maven 2.1 that just has lingering bugs,
and it's not going to be without its regressions. We have a lot of
work in the trunk of SVN that's just been sitting there for like a
year now, in some cases, and I'd just like to get that out as an
alpha, so we can start some actual movement on the 2.1 front.
FWIW, any additions to the model will require a refactor of the
MavenProjectBuilder, so as to allow parsing of multiple
modelVersion's within the same build. Currently, we cannot even
approach the addition of new elements, because it would mean all
sorts of special-case work to make it backward compatible in what is
currently one of the hotspots of the core (the project builder is
something like 1600 lines IIRC, and almost impossible to understand
at a glance).
I want to tackle these things, but I don't think holding up this
alpha is the appropriate way to do it, that's all. And, this is just
my opinion on the matter...
I'd prefer we had formal write-ups for any new features we're going
to put into Maven from here on (not sure the build-plan has one, but
it's mentioned in the suppression-and-ordering document about plugin
ordering within the pom...and I'll be happy to formalize it further.
Also, see the javadocs for more info on it.)...again, just my two cents.
I don't mean to come off sharpish about this stuff, but I do feel
strongly that we really need to move this community into the habit of
releasing more incrementally.
Thanks,
-john
On Jul 11, 2007, at 11:58 AM, Daniel Kulp wrote:
From the resource filtering discussion, it might be a really good
idea to
get a list of schema changes that would be nice to get in and at least
get those into the 2.1 alpha so people can try them and comment on
them
and such.
The three things on my list that I'd like to see are:
1) Do something about the resource filtering (see that thread).
Maybe "filterType" and "escapeSequences" or similar.
2) Create a "repositoryManagement" section to act like the
dependencyManagement and pluginManagement sections. Sub-poms can
access respository just by repository ID defined in
the "repositoryManagement" section.
3) Add "includes" and "excludes" filters to the Repositories.
Thus, I
can set the "java.net" repository to only
include "com.sun.*:*,javax.*:*" or similar so it doesn't need to look
there for everything. (likewise org.apache.* for the incubator and
apache snapshot repositories, etc...)
Dan
On Wednesday 11 July 2007 11:15, John Casey wrote:
Hi everyone,
We've been trying for quite a long time to get into a mode of faster,
more incremental releases. However, when it comes to actually doing
this, we seem married to the idea of pushing out impressive feature
lists with new releases.
I'd like to call an end to that practice, and start pushing out a
2.1-
alpha-1 release of Maven. No, it's not perfect. No, it doesn't have
even the beginnings of some of the features we'd like to have in 2.1
eventually. Yes, there will be some regressions. But after all, this
would be the first alpha release of the 2.1 minor version...so it's
expected to be more of a quick sketch, and lacking some (perhaps
important) details.
2.1-SNAPSHOT already has some interesting new capabilities. I'm sure
I can't name them all, but I know that personally, I've enabled
custom profile activators and the ability to preview the build plan
before it's executed, among other things. We've (primarily Jason)
been steadily improving the embedder support, and that's gotten
pretty damn good at this point, too. I for one would like to start
getting some feedback about the stuff we're working on out here, and
I think putting together a packaged distribution is the best way to
go about that.
What do others think?
-john
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/buildchimp
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
[EMAIL PROTECTED]
http://www.dankulp.com/blog
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot org
blog: http://www.ejlife.net/blogs/john
