Resolution: Won't Fix
Affects Version/s: 1.0-milestone-9
Fix Version/s: None
Specifying a different project output folder than the default for a source set, such as in the following:
will result in the project being unusable as a dependency. This is currently being used to create an exploded jar in a library directory which we use to share among deployments in JBoss. We specify the dependency as the following:
Our current workaround is to put the output directory into a variable and specify the directory as the following:
Attached is a sample project which displays the issue.