Eliminate deprecation warnings (Gradle 1.0 RC1) #1

Merged
merged 2 commits into from Apr 20, 2012

Conversation

Projects
None yet
2 participants
Member

ghillert commented Apr 15, 2012

No description provided.

Contributor

cbeams commented Apr 16, 2012

Gunnar,

This looks good, but you don't need to change the version. The artifactory release management plugin in Bamboo will do that for us.

I'm waiting on the resolution of an issue with Gradleware support right now, dealing with a weird stack trace that I'm getting when using newly published versions of the docbook-reference plugin. I assume I'll get the same with a newly-published version of the bundlor plugin too.

Please update this PR and back out the version changes. As soon as I get word back from Gradleware about how to proceed, I'll merge this and publish an 0.1.3 release. In the meantime it's just deprecation warnings we're dealing with so you should be good to go, yeah?

Thanks for submitting this in any case.

Member

ghillert commented Apr 16, 2012

Thanks Chris,

I reverted the version number.

Cheers,

Gunnar

cbeams added a commit that referenced this pull request Apr 20, 2012

Merge pull request #1 from ghillert/GRADLE-1.0RC1-UPGRADE
Eliminate deprecation warnings (Gradle 1.0 RC1)

@cbeams cbeams merged commit 9640d4a into spring-projects:master Apr 20, 2012

Contributor

cbeams commented Apr 20, 2012

This is now released as bundlor-plugin 0.1.2. Thanks Gunnar!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment