Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Migrated to another ITS
    • Affects Version/s: 3.3.0.Beta3
    • Fix Version/s: LATER
    • Component/s: build, upstream
    • Labels:
      None

      Description

      If I run JBT tycho build locally for trunk, for example:
      mvn clean install -fae -e -P default -f cdi/tests/pom.xml
      and there is some test failures then I don't see any stacktrace in console. Just a text message from the JUnit test assert.
      -Dsurefire.useFile=false does not help.
      But I see the stacktrace in <target>/surefire-reports

      In Beta1 branch it works fine.

      I don't see stacktrace in console output in Hudson either but I'm not sure it's a problem there.
      For example https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--cdi/lastCompletedBuild/console
      But for local builds it's very useful to see the full stacktrace in console.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  mickael_istria Mickael Istria
                  Reporter:
                  akazakov Alexey Kazakov
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: