OK, I'll work on updating the plugin code then. But I am running into
issues (uncertainties related to skimpy docs) implementing the new
publishing stuff in our build, so I'll have to get around those first.
http://forums.gradle.org/gradle/topics/new_publishing_model_best_practices_for_multi_project_builds_and_generated_pom
http://forums.gradle.org/gradle/topics/new_publishing_model_and_pom_customization_via_xmlprovider
^^ if you have a moment.
On Fri 05 Apr 2013 01:56:03 PM CDT, Adam Murdoch wrote:
On 06/04/2013, at 12:16 AM, 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?
It hasn't yet, but we do plan to (the new publication DSL is still a
work-in-progress). At this stage, you'll need to update your plugin.
You should be able to remove a whole pile of reflection code.
If you like, you might also turn the plugin into a pull request and we
can merge it into Gradle.
--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com
Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara,
CA: http://www.gradlesummit.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
