1:04 a.m.
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtimes
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Snjezana Peco
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:39 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9605:
---------------------------------------
Fix Version/s: 3.3.0.M4
Assignee: Rob Stryker (was: Snjezana Peco)
Component/s: JBossAS
(was: runtimes)
wrong component/assignee. now fixed.
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:14 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-9605:
-------------------------------
Fix Version/s: 3.3.0.M3
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M3, 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:14 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9605:
------------------------------------
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 @@
}
public static void saveFilesets(IRuntimeType runtime, IDefaultPathProvider[] sets) {
+ if( !DEFAULT_CLASSPATH_FS_ROOT.toFile().exists()) {
+ DEFAULT_CLASSPATH_FS_ROOT.toFile().mkdirs();
+ }
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++ ) {
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M3, 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9605:
--------------------------------------------
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.
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M3, 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:53 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-9605.
--------------------------------
Resolution: Done
committed to branch and trunk
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M3, 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-9605:
-------------------------------------
verified on 3.3.0.M3-H18
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M3, 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-9605) Runtimes are not configurable (JBIDE-1354)
[
https://issues.jboss.org/browse/JBIDE-9605?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-9605.
-------------------------------
Runtimes are not configurable (JBIDE-1354)
------------------------------------------
Key: JBIDE-9605
URL: https://issues.jboss.org/browse/JBIDE-9605
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M2
Reporter: Juergen Zimmermann
Assignee: Rob Stryker
Fix For: 3.3.0.M3, 3.3.0.M4
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4683
days inactive
4696
days old
jbosstools-issues@lists.jboss.org
7 comments
4 participants
participants (4)
-
Juergen Zimmermann (JIRA) -
Libor Zoubek (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)