Stefan Bodewig wrote:
> OK,
>
> Maven didn't even start to build because it depends on commons-util as
> well - I've now also removed that dependency, just to get:
>
> Buildfile: build-gump.xml does not exist!
> Build failed
>
> well, that's true.
>
> Maybe you've forgotten to check in that file, Dion?
>
> Anyway, at this point its fairly clear that we either need a way to
> bootstrap Maven or have Maven-independent build files for commons-util
> and commons-xo if we want to get anywhere.
>
> As the number of projects that use Maven is likely to grow, I'd expect
> more circular dependencies to appear, so bootstraping Maven is
> probably the better option - do you see any chance?
I agree. The bootstrap process is definitely a better approach.
Perhaps it should be done when ANT is bootstrapped?
-oOo-
Another possibility:
Maven has a "repository", correct? Perhaps, the bootstrap process will
compile enough to download the necessary dependancies to build the rest
of Maven.
This particular entry would be "maven-bootstrap".
That way projects that Maven depends on (and they depend on Maven) will
be able to build.
Then GUMP has another entry for "maven" to build the tool with the
latest and greatest binaries so that it can have the benefit of the
early warning that GUMP provides if a dependancy changes the API.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
