[
https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi...
]
Fred Bricon resolved JBIDE-18128.
---------------------------------
Fix Version/s: 4.2.2.Final
(was: 4.3.x)
Resolution: Rejected
After discussing with Federico, it turns out the issue was caused by external Maven clean
builds deleting the classes causing workspace desynchronisation.
The workspace didn't see the classes until a refresh was triggered, meaning the server
adapter had no classes to deploy.
In order to avoid this problem in the future, one can either :
1 - not perform external Maven builds while Eclipse is running
2 - Manually refresh the projects' target folder once a CLI build has been performed.
3 - Go to Preferences > General > Workspace and enable "Refresh using native
hooks or polling". Not that it can potentially cause endless loop builds within
Eclipse. If that happens, then fall back to option #2
JBoss Tools 4.2 (for Luna) doesn't deploy all .class
----------------------------------------------------
Key: JBIDE-18128
URL:
https://issues.jboss.org/browse/JBIDE-18128
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven, server
Affects Versions: 4.2.0.Beta3
Reporter: fede pia
Assignee: Fred Bricon
Fix For: 4.2.2.Final
Attachments: 2014-09-04 error.png, 2014-09-04 output.txt,
integration-wildfly-branch.zip, jboss-test.zip, TestJboss-2014-09-03.zip
The problem I'm facing is that when I run/debug my aplication from Server view in
Eclipse the jboss plugin doesn't deploy all the .class files, thus I get
ClassNotFoundException.
I've tried cleaning the project, cleaning jboss, remove temporaries but nothing
works. The not found classes are random.
For Eclipse 4.3 everything works fine, although this issue usually happens but I can
solve it with a Project -> Clean
As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools
plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I
tested were JBoss 7.1 and Wildfly 8.1.
I also tried building the war outside Eclipse and deployed manually to JBoss and
everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)