I always check out branches into a separate directory from the trunk version (a common practice). So if I have a project "myproject" and it has a 1.0 branch this gets checked out into a myproject1.0 directory.
The problem is that gradle uses the project's directory name as the the base name for everything. So if I have a version 1.0.1 everything becomes named like myproject1.0-1.0.1. This is undesirable. I have set a archivesBaseName which fixes this for the jar that gets produced in the assemble task. However, when I used uploadArchives it uses myproject1.0 as the module name. It also uses "myproject1.0-1.0.1 API" for apiDocTitle. Is there any variable I can set that it will use as the base of everything rather than the directory name? I tried setting "module" but got an error that said that was read-only. This is a blocker for me as I don't want a new module in my Ivy repository for every branch. I just want another version in the same module. -- View this message in context: http://old.nabble.com/Gradle-doesn%27t-handle-branch-checkouts-very-well-tp28540196p28540196.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
