Hi Peter,
Normally gatein should be independent of the build system and we should not have eclipse specific files, however I don't know much about selenium sniff tests and whether or not those files have just been imported by mistake or if that's really a necessity.
to eclipse users : can someone tell us if those files are just leftover configuration imported by mistake or if it is required for running selenium sniff tests ?
until we find out you should probably add gatein-portal/testsuite/selenium-snifftests/src/eclipse/*.lauch to your .gitignore if you can afford to.
Julien Vietjulienviet.com
On Friday, June 8, 2012 at 3:41 PM, Peter Palaga wrote:
Ladies and Gentlemen,
As I imported gatein-portal into my Eclipse workspace, my m2e (anEclipse plugin) has by itself inserted the following two lines into thetwo *.launch files undergatein-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, Icould surely tell git to never commit it somehow but generally, would itnot be better not to have IDE-specific files commited to scm?
Thanks,
Peter_______________________________________________gatein-dev mailing list