ast transforms do not behave when compiler used standalone (outside of the IDE)

What prevents this working is the lack of a defining project when setting up the groovy parser with the appropriate groovy class loader for transforms. With no project it doesn't discover the projects classpath and that classpath is what is used to populate the GroovyClassLoader that will be searched for transforms. We just have to add the extra logic in to cope with the batch case and retrieve the path from the FileSystem in the LookupEnvironment.

fixed

Hi! That's good news. When will this be available via the groovy-eclipse-compiler for Maven projects? Or: What do I have to do to use it in maven projects?

Andrew Eisenberg was kicking off a rebuild of the jars for that yesterday, should be available imminently. Not sure if he will build a new version or switch to a snapshot model - I guess either way you will have to slightly edit your pom to pick it up. Look out for the announce. That build does include something else I was temporarily working on (but have now backed out) - so I hope that change doesn't disturb compilation for you. If you see problems about things being unresolved, let me know. It will also be groovy 1.7.5 level.

OK. Thanks for the quick answer!

Stefan

It's now available using 0.5.1-SNAPSHOT. If you get a chance, we'd appreciate feedback on the mailing list.

Stefan reports it is still not working for him, but has now attached a sample project.

My fix was good, I believe the packaging process for the snapshot was broken. It should now be fixed and Andrew tells me he uploaded a new snapshot correctly built.

Works fine for me now. Theanks.

Stefan