[JBoss JIRA] Created: (JBIDE-5102) Renaming ESB / BPEL project does not change deploy-name in plugin.xml
by Rob Stryker (JIRA)
Renaming ESB / BPEL project does not change deploy-name in plugin.xml
---------------------------------------------------------------------
Key: JBIDE-5102
URL: https://jira.jboss.org/jira/browse/JBIDE-5102
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.M3
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.1.0.CR1
This is related to JBIDE-2887, where there'd be an IllegalArgumentExcepton when renaming an ESB project.
The fix to that bug was to limit the refactor listener to only work on WTP projects (for maintenance release no larger changes could be made). This means that our projects do not benefit from the functionality contained therein, such as automatic removal of the old module from the server and addition of the new.
--
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, 9 months
- 2
- 9
[JBoss JIRA] Created: (JBIDE-5373) Added Server Runtime Environment changes don't reflect cancellation
by Jiri Peterka (JIRA)
Added Server Runtime Environment changes don't reflect cancellation
-------------------------------------------------------------------
Key: JBIDE-5373
URL: https://jira.jboss.org/jira/browse/JBIDE-5373
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.M4
Environment: JBT 3.1.M4, JBDS 3.1.1
Linux 64
Reporter: Jiri Peterka
Added Server Runtime Environment changes don't reflect cancellation
Steps to reproduce:
1. Windows -> Preferences
2. Server -> Runtime Environments
3. Add any new Runtime
4. After runtime is added into the server runtime environments list, Click Cancel
5. After checking Server runtimes, Cancel operation is't took into account.
Compare with adding JDK behaviour in Installed JREs.
--
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, 9 months
- 3
- 9
[JBoss JIRA] Created: (JBIDE-5938) java.lang.NullPointerException is occured after creating Seam 2.2 project in clean workspace.
by Anton Klimkovich (JIRA)
java.lang.NullPointerException is occured after creating Seam 2.2 project in clean workspace.
---------------------------------------------------------------------------------------------
Key: JBIDE-5938
URL: https://jira.jboss.org/jira/browse/JBIDE-5938
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.1.0.CR2
Environment: jbdevstudio-eap-win32-3.0.0.v201002232140M-H180-CR2
Reporter: Anton Klimkovich
Assignee: Alexey Kazakov
EXECUTE: install build jbdevstudio-eap-win32-3.0.0.v201002232140M-H180-CR2
EXECUTE: Create seam 2.2 War project
FAILURE: java.lang.NullPointerException is occured after creating Seam 2.2 project in clean workspace.
Exception is occured rarely. I can't stable reproduce it.
java.lang.NullPointerException
at org.eclipse.wst.server.core.internal.Server.isModuleDeployed(Server.java:783)
at org.eclipse.wst.server.core.internal.Server.handleModuleProjectChange(Server.java:754)
at org.eclipse.wst.server.core.internal.ResourceManager.publishHandleProjectChange(ResourceManager.java:977)
at org.eclipse.wst.server.core.internal.ResourceManager$ServerResourceChangeListener$1.visit(ResourceManager.java:122)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:79)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48)
at org.eclipse.wst.server.core.internal.ResourceManager$ServerResourceChangeListener.resourceChanged(ResourceManager.java:116)
at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastBuildEvent(Workspace.java:297)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:532)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1782)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:502)
at org.eclipse.core.internal.resources.Project.build(Project.java:94)
at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.buildProjects(SeamProjectWizard.java:477)
at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:394)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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, 9 months
- 3
- 8