On Mon, May 25, 2009 at 10:10 AM, Hans Dockter <[email protected]> wrote: > > On May 19, 2009, at 9:56 PM, Jeppe Nejsum Madsen wrote:
[...] >> - The .classpath file is generated with absolute paths to the >> dependencies. This makes it difficult to share the generated Eclipse >> project. Maven uses the M2_REPO var to specify the location of the >> repo > > http://jira.codehaus.org/browse/GRADLE-196 > >> . >> - The generated jar references doesn't include any javadoc our source. >> Maven provides the ability do download and attach both doc & source if >> specified in the poms > > http://jira.codehaus.org/browse/GRADLE-238 Ahh sorry for not checking Jira first :-( >> Is it possible to generate a pom.xml from my build.gradle >> dependencies? > > Yes. Maybe "possible" was a bad choice, since the answer is (almost) obviously yes :-) What I meant was, is there builtin support for this? If the answer is still yes, any pointers? I _did_ try to locate some info about this one :-) On a separate note: I'm working with Scala and using the patch from http://jira.codehaus.org/browse/GRADLE-287. What is needed to get Scala fully supported? It works fine for now (I've not yet tested with 0.6) and I'll probably do some hacking with this. What is the best setup for doing Gradle development? Is it possible to do integrated (Java & Groovy) debugging etc using Eclipse? /Jeppe --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
