2.x migration beta

[johannol]

Hi Trygvea

The 2.x migration is not finished for me, but this is working:

• Standalone for test/dev
• In a project as plugin

Still to do:

• Remove warning with changing deprecated stuffs
• Improve the way to remove injected methods,

[trygvea]

Thanks for the contribution. Smart way you detect the injected/instrumented methods. But I still I get a handful of unwanted methods, namely currentGorm*Api() and initErrors/hasErrors/setErrors. Also, maybe not so important, but still part of the included test-domains, the EmbeddedPart has too many attributes.

I will look into it.

[johannol]

i just added the removing of warnings because of the deprecated "ConfigurationHolder"

The way to remove injected methods is still to be improved. It worked well on my projects, but indeed not so well on your more complete test case. I had also the idea to create on the fly objects to compare (more complex), or use a complete test case like your one, to reference all methods... or something else. ;-)

[huweihong]

My project is in Grails 2.2,I also need this plugin support Grails 2.

[johannol]

For huweihong:
My fork (https://github.com/johannol/grails-class-diagram) is now working on Grails 2, and a poll request is done to trygvea. The remaining issue is there are still some remaining Grails's injected method/attribute in some domain objects (depend of the project).

It could be released "at is" for now, or still waiting to improve this fisrt. I prefer the "release often" option, but trygvea decide. Anyway, you can compile my fork, or help us to find an idea ;)

[mgnzna]

Hi johannol,

Do you know what is happening with this in terms of merging back into the official grails plugin? I don't know what the etiquette here is but the original version is effectively obsolete and yours works (thank you) but there's only a complicated way to get hold of it by checking the project out of github, building it and installing it.

The problem is not just about GitHub it's more about the grails plugin site.