MyEclipse: Changes Starting in 2013
Most projects created in older versions of MyEclipse will need to be migrated to work in 2013 and higher.
Since the release of MyEclipse 9, we've asked users to migrate projects created in older versions of MyEclipse to take advantage of newer features. Starting with MyEclipse 2013, instead of having multiple migration wizards (prior we had three, based on where your project was coming from), we have a single wizard with a single intelligent migration process. This will ensure that your project works fine in 2013 or higher, whether it is one you are migrating from a prior version of MyEclipse, from IBM's RAD or from the Eclipse Web Tools project.
In addition to simply migrating project metadata, the migration process allows you to assign runtimes to your project where applicable (more on runtimes later) or even help change the WebSphere version your project is targeted to, when dealing with WebSphere projects in MyEclipse with WebSphere support. Errors encountered during migration are better communicated in the migration wizard.
The migration process is not destructive and migrated projects will continue to work in prior versions of MyEclipse; changes made in 2013 or higher will not appear in prior versions, of course. In some cases, projects may not even require migration and will work out of the box with MyEclipse 2013 or higher.
The migration wizard is displayed automatically for projects requiring migration, but migration is not forced. The migration status of projects is displayed in the Project Migration view from which projects can also be manually migrated.
There were several changes in the project management area beginning in 2013.
In MyEclipse 2013, we improved our framework container support significantly. Instead of adding dozens of containers to your project to support a given framework, we add only a single configurable container. Besides being customizable globally, these containers can also be customized at a project level.
- The older project containers no longer function in MyEclipse 2013 or higher - conversion from the older containers to the newer containers is handled by the migration process; you must migrate your projects for libraries to become available.
The older containers are not removed from the project's metadata so they will continue to function if the same project is opened in MyEclipse 10.x or below.
- If you have customized MyEclipse project containers, these customizations are migrated to the newer containers only if you open the same workspace with MyEclipse 2013 or higher (these customizations are stored at the workspace level).
Only additions to the containers will be picked up. If you removed JARs from the containers, these JARs need to be removed from the newer containers manually.
Eclipse library support for some projects allows you to download external libraries seamlessly for use alongside those provided by MyEclipse.
Starting with MyEclipse 2013, the project creation wizards allow you to assign target runtimes to your projects. You can also assign target runtimes to existing projects from the MyEclipse>Targeted Runtimes property page.
Runtimes represent your project's intended deployment environment. Target runtimes can be generic like the "MyEclipse Generic Runtime for JavaEE 6.0" or specific like "WebSphere 8.5". The former uses libraries that are shipped with MyEclipse, while the latter references libraries taken from your local WebSphere installation.
While we already supported this in prior versions of MyEclipse, it was never easy to change your runtime or even assign one to projects that were not migrated from RAD (in MyEclipse for WebSphere) without a lot of manual hacking. The Targeted Runtimes property page makes this easy. Note that other project containers could also intelligently change their contents based on the runtime that your project has assigned to it.
We have done away with most of our deployment preferences in favor of the Deployment Assembly mechanism, which is much more transparent. Use the project's deployment assembly property page to precisely control the deployment of your project's resources if you need more control. For instance, users who have been waiting for deployment exclusion support can now easily use settings on this page to prevent project resources from being deployed. Learn more about deployment assembly in MyEclipse Deployment Assembly.
Other deployment features:
- The Servers view tells you exactly which modules are out-of-sync, as opposed to marking the entire deployment as such.
- Several deployment states have been added to precisely indicate the current deployment phase. The re-deployment state is especially useful in the case of long hot-sync processes - you will know exactly when your changes are synchronized.
Note: The previous Server status information applies to MyEclipse 2013. The server connector framework has been reworked for MyEclipse 2015 and newer. Starting in MyEclipse 2015, you can see modules that are out of date and when you need to republish the server.
Beginning with MyEclipse 2013, the visual designer works on Windows 64 and OS X Cocoa. Superior HTML5 support is available in our tooling:
- Dozens of new elements and attributes added and existing elements refreshed to be compliant with the most recent December 2012 version of the specification.
- DOM / Window objects available in the HTML5 Browser support library (added to web projects) have been refreshed to pick up recent specification changes.
- The visual designer palette contains new HTML5 elements allowing you to easily create these elements in the Design pane.
MyEclipse 2013 and higher focuses on providing a streamlined IDE for individual developers. Reacting to customer feedback, we have taken MyEclipse back to its Eclipse Classic roots while moving our team sharing and management features to the MyEclipse Secure product.
3.1 MyEclipse Configuration Center Removed
The configuration center is no longer part of 2013 and future releases. To add and remove components, use the simple and efficient Components Dialog (Help>Choose Components...) instead of the Dashboard in the Configuration center.
We replaced the Pulse catalog in the Software tab with the MyEclipse Secure Marketplace. To add software to your installation, you can use this or other marketplaces, drag and drop from marketplace enabled sites or directly use the classic Eclipse Install Software wizard.
Profile sharing and management features in the Collaboration tab
are now available in MyEclipse Secure Edition. The configuration,
sharing and team management features available in the Secure
Edition are significantly more advanced, versatile and robust
compared to those previously available in the Collaboration tab.
The secure edition also allows you to activate MyEclipse behind
3.2 Installation / Update Process Enhancements
Rather than having to explicitly check for updates, MyEclipse periodically check for updates and unobtrusively informs you when one is available.
Note: The frequency at which updates are checked can be changed by the user or the update check can be turned off entirely. See Window>Preferences> Install/Update>Automatic Updates. You can also manually check for updates at any time using Help>Check for Updates.
Besides updating your installation to a new version of MyEclipse, you can also downgrade your installation to prior versions of MyEclipse (2013 and later). Installations are fully self-contained and simple to manage. All Eclipse plug-in installation techniques like dropins or even using the "links" folder work seamlessly. There are enormous performance improvements when checking for updates and installing new software.
3.3 Users of MyEclipse 8.x, 9.x and 10.x
- The MyEclipse Configuration Center will continue to work as before, nothing changes.
- Profiles can still be shared, shared profiles, groups, etc. will continue to function.
- The Pulse Explorer will no longer be available; however, all installed profiles can still be used without issue; for team and sharing related functions, use the Configuration Center.