5:12 p.m.
Alexey Kazakov created JBIDE-11301:
--------------------------------------
Summary: no stacktrace when junit tests fail
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 p.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Alexey Kazakov updated JBIDE-11301:
-----------------------------------
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
was:
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.
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:22 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11301:
----------------------------------------
You can see a stacktrace for the failing test here:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
Is this what you are looking for?
Also, have you looked into the .log file?
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Alexey Kazakov
Assignee: Mickael Istria
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-11301:
----------------------------------------
Yes, I can find a stacktrace in Hudson in result page and I even can find this stacktrace
in <plugin>/<target>/surefire-reports folder (see the description of this
issue) but I can't see it in console output when I running the build *locally*.
It's very easy to reproduce:
1. Open org.jboss.tools.cdi.core.test.CDIImagesTest
2. Add the following method
{code}
public void testFoo() {
fail("You should see a stacktrace here");
}
{code}
3. mvn clean install -fae -e -P default -f
cdi/tests/org.jboss.tools.cdi.core.test/pom.xml
4. There is no stacktrace for testFoo() in console output (*that's the problem!*). But
you can find it in cdi/tests/org.jboss.tools.cdi.core.test/target/surefire-reports/*
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Alexey Kazakov
Assignee: Mickael Istria
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11301:
----------------------------------------
Ok,
I guess surefire-plugin was updated to not show stack trance in console in order to
prevent from huge outputs. There might be an option for it, I'll investigate. If you
find the magic option before me, please share it.
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta2
Reporter: Alexey Kazakov
Assignee: Mickael Istria
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11301:
---------------------------------------------
googling says "mvn -Dsurefire.useFile=false test"
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:58 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11301:
----------------------------------------
there may be an issue in tycho-surefire-plugin that does not honor this property any
more.
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11301:
---------------------------------------------
relevant comment in tycho git repo:
" 367778 TestMojo: don't redirect console to file by default
Revert to old default behaviour which prints console
logs from tests to System.out by default.
Make test output redirection to file configurable
using TestMojo parameter "redirectTestOutputToFile",
same as maven-surefire-plugin, see [1]
[1]
http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#redi...
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11301:
----------------------------------------
Fix Version/s: 3.3.x
Priority: Minor (was: Major)
Component/s: UpStream
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11301:
---------------------------------------------
on plane right now and missing dependencies so can't test this but in tychosurefire
code is looks like useFile is hardcoded to true but there is a
"redirectTestOutputToFile" that might be worth trying.
definitely should try get this fixed in tycho if still the case.
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11301:
----------------------------------------
Alexey,
When I look at this build:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
I see the following
{code}
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.cdi.core.test.CDICoreAllTests
Exception in thread "Thread-6" java.lang.NullPointerException
at org.jboss.tools.common.java.ParametedType.findParameter(ParametedType.java:302)
at
org.jboss.tools.common.java.ParametedTypeFactory.getParametedType(ParametedTypeFactory.java:85)
at org.jboss.tools.common.java.ParametedType.buildInheritance(ParametedType.java:183)
at org.jboss.tools.common.java.ParametedType.getInheritedTypes(ParametedType.java:229)
at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:319)
at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
at org.jboss.tools.common.java.ParametedType.buildAllTypes(ParametedType.java:321)
at org.jboss.tools.common.java.ParametedType.getAllTypes(ParametedType.java:307)
at org.jboss.tools.cdi.core.test.TypeTest$R.run(TypeTest.java:76)
at java.lang.Thread.run(Thread.java:662)
Running Update class path of kb project RemoveJarTest
Running Update class path of kb project RemoveJarTest
2
void addEntry(Object) [in ClassFragmentLogger [in ClassFragmentLogger.java [in
org.jboss.jsr299.tck.tests.jbt.validation.observers [in JavaSource [in tck]]]]]
void observeObject(Object) [in EventTypeFamilyObserver [in EventTypeFamilyObserver.java
[in org.jboss.jsr299.tck.tests.event.eventTypes [in JavaSource [in tck]]]]]
Tests run: 432, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 288.383 sec <<<
FAILURE!
Results :
Failed tests: testType(org.jboss.tools.cdi.core.test.TypeTest): expected:<11> but
was:<0>
Tests run: 432, Failures: 1, Errors: 0, Skipped: 0
{code}
Does this output mean this issue is fixed or do you expect more?
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:48 p.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Alexey Kazakov commented on JBIDE-11301:
----------------------------------------
I'm not sure.
This is not an AssertionFailedError which is usually thrown by assert() or fail() in
tests.
Anyway I just ran our tests locally and still don't see the stacktrace in console. But
maybe it works in Hudson?
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 p.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich commented on JBIDE-11301:
-----------------------------------------------
Alexey, as you suggested, method ParametedType.findParameter is not thread safe. I have
committed the fix.
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 a.m.
[
https://issues.jboss.org/browse/JBIDE-11301?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11301:
----------------------------------------
Highly related:
http://dev.eclipse.org/mhonarc/lists/tycho-user/msg02465.html
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378938
no stacktrace when junit tests fail
-----------------------------------
Key: JBIDE-11301
URL: https://issues.jboss.org/browse/JBIDE-11301
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, UpStream
Affects Versions: 3.3.0.Beta3
Reporter: Alexey Kazakov
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.x
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/jo...
But for local builds it's very useful to see the full stacktrace in console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5086
days inactive
5143
days old
jbosstools-issues@lists.jboss.org
13 comments
4 participants
participants (4)
-
Alexey Kazakov (JIRA) -
Max Rydahl Andersen (JIRA)
-
Mickael Istria (JIRA)
-
Viacheslav Kabanovich (JIRA)