Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Error with Ganymede, can't launch run configuration against current workspace
Error with Ganymede, can't launch run configuration against current workspace [message #329814] Sun, 06 July 2008 23:45 Go to next message
Eclipse UserFriend
Originally posted by: apicard.tampabay.rr.com

Hi,

Since the days of 3.1 we have always had some launch configurations that
are used for code generation and that run in the current workspace by
running a launcher application.

Now it won't even get that far and it tells me that my workspace is
locked or already in use. Well it is the current workspace. This would
normally happen if you tried to launch a full runtime workbench to its
current workspace, but never to run those applications.

Can you shed some lights on what has changed (btw i went to a 3.3
version and it doesn't do that).

Thanks
Alain
Re: Error with Ganymede, can't launch run configuration against current workspace [message #329822 is a reply to message #329814] Mon, 07 July 2008 07:55 Go to previous messageGo to next message
Eclipse UserFriend
Alain,

Is the launched application specifying the same workspace as is being
used by the running Eclipse? It sounds like it is, but I wouldn't
expect that ever to have worked...


Alain Picard wrote:
> Hi,
>
> Since the days of 3.1 we have always had some launch configurations
> that are used for code generation and that run in the current
> workspace by running a launcher application.
>
> Now it won't even get that far and it tells me that my workspace is
> locked or already in use. Well it is the current workspace. This would
> normally happen if you tried to launch a full runtime workbench to its
> current workspace, but never to run those applications.
>
> Can you shed some lights on what has changed (btw i went to a 3.3
> version and it doesn't do that).
>
> Thanks
> Alain
Re: Error with Ganymede, can't launch run configuration against current workspace [message #329824 is a reply to message #329822] Mon, 07 July 2008 08:54 Go to previous message
Eclipse UserFriend
Originally posted by: apicard.tampabay.rr.com

Ed,

The answer to your question is yes, and it has always worked. Like I
said, starting a full runtime-workspace would not work, but this always did.

Any idea what would have changed in 3.4?

Thanks
Alain


Here is one of those launch config:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.pde.ui.RuntimeWorkbench">
<stringAttribute key="application"
value="com.castortech.iris.IrisApplicationLauncher"/>
<booleanAttribute key="askclear" value="true"/>
<booleanAttribute key="automaticAdd" value="true"/>
<booleanAttribute key="automaticValidate" value="true"/>
<stringAttribute key="bootstrap" value=""/>
<stringAttribute key="checked" value="[NONE]"/>
<booleanAttribute key="clearConfig" value="false"/>
<booleanAttribute key="clearws" value="false"/>
<booleanAttribute key="clearwslog" value="false"/>
<stringAttribute key="configLocation"
value=" ${workspace_loc}/.metadata/.plugins/org.eclipse.pde.core/Gen erate
JTB step - C"/>
<booleanAttribute key="default" value="false"/>
<stringAttribute key="deselected_workspace_plugins" value="VMF.editor"/>
<booleanAttribute key="includeOptional" value="true"/>
<stringAttribute key="location" value="${workspace_loc}"/>
<booleanAttribute
key="org.eclipse.debug.core.appendEnvironmentVariables" value="true"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS"
value="-os win32 -ws win32 -arch x86 -nl en_US -nosplash
EDU.purdue.jtb.JTB
&quot;${resource_loc:/CLanguageBundle/src/com/castortech /cinterpreter/Configuration.xml}&quot; "/>
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER"
value="org.eclipse.pde.ui.workbenchClasspathProvider"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS"
value="-Xms256m -Xmx512m -ea -XX:MaxPermSize=128m"/>
<stringAttribute key="org.eclipse.jdt.launching.WORKING_DIRECTORY"
value=" ${workspace_loc:CLanguageBundle/src/com/castortech/cinterpre ter} "/>
<stringAttribute key="pde.version" value="3.3"/>
<stringAttribute key="product" value="org.eclipse.sdk.ide"/>
<stringAttribute key="selected_target_plugins"
value=" com.ibm.icu,com.jcraft.jsch,javax.servlet,javax.servlet,net. sourceforge.lpg.lpgjavaruntime,net.sourceforge.lpg.lpgjavaru ntime,org.apache.commons.logging,org.apache.commons.logging, org.apache.log4j,org.apache.lucene,org.apache.lucene.analysi s,org.eclipse.ant.core,org.eclipse.compare,org.eclipse.core. commands,org.eclipse.core.contenttype,org.eclipse.core.datab inding,org.eclipse.core.expressions,org.eclipse.core.filebuf fers,org.eclipse.core.filesystem,org.eclipse.core.filesystem .win32.x86,org.eclipse.core.jobs,org.eclipse.core.net,org.ec lipse.core.resources,org.eclipse.core.resources.compatibilit y,org.eclipse.core.resources.win32,org.eclipse.core.runtime, org.eclipse.core.runtime.compatibility,org.eclipse.core.runt ime.compatibility.auth,org.eclipse.core.runtime.compatibilit y.registry,org.eclipse.core.variables,org.eclipse.debug.core ,org.eclipse.emf.codegen,org.eclipse.emf.codegen.ecore,org.e clipse.emf.codegen.ecore.ui,org.eclipse.emf.common,org.eclip se.emf.common.ui,org.e
clipse.emf.converter,org.eclipse.emf.ecore,org.eclipse.emf.e core.change,org.eclipse.emf.ecore.edit,org.eclipse.emf.ecore .xmi,org.eclipse.emf.edit,org.eclipse.emf.edit.ui,org.eclips e.emf.importer,org.eclipse.emf.ocl,org.eclipse.emf.teneo,org .eclipse.emf.teneo.annotations,org.eclipse.emf.teneo.doc,org .eclipse.emf.teneo.eclipse,org.eclipse.emf.teneo.hibernate,o rg.eclipse.emf.teneo.hibernate.eclipse,org.eclipse.emf.teneo .hibernate.mapper,org.eclipse.emf.teneo.libraries,org.eclips e.emf.teneo.source,org.eclipse.equinox.app,org.eclipse.equin ox.common,org.eclipse.equinox.http.jetty,org.eclipse.equinox .http.servlet,org.eclipse.equinox.preferences,org.eclipse.eq uinox.registry,org.eclipse.help,org.eclipse.help.base,org.ec lipse.help.ui,org.eclipse.jdt,org.eclipse.jdt.compiler.apt,o rg.eclipse.jdt.compiler.tool,org.eclipse.jdt.core,org.eclips e.jdt.core.manipulation,org.eclipse.jdt.debug,org.eclipse.jd t.launching,org.eclipse.jface,org.eclipse.jface.databinding, org.eclipse.jface.text,org.ecl
ipse.jsch.core,org.eclipse.ltk.core.refactoring,org.eclipse. ltk.ui.refactoring,org.eclipse.ocl,org.eclipse.ocl.ecore,org .eclipse.osgi,org.eclipse.osgi.services,org.eclipse.pde.buil d,org.eclipse.pde.core,org.eclipse.swt,org.eclipse.swt.win32 .win32.x86,org.eclipse.team.core,org.eclipse.team.cvs.core,o rg.eclipse.team.cvs.ui,org.eclipse.team.ui,org.eclipse.text, org.eclipse.ui,org.eclipse.ui.cheatsheets,org.eclipse.ui.con sole,org.eclipse.ui.editors,org.eclipse.ui.forms,org.eclipse .ui.ide,org.eclipse.ui.intro,org.eclipse.ui.navigator,org.ec lipse.ui.navigator.resources,org.eclipse.ui.views,org.eclips e.ui.views.properties.tabbed,org.eclipse.ui.win32,org.eclips e.ui.workbench,org.eclipse.ui.workbench.texteditor,org.eclip se.update.configurator,org.eclipse.update.core,org.eclipse.u pdate.core.win32,org.eclipse.update.ui,org.junit,org.junit4, org.mortbay.jetty "/>
<stringAttribute key="templateConfig"
value="${target_home}\configuration\config.ini"/>
<booleanAttribute key="tracing" value="false"/>
<booleanAttribute key="useDefaultConfig" value="true"/>
<booleanAttribute key="useDefaultConfigArea" value="true"/>
<booleanAttribute key="useProduct" value="false"/>
<booleanAttribute key="usefeatures" value="false"/>
</launchConfiguration>


Ed Merks wrote:
> Alain,
>
> Is the launched application specifying the same workspace as is being
> used by the running Eclipse? It sounds like it is, but I wouldn't
> expect that ever to have worked...
>
Previous Topic:Eclipse crashes with no message or error log
Next Topic:Obtaining the 'branding' plugin
Goto Forum:
  


Current Time: Fri May 09 21:40:46 EDT 2025

Powered by FUDForum. Page generated in 0.03445 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top