I think this might work if you put the groovy files in src/main/groovy and put the Java files in src/main/java. The joint compiler is supposed to look in both places. However the javadoc task may need to see only Java in src/main/java. Give it a shot.
In the documentation.... "Once loaded, the groovyc compiler will be automatically selected if any .groovy source files are found under src/main/groovy directory, compiling them by default into the target/classes directory.... If the project has java sources in src/main/java they will get compiled using the groovyc joint compiler." On Thu, Nov 11, 2010 at 11:04 AM, Simon Harrer <[email protected]>wrote: > Hi buildr Community. > > I think buildr is really cool. But currently, I am stuck generating javadoc > > project structure: > src/main/java <-- java and groovy sources > target/classes <-- output folder > > This works perfectly with the groovyc joint compiler. > > However, when using the doc command, buildr states that it cannot guess the > language and aborts. And I do not find a way to specify that I want javadoc > generated for src/main/java. > > My only other solution would be to create such a javadoc task myself by > leveraging ant or the command line. Or is there a solution with buildr? > > Best regards, > Simon >
