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
