Hi!
On Thu, Jun 26, 2008 at 2:50 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
> Pedro Pedruzzi wrote:
>>
>> Using Maven as build tool, I would prefer running every build phase
>> with it. For example, if I ask maven to build, pack and install some
>> project, it will pass trough the test phase. If some tests happen to
>> fail than I will have to rerun those externaly (from Maven) to get
>> more information (stack trace) and have IDE integration, without
>> having to handle generated report files directly.
>>
>> It is really very natural testing with 'Run as...', but if Maven has
>> its own testing phase, it would be very nice to have that more
>> integrated with JUnit or TestNG, eclipse GUIs (specially in a failure
>> case).
>>
>
> I see where you coming from, but that I guess it really depend on the
> developer's workflow.
>
> The primary goal of m2eclipse is to support quick turnaround during
> development cycles and to facilitate edit, compile (which is done
> transparently by JDT) and test from within the IDE.
And it does a _great_ job in that! :-)
> Using workspace
> resolution provided by m2eclipse you don't have to install or deploy
> anything while coding. So you don't really need to run mvn install in order
> to run your tests. Again, because m2eclipse made it transparent, using Run
> As... / JUnit in the IDE would give you the same results as running mvn test
> (assuming that you have up to date project configuration in the IDE). You
> don't really want to run "mvn install" every time you edited something in
> your IDE, but at the point you get to installing your stuff you should be
> secure that all tests would pass.
That is right. I see your point.
> All in all I'd say it wouldn't be a high priority for m2eclipse team to
> implement support showing surefire reports in junit view, but if someone
> would want to contribute such feature, we will be glad to accept the patch
> and will help implementing it.
Thank for the clarifying!
Regards,
--
Pedro Pedruzzi | V2COM
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
