Okay so from what I can parse there are different streams of work here
1. The JDK could be well served by a "standard" build tool.
I don't think this is controversial, but I'm nowhere near qualified enough
to say what the "right" choice is. Maybe it is just taking gradle, who
knows.
What I do
> We already have Ant+Ivy, Maven, Gradle and they have significantly
different philosophies such that agreeing on a single dependency management
tool may be too ambitious.
Maybe it would be useful to dig into what those different philosophies are?
> I suggest looking at what Gradle has done in
This email is mostly to test the waters, I expect some hostility.
Say, as a premise, that an API for resolving external dependencies was
something that the JDK concerned itself with providing.
I think the foundation for that is there - the POM v4 format is more or
less around forever, maven
