[jbosstools-issues] [JBoss JIRA] (JBIDE-6117) JBOSS tools native support for code gen in Groovy, and new Groovy seam project

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen resolved JBIDE-6117.
----------------------------------------

    Resolution: Out of Date


Thank you for reporting this issue but this issue have been resolved as out-of-date since it has not had any updates for the last 2+ years (730 days).

If you believe this issue is still relevant and important then please reopen the issue or create a new one mentioning/linking this jira for background information.

Thank you!


                
> JBOSS tools native support for code gen in Groovy, and new Groovy seam project
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-6117
>                 URL: https://issues.jboss.org/browse/JBIDE-6117
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: seam2
>    Affects Versions: 3.1.0.GA
>         Environment: eclipse 3.5 with jboss tools 3.1 GA
>            Reporter: William Woodman
>            Assignee: Denis Golovin
>             Fix For: LATER
>
>
> Trying to use Groovy with Jboss tools and i'm having to hand craft all the files.  Essentially i have to generate the types in the IDE, then cut/copy the code back into groovy files and save.
> also have to install groovy IDE files separately and then enable grrovy support fr the project and set the j2ee module dependencies to get the deployed build to work.
> Groovy is actually really nice for the entity builds (so much less clutter) and closure features etc are nice in the language.
> What i'd like is that rather than just jboss tools being flexible to knit groovy in - it should have first class support in the jboss tools.
> I'm using seam so lets lay out thje basic requirement
> 1.  future near build of jboss tools to provide install support for groovy.  Create seam project and in wizard indicate that that you default code gen to be groovy or java.
> if groovy - inlude the latest groovy all jar in the ejb/war projects and automatically include the J2ee module dependency so that groovy files work when exporting project to server.
> 2.  do some integration work with the groovy IDE guys, or duplicate equivalent builders into the JBOSS tools standard download.
> 3.  when user selects new entity, form, conversation,  etc show the default class gen type (from startup wizard) but let a user overwrite in the wizard (allows mixed mode working - with default for project as set at startup).
> 4. if groovy selected ensure that full debug support included for groovy files.
> This would be a fabulous improvement.  At present although i can build a grooy project its very manually intensive and I have to do all the hard work by hand/cut copy etc .
> would be fabulous if jboss tools fully supported this natively.  
> Also with seam v3 on the build, ensuring that groovy option is included into weld/seam v3 would be a plus also 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira