Gradle-based projects -SNAPSHOT artifact publishing

[Roman Shaposhnik <rv...@apache.org>]

Hi!

I'm used to the Maven projects just inhering from
top level ASF pom and automagically getting all
the right things in place to be able to do mvn publish
on any of our Jenkins slaves.

What's the easiest way to achieve that same level
of integration for gradle-based projects?

Thanks,
Roman.

Re: Gradle-based projects -SNAPSHOT artifact publishing

[Roman Shaposhnik <ro...@shaposhnik.org>]

After some sleuthing around I finally figured out a way
to automate it so that Gradle can push from our Jenkins
slaves as easy as Maven builds. Here's the patch:
   https://issues.apache.org/jira/browse/GEODE-19
that now honors settings.xml because of a combination
of two plugins:
   maven-publish
and
   maven-publish-auth

Shall we add this to publishing FAQ around Maven
artifacts?

Thanks,
Roman.


On Thu, May 7, 2015 at 9:19 PM, Giridharan Kesavan
<gk...@hortonworks.com> wrote:
> Roman,
>
> To my knowledge gradle doesn’t honor settings.xml. Most of the gradle
> projects that I work on
> I use the username and plain txt password by implementing the
> MavenDeployer interface.
>
> http://gradle.org/docs/current/javadoc/org/gradle/api/artifacts/maven/Maven
> Deployer.html
>
> I would be more than happy to learn, if someone knows a better/easier way
> of doing it.
>
>
>
>
>
>
> On 5/7/15, 1:25 PM, "Roman Shaposhnik" <rv...@apache.org> wrote:
>
>>Hi!
>>
>>I'm used to the Maven projects just inhering from
>>top level ASF pom and automagically getting all
>>the right things in place to be able to do mvn publish
>>on any of our Jenkins slaves.
>>
>>What's the easiest way to achieve that same level
>>of integration for gradle-based projects?
>>
>>Thanks,
>>Roman.

Re: Gradle-based projects -SNAPSHOT artifact publishing

[Giridharan Kesavan <gk...@hortonworks.com>]

Roman, 

To my knowledge gradle doesn’t honor settings.xml. Most of the gradle 
projects that I work on
I use the username and plain txt password by implementing the 
MavenDeployer interface. 

http://gradle.org/docs/current/javadoc/org/gradle/api/artifacts/maven/Maven
Deployer.html

I would be more than happy to learn, if someone knows a better/easier way 
of doing it. 






On 5/7/15, 1:25 PM, "Roman Shaposhnik" <rv...@apache.org> wrote:

>Hi!
>
>I'm used to the Maven projects just inhering from
>top level ASF pom and automagically getting all
>the right things in place to be able to do mvn publish
>on any of our Jenkins slaves.
>
>What's the easiest way to achieve that same level
>of integration for gradle-based projects?
>
>Thanks,
>Roman.