Hey Daz,
The "upload auth" plugin[1] reads credentials from maven settings.xml
etc and applies them to any same-named repositories referenced in a
Gradle build through an Upload task. So, as I understand it, that
would not apply here.
Applying the credentials to the resolution repos would be a good thing
too.
[1] https://github.com/sebersole/gradle-upload-auth-plugin
On Fri 05 Apr 2013 02:21:07 PM CDT, Daz DeBoer wrote:
On 5 April 2013 07:16, Steve Ebersole <st...@hibernate.org
<mailto:st...@hibernate.org>> wrote:
I am just upgrading Hibernate to Gradle 1.5 and am reading about
the new publications stuff. I really like the new DSL much, much
better.
I did have one question though that was not addressed in the docs.
For the old style of "uploading" I had developed a plugin that
provided authorization based on users local Maven install. From
my recollection the intent in the new maven publication code was
to provide this behavior out-of-the-box. So I am curious if that
code ever made it into the
MavenArtifactRepository/__MavenPublication code. Or do I need to
update my gradle-upload-auth-plugin to handle this new API?
The new Publication support copies the credentials from the
MavenArtifactRepository (see the poorly named
org.gradle.api.publish.maven.internal.publisher.MavenDeployerConfigurer).
So any plugin code that you use to add credentials to maven
repositories used for resolution should also work for publication.
--
Darrell (Daz) DeBoer
Principal Engineer, Gradleware
http://www.gradleware.com <http://www.gradleware.com/>
Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara,
CA: http://www.gradlesummit.com <http://www.gradlesummit.com/>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
