eclipsify and VCS

[GrailsDeveloper]

Hi,

I would appreciated if the eclipsify command get an option so that
the .classpath could be put into the VCS.
Here is an snippte of an .classpath file which is ready for VCS:
<classpathentry kind="var" path="PLAY_HOME1.0.2/play.jar"
sourcepath="/PLAY_HOME1.0.2/"/>
<classpathentry kind="var" path="PLAY_HOME1.0.2/lib/activation.jar"/>
<classpathentry kind="var" path="PLAY_HOME1.0.2/lib/antlr-2.7.6.jar"/
>
<classpathentry kind="var" path="PLAY_HOME1.0.2/lib/asyncweb-
common-0.9.0-SNAPSHOT.jar"/>
<classpathentry kind="var" path="PLAY_HOME1.0.2/lib/backport-util-
concurrent-3.0.jar"/>
<classpathentry kind="var" path="PLAY_HOME1.0.2/lib/bcprov-
jdk15-142.jar"/>

So you only must change from kind="lib" to kind="var" and C:\frameworks
\play-1.0.2.1\framework durch PLAY_HOME1.0.2.
In eclispe you define the variable PLAY_HOME1.0.2 in the preferences
at "classpath variables".

This works under grails very good.
What do you think?

[Guillaume Bort]

Well I'm not a big fan of committing the IDE configuration into VCS.
And the problem with your proposition is that it will be a little more
complex to setup an eclipse project.

> --
> You received this message because you are subscribed to the Google Groups "play-framework" group.
> To post to this group, send email to play-fr...@googlegroups.com.
> To unsubscribe from this group, send email to play-framewor...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/play-framework?hl=en.
>
>

--
Guillaume Bort, http://guillaume.bort.fr

For anything work-related, use g...@zenexity.fr; for everything else,
write guillau...@gmail.com

[GrailsDeveloper]

What's the problem with committing the IDE configuration or to be more
correct the project-configuration? In a greater team you can simply
checkout the project and everything is OK. For example if you add some
source or javadoc information for a jar-file, than this information is
relevant for everyone. Furthermore you shouldn't call eclipsiify after
such a change. So everybody must add a new jar manually to
the .classpath file.
So I would say with variables you must do a little bit one at project
beginning, with the given solution you must do it every time you must
change the classpath.
For grails and eclipse my experience was that it was really
convenience.

[GrailsDeveloper]

At the moment I stopped to change my eclispe-settings manually using
the variable. But I still miss the possibility to attach source-code
or java-doc to a jar. Is there any convention which enable this?
Niels

[Niko]

I agree, it would fasten the setup process of a new team member if the
Eclipse project files are under VCS/SCM control. You just start up
Eclipse and can import/checkout an existing project. Currently I have
search & replace the hard coded path by a PLAY_HOME classpath and
linked resource variable.

Therefore I have reported a bug, if someone else finds this useful
please vote on:

https://bugs.launchpad.net/play/+bug/614830

Cheers,
Niko