Re: [gatein-dev] Purpose and Fate of *.launch Files under gatein-portal/testsuite/selenium-snifftests/src/eclipse
I'm not an Eclipse user myself (IntelliJ IDEA FTW) so I cannot comment on those
settings.
However we agreed quite a long time ago that we don't want to keep IDE related files
in source control. There is always additional maintenance related to this.
I personally don't see the benefit as IDEA has first class maven support and I just
import project by pointing to pom. Does it make that much sense for Eclipse project files
actually?
Bolek
On Jun 8, 2012, at 3:41 PM, Peter Palaga wrote:
Ladies and Gentlemen,
As I imported gatein-portal into my Eclipse workspace, my m2e (an
Eclipse plugin) has by itself inserted the following two lines into the
two *.launch files under
gatein-portal/testsuite/selenium-snifftests/src/eclipse:
<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER"
value="org.eclipse.m2e.launchconfig.classpathProvider"/>
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER"
value="org.eclipse.m2e.launchconfig.sourcepathProvider"/>
I would like to learn what should happen with these changes. Yes, I
could surely tell git to never commit it somehow but generally, would it
not be better not to have IDE-specific files commited to scm?
Thanks,
Peter
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev