Hi,
thanks for the reply. I already use the uploadArchive task to push my
artifacts to my internal repo. A second uploadReleaseTask to get some of
the artifacts in my release repository was my next idea :-)
regards,
René
ps: If you want to you can add EADS to the list of companies which uses
gradle :-) (http://www.eads.com)
have a nice we.
Am 24.04.10 09:24, schrieb Hans Dockter:
On Thu, Apr 22, 2010 at 10:36 AM, Rene Groeschke <[email protected]
<mailto:[email protected]>> wrote:
Hi there,
In my release build I want to move some of my artifacts from my
internal
repository to an external available one. I define the the
artifacts I want
to push to the new repository via a configuration:
configurations{
release "org.acme:DefaultWebApp:1...@war"
}
That shouldn't work.
configurations {
release
}
artifacts {
release yourWarTask
}
How can I push the artifacts of my release configuration to a new
repository. I tried it with the Upload task but didn't get it
working yet.
Furthermore it would be nice to modify the pom. thats way i tried
it with
Upload.
You would configure the uploadRelease task.
See:
http://gradle.org/0.9-preview-1/docs/userguide/artifact_management.html#N13179
- Hans
--
Hans Dockter
Founder, Gradle
http://www.gradle.org, http://twitter.com/gradleorg
CEO, Gradle Inc. - Gradle Training, Support, Consulting
http://www.gradle.biz
Any ideas to get this working? I stumbled over
configurations.release.publish(...) but don't know how to use it,
nor if
this is useful here.
regards,
René
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
------------------------------------
Rene Groeschke
[email protected]
http://www.breskeby.com
http://twitter.com/breskeby
------------------------------------
