Inline.
On 08/11/2011 04:57 AM, Max Rydahl Andersen wrote:
>> What exactly is the problem? Is eclipse not picking up the configuration in the
pom when running the tests, or something else?
>
> The Eclipse JUnit runner does not read from the Surefire config, so the
> sysprops aren't set in default launch "Run As> JUnit".
would creation of symbolic links work as a stop-gap solution ?
Nice thought, but I hesitate due to cross-platform concerns.
While we ponder the general testsuite reorg in my other Thread, I'm
looking at what we can do here that's not too hacky.
S,
ALR
/max
>
> S,
> ALR
>
>>
>> Stuart
>>
>>>
>>> I think I lean for 3), assuming it can be done intelligently enough.
>>> Then we'll only start/stop the server ONCE for a full build, and blow
>>> through all tests there regardless of their source module. The source
>>> modules are important as they stand in order to assert our compile
>>> dependencies.
>>>
>>> S,
>>> ALR
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
/max
http://about.me/maxandersen
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev