[
https://issues.jboss.org/browse/JBIDE-18741?page=com.atlassian.jira.plugi...
]
Valentin Baciu updated JBIDE-18741:
-----------------------------------
Description:
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.
was:
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 class path 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.
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
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)