[
https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi...
]
Rastislav Wagner commented on JBIDE-17696:
------------------------------------------
[~snjeza] [~dgolovin]
Yes, this was an automated reddeer UI test. But I just tried manually and i was able to
reproduce 2 times. My steps were:
1. I've added runtime (this time it was wildfly 8)
2. than I created 10-15 different projects ie.
- dynamic web project with runtime, which i converted to maven project and skipped
dependency conversion
- dynamic web project without runtime, converted to maven, added cdi-api 1.0
- dynamic web project without runtime, converted to maven, added cdi-api 1.1
- ejb project with runtime, converted to maven, skipped dependency conversion
- ejb project without runtime, converted to maven, with cdi-api 1.0 or 1.1
- dynamic web project, without runtime, added persistence.xml, converted to maven (or
convert to maven, then add persistence.xml)
3. In both cases (always with clean new workspace) I hit this issue after creating dynamic
web project, without runtime, added persistence.xml and then i tried to convert it to
maven project. Maybe it was just a coincidence - i know that its happening randomly also
for other projects - but you always have to create some projects before (step n.2). Sorry,
I have no particular number, I'm always trying until I see the waiting job..
This is not happening only on my machine. Im running automated tests on jenkins slaves and
i can see this issue also on windows (64bit, xp)
Im attaching JVM thread dumps and screenshots again.
Enabling Maven Dependency Management job waits forever
------------------------------------------------------
Key: JBIDE-17696
URL:
https://issues.jboss.org/browse/JBIDE-17696
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.2.0.Beta2
Environment: OpenJDK 1.7, 64b
Ubuntu 12.04, 64b
Reporter: Rastislav Wagner
Attachments: jstack_mvn.out, mvn.png
I dont have exact steps to reproduce because this usually occurs after longer work.
I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
1. Create Dynamic Web Project
2. Convert to maven project (using Configure -> Convert to maven..)
3. Add some dependency
4. check if proper facet was enabled
5. delete project and repeat
After trying this 10-15 times (sometimes more, sometimes less), during step 2
"Enabling Maven Dependency Management" job is waiting and never ends - see
screenshot - there's always "Setting classpath containers".
JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)