Bug 778864 (SOA-2636)

Summary:	Issues must be dealt with migrating from MM 5.5.x to Teiid Designer regarding refactoring of package names from com.metamatrix to org.teiid.designer
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	John Verhaeg <jverhaeg>
Component:	unspecified	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.1.0 GA	CC:	vhalbert
Target Milestone:	---
Target Release:	5.1.0 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2636
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-14 17:07:25 UTC	Type:	Component Upgrade
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	779590

Description John Verhaeg 2009-05-05 20:16:36 UTC

Affects: Compatibility/Configuration, Release Notes
project_key: SOA

1) Old model nature ID in .project files breaks the "Open existing" wizards and will in general prevent existing projects from being seen after upgrade.  We could either just modify to wizards to auto-modify the files on import and leave it up to the user to re-open/import their existing models, or we could write some startup code to auto-convert everything.  We probably want to do the former anyway, at least for one release.

Comment 1 Van Halbert 2010-02-16 16:29:00 UTC

Affects: Removed: [Release Notes, Compatibility/Configuration] Added: [Compatibility/Configuration, Release Notes]

Comment 2 Van Halbert 2010-02-19 21:18:02 UTC

Parent: Added: JBEDSP-1191

Comment 3 Anne-Louise Tangring 2010-12-06 19:08:56 UTC

This needs to be part of the migration information. KBase article is planned.

Comment 4 Van Halbert 2011-01-03 18:08:01 UTC

Link: Added: This issue depends TEIIDDES-701

Comment 5 Van Halbert 2011-01-03 18:08:02 UTC

The TEIIDDES jira is documenting the steps for importing MMX projects.

Comment 7 Dana Mison 2011-01-05 00:14:41 UTC

Writer: Added: dlesage

Comment 8 Van Halbert 2011-02-14 17:06:38 UTC

This problem is handled by following the instructions for importing a project set, which will be described in the migration document.   The user will be able to migrate their existing MMx projects to EDS.   See SOA-2496/