Back to bug 781108
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Van Halbert | 2011-11-17 16:53:14 UTC | Assignee | jbpapp-maint | vhalbert |
| Van Halbert | 2011-11-17 16:56:55 UTC | Extra Versions | JBDS | |
| Len DiMaggio | 2011-11-29 18:35:38 UTC | Extra Versions | JBDS | |
| Van Halbert | 2011-12-13 13:36:32 UTC | Target Release | FUTURE | |
| Van Halbert | 2012-01-30 20:53:17 UTC | Group | devel | |
| CC | vhalbert | |||
| Van Halbert | 2012-09-04 13:29:44 UTC | Target Release | JBDS | |
| CC | soa-p-jira | |||
| Component | EDS | EDS | ||
| Version | 5.1.0 GA, 5.2.0.ER6 | 6.0 | ||
| Product | JBoss Enterprise SOA Platform 5 | JBoss Enterprise SOA Platform 6 | ||
| Van Halbert | 2013-02-06 22:28:58 UTC | Group | devel | |
| Target Release | FUTURE, JBDS | --- | ||
| Component | EDS | Tooling | ||
| Version | 6.0 | unspecified | ||
| Assignee | vhalbert | vhalbert | ||
| Product | JBoss Enterprise SOA Platform 6 | JBoss Data Services Platform 6 | ||
| Van Halbert | 2014-02-25 21:26:34 UTC | CC | belong | |
| Doc Text | It has been requested that users be able to manage multiple versions of models more effectively. | |||
| Doc Text | It has been requested that users be able to manage multiple versions of models more effectively. | It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | ||
| Doc Text | this feature will not be provided in Data Services 6. The current recommended approach to managing multiple model versions is to use a version control system. | |||
| Doc Text | It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | ||
| Doc Text | , this feature will not be provided in Data Services 6. The current recommended approach to managing multiple model versions is to use a version control system. | , this feature will not be provided in JBoss Data Virtualization 6. The current recommended approach to managing multiple model versions is to use a version control system. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Doc Text | It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | Enhancement Request: It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | ||
| Doc Text | , this feature will not be provided in JBoss Data Virtualization 6. The current recommended approach to managing multiple model versions is to use a version control system. | , this feature will not be provided in JBoss Data Virtualization 6. The current recommended approach to managing multiple model versions is to use a version control system. | ||
| Doc Type | Known Issue | Enhancement | ||
| Doc Text | Enhancement Request: It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | It has been requested that users be able to manage multiple versions of models more effectively. Due to other priorities | ||
| Doc Text | , this feature will not be provided in JBoss Data Virtualization 6. The current recommended approach to managing multiple model versions is to use a version control system. | , this feature will not be provided in JBoss Data Virtualization 6. The current recommended approach to managing multiple model versions is to use a version control system. | ||
| Status | NEW | CLOSED | ||
| Resolution | --- | WONTFIX | ||
| Last Closed | 2014-02-25 16:26:34 UTC |
Back to bug 781108