[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3537) Changing runtime name leaves projects, servers with stale references
Rob Stryker (JIRA)
jira-events at lists.jboss.org
Mon Jan 26 22:57:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBIDE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Stryker updated JBIDE-3537:
-------------------------------
Fix Version/s: LATER
(was: 3.0.1.GA)
Since this has been the way WTP has worked since 1.0, it's not a huge priority right now. If I trim my JIRA list down I'll try to come up with a patch for upstream and if they take too long I'll try to put it in our code as well.
Marked as later.
> Changing runtime name leaves projects, servers with stale references
> --------------------------------------------------------------------
>
> Key: JBIDE-3537
> URL: https://jira.jboss.org/jira/browse/JBIDE-3537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS, UpStream
> Affects Versions: 3.0.0.cr1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: LATER
>
>
> Changing a runtime's name also changes its ID. Changing a runtime's ID leaves projects and servers that reference it with stale references and leads to compile errors in projects or servers that can't start.
--
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
More information about the jbosstools-issues
mailing list