r1 - 2017-01-05 - 14:59:36 - LarrySmithYou are here: TWiki >  Deployment Web > CLMEclipseFixForUnconfiguredProcess

Configuring Eclipse with a VM parameter to avoid "unconfigured" project area editors todo.png

Authors: LarrySmith
Build basis: CLM 6.0+, Eclipse 4.4+, Java 8

This article discusses how to configure recent Eclipse (e.g. Eclipse 4.4 Neon) versions to remove an issue where the project area is shown with all sections "Unconfigured".

VM Argument to Enable Access to External Schema

The issue is caused by a new Java VM parameter that requires opt-in to allow the client to access external schema, which is required to configure the project area. When opening a project area editor in Eclipse, all sections are shown as "Unconfigured".

In addition, an error in the process configuration.xml flags to the access to external schema. The failing "Schema Error" line in the process.xml is like:

<process-specification xmlns="http://com.ibm.team.process">

The fix for this is to add a VM argument to the eclipse.ini file. In Windows this file is the Eclipse installation directory; in Mac you must select eclipse.app and use the menu item "Show Package Contents" then update the /Content/MacOS/eclipse.ini file.

The change is to add a line at the end:


A final eclipse.ini file may look like this:


External Links

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project