Would be good to know if its because of tycho 0.14....they do have their own custom
surefire fork to deal with p2/osgi launches which
they have aligned more and more with the original surefire....but I thought they always
ran default with showing the stacktrace too.
if it doesnt happen in branch for you but only in trunk - then yeah its most likely tycho
0.14 unless some other setting was changed in parent -
but on my first look I cant see it.
Guess its time to try and get mvn build running on my machine again now that I got my
harddrive back ;)
/max
Thanks, Nick, Max,
I think it's related to new Tycho 0.14.1 (didn't see this problem before
trunk had migrated to Tycho 0.14.1) I will double check it and report
this to upstream.
On 03/07/2012 10:22 PM, Nick Boldt wrote:
> -e -fae flags SHOULD do the trick, but trunk uses Tycho 0.14.1 instead
> of 0.13.0, so maybe they broke the implementation of the log? Can you
> report this to upstream?
>
>
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Tycho
>
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;classific...
>
>
> On 03/08/2012 12:58 AM, Alexey Kazakov wrote:
>> I'm talking about local builds. Not hudson.
>> And I do run it with the -e flag.
>> For example:
>> mvn clean install -fae -e -P default -f cdi/tests/pom.xml
>> I will take a look at .log file in target folder but anyway it would be
>> much more useful to get a stacktrace in console as we had before.
>>
>> On 03/07/2012 09:26 PM, Nick Boldt wrote:
>>> Builds should be running with the -e flag so that when they fail you
>>> get a stacktrace. Failing that, check the console .log for the eclipse
>>> instance running the test, for example:
>>>
>>>
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
>>>
>>>
>>>
>>> (or more generically...)
>>>
>>>
https://hudson.qa.jboss.com/hudson/job/{jobname}/ws/sources/tests/{testcl...
>>>
>>>
>>>
>>> Going forward, we plan to archive these log files so they persist
>>> longer in Jenkins between builds. See
>>>
https://issues.jboss.org/browse/JBDS-2031.
>>>
>>> N
>>>
>>> On 03/07/2012 08:33 PM, Alexey Kazakov wrote:
>>>> Hi Nick,
>>>> There is no stacktrace anymore when tests are failed in tycho build.
>>>> Just a short message like: Test failure: testNNN(org.jboss.NNN): some
>>>> test message.
>>>> Stacktrace was very useful there. Can we get it back somehow?
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev