Closed pniederw closed 10 years ago
We have a bug in the publishing plugin I'm tracking down
On Aug 13, 2014, at 5:54 PM, Peter Niederwieser notifications@github.com wrote:
The published POM for 1.12.1 and 1.12.2-SNAPSHOT defines a runtime dependency on nebula-test. As a result, nebula-test and spock-core-groovy-1.8 will end up on the consuming build's buildscript classpath, which will blow up immediately under Gradle 2.0/Groovy 2.3.
Not sure how nebula-test makes it into the POM as a runtime dependency. Workaround is to add an exclude for nebula-test.
— Reply to this email directly or view it on GitHub.
@rspieldenner Is this still an issue?
We stopped auto publishing test jars and so that removed the weird runtime dependency on spock.
On Tue, Sep 23, 2014 at 11:53 AM, Benjamin Muschko <notifications@github.com
wrote:
@rspieldenner https://github.com/rspieldenner Is this still an issue?
— Reply to this email directly or view it on GitHub https://github.com/nebula-plugins/gradle-extra-configurations-plugin/issues/9#issuecomment-56570713 .
@rspieldenner @pniederw The published POM of version 1.12.3 and 2.0.0 do not include a dependency on nebula-test anymore. Good to close this issue?
I think so.
On Tue, Sep 23, 2014 at 12:10 PM, Benjamin Muschko <notifications@github.com
wrote:
@rspieldenner https://github.com/rspieldenner @pniederw https://github.com/pniederw The POM of version 1.12.3 and 2.0.0 do not include a dependency on nebula-test anymore. Good to close this issue?
— Reply to this email directly or view it on GitHub https://github.com/nebula-plugins/gradle-extra-configurations-plugin/issues/9#issuecomment-56573375 .
OK, I am going to close this issue for now. Please reopened if needed.
The generated POM for 1.12.1 and 1.12.2-SNAPSHOT defines a runtime dependency on nebula-test. As a result, nebula-test and spock-core-groovy-1.8 will end up on the consuming build's buildscript classpath, which will blow up immediately under Gradle 2.0/Groovy 2.3.
Not sure how nebula-test makes it into the POM as a runtime dependency. Workaround is to add an exclude for nebula-test.