[jbosstools-issues] [JBoss JIRA] (JBIDE-14317) Forge Preferences accept invalid runtime paths without user warning
Denis Golovin (JIRA)
jira-events at lists.jboss.org
Mon May 13 21:06:06 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-14317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773962#comment-12773962 ]
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}
> Forge Preferences accept invalid runtime paths without user warning
> -------------------------------------------------------------------
>
> Key: JBIDE-14317
> URL: https://issues.jboss.org/browse/JBIDE-14317
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Alpha1
> Reporter: Pavol Srna
> Fix For: 4.1.0.Beta1
>
> Attachments: forge-1.png
>
>
> User should be warned that forge cannot start due to an invalid runtime location in preferences.
> Actually no exception is thrown and forge seems to be always trying to start. (the number of dots in console is increasing: see screenshot)
--
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
More information about the jbosstools-issues
mailing list