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
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 mor
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.
