IDE Descriptor Files Generation

[mykol]

I'm having a hard time importing existing Grails projects to Intellij Idea. And it seems this had been discussed for a number of occasions already in this list and elsewhere. I've noticed that in the grails.org example sources, the idea descriptor files is checked in (.ipr, .iml, etc). So I'm assuming that, from the development team's stand point, this is the way to go?

As an alternative, could an IDE descriptor files generator script be created so that the version control tree is not laced with these IDE specific files? I don't see Grails currently having the luxury of having an Ant or Maven project import currently supported by the top IDEs. But maybe a Grails plugin could be created which mimics how Maven Eclipse Plugin and Maven Idea Plugin do for Maven projects. Something like:

grails generate-idea-project
grails generate-eclipse-project

Also, this would mean the generated eclipse descriptor files be considered for removal from the create-app script. Imho that's a cleaner separation of work. Let me know your thoughts. I'll try my best to start something up just in case ;)


Regards,
Michael Mallete
http://noisyheads.com

[tomas lin]

For our projects, we usually do a grails-upgrade and then simply point
Idea to the .project file generated, which I think also works for
Eclipse.

With the JetGroovy plugin installed, it seems to work properly.

While the idea of pointing to different IDE files seems like a good
idea, it seems to reproduce a lot of work available elsewhere. Once
the maven integration is more robust, I can't see why grails will need
it's own IDEA generator rather than simply use the built-in Maven or
mvn idea:idea goals...






On Mon, Jun 16, 2008 at 12:09 AM, Michael Mallete <mrmallete@...> wrote:

> I'm having a hard time importing existing Grails projects to Intellij Idea.
> And it seems this had been discussed for a number of occasions already in
> this list and elsewhere. I've noticed that in the grails.org example
> sources, the idea descriptor files is checked in (.ipr, .iml, etc). So I'm
> assuming that, from the development team's stand point, this is the way to
> go?
>
> As an alternative, could an IDE descriptor files generator script be created
> so that the version control tree is not laced with these IDE specific files?
> I don't see Grails currently having the luxury of having an Ant or Maven
> project import currently supported by the top IDEs. But maybe a Grails
> plugin could be created which mimics how Maven Eclipse Plugin and Maven Idea
> Plugin do for Maven projects. Something like:
>
> grails generate-idea-project
> grails generate-eclipse-project
>
> Also, this would mean the generated eclipse descriptor files be considered
> for removal from the create-app script. Imho that's a cleaner separation of
> work. Let me know your thoughts. I'll try my best to start something up just
> in case ;)
>
>
> Regards,
> Michael Mallete
> http://noisyheads.com
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[mykol]

.project is an Eclipse descriptor file so it is expected to work. It's Idea's eclipse integration that probably makes your method possible.

Different IDEs makes use of different descriptor files, that's why I believe it's always optimal if each are given their proper ones. A go-between usually is a build framework such as Ant and Maven. And, hopefully, Maven integration would eventually catch up to support this out of the box.

On Mon, Jun 16, 2008 at 12:47 PM, Tomas Lin <tomaslin@...> wrote:

For our projects, we usually do a grails-upgrade and then simply point
Idea to the .project file generated, which I think also works for
Eclipse.

With the JetGroovy plugin installed, it seems to work properly.

While the idea of pointing to different IDE files seems like a good
idea, it seems to reproduce a lot of work available elsewhere. Once
the maven integration is more robust, I can't see why grails will need
it's own IDEA generator rather than simply use the built-in Maven or
mvn idea:idea goals...

On Mon, Jun 16, 2008 at 12:09 AM, Michael Mallete <mrmallete@...> wrote:
> I'm having a hard time importing existing Grails projects to Intellij Idea.
> And it seems this had been discussed for a number of occasions already in
> this list and elsewhere. I've noticed that in the grails.org example
> sources, the idea descriptor files is checked in (.ipr, .iml, etc). So I'm
> assuming that, from the development team's stand point, this is the way to
> go?
>
> As an alternative, could an IDE descriptor files generator script be created
> so that the version control tree is not laced with these IDE specific files?
> I don't see Grails currently having the luxury of having an Ant or Maven
> project import currently supported by the top IDEs. But maybe a Grails
> plugin could be created which mimics how Maven Eclipse Plugin and Maven Idea
> Plugin do for Maven projects. Something like:
>
> grails generate-idea-project
> grails generate-eclipse-project
>
> Also, this would mean the generated eclipse descriptor files be considered
> for removal from the create-app script. Imho that's a cleaner separation of
> work. Let me know your thoughts. I'll try my best to start something up just
> in case ;)
>
>
> Regards,
> Michael Mallete
> http://noisyheads.com
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email