Hi Helmut,
On Aug 29, 2008, at 4:50 AM, Helmut Denk wrote:
hi gradle-users,
we use an inhouse-built buildsystem that is
based on ant+ivy+hudson. this works quite good. but
as always and everywhere ... improvement is possible.
so, after reading the gradle-usersguide, i decided to
give gradle a try.
as we already use ivy, we have a set of common-used ivysettings.xml
and they are quite sophisticated (5+ repositories chained,
mixed filesystem- and url-resolving, use of changing-pattern for
SNAPSHOTS, special config of ivy-cache etc.)
from our perspective it would be nice to use existing
ivysettings.xml for gradle-builds too. -> keep build-configs
dry.
are there ways to achieve this ?
Not yet (may be with some dirty hacking, I'm not sure).
But we consider this as an important feature. On the ivy list people
complained already about this. For 0.4 we will increase the
flexibility to make a hand crafted solution rather easy. In a later
release we will provide out-of-the-box behavior for this.
Here is the issue: http://jira.codehaus.org/browse/GRADLE-197
And related: GRADLE-188 Provide listeners for Ivy ivysettings and
module descriptor generation. You may watch 188. It will be
implemented with your use case in mind.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
