Hi, There are a few things about the new publication DSL that could do with a little polish:
* When the group or version for the project is not specified, publishing should probably fail. Right now, publishing to Ivy uses an empty group and 'unspecified' for the version. Empty group works poorly with the Ivy pattern substitution, so that for something like '/[organisation]/[module]' you end up with '/my-project-name'. And using 'unspecified' for version is not useful at all for the consumer. Publishing to Maven fails due to the empty group. * When running 'gradle publish' with no outgoing repositories of the appropriate type defined, we should probably log a warning to let you know that you've forgotten to do this. * When running 'gradle publish' and there are unused repositories defined (e.g. I've applied the maven-publish plugin but defined an ivy repository), we should probably log a warning to let you know that the repository isn't going to be used. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
