Re: [gradle-dev] mavenLocal regression in 1.9

[Luke Daley]

On 26 Dec 2013, at 20:01, Xavier Ducrohet wrote:

So I tried using

uploadArchives {
repositories {
 mavenInstaller()
}
}

and I see the artifacts being correctly deployed to the local repo
with the maven-metadata-local.xml
file.

However I am able to reproduce the problem that my users are finding.

Wasn't this that the maven local dir according to ~/.m2/settings.xml was 
not found?


If I upload an aar to the local repository, then I see to add @aar to 
the
dependency declaration for gradle to find it. This wasn't the case 
before I
think.
Also, once I do that it does find the dependency but it doesn't find
transitive dependencies (in my test case it was a simple jar that was 
also
in the local repo).

I can send you a test project if you want.

Yes please.



On Mon, Dec 23, 2013 at 12:48 PM, Luke Daley 
<luke.da...@gradleware.com>wrote:

The old maven stuff does not have this problem.

The config you need is:

uploadArchives {
repositories {
 mavenInstaller()

}
}

On 23 Dec 2013, at 20:31, Xavier Ducrohet wrote:

That seems to be for the new publishing plugin.

Does the older plugin support publishing to the local repository the 
right
way (versus publishing to a repository that happens to be in
~/.m2/repository)? That was my "issue" I mentioned above.

I tried to do this:

uploadArchives {
repositories {
  mavenDeployer {
      mavenLocal()
  }
}
}

But I get:

* What went wrong:
Execution failed for task ':uploadArchives'.

Could not publish configuration 'archives'

A distributionManagement element or remoteRepository element is
required to deploy




On Mon, Dec 23, 2013 at 8:32 AM, Luke Daley 
<luke.da...@gradleware.com>
wrote:

Found the problem: 
http://forums.gradle.org/gradle/topics/maven_publish_
plugin_stopped_honoring_the_local_maven_repository_location (JIRA 
issue
linked).

I'm in the processing of pushing a fix for 1.11. I can't think of a
workaround for 1.9 and 1.10 unfortunately.


On 20 Dec 2013, at 18:38, Xavier Ducrohet wrote:

I was trying to reproduce but ran into an issue.


How do I publish to mavenLocal()? On a regular Java project, 
there's an
install task but this task requires the JavaPlugin to be there or 
the
Maven
plugin doesn't create it.

The Android plugin only applies the JavaBasePlugin so the task 
isn't
there.
I had tried to make the Android plugin work with the new 
publishing
plugin
but ran into issues. Does this means there's no clean way to 
publish an
Android artifact into mavenLocal?


On Thu, Dec 19, 2013 at 2:49 PM, johnrengelman <
john.r.engel...@gmail.com

wrote:


Here's one forum thread regarding the issue:

http://forums.gradle.org/gradle/topics/maven_publish_
plugin_publishes_snapshot_versions_to_mavenlocal_using_setunique_true

And here is a working link to the Maven 3 compatibility notes:
https://cwiki.apache.org/confluence/display/MAVEN/
Maven+3.x+Compatibility+Notes

Without more details it's hard to determine what the issue would 
be.
Specifically, what is the error message, the dependency 
declaration
from
the build.gradle file and the contents of the corresponding 
artifact
version under ~/.m2/repository (there should be a
maven-metadata-local.xml,
if this file doesn't exists, but you have a maven-metadata.xml 
then
whatever put the artifacts into your mavenLocal did it wrong).

--
John Engelman

On Thursday, December 19, 2013 at 4:24 PM, Xavier Ducrohet [via 
Gradle]
wrote:

I haven't tried to repro those issues yet.
I think it's basically not finding the dependencies.

I did ask one user to see if he could rebuild the artifacts and 
see if
this helps and he told me it didn't change anything.

Are the rule difference documented somewhere?


On Thu, Dec 19, 2013 at 2:09 PM, johnrengelman <[hidden email]<
http://user/SendEmail.jtp?type=node&node=5712126&i=0>

wrote:



There were a number of changes in 1.9 surrounding mavenLocal and
properly
handling artifacts contained in it and publishing (installing) to 
it.

What kind of errors are you seeing? Dependency resolution errors? 
How
are
the artifacts in your mavenLocal getting into there? Where they
published
(installed) from a previous version of Gradle?

The change you're making to work around the issue is setting up a
normal
Maven distribution repository at the same path as mavenLocal. 
While
this
works, this is actually the issue that was fixed in 1.9 because
mavenLocal
has different rules around its behavior then standard maven 
repository.



--
View this message in context:
http://gradle.1045684.n5.nabble.com/mavenLocal-regression-in-1-9-
tp5712124p5712125.html
Sent from the gradle-dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email





------------------------------

If you reply to this email, your message will be added to the
discussion
below:

http://gradle.1045684.n5.nabble.com/mavenLocal-regression-in-1-9-
tp5712124p5712126.html
To start a new topic under gradle-dev, email [hidden email]<
http://user/SendEmail.jtp?type=node&node=5712127&i=0>

To unsubscribe from gradle-dev, click here.
NAML<http://gradle.1045684.n5.nabble.com/template/
NamlServlet.jtp?macro=macro_viewer&id=instant_html%
21nabble%3Aemail.naml&base=nabble.naml.namespaces.
BasicNamespace-nabble.view.web.template.NabbleNamespace-
nabble.view.web.template.NodeNamespace&breadcrumbs=
notify_subscribers%21nabble%3Aemail.naml-instant_emails%
21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>



------------------------------
View this message in context: Re: mavenLocal regression in 1.9<
http://gradle.1045684.n5.nabble.com/mavenLocal-regression-in-1-9-
tp5712124p5712127.html>

Sent from the gradle-dev mailing list 
archive<http://gradle.1045684.
n5.nabble.com/gradle-dev-f1436218.html>at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email