Important changes for running Gradle from an IDE.

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Important changes for running Gradle from an IDE.

hans_d
Administrator
Hi,

the work on the logging has as a side effect improved our  
bootstrapping. It is now more flexible. If you run Gradle from an IDE  
you now use the same class as an entry point as when running Gradle  
from the command line. This is the BootstrapMain class. You don't  
need any longer an additional installed version of Gradle when  
running Gradle from an IDE. And before those changes the IDE  
classpath were not used in all of the places (e.g. compiling the  
build sources). This is different now.

I have updated the development wiki: See http://docs.codehaus.org/ 
display/GRADLE/How+to+run+the+Gradle+project+in+IntelliJ+against+any
+Gradle+build

- Hans

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Important changes for running Gradle from an IDE.

Stefan Groschupf
> I have updated the development wiki: See http://docs.codehaus.org/display/GRADLE/How+to+run+the+Gradle+project+in+IntelliJ+against+any+Gradle+build

WOW! This is pretty overwhelming for people want to look into the  
gradle code.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Important changes for running Gradle from an IDE.

hans_d
Administrator

On Sep 24, 2008, at 12:24 AM, Stefan Groschupf wrote:

>> I have updated the development wiki: See http://docs.codehaus.org/ 
>> display/GRADLE/How+to+run+the+Gradle+project+in+IntelliJ+against
>> +any+Gradle+build
>
> WOW! This is pretty overwhelming for people want to look into the  
> gradle code.

This is for people who want to RUN Gradle from there IDE to do  
debugging. These are mostly Gradle developers. For just looking at  
the code is it good enough to follow these steps: http://
docs.codehaus.org/display/GRADLE/How+to+set+up+the+Gradle+project+in
+IntelliJ

Of course a Gradle IntelliJ plugin would be even nicer :)

- Hans

--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Important changes for running Gradle from an IDE.

Stefan Groschupf
>> WOW! This is pretty overwhelming for people want to look into the  
>> gradle code.
> This is for people who want to RUN Gradle from there IDE to do  
> debugging. These are mostly Gradle developers. For just looking at  
> the code is it good enough to follow these steps: http://docs.codehaus.org/display/GRADLE/How+to+set+up+the+Gradle+project+in+IntelliJ

STILL  WOW!!!!
This is way to much. Right here is your barrier to get new developers.
For example what you need to do to get katta our gradle build open  
source project up and running:

1.) check out the code
2.) add src/main{java|test} as sourcefolder
3.) add all under lib to the classpath

Run Katta.main() - READY!
Everything else is too much. If you want to get more contributors you  
need to make this a no-brainer.
Also screw intellij, 95 % of all developers are not using intellij,  
they use vi, wordpad, eclipse or what ever so do not make it intellij  
only that for example turns me off.

... just my 2 cents feedback.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Important changes for running Gradle from an IDE.

hans_d
Administrator

On Sep 24, 2008, at 1:34 AM, Stefan Groschupf wrote:

>>> WOW! This is pretty overwhelming for people want to look into the  
>>> gradle code.
>> This is for people who want to RUN Gradle from there IDE to do  
>> debugging. These are mostly Gradle developers. For just looking at  
>> the code is it good enough to follow these steps: http://
>> docs.codehaus.org/display/GRADLE/How+to+set+up+the+Gradle+project
>> +in+IntelliJ
>
> STILL  WOW!!!!
> This is way to much. Right here is your barrier to get new developers.
> For example what you need to do to get katta our gradle build open  
> source project up and running:
>
> 1.) check out the code
> 2.) add src/main{java|test} as sourcefolder
> 3.) add all under lib to the classpath

The directions for settings up a Katta project in IntellIJ would be  
EXACTLY the same. Except the bits to add Groovy support. There is  
nothing to improve AFAICT.

>
> Run Katta.main() - READY!

Running Gradle is much more complex then running Katta. After all it  
is a installable command line distribution with many options. The  
challenge is to make it possible to run Gradle from a Main class  
without the necessity to have Gradle installed. This is possible with  
Gradle and we are very happy about this.

> Everything else is too much. If you want to get more contributors  
> you need to make this a no-brainer.
> Also screw intellij, 95 % of all developers are not using intellij,  
> they use vi, wordpad, eclipse or what ever so do not make it  
> intellij only that for example turns me off.

As we are a project which uses a lot of Groovy IntelliJ is a natural  
choice at the moment. But I agree that it would be good to have a  
page for Eclipse as well.

Thanks for your feedback.

- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org





---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email