[
https://issues.jboss.org/browse/JBIDE-18741?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-18741.
---------------------------------
I checked that the missing classpath entries are now added (not only are they now included
in Default Set in preferences, but when I create a dynamic web project, they are included
in the classpath).
Rasto is right that those two (deploy.api and xml.registry.api) are not there (they are in
the default list, but not in the actual classpath when I create a project). But I guess
that's not an issue to have something extra there.
Verified in JBDS 8.0.1.CR1 B333.
Java EE 7 batch API missing from WildFly classpath container
------------------------------------------------------------
Key: JBIDE-18741
URL:
https://issues.jboss.org/browse/JBIDE-18741
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Final
Reporter: Valentin Baciu
Assignee: Rob Stryker
Fix For: 4.2.1.Final, 4.3.0.Alpha1
I recently upgraded to Eclipse Luna SR1 + JBoss Tools 4.2 and my workspace failed to
build properly.
It appears that the javax.batch API is missing from the WildFly classpath container. The
API is exposed by the javax.batch.api WildFly module
(jboss-batch-api_1.0_spec-1.0.0.Final.jar).
As a workaround, I had to add the module via Preferences->Server->Runtime
Environments->Default Classpath Entries.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)