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
Yes, open an Infra ticket. Though I'd also recommend taking a look at how
Kafka is bootstrapping ./gradlew without needing the specific newer version
of gradle installed - it gets around the jar file being checked in too.
A.
On Thu, May 7, 2015 at 4:28 PM, Roman Shaposhnik
wrote:
> Please let m
Please let me know if I need to file an INFRA ticket instead.
Thanks,
Roman.
I'll follow up with CloudBees - thanks for letting us know.
A.
On Thu, May 7, 2015 at 2:08 PM, Steve Rowe wrote:
> I got the following message when I visited builds.apache.org today:
>
> Your license expires in 29 days. Please ask your Administrator to
> renew.
>
> Steve
>
>
I got the following message when I visited builds.apache.org today:
Your license expires in 29 days. Please ask your Administrator to renew.
Steve
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.