Thank you, Hans,
Actually, the syntax seems to be as follows:
dists {
jar(baseName: 'myClient') {
baseName = 'myClient'
dependsOn = [ 'myClientCompile' ]
...
}
}
The first baseName sets the task name to myClient_jar and the second one
sets the file name to myClient....jar. If you just use jar() then the task
name is archive_jar, which already exists --> error. If you don't set the
second then the file name is <archivesBaseName>....jar.
This is a quite confusing behavior, as both appendix and classifier within
the jar(...) are also used for the filename, if not overwritten in the
closure, whereas baseName is not.
--
View this message in context:
http://www.nabble.com/Additional-dependency-configuration-and-additional-compile-task-tp19991304p20105175.html
Sent from the gradle-user mailing list archive at Nabble.com.
