I am curious what you mean about solving the use case in a better way.
The use case reported in http://issues.gradle.org/browse/GRADLE-2762 at
least is about people using both Maven and Gradle locally. We've seen
this where people build Hibernate locally using Gradle and want to
consume this in some Maven-based build. I think we all agree that
everyone using Gradle instead of Maven in fact is the better way ;)
But ultimately I don't see what else Gradle's maven-publishing can do
here but to push the correct jar file name into the local maven cache...
On Fri 02 Aug 2013 02:08:27 PM CDT, Adam Murdoch wrote:
On 02/08/2013, at 8:14 PM, Luke Daley <luke.da...@gradleware.com
<mailto:luke.da...@gradleware.com>> wrote:
Hi,
Our handling of mavenLocal() is pretty busted. There are numerous
issues for this.
The most important is that fact that we don't treat mavenLocal() in
that same way that m2 does; we stop resolution if we find any
artifacts (including POMs) for a dependency in there. Recently I've
had lots of people struggling with this because they have lots of
POMs and no jars for artifacts in their maven local cache. I'm not
sure what tooling exactly is populating the local m2 repo with just
POMs, but it seems fairly common.
The other big problem is that we install unique snapshots into the
local cache, while mvn does not. Even in m3.
Just wondering what our short - medium term plan on this is. Many
people rely on mavenLocal() daily for sharing development snapshots,
regardless of all the inherent problems with that concept. I can
sense some pressure building around this, and it feels like something
we should come up with a solution for some time soonish.
The plan is to fix the issues, then solve the use case in a better way
at some point. It's a matter of finding the bandwidth.
--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
