[gradle-dev] Re: Maven local issues.

I fixed up the issues with publishing to MavenLocal (especially with snapshot versions) and issued a pull request here: https://github.com/gradle/gradle/pull/188 -- John Engelman -- View this message in context: http://gradle.1045684.n5.nabble.com/Maven-local-issues-tp5711584p5711790.h

[gradle-dev] Re: Maven local issues.

Daz - I just submitted the signed document to i...@gradleware.com Thanks! -- John Engelman On Sunday, September 1, 2013 at 5:31 AM, Daz DeBoer-2 [via Gradle] wrote: > Hi John > > I can't see a record of you submitting a signed CLA: if you haven't done so > can you please submit as per >

Re: [gradle-dev] Re: Maven local issues.

Hi John I can't see a record of you submitting a signed CLA: if you haven't done so can you please submit as per https://github.com/gradle/gradle/blob/master/CONTRIBUTING.md. If you have done so, just let us know and we'll follow up on it. Thanks Daz On Fri, Aug 30, 2013 at 4:26 PM, johnrengelm

[gradle-dev] Re: Maven local issues.

Just issued Pull Request #187 - https://github.com/gradle/gradle/pull/187 Included tests for pom packaging, snapshots, non-unique snapshots, and normal artifacts. -- John Engelman On Thursday, August 29, 2013 at 11:07 PM, John Engelman wrote: > Great. I have the resolver part worked out, just

[gradle-dev] Re: Maven local issues.

Great. I have the resolver part worked out, just writing some tests around it. Using the extra information in the ModuleVersionMetaData will be very helpful. -- John Engelman On Thursday, August 29, 2013 at 11:05 PM, Adam Murdoch [via Gradle] wrote: > > On 30/08/2013, at 7:38 AM, Adam Murdoc

[gradle-dev] Re: Maven local issues.

I've gone back to the drawing board and came up with a simpler solution where in ExternalResourceResolver I check for any artifact existing and then only mark the artifact as resolved by that repository if one is found. The problem I'm having is handling POM dependencies. There doesn't seem to be

[gradle-dev] Re: Maven local issues.

The reason I'm delegating the snapshot behavior is because there is already additional checks for the snapshot timestamping and such. At first glance, I thought snapshot resolution would work ok, because the POM would be there but then it wouldn't find an artifact…I'll check to make sure. Good

Re: [gradle-dev] Re: Maven local issues.

On 23/08/2013, at 2:47 AM, johnrengelman wrote: > I've started looking at a fix for GRADLE-2034 > with respect to mavenLocal() > having artifact POMs but not the corresponding artifact. It appears the > Maven does this a lot. I've been seeing it a

[gradle-dev] Re: Maven local issues.

I've started looking at a fix for GRADLE-2034 with respect to mavenLocal() having artifact POMs but not the corresponding artifact. It appears the Maven does this a lot. I've been seeing it anytime I execute a 'mvn install' on the same machine that I