[jbosstools-issues] [JBoss JIRA] (JBIDE-14317) Forge Preferences accept invalid runtime paths without user warning

[ https://issues.jboss.org/browse/JBIDE-14317?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-14317: --------------------------------------- the same problem with runtime name. After adding runtime with name <name/> there would be an exception after attempt to start forge from view: {code}java.lang.RuntimeException: Problem while creating launch configuration working copy. at org.jboss.tools.forge.core.process.ForgeLaunchHelper.createWorkingCopy(ForgeLaunchHelper.java:93) at org.jboss.tools.forge.core.process.ForgeLaunchHelper.doLaunch(ForgeLaunchHelper.java:65) at org.jboss.tools.forge.core.process.ForgeLaunchHelper.launch(ForgeLaunchHelper.java:53) at org.jboss.tools.forge.core.process.ForgeAbstractRuntime.start(ForgeAbstractRuntime.java:50) at org.jboss.tools.forge.ui.util.ForgeHelper$1.run(ForgeHelper.java:41) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: org.eclipse.core.runtime.CoreException: Local configuration cannot be nested in a directory. at org.eclipse.debug.internal.core.LaunchConfigurationType.newInstance(LaunchConfigurationType.java:463) at org.jboss.tools.forge.core.process.ForgeLaunchHelper.createWorkingCopy(ForgeLaunchHelper.java:86) ... 5 more {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira