[jboss-as7-dev] Arquillian Tests not Running From IDE

Max Rydahl Andersen max.andersen at redhat.com
Thu Aug 11 17:08:22 EDT 2011


>> 
>> ah gotcha.
>> 
>> Can you point me to the github location of this surefire config and ill look if we could
>> actually somehow make our m2e integration understand this ?
> 
> https://github.com/jbossas/jboss-as/blob/master/testsuite/pom.xml#L166
> 
> And I appreciate the offer to look into IDE integration options, but IMO 
> it's really not the job of the IDE here to parse out both the Surefire 
> config for that profile *and* apply the jboss.home var correctly.  Those 
> are part of the build.

well, that is mostly how any of the decent maven integration works (reading the pom and 
creates matching IDE concepts)

> What I'm after is a solution that is friendly to all default runners, be 
> it Eclipse JUnit, IDEA, Ant, etc.  Right now we're relying on Maven config.

gotcha.

/max

> 
> S,
> ALR
> 
>> 
>> /max
>> 
>>> 
>>> S,
>>> ALR
>>> 
>>> On 08/09/2011 01:18 PM, Max Rydahl Andersen wrote:
>>>> i'm curious - how did the IDE know how to pick up the jars before ?
>>>> 
>>>> /max
>>>> 
>>>> On Aug 9, 2011, at 14:19, Andrew Lee Rubinger wrote:
>>>> 
>>>>> Hiya.
>>>>> 
>>>>> Since we've stopped copying the modules under JBOSS_HOME for the
>>>>> testsuite (in order to save space), the default launch config from the
>>>>> IDE doesn't know where to pick these up (unless manually configured with
>>>>> a sysprop at launch).
>>>>> 
>>>>> How do we feel about:
>>>>> 
>>>>> 1) Doing full copies of JBOSS_HOME like we used to? (Drawback: space)
>>>>> 2) Trying to put something in the AS7 ARQ Containers so that it'll find
>>>>> the modules by default (Drawback: Hacky/Programmatic Guesswork)
>>>>> 3) Reorganizing things such that the testsuite module source keeps their
>>>>> current structure, but instead we fire off the testsuite runs from
>>>>> another module all in one go, with a full JBOSS_HOME to back it?
>>>>> (Drawback: Build Complexity)
>>>>> 
>>>>> 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 at 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 at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

/max
http://about.me/maxandersen






More information about the jboss-as7-dev mailing list