[JBoss JIRA] Created: (JBIDE-5931) Renamaing deployed project on running server results in the project to be deployed twice
5:22 a.m.
Renamaing deployed project on running server results in the project to be deployed twice
----------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
5:26 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5931) Renamaing deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-5931:
--------------------------------------------
hmm....this should be an refactor listener I guess that allow users to undeploy the
original one.
But I have a feeling this would be better done at the WTP level, not by us.
Renamaing deployed project on running server results in the project
to be deployed twice
----------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
5:30 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5931) Renamaing deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen updated JBIDE-5931:
---------------------------------------
Fix Version/s: 3.2.next
Renamaing deployed project on running server results in the project
to be deployed twice
----------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
6 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Dominik Pospisil updated JBIDE-5931:
------------------------------------
Summary: Renaming deployed project on running server results in the project to be
deployed twice (was: Renamaing deployed project on running server results in the project
to be deployed twice)
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
4:13 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5931:
------------------------------------
Interestingly, this is an expected use case in WTP nad they have project refactor
listeners ot handle this.
However, a quick trace reveals... (... ... ...) that they don't work all that great
;)
I'll get to testing nad patching I guess
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
5:37 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5931:
------------------------------------
It seems in the seam case, we have two modules deployed to the server (one is the
datasource, the other is the project).
The refactor listeners are grabbing the first one in the list and undeploying it. It is
not undeploying *all* modules from the previous project.
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
5:39 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Rob Stryker updated JBIDE-5931:
-------------------------------
Component/s: UpStream
marking as upstream
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, UpStream
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
6:53 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Rob Stryker commented on JBIDE-5931:
------------------------------------
https://bugs.eclipse.org/bugs/show_bug.cgi?id=304347
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, UpStream
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
1:40 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://jira.jboss.org/jira/browse/JBIDE-5931?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-5931.
--------------------------------
Fix Version/s: 3.6-Helios
Resolution: Done
This is done upstream
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://jira.jboss.org/jira/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, UpStream
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.next, 3.6-Helios
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
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
6:49 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-5931) Renaming deployed project on running server results in the project to be deployed twice
[
https://issues.jboss.org/browse/JBIDE-5931?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-5931:
---------------------------------
Fix Version/s: (was: 3.2.x)
Renaming deployed project on running server results in the project to
be deployed twice
---------------------------------------------------------------------------------------
Key: JBIDE-5931
URL: https://issues.jboss.org/browse/JBIDE-5931
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, UpStream
Affects Versions: 3.1.0.CR2
Reporter: Dominik Pospisil
Assignee: Rob Stryker
Fix For: 3.2.0.M1
When a user renames a project deployed on running server, the project remains deployed
using original name and an attempt to deploy using new name is made. The project should be
undeployed first. If the project contains named resources (datasources, queues, ws...) the
second deployment fails.
1) Create Dynamic web project
2) Run the project on server
3) Choose Refactor -> Rename on the project
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5531
days inactive
5888
days old
jbosstools-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Denis Golovin (JIRA) -
Dominik Pospisil (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)