[jbosstools-issues] [JBoss JIRA] Closed: (JBIDE-981) classToLaunch error when starting server

[Max Andersen (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBIDE-981?page=all ]

Max Andersen closed JBIDE-981.
------------------------------

    Resolution: Done

Fixed - but the defaults checking/setting feels really weird since it seem to always to have to be there (and most things hardcoded) so why is it required ?

> classToLaunch error when starting server
> ----------------------------------------
>
>                 Key: JBIDE-981
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-981
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 2.0.0.Beta3
>            Reporter: Max Andersen
>         Assigned To: Max Andersen
>            Priority: Blocker
>             Fix For: 2.0.0.Beta4
>
>
> When running server classToLaunch cannot be null error occurs.
> Caused since jboss 4.2 launch config's suddenly does not contain any launch info anymore:
> Now:
> <?xml version="1.0" encoding="UTF-8"?>
> <launchConfiguration type="org.jboss.ide.eclipse.as.core.server.startupConfiguration">
> <stringAttribute key="server-id" value="10_1_07_2_28_PM2"/>
> </launchConfiguration>
> Before:
> <?xml version="1.0" encoding="UTF-8"?>
> <launchConfiguration type="org.jboss.ide.eclipse.as.core.server.startupConfiguration">
> <booleanAttribute key="jboss.defaults.been.set" value="true"/>
> <listAttribute key="org.eclipse.jdt.launching.CLASSPATH">
> <listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#10;&lt;runtimeClasspathEntry externalArchive=&quot;/home/max/rhdevstudiob2/jboss-eap/jboss-as/bin/run.jar&quot; path=&quot;3&quot; type=&quot;2&quot;/&gt;&#10;"/>
> <listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#10;&lt;runtimeClasspathEntry containerPath=&quot;org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.5.0_12&quot; path=&quot;2&quot; type=&quot;4&quot;/&gt;&#10;"/>
> <listEntry value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&#10;&lt;runtimeClasspathEntry externalArchive=&quot;/usr/java/jdk1.5.0_12/lib/tools.jar&quot; path=&quot;3&quot; type=&quot;2&quot;/&gt;&#10;"/>
> </listAttribute>
> <booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH" value="false"/>
> <stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="org.jboss.Main"/>
> <stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="--configuration=default"/>
> <stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY" value="/home/max/rhdevstudiob2/jboss-eap/jboss-as/bin"/>
> <stringAttribute key="server-id" value="9_28_07_3_27_PM1"/>
> </launchConfiguration>
> Caused by this change: http://fisheye.jboss.org/browse/JBossTools/trunk/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/server/internal/launch/JBossServerStartupLaunchConfiguration.java?r1=3743&r2=3907 as a fix to http://jira.jboss.org/jira/browse/JBIDE-974

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira