v4.7.0

• Removes nebula-core dependency on latest.release which causes compatibility issues with older versions of Gradle
• Uses stock nebula plugin build configuration so we're not at risk of broken build logic like this again

v4.6.0

• Publish the selected group and name for dependencies, so that published dependencies reflect resolution rules and module replacements (a workaround for https://issues.gradle.org/browse/GRADLE-3390)
• Add revConstraint for Ivy dependencies that have dynamic constraints

v4.5.0

Make ivy-excludes conditional on Gradle version to avoid duplicate excludes due to Gradle 2.11's support for Ivy excludes.

v4.4.4

• Add conf to test jar and add safety checks to origin URL manipulation

v4.4.3

Bugfix to add conf and type to source and javadoc jar artifacts published to Ivy repositories

v4.4.2

• Bugfix to guard against trying to apply dependency excludes on transitive deps

v4.4.1

• Fix build.gradle to publish to plugin portal

4.4.0

• Removed nebula.maven-dependencies and nebula.ivy-dependencies because we no longer care about publishing WARs and building insight from their dependencies
• Added the minimal set of configurations to Ivy files necessary to make them Maven interoperable.
• BUGFIX: Update nebula.test-jar to behave as documented during interproject dependency

v4.3.2

• Bugfix so that if these plugins are applied without a language plugin they do not fail the project

v4.3.0

• Remove the need for the afterEvaluate check to determine jar or war

v4.2.2

• Fix issue where a changed status was not being reflected in the published ivy file
• move to gradle 2.8