Added a failing test to demonstrate the issue
Make sure that we only add the Java component if the war plugin hasn't been added to the project
Moved the publication/component building logic to the PublicationExtension configuration, delaying execution to last moment
Minor updates to the way that we establish the configurations
Update tests to reflect new naming convention from mavenJava to mavenNebula
Logic added to add artifacts and dependencies from component usages for Maven Publications
Fixed bug where the runtime configuration for the Java Plugin was being resolved too early
Change the domainobjectset collection type for the CustomComponentPlugin to fix a hashcode remove item bug
Merging upstream changes from master
Moved the MavenArtifact cleanup logic to a method
Merge branch 'master' into bug/multiple-components
Merge remote-tracking branch 'origin/gradle-1.12' into bug/multiple-components
[Gradle Release Plugin] - pre tag commit:  '1.12.1'.
[Gradle Release Plugin] - new version commit:  '1.12.2-SNAPSHOT'.
Merge remote-tracking branch 'origin/gradle-1.12' into bug/multiple-components
Code review fix: Migrating the fromSoftwareComponent code from default impls to interfaces
Switching fix to use a different hashcode algorithm rather than a different collection algorithm
Code Review: Removing the HashCodeDomainObjectSet
Merge pull request #5 from nebula-plugins/bug/multiple-components

Nebula Maven Publishing
Fix type on the Resolution Result