hi hans, i have guessed, that the sources-problem can be solved by combining ivy and some convention. that combination, together with dsl-technique is a real winner ...
as i am convinced of its quality. i have mentioned gradle in some of the community-forums, that i visit ... i hope you dont mind. IMO an adaption of gradle by the springframework would be great. i think, they build partly with maven and partly with ant + ivy. there build-quality is not bad, but could be better and they surely want to unify their builds. you may know their http://www.springsource.com/repository repository . im afraid there is another topic in my mind, that i will ask stupid questions about soon: release-build ;-) ... sometimes stupid questions are helpful too, are'nt they ? thank you & have a successful day hdockter wrote: > > 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 > > > > -- View this message in context: http://www.nabble.com/howto-retrieve-sources-for-thirdparty-libs-tp19273681p19292782.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
