This is for the general population but I'm nudging you Ralph because I
know that you want to make some changes for not requiring the version
in the parent element.
I don't think I'll be too keen on making substantive changes to how
the POM is constructed until alpha-3/4 (because we need to deal with
the thorny issue of interoperability between versions of the POM and
version of Maven) but have a look at this:
http://svn.apache.org/repos/asf/maven/components/trunk/maven-project-spec.pdf
Shane tried to codify the behavior as much as possible into this spec
and I think it servers as the new location for existing behavior and
changes we want to make in the future. I think we can clearly mark
proposals and then transition them into the document proper as
proposals are accepted.
This is really to get the ball rolling and get your thoughts as you
have the only concrete proposal that's been tested I know of. I am
going to translate that document into Confluence markup as I don't
think Tex is very popular. Once that is done we can also incorporate
proposals that have been made by users and link back to the JIRA. This
should make the behavior more visible and potential changes known.
We'll have something similar for Mercury which will tie the whole
process together but this is a place to start.
(The Tex source is right beside the PDF if you actually want to edit
the Tex content)
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A man enjoys his work when he understands the whole and when he
is responsible for the quality of the whole
-- Christopher Alexander, A Pattern Language
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
