On 15-Dec-08, at 12:55 AM, Brett Porter wrote:
=
=====================================================================
--- maven/components/trunk/maven-core/pom.xml (original)
+++ maven/components/trunk/maven-core/pom.xml Sun Dec 14 11:51:59
2008
@@ -111,8 +111,8 @@
<version>${project.version}</version>
</dependency>
<dependency>
- <groupId>org.apache.maven.shared</groupId>
- <artifactId>maven-shared-model</artifactId>
+ <groupId>org.sonatype.spice</groupId>
+ <artifactId>model-builder</artifactId>
</dependency>
</dependencies>
<build>
I can't believe I even have to say this, but moving components
critical to the function of Maven out of our subversion repository
is not a way to solve the problem of unreleased snapshots, IMO. Can
you explain to me how this is anything other than a move to route
around Apache's release rules? Why couldn't it be done where it was?
Nothing in there is Maven specific in the slightest. We are using that
component in NMaven (not here), Byldan (not here), Nexus and Hudson.
It's general XML manipulation.
For something like Mercury which is related to dependency management
it is obviously in the domain of Maven. XML manipulation is not.
Also in the course of 6 months of development of the model-builder we
have not had a single contribution from anyone else. Zero interest. So
yes, it is easier to release elsewhere and that has allowed me to
patch, test, release in rapid succession to try and get the alpha-1 to
the point of release.
I don't buy the argument that it's because it's useful outside of
Maven, since one of the great things about Maven is that anyone can
reuse it no matter what it is called. Considering the licenses and
packages weren't even changed from o.a.m.shared and the ASF header
for a version 1.0, I guess that's not the issue.
Brett, I'm honestly more interested in servicing the user community
and that means getting releases out. I mean honestly Brett what right
do you really have over the domain of this code? And are you worried
that folks who want to work on it aren't going to get access? Come on.
Anyone who has ever wanted contribute to Plexus or Modello from the
Maven side has never had a problem and the libraries at Sonatype are
not going to be any different. No different then Codehaus except we
have more control over the infrastructure like the repositories and CI.
This is no different then Woodstox which is 1-2 guys at Codehaus. If
anyone wanted access from Dan or Tatu it wouldn't be a problem, but
I've never gone hacking in Woodstox so I don't need it.
Like Plexus, I know well enough how often developing on Maven is
going to require digging into the code for such dependencies as this
and the plugin manager, and probably making changes to fix bugs in
the future. This move will be a barrier to some of the Maven
committers.
With m2eclipse, ( and probably Netbeans, or IDEA) everything is
available visually and easy to materialize by right clicking on a
dependency. I also plan to make a project materialization descriptor
for Maven so no one is going to have to go hunting for anything in
Maven. If anyone wants access to the sources to debug it will be dead
simple. Tim will be writing a developer guide so I think historically
this will become the easiest, most documented way to develop Maven.
That will be available by alpha 3 or 4.
I want to encourage more people to work on the core, but again in the
last 6 months I can count on one hand the number of people who have
worked on the core.
So I really don't think the location of libraries is the barrier.
We need a deadly fast way to get new potential developers initialized
and get working with the code almost immediately.
Could you please make clear what your intentions are? Are you
intending to move anything else?
For 3.x the dependency set is all releases now and we have all the
components we need. Once I release the alpha-1 the current location of
dependencies won't change. I imagine most of the work will happen WRT
Mercury, and I honestly don't see any additional dependencies being
needed for 3.x itself. I'll reduce them if it goes in any direction.
For the transitive dependencies underneath when Plexus is 1.0 I would
still like to move that to Apache. The XWiki folks are waiting for
this, and after chatting with some folks it would also make the
Eclipse IP work easier in the future for m2eclipse.
Thanks,
Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We all have problems. How we deal with them is a measure of our worth.
-- Unknown
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
