Re: [gradle-user] Multi-project build - custom artifact names

[Adam Murdoch]

Les Hazlewood wrote: Any idea on how I can get the -SNAPSHOT designation appended after the version number if the "release" target is called (I'm using the code shown in the 2.11 section of the user guide) until this bug is fixed? The code in section 2.11 should work regardless of this bug. Can you send in this snippet of code from your build file. Also, can you be a little more specific about what isn't working exactly? Unfortunately for me, this one nagging thing is a primary factor in how I get gradle incorporated into our organization: We're an Ant+Ivy shop, but we need the ability to upload artifacts to a intranet Maven repo - this is where our Ivy config downloads artifacts from.  The -SNAPSHOT designator is needed to indicate it as a snapshot to the Maven repo.  Our other builds rely on this designator for up-to-the-minute verification of API consistency. Since Ant+Ivy doesn't do Maven repo uploads like Gradle 0.5 can, this is the primary reason we're investigating Gradle.  So, is there a recommended workaround for this until 5.1 is released? Thanks again! Les On Fri, Dec 26, 2008 at 3:18 PM, Hans Dockter <m...@dockter.biz> wrote: I'm putting the logic to append the -SNAPSHOT designator, as well as to do the artifact renaming (and manifest name changes) in the init method.  This isn't working.  Any reason why?  Any help is _sincerely_ appreciated! Unfortunately you ran into a Gradle bug: http://jira.codehaus.org/browse/GRADLE-330 A fix for this will be provided with the 0.5.1 release. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email