[JBoss JIRA] Created: (JBIDE-6249) Error when adding JBoss EJB Libraries to project
by Kip Moore (JIRA)
Error when adding JBoss EJB Libraries to project
------------------------------------------------
Key: JBIDE-6249
URL: https://jira.jboss.org/jira/browse/JBIDE-6249
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: ejb3
Affects Versions: 3.1.x
Environment: Eclipse 3.5.2
Reporter: Kip Moore
I'm having trouble adding JBoss EJB 3 libraries to an existing project.
I have downloaded a fresh version of Eclipse 3.5.2, and successfully used the built in "Install" wizard to download and install JBossTools 3.1.0GA. For the sake of troubleshooting, I have created a brand-new Java Project in the IDE. I have also sucessfully created three different Servers, one each for installations of JBoss 4.2.2, JBoss 5.1, and JBoss 6.0M2 that I am currently working with.
So I go ahead and enter the project Properties, select "Java Build Path", and then go to the "Libraries" tab. I click on the "Add Library..." button, select "JBoss EJB3 Libraries", then "Next...", select any one of the declared Servers, and hit "Finish", which brings up the following error:
"The selected configuration <JBoss server> does not contain the expected EJB3 libraries. Please install JBoss with EJB3 enabled, or try another configuration."
I get this error regardless of which server I have selected. Using an existing EJB3 project, I have also verified that EJB3 is indeed installed and working properly across all 3 servers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6233) Cannot compile org.jboss.tools.ui.bot.ext
by Nick Boldt (JIRA)
Cannot compile org.jboss.tools.ui.bot.ext
-----------------------------------------
Key: JBIDE-6233
URL: https://jira.jboss.org/jira/browse/JBIDE-6233
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing
Affects Versions: 3.2.next
Reporter: Nick Boldt
Assignee: Dominik Pospisil
Is this a coding error? A change in SWTBot? Something I need to help you fix? Does it work locally?
[java] [javac] 211. ERROR in /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.2.next/jbds-build/eclipse/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/config/requirement/ClearWorkspace.java (at line 23)
[java] [javac] SWTTestExt.bot.closeAllShells();
[java] [javac] ^^^^^^^^^^^^^^
[java] [javac] The method closeAllShells() is undefined for the type SWTBotExt
[java] [javac] ----------
[java] [javac] 212. ERROR in /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.2.next/jbds-build/eclipse/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/config/requirement/ClearWorkspace.java (at line 24)
[java] [javac] SWTTestExt.bot.closeAllEditors();
[java] [javac] ^^^^^^^^^^^^^^^
[java] [javac] The method closeAllEditors() is undefined for the type SWTBotExt
http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.2.next/171/con...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBDS-1177) .metadata deploy issues
by Brice Ruth (JIRA)
.metadata deploy issues
-----------------------
Key: JBDS-1177
URL: https://jira.jboss.org/jira/browse/JBDS-1177
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Environment: WinXP SP2, jdk1.5.0_13, eclipse-jee-galileo-sr2, jboss_tools 3.1 final, m2e 0.10
Reporter: Brice Ruth
>From #JbossTools on IRC:
[11:07] <bruth> Another issue: apparently when I change from the default of deploying to .metadata to using the JBoss deploy/ folder, two things don't happen, (1) the files aren't cleaned out from .metadata and (2) the references that tell the JBoss instance to deploy things in the .metadata folder aren't removed, so JBoss starts, deploys from deploy/ then also tries to deploy from .metadata, generating all sorts of duplicate MBean errors
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6102) Server deployment status synchronization improvements
by Dominik Pospisil (JIRA)
Server deployment status synchronization improvements
-----------------------------------------------------
Key: JBIDE-6102
URL: https://jira.jboss.org/jira/browse/JBIDE-6102
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
I can see couple of ways how the project deployment status could be improved.
1) Currently, project deployment status could get easily out of sync.
Once the JBT successfully initiates project deployment, it always assumes that the deployment was successful. JBT does not detect deployment failures and If something went wrong it gets out of sync. JBT should check deployment result.
Also, when a project is manually undeployed / deployed from the server the change is not picked up by JBT.
2) The server view only displays deployments managed by JBT within current workspace. It would be nice if the user has an overview of projects/applications/resources deployed in different workspaces or externally. It would be really handy e.g. when a user often switches workspaces, deploy various project in different workspaces. It could prevent a user of being confused what actually is or is not deployed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months