Running a single jUnit test in a maven project doesn't use maven surefire in 6.7

View: New views
3 Messages — Rating Filter:   Alert me  

Running a single jUnit test in a maven project doesn't use maven surefire in 6.7

by Edward Samson-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

When I run/debug a jUnit test class in my maven project, NetBeans 6.7
doesn't use the surefire plugin to run the tests. Unit tests that rely
on some configuration in surefire are now failing.

In my specific case, surefire is configured to set some
developer-specific environment settings like where the native
libraries are installed.

This used to work as expected in NetBeans 6.5. Is there a way to tell
NetBeans 6.7 to use maven to run the jUnit tests instead of its own
test runner?

Thanks,

--
Edward Samson

Re: Running a single jUnit test in a maven project doesn't use maven surefire in 6.7

by mkleint-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'm currently working on fixing these 2 bugs associated with CoS and
surefire configs. Hopefully it makes it into the patch release.

http://www.netbeans.org/issues/show_bug.cgi?id=168036
http://www.netbeans.org/issues/show_bug.cgi?id=168041

you can workaround the problem by disabling Compile on Save in the
project properties dialog. Then you should have the same behaviour as in 6.5

Milos

Edward Samson wrote:

> Hi,
>
> When I run/debug a jUnit test class in my maven project, NetBeans 6.7
> doesn't use the surefire plugin to run the tests. Unit tests that rely
> on some configuration in surefire are now failing.
>
> In my specific case, surefire is configured to set some
> developer-specific environment settings like where the native
> libraries are installed.
>
> This used to work as expected in NetBeans 6.5. Is there a way to tell
> NetBeans 6.7 to use maven to run the jUnit tests instead of its own
> test runner?
>
> Thanks,
>
>  


Re: Running a single jUnit test in a maven project doesn't use maven surefire in 6.7

by Edward Samson :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Who would've thought it would be the compile on save feature. :)

Thanks for the workaround (need to get some work done before trying
out the latest nb build) and thanks for all your great work.

On Fri, Jul 3, 2009 at 7:44 PM, mkleint<Milos.Kleint@...> wrote:

> I'm currently working on fixing these 2 bugs associated with CoS and
> surefire configs. Hopefully it makes it into the patch release.
>
> http://www.netbeans.org/issues/show_bug.cgi?id=168036
> http://www.netbeans.org/issues/show_bug.cgi?id=168041
>
> you can workaround the problem by disabling Compile on Save in the project
> properties dialog. Then you should have the same behaviour as in 6.5
>
> Milos
>
> Edward Samson wrote:
>>
>> Hi,
>>
>> When I run/debug a jUnit test class in my maven project, NetBeans 6.7
>> doesn't use the surefire plugin to run the tests. Unit tests that rely
>> on some configuration in surefire are now failing.
>>
>> In my specific case, surefire is configured to set some
>> developer-specific environment settings like where the native
>> libraries are installed.
>>
>> This used to work as expected in NetBeans 6.5. Is there a way to tell
>> NetBeans 6.7 to use maven to run the jUnit tests instead of its own
>> test runner?
>>
>> Thanks,
>>
>>
>
>



--
Edward Samson