[#GRVY-808] Domain class packages apparently not supported

Groovy

Domain class packages apparently not supported

Created: 15 Dec 07 00:43 Updated: 05 Jul 08 12:10

Component/s:

Grails editor support

Affects Version/s:

None

Fix Version/s:

None

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

« Hide

Idea doesn't seem to properly support Grails domain classes when they're in a package. With JetGroovy 0.1.13053:

The switcher that allows you to move between domain classes, their controllers and their tests does not work
The domain class dependencies diagram shows up blank

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Arnaud Crasborn - 02 Jan 08 18:07

I will greatly appreciate supports for Grails domain classes that are in a package, since Java code cannot work with Grails domain classes that are in default package.

In JetGroovy 1.0.13464 are the switcher not showed for such domain classes -> I cannot generate the controllers and views (Note: it works in command line with grails generate-all de.compagny.project.model.Item)

Thanks for this great plugin.

[ Permlink | « Hide ]

Barry Kaplan - 06 Feb 08 03:57

The lack of package support lops off a huge chunk of benefit from JetGroovy.

[ Permlink | « Hide ]

Horacio Gutierrez - 26 Mar 08 19:35

I'm starting to use Groovy and Grails (and thus JetGroovy) more and more and have found the lack of package support in Grails to be one of the main pain points of this otherwise very nice plugin. Putting code in the default package may be fine for small demos and prototypes, but it isn't really an option for production code. Any plans for adding package support soon?
Thanks!

[ Permlink | « Hide ]

olivier FRESSE - 08 Apr 08 21:33

I'm ready to move to Intellij just because of this great plugin.
But the lack of domains packages is a no go for me.
I really can't put all my domain classes at the default level

I also use the RichUI plugin which is not recognized because of packages.

[ Permlink | « Hide ]

Roan OSullivan - 04 Jun 08 20:05

This is important for me too. Is there any chance of it being patched in the near future?

[ Permlink | « Hide ]

Roan OSullivan - 04 Jun 08 20:08

Forgot to mention that I first encountered this issue when editing a Controller that was in a package. The groovy editor does not recognize the package under the grails-app/controllers folder (e.g. grails-app/controllers/com/abc) and flags the package statement ("package com.abc") as an error.

[ Permlink | « Hide ]

Ricardo J. Méndez - 05 Jun 08 00:21

This seems like a pretty important issue, since packages are pretty much a must for a large application. Any chance we can get a reply from IntelliJ on this?

[ Permlink | « Hide ]

Artur Karazniewicz - 05 Jul 08 11:31

This is must have feature for me and really show-stoper. Also seems to be trivial to fix.

[ Permlink | « Hide ]

Ricardo J. Méndez - 05 Jul 08 12:10

Chiming in again - this is a very important issue for enterprise Grails development. Groovy / Grails was the reason that pushed me to purchase Idea. Can anyone from IntelliJ state if they have plans to add it, and if so when?