Thanks again Rene. This works! Now if I could only figure out a way to rename the project.name so that the resolved ivy file gets published with a different name to match the same pattern as the rest of my artifacts. When I try to override project.name I get
Cause: Cannot set the value of read-only property 'name' on root project -----Original Message----- From: Rene Groeschke [mailto:[email protected]] Sent: Monday, January 03, 2011 5:36 PM To: [email protected] Subject: Re: [gradle-user] uploadArchives for non-java project Hi Pablo, well an import statement should do the trick: ------- import org.gradle.api.internal.artifacts.publish.DefaultPublishArtifact ------- regards, René Am 03.01.11 18:03, schrieb Munoz, Pablo [Tech]: > Thanks for the info Rene. Unfortunately it didn't work for me. Got the > following error: > > > build_gradle_6f04a51e7b499a797c036a90ac3651bd: 5: unable to resolve class > DefaultPublishArtifact > @ line 5, column 11. > archives new DefaultPublishArtifact("myassembly", "jar", "jar", null, > new Date(), file('myassembly/target/myassembly.jar')) > ^ > > > Here is my build.gradle snippet: > > > apply plugin: 'base' > apply from: 'ivy.gradle' > > artifacts { > archives new DefaultPublishArtifact("myassembly", "jar", "jar", null, > new Date(), file(myassembly/target/myassembly.jar')) > } > > > -----Original Message----- > From: Rene Groeschke [mailto:[email protected]] > Sent: Monday, January 03, 2011 9:35 AM > To: [email protected] > Subject: Re: [gradle-user] uploadArchives for non-java project > > Hi pablo, > have a look at this thread on the mailinglist: > http://gradle.1045684.n5.nabble.com/adding-a-builded-DLL-to-a-configuration-publishing-to-artifactory-td1436111.html > > hope this helps, > regards, > René > > Am 03.01.11 15:24, schrieb Munoz, Pablo [Tech]: >> Thanks Adam, >> >> What about non-standard assemblies or non-archives? How would I attach >> individual dll's to the archives conf for example? >> >> Thanks, Pablo Munoz >> >> >> From: Adam Murdoch [mailto:[email protected]] >> Sent: Saturday, January 01, 2011 7:49 PM >> To: [email protected] >> Subject: Re: [gradle-user] uploadArchives for non-java project >> >> >> On 01/01/2011, at 7:56 AM, Munoz, Pablo [Tech] wrote: >> >> >> Does anyone have a working sample of uploading archives from a non-java >> project? Couldn't find anything in the samples or docs. >> >> >> You can use the 'base' plugin, which is what the 'java' plugin uses to >> configure the uploads. The only difference between the two is that you need >> to explicitly declare which archives to upload. Here's an example: >> >> apply plugin: 'base' >> >> artifacts { >> archives someZipTask >> } >> >> uploadArchives { >> repositories { >> // as per java plugin >> } >> // you might also want this, if you don't need an ivy.xml or pom.xml >> uploadDescriptor = false >> } >> >> Have a look at http://gradle.org/0.9/docs/userguide/artifact_management.html >> for more details. >> >> You can also do this without the 'base' plugin, but you need to configure >> more stuff yourself. >> >> >> -- >> Adam Murdoch >> Gradle Developer >> http://www.gradle.org >> CTO, Gradle Inc. - Gradle Training, Support, Consulting >> http://www.gradle.biz >> >> > -- ------------------------------------ Rene Groeschke [email protected] http://www.breskeby.com http://twitter.com/breskeby ------------------------------------ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
