Hi Helmut,
On Sep 2, 2008, at 6:38 PM, Helmut Denk wrote:
hello gradle-users,
is there a decent way, to let gradle retrieve lib-sources
to the ide-workspace (or another proper location), so that
a comfortable debug into thirdparty-code is possible ?
in our 'pre-gradle' ;-) builds we do kind of this:
<dependency org="com.lowagie" name="itext" rev="2.0.8"
conf="compile->default">
<artifact name="itext" type="jar" ext="jar"/>
<artifact name="itext" type="source" ext="src.zip"/>
</dependency>
(we retrieve all artifacts through cache to $basedir/lib
and handset build-path with source-attachments)
apologies for the late response. I'm often torn between focussing on
implementing a certain feature and being responsive to the community.
For the first iteration of our Ivy DSL the aim was to provide as
least as much as the Maven dependency management does. It provides
only a subset of what is possible with Ivy. As we want to enable all
the power of Ivy in an easy way we follow a couple of strategies:
- Enhance our DSL. The above use case definitely should be solvable
with our DSL. Please file a Jira. BTW: Such stuff is very easy to
implement. We have a class ModuleDependency which creates an Ivy
ModuleDescriptor. So we just have to add methods/properties to a
ModuelDependency and then stuff it into the Ivy ModuleDescriptor object.
- What you can do now already is, to create your own Ivy
ModuleDescriptor object and add it to the dependencies. This would
solve your use case above. Not as convenient as it should be though.
- For 0.4: Add a listener framework around the Ivy objects the Gradle
Ivy DSL creates.
- Hans
this is probably a point for the 'gradle eclipse' command too.
That would be nice. I have happily used such a feature with the Maven
Eclipse plugin.
Please another Jira :)
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
