The launcher project is a java project, not a groovy project (although it does use groovy for the tests). This is intentional: the code in launcher must have as fast a start-up time as we can manage, so Groovy is out for implementation.
What are you adding? It might have a better home, where Groovy may be an option. On 05/05/2011, at 4:31 AM, Eric Berry wrote: > Hello, > I'm trying to build Gradle from source but I've run in to a little issue > after adding a Groovy class to the launcher subproject. > > I followed the instructions here: > http://gradle.org/build.html > > Which upon clone from git, works fine. > > However, I added just a small groovy class to the launcher project under > src/main/groovy. Now it will no longer build or install. > > I see this in the output when I remove my groovy class: > [quote] > :launcher:compileJava > :launcher:compileGroovy UP-TO-DATE > :launcher:processResources UP-TO-DATE > :launcher:classes > [/quote] > > But adding a groovy class to launcher/src/main/groovy causes compileJava to > fail. > > -- > Learn from the past. Live in the present. Plan for the future. > Blog: http://eric-berry.blogspot.com > jEdit <http://www.jedit.org> - Programmer's Text Editor > Bazaar <http://bazaar.canonical.com> - Version Control for Humans -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
