December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Darryl Miles edited comment on JBIDE-18860 at 12/2/14 6:42 AM: --------------------------------------------------------------- Version 1 of a sample set of 6 Maven projects: org.example.jbide18860.build/ Faceted:no org.example.jbide18860.ear/ Faceted:yes EAR:6 org.example.jbide18860.ejb/ Faceted:no org.example.jbide18860.jar/ Faceted:no org.example.jbide18860.parent/ Faceted:no org.example.jbide18860.war/ Faceted:yes (nothing set) I indicate the Eclipse faceted project dialog info as maybe it is relevant to the problem. I added projects to workspace with File -> Import -> Existing Maven Projects -> Select all 6 projects at once Did Maven -> Update Project on each project in turn. On org.eclipse.jbide18860.build do Run As -> Maven: install, to confirm success. Then manually inspect EAR in EAR project targets folder for correctness, this would be: <pre> $ unzip -lv org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear Archive: org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear Length Method Size Cmpr Date Time CRC-32 Name -------- ------ ------- ---- ---------- ----- -------- ---- 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/ 146 Defl:N 119 19% 12-02-2014 11:39 5249c220 META-INF/MANIFEST.MF 0 Stored 0 0% 12-02-2014 11:39 00000000 lib/ 3722 Defl:N 1855 50% 12-02-2014 11:39 9fd53ec2 lib/org-example-jbide18860-jar-0.0.1-SNAPSHOT.jar 29257 Defl:N 25597 13% 12-02-2014 11:39 0495bd31 lib/org-slf4j-slf4j-api-1.7.7.jar 632 Defl:N 308 51% 12-02-2014 11:39 991766b3 META-INF/application.xml 438 Defl:N 227 48% 12-02-2014 11:39 604fe086 META-INF/jboss-deployment-structure.xml 4978 Defl:N 2565 49% 12-02-2014 11:39 9ac1bc7b org-example-jbide18860-ejb-0.0.1-SNAPSHOT.jar 33646 Defl:N 31086 8% 12-02-2014 11:39 2c580520 org-example-jbide18860-war-0.0.1-SNAPSHOT.war 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/ 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/org.example.jbide18860/ 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/org.example.jbide18860/ear/ 2651 Defl:N 783 71% 12-02-2014 11:20 dd27064a META-INF/maven/org.example.jbide18860/ear/pom.xml 124 Defl:N 123 1% 12-02-2014 11:39 9c182c62 META-INF/maven/org.example.jbide18860/ear/pom.properties -------- ------- --- ------- 75594 62663 17% 14 files </pre> Import all projects into Eclipse workspace. Build the *.build project with maven using target verify (or better such as install/deploy) Example the *.ear/target/*.ear file and the contents. Deploy this file manually to the AS to confirm it is valid and works. Now try to use the server runtime, but add the EAR project as the module. The EJB and WAR projects do not make it into the wildfly-8.x.0.Final\standalone\deployments\*.ear\ folder for me. I would expect it to just work in that scenario. In the server runtime view for me there is only the JAR project listed underneath the EAR tree created. was (Author: dlmiles): Version 1 of a sample set of 6 Maven projects: org.example.jbide18860.build/ Faceted:no org.example.jbide18860.ear/ Faceted:yes EAR:6 org.example.jbide18860.ejb/ Faceted:no org.example.jbide18860.jar/ Faceted:no org.example.jbide18860.parent/ Faceted:no org.example.jbide18860.war/ Faceted:yes (nothing set) I indicate the Eclipse faceted project dialog info as maybe it is relevant to the problem. I added projects to workspace with File -> Import -> Existing Maven Projects -> Select all 6 projects at once Did Maven -> Update Project on each project in turn. On org.eclipse.jbide18860.build do Run As -> Maven: install, to confirm success. Then manually inspect EAR in EAR project targets folder for correctness, this would be: $ unzip -lv org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear Archive: org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear Length Method Size Cmpr Date Time CRC-32 Name -------- ------ ------- ---- ---------- ----- -------- ---- 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/ 146 Defl:N 119 19% 12-02-2014 11:39 5249c220 META-INF/MANIFEST.MF 0 Stored 0 0% 12-02-2014 11:39 00000000 lib/ 3722 Defl:N 1855 50% 12-02-2014 11:39 9fd53ec2 lib/org-example-jbide18860-jar-0.0.1-SNAPSHOT.jar 29257 Defl:N 25597 13% 12-02-2014 11:39 0495bd31 lib/org-slf4j-slf4j-api-1.7.7.jar 632 Defl:N 308 51% 12-02-2014 11:39 991766b3 META-INF/application.xml 438 Defl:N 227 48% 12-02-2014 11:39 604fe086 META-INF/jboss-deployment-structure.xml 4978 Defl:N 2565 49% 12-02-2014 11:39 9ac1bc7b org-example-jbide18860-ejb-0.0.1-SNAPSHOT.jar 33646 Defl:N 31086 8% 12-02-2014 11:39 2c580520 org-example-jbide18860-war-0.0.1-SNAPSHOT.war 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/ 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/org.example.jbide18860/ 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/org.example.jbide18860/ear/ 2651 Defl:N 783 71% 12-02-2014 11:20 dd27064a META-INF/maven/org.example.jbide18860/ear/pom.xml 124 Defl:N 123 1% 12-02-2014 11:39 9c182c62 META-INF/maven/org.example.jbide18860/ear/pom.properties -------- ------- --- ------- 75594 62663 17% 14 files Import all projects into Eclipse workspace. Build the *.build project with maven using target verify (or better such as install/deploy) Example the *.ear/target/*.ear file and the contents. Deploy this file manually to the AS to confirm it is valid and works. Now try to use the server runtime, but add the EAR project as the module. The EJB and WAR projects do not make it into the wildfly-8.x.0.Final\standalone\deployments\*.ear\ folder for me. I would expect it to just work in that scenario. In the server runtime view for me there is only the JAR project listed underneath the EAR tree created. > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Darryl Miles updated JBIDE-18860: --------------------------------- Attachment: org.example.jbide18860.tar.gz Version 1 of a sample set of 6 Maven projects: org.example.jbide18860.build/ Faceted:no org.example.jbide18860.ear/ Faceted:yes EAR:6 org.example.jbide18860.ejb/ Faceted:no org.example.jbide18860.jar/ Faceted:no org.example.jbide18860.parent/ Faceted:no org.example.jbide18860.war/ Faceted:yes (nothing set) I indicate the Eclipse faceted project dialog info as maybe it is relevant to the problem. I added projects to workspace with File -> Import -> Existing Maven Projects -> Select all 6 projects at once Did Maven -> Update Project on each project in turn. On org.eclipse.jbide18860.build do Run As -> Maven: install, to confirm success. Then manually inspect EAR in EAR project targets folder for correctness, this would be: $ unzip -lv org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear Archive: org.example.jbide18860.ear/target/ear-0.0.1-SNAPSHOT.ear Length Method Size Cmpr Date Time CRC-32 Name -------- ------ ------- ---- ---------- ----- -------- ---- 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/ 146 Defl:N 119 19% 12-02-2014 11:39 5249c220 META-INF/MANIFEST.MF 0 Stored 0 0% 12-02-2014 11:39 00000000 lib/ 3722 Defl:N 1855 50% 12-02-2014 11:39 9fd53ec2 lib/org-example-jbide18860-jar-0.0.1-SNAPSHOT.jar 29257 Defl:N 25597 13% 12-02-2014 11:39 0495bd31 lib/org-slf4j-slf4j-api-1.7.7.jar 632 Defl:N 308 51% 12-02-2014 11:39 991766b3 META-INF/application.xml 438 Defl:N 227 48% 12-02-2014 11:39 604fe086 META-INF/jboss-deployment-structure.xml 4978 Defl:N 2565 49% 12-02-2014 11:39 9ac1bc7b org-example-jbide18860-ejb-0.0.1-SNAPSHOT.jar 33646 Defl:N 31086 8% 12-02-2014 11:39 2c580520 org-example-jbide18860-war-0.0.1-SNAPSHOT.war 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/ 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/org.example.jbide18860/ 0 Stored 0 0% 12-02-2014 11:39 00000000 META-INF/maven/org.example.jbide18860/ear/ 2651 Defl:N 783 71% 12-02-2014 11:20 dd27064a META-INF/maven/org.example.jbide18860/ear/pom.xml 124 Defl:N 123 1% 12-02-2014 11:39 9c182c62 META-INF/maven/org.example.jbide18860/ear/pom.properties -------- ------- --- ------- 75594 62663 17% 14 files Import all projects into Eclipse workspace. Build the *.build project with maven using target verify (or better such as install/deploy) Example the *.ear/target/*.ear file and the contents. Deploy this file manually to the AS to confirm it is valid and works. Now try to use the server runtime, but add the EAR project as the module. The EJB and WAR projects do not make it into the wildfly-8.x.0.Final\standalone\deployments\*.ear\ folder for me. I would expect it to just work in that scenario. In the server runtime view for me there is only the JAR project listed underneath the EAR tree created. > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18862: --------------------------------------------- these files are maintained by wildfly not us. we just put .dodeploy and it should definitely not start deploing a .ear before it is fully written. That was a "bug" of previous AS's, since AS7 and wf that is not happening so let us know what error you are seeing ? > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Priority: Minor > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Darryl Miles (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18862?page=com.atlassian.jira.plugi... ] Darryl Miles updated JBIDE-18862: --------------------------------- Description: module removal does not delete the various marker files relating to it: *.undeployed *.dodeploy The same should be true when ADDING a module, it should clean out any marker files. Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. Write out the*.ear file. Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). was: module removal does not delete the various marker files relating to it: *.undeployed *.dodeploy The same should be true when ADDING a module, it should clean out any marker files. Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. write out the*.ear file, adjust the marker files a necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). > when removing a module from AS runtime marker files are not removed automatically > --------------------------------------------------------------------------------- > > Key: JBIDE-18862 > URL: https://issues.jboss.org/browse/JBIDE-18862 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Windiws7 64bit, JDK 8u25 > Reporter: Darryl Miles > Priority: Minor > > module removal does not delete the various marker files relating to it: > *.undeployed > *.dodeploy > The same should be true when ADDING a module, it should clean out any marker files. > Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. > Write out the*.ear file. > Then adjust the marker files as necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18862) when removing a module from AS runtime marker files are not removed automatically

by Darryl Miles (JIRA)

Darryl Miles created JBIDE-18862: ------------------------------------ Summary: when removing a module from AS runtime marker files are not removed automatically Key: JBIDE-18862 URL: https://issues.jboss.org/browse/JBIDE-18862 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Environment: Windiws7 64bit, JDK 8u25 Reporter: Darryl Miles Priority: Minor module removal does not delete the various marker files relating to it: *.undeployed *.dodeploy The same should be true when ADDING a module, it should clean out any marker files. Setup an deploy-inhibiting marker file to ensure it won't try to deploy it before the *.ear is full written. write out the*.ear file, adjust the marker files a necessary to reflect the intended state of the module (if it should be started then remove the inhibiting marker file in the previous step). -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18861) module start action does not delete *.undeployed file

by Darryl Miles (JIRA)

Darryl Miles created JBIDE-18861: ------------------------------------ Summary: module start action does not delete *.undeployed file Key: JBIDE-18861 URL: https://issues.jboss.org/browse/JBIDE-18861 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Environment: Windows7 64bit, JDK 8u25 Reporter: Darryl Miles Priority: Minor If you start Wildfly with all modules enabled and started. Now use STOP action on an EAR module. Now stop Wildfly. Now start Wildfly (debug or run). It will start up without the EAR module running, this is correct behavior at this point. Now use START on EAR module. It fails to start at all. This is because the file *.undeployed still exists. If you manually remove the file (using system file manager) the module will start up. If you perform a "full publish" on the module that appears to cause it to start up as well. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15383. --------------------------------- I checked that custom entries are properly persisted - they do not disappear. And the revert button works as expected. Closing. Verified in JBDS 8.0.1.CR1 B333. > Server Launch Configuration loses Classpath User Entries > -------------------------------------------------------- > > Key: JBIDE-15383 > URL: https://issues.jboss.org/browse/JBIDE-15383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: JBIDE_1.png, JBIDE_2.png, JBIDE_3.png > > > Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. > This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. > Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". > The attachments describe what happens: > * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. > * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). > * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. > * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. > I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. > I've been able to replicate this on two separate (similarly configured) machines. > This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new issue. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16580) jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16580?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-16580. --------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.Beta1) Resolution: Done marking as closed! missed in query for bulk update ;/ > jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16580 > URL: https://issues.jboss.org/browse/JBIDE-16580 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16580) jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16580?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16580: ---------------------------------------- Epic Status: Done (was: To Do) > jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16580 > URL: https://issues.jboss.org/browse/JBIDE-16580 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18741) Java EE 7 batch API missing from WildFly classpath container

by Martin Malina (JIRA)

[ 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)

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014