On Sun, Mar 6, 2011 at 7:49 AM, Niclas Hedhman <[email protected]> wrote:
To package the SDK, use a Zip task
Declare the zip in artifacts so that it will be uploaded.
// Create the SDK bundle
task doZip(type: Zip {
// zip definition stuff here
from configurations.yourDepencyConfiguration {
into "libs"
}
}
// Define the resultant zip as an artifact.
artifacts {
archives doZip
}
the zip will be uploaded as per your upload configuration. If you are uploading to a maven repo, you can use filters to generate poms for the additional artifacts (http://www.gradle.org/1.0-milestone-1/docs/userguide/userguide_single.html#uploading_to_maven_repositories)
I am just on the final step to be able to create a full release with
Gradle, but something is stomping me on the last step.
The binary SDK is going to contain all the dependencies as well. And
we want to do that as a 'maven repo' inside the zip file. But,
uploadDefault will only upload artifacts that has been produced by the
build. I can't figure out how to pull in all the runtime dependencies
in that 'upload'.
Any ideas?
To package the SDK, use a Zip task
Declare the zip in artifacts so that it will be uploaded.
// Create the SDK bundle
task doZip(type: Zip {
// zip definition stuff here
from configurations.yourDepencyConfiguration {
into "libs"
}
}
// Define the resultant zip as an artifact.
artifacts {
archives doZip
}
the zip will be uploaded as per your upload configuration. If you are uploading to a maven repo, you can use filters to generate poms for the additional artifacts (http://www.gradle.org/1.0-milestone-1/docs/userguide/userguide_single.html#uploading_to_maven_repositories)
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/3xugrbk
I work here; http://tinyurl.com/24svnvk
I relax here; http://tinyurl.com/2cgsug
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
