[jboss-dev] Including testsuite in Eclipse

[Paul Gier]

The current version of m2eclipse (0.10.0) seems to work ok for me as far as
building the classpath.  In general I would prefer not to have IDE specific
config files checked into svn, but I guess it's the only choice if it's too
difficult to get m2eclipse working.

Jason T. Greene wrote:
> Paul, any thoughts on this?
> 
> I suppose we could commit a .classpath that refers to the M2 stuff and
> somehow exclude m2e from running in testsuite.
> 
> Vladimir Blagojevic wrote:
>> I was complaining about this yesterday on jboss-dev. If m2eclipse is
>> not creating correct .project and .classpath can we check the
>> appropriate versions in svn?
>>
>> On 2010-04-09, at 8:39 AM, Thomas Diesler wrote:
>>
>>> Here are some settings that I had to manually create and then modify
>>>
>>> [tdiesler at tdbell testsuite]$ svn diff
>>> Index: .classpath-example
>>> ===================================================================
>>> --- .classpath-example    (revision 0)
>>> +++ .classpath-example    (revision 0)
>>> @@ -0,0 +1,9 @@
>>> +<?xml version="1.0" encoding="UTF-8"?>
>>> +<classpath>
>>> + <classpathentry excluding="org/jboss/test/jsf/webapp/" kind="src"
>>> path="src/main"/>
>>> + <classpathentry kind="src" path="output/gen-src"/>
>>> + <classpathentry kind="src" path="src/resources"/>
>>> + <classpathentry kind="con"
>>> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
>>> + <classpathentry kind="con"
>>> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
>>> + <classpathentry kind="output" path="output/classes"/>
>>> +</classpath>
>>> Index: .project-example
>>> ===================================================================
>>> --- .project-example    (revision 0)
>>> +++ .project-example    (revision 0)
>>> @@ -0,0 +1,23 @@
>>> +<?xml version="1.0" encoding="UTF-8"?>
>>> +<projectDescription>
>>> + <name>jboss-as-testsuite</name>
>>> + <comment></comment>
>>> + <projects>
>>> + </projects>
>>> + <buildSpec>
>>> + <buildCommand>
>>> + <name>org.eclipse.jdt.core.javabuilder</name>
>>> + <arguments>
>>> + </arguments>
>>> + </buildCommand>
>>> + <buildCommand>
>>> + <name>org.maven.ide.eclipse.maven2Builder</name>
>>> + <arguments>
>>> + </arguments>
>>> + </buildCommand>
>>> + </buildSpec>
>>> + <natures>
>>> + <nature>org.maven.ide.eclipse.maven2Nature</nature>
>>> + <nature>org.eclipse.jdt.core.javanature</nature>
>>> + </natures>
>>> +</projectDescription>
>>>
>>>
>>> On 04/09/2010 02:23 PM, Thomas Diesler wrote:
>>>> I am having a hard time including jbossas/trunk/testsuite into eclipse.
>>>> What is the reason that eclpise project files (that do not contain
>>>> local
>>>> settings) are not checked in any more?
>>>>
>>>> More importantly, how do you work with the testsuite in eclipse?
>>>>
>>>> cheers
>>>> -thomas
>>>>
>>>>
>>> -- 
>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>> Thomas Diesler
>>> JBoss OSGi Lead
>>> JBoss, a division of Red Hat
>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
>