Jan 18th, 2013, 05:25 PM
Depending on how the dependencies amongst sources are arranged, you may be able to organize it to compile.
If the groovy has no dependencies on the java you can build the groovy and then depend on it from an ajc compile step that builds the java with aspects and depends on the groovy.
If the groovy depends on the java but the java can build without the aspects in the mix, you can build the groovy/java in one step then depend upon it from an ajc step that weaves in the aspects.
If the dependencies are more tangled and it'll only work if all built together, unfortunately we have no current solution (yes, it sucks):
Groovy-Eclipse is a modified eclipse java compiler that understands groovy. AspectJ is a modified eclipse java compiler that understands AspectJ. We have an open bugzilla to create one modified eclipse compiler that understands java/groovy and AspectJ, but haven't done the work yet ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=287092 )...
Jan 18th, 2013, 05:45 PM
But even if Eclipse did that, that would have no help to me since I don't use Eclipse as my IDE. IntelliJ here and also run maven on the command line.
Jan 21st, 2013, 10:03 AM
My initial comments in the previous post were talking about possible maven configurations that might work depending on the dependencies amongst the elements. If that I enhancement I mentioned were implemented, the resultant compiler would be useful not only in Eclipse itself but in maven, for compiling projects involving all three languages where the dependencies were such that they couldn't be compiled as a two stage process. I can't comment on IntelliJ setup unfortunately, but I presume it can call out to maven to do the builds.
Jan 21st, 2013, 10:52 AM