Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 3.3.0.M2
-
Component/s: server
-
Labels:None
Description
JBIDE-1354 should provide the possibility to save runtime configurations. These configurations are stored in the paths .plugins/org.jboss.ide.eclipse.as.core/.global/filesets/runtimeClasspaths/org.jboss.ide.eclipse.as.runtime.32 etc.
However, there is only the path .plugins/org.jboss.ide.eclipse.as.core/.global/filesets/default and additions to a runtime like "JBoss 7.x Runtime" are not possible. If I manually create the path .plugins/org.jboss.ide.eclipse.as.core/.global/filesets/runtimeClasspaths, then a new entry can be added and there is e.g. org.jboss.ide.eclipse.as.runtime.70.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
Requesting permission for following patch:
-
-
- Eclipse Workspace Patch 1.0
#P org.jboss.ide.eclipse.as.classpath.core
Index: src/org/jboss/ide/eclipse/as/classpath/core/runtime/CustomRuntimeClasspathModel.java
===================================================================
- src/org/jboss/ide/eclipse/as/classpath/core/runtime/CustomRuntimeClasspathModel.java (revision 34514)
+++ src/org/jboss/ide/eclipse/as/classpath/core/runtime/CustomRuntimeClasspathModel.java (working copy)
@@ -219,6 +219,9 @@
}
- Eclipse Workspace Patch 1.0
-
public static void saveFilesets(IRuntimeType runtime, IDefaultPathProvider[] sets) {
+ if( !DEFAULT_CLASSPATH_FS_ROOT.toFile().exists())
IPath fileToWrite = DEFAULT_CLASSPATH_FS_ROOT.append(runtime.getId());
XMLMemento memento = XMLMemento.createWriteRoot("classpathProviders"); //$NON-NLS-1$
for( int i = 0; i < sets.length; i++ ) {
rob - okey to put in since there are other respins.
One thing though for future reference - the location shouldn't be a constant since that location is dynamic in an eclipse installation.
Max Rydahl Andersen
added a comment - rob - okey to put in since there are other respins.
One thing though for future reference - the location shouldn't be a constant since that location is dynamic in an eclipse installation. committed to branch and trunk
verified on 3.3.0.M3-H18
Libor Zoubek
added a comment - verified on 3.3.0.M3-H18 
wrong component/assignee. now fixed.