MyEclipse Use Tutorial: Project migration Frequently Asked questions

What is a project migration and why is it needed?

In the MyEclipse 2013 release, we changed the metadata of most projects to extend the functionality of the IDE. In order for the old project to work properly in MyEclipse 2013 or later, it is necessary to migrate some of the old project's metadata to the new format, but not all projects need to be migrated.

In addition to the migration of project metadata, when working with projects under the WebSphere platform, allowing the runtime to be assigned to your project as appropriate during the migration will help to change the WebSphere version of the project. The Migration Wizard provides good help when you encounter errors during the migration process.

The migration process is not destructive, and migrated projects can be used in previous versions of MyEclipse. Of course, the changes made in the new version of MyEclipse will not appear in previous versions.

The Migration Wizard automatically displays the items that need to be migrated, but the migration is not mandatory. Project migration status is displayed in the workspace migration view. MyEclipse Previous versions included three different wizards, one for the old MyEclipse project, one for the Webtools project, and another for the RAD project. Starting with MyEclipse 2013, the migration process is simplified, using only a single Migration wizard and process. This will ensure that your project is ready, regardless of its origin.

What do I need to do after the project is migrated?

Although we have tried to consider the configuration of various aspects of the project, in some rare cases, there is no detection of a particular technology or the wrong framework version in the migration process. To ensure that all aspects of the project are properly migrated, you can check the Myeclipse>project Facets property page of the project.

MyEclipse 2013 has fully supported the deployment configuration and set it correctly as one of the migration actions for migrated projects in MyEclipse 10.x and later. You can check that the deployment components for your project are configured correctly, and for more information, see MyEclipse Deployment Configuration.

The target server is already configured, but it is not a visible target runtime

We continue to increase the number of connectors on the server to provide a target runtime. If your service connector does not provide a runtime, you can rest assured that the JEE Universal Runtime version is available to meet your project requirements.

MyEclipse and WebSphere Support: Migrating projects from MyEclipse 10.x, the deployment mode in the workspace does not work

In previous versions of MyEclipse, heuristics were used to determine which libraries should be deployed using the online workspace deployment pattern, starting with MyEclipse 2013 and the exact project structure described in the project expansion component configuration as the deployment pattern in the workspace. During the migration from previous versions of MyEclipse, deployment components were configured to reflect the archive structure of classic and enhanced deployments. Workspace mode in the archive structure on WebSphere will have additional restrictions, so you may need to adjust the configuration of the deployment components. The most common problem is that the class is loaded, and the module hierarchy required by the WebSphere workspace pattern follows the strict rules of JEE.

Project has one aspect of constraint errors

Some items may not be suitable for automatic migrations due to some configuration issues. The exact problem report in the Migration Wizard's problem report, it must resolve the migration process to continue. The usual problem is that the Java aspect of the version is incorrect, which prevents the problem from being automatically corrected during the migration process. It is recommended that you close the Migration Wizard and open the problematic project properties (right-click the project's Package explorer and select Properties from the menu). Navigate to the Myeclipse> Project facets page to correct the problem by changing the version or deletion. As a last resort, you can manually modify the configuration file, which is located under the. Settings folder and is named:org.eclipse.wst.common.project.facet.core.xml.

Note : the. Settings folder may not appear in the Package Explorer view; you need to disable. * Resources filter to see it. To do this, click the White triangle (View menu) in the upper-right corner of the Package Explorer view, then select Filter, then deselect. * Resources filter and click OK. Now you should be able to see the. settings file.

Unable to detect spring facet version

The correct version of spring support used in the project needs to be detected during the migration, and if the process fails, detection is based on the container version used by the project, which will be read from the. springbeans file. If the file is missing, the migration process cannot continue.

Before you invoke the Migration Wizard, you need to manually create the root directory of the project. To do this, right-click the project and select New > file from the menu, enter . Springbeans as the file name, and then click Finish. Open the. Springbeans in the file editor, paste the following code above and save the file.

1234567

<!--? XML version= " 1.0 "encoding= " UTF-8 "?--> <beansprojectdescription> <SPRINGVERSION> 2.0 </springversion> </beansprojectdescription>

You can now select Myeclipse>migrate Projects in the MyEclipse menu to rerun the migration process, or to run the migration process from the migration view.

Note : the. Settings folder may not appear in the Package Explorer view; you need to disable. * Resources filter to see it. To do this, click the White triangle (View menu) in the upper-right corner of the Package Explorer view, then select Filter, then deselect. * Resources filter and click OK. Now you should be able to see the. settings file.

my question is not mentioned.

If your question is not listed, please post it on our forum.

MyEclipse official Chinese online line, welcome to download Communication!

MyEclipse Use Tutorial: Project migration Frequently Asked questions