The problem is that the notion of a repository is extremely valuable and unfortunately the "maven repository" (as in layout) is by far the most ubiquitious. But that notion is completely separate from maven-as-a-tool.
On Tuesday, March 29, 2011, at 07:27 am, Philippe Lhoste wrote: > On 29/03/2011 04:52, Rickard Öberg wrote: > > I have all libraries in my local Maven repo. Isn't that enough? > > I just avoid Maven... :-) (that's why I went directly to Gradle) > (I know, I suppose that a "local Maven repo" is probably distinct from > Maven-the-tool itself.) > > And I don't know Ivy. > Beside, I grown an habit to just download the jar files of the libraries. > Perhaps stupid with modern tools, but so far I wasn't hurt by the process > at my modest personal level. > > Of course, with a team, real projects, various versions, something more > sophisticated would be useful. At work, the integration manager still > manages the versions by hand and with Ant. They think about using Maven, I > try to push them toward Gradle... :-) --- Steve Ebersole <[email protected]> http://hibernate.org
