google-code-export / cypal-studio

Automatically exported from code.google.com/p/cypal-studio
0 stars 0 forks source link

Error on Launch: Unsupported launch configuratio type in.cypal.studio.gwt.core.launchConfigurationType #115

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Not Sure
2.
3.

What is the expected output? What do you see instead?
Launching the App

What version of the product are you using? On what operating system?
Cypal 1 on Eclipse 3.3

Please provide any additional information below.
Not sure what happens, but I get this error:

"Unsupported launch configuratio type
in.cypal.studio.gwt.core.launchConfigurationType" when I run.  Not sure
what happens to cause it.  It works, and then it stops working.  I am using
Maven in my setup.

Original issue reported on code.google.com by joshblin...@gmail.com on 29 Sep 2008 at 2:02

GoogleCodeExporter commented 9 years ago
Please attach the stack trace if you find any in the Error Logs view. It will be
helpful for analyzing the issue

Original comment by grprakash on 29 Sep 2008 at 2:32

GoogleCodeExporter commented 9 years ago
Hi, 
I also have this error. 
It started when I upgraded my maven dependency from GWT 1.5.0 to 1.5.2.
I'll try to get a clean project from svn before investigating further. I'll 
tell you
if I find something tomorrow

Original comment by ane.o.n...@gmail.com on 6 Oct 2008 at 4:59

GoogleCodeExporter commented 9 years ago
Hi again, 
After removing all previous launch configuration, all seems to work well again 
with
GWT 1.5.2. No more error !

Original comment by ane.o.n...@gmail.com on 7 Oct 2008 at 7:59

GoogleCodeExporter commented 9 years ago
Cypal doesn't respect the classpath and sourcepathProvider. If the
launchconfiguration contains org.eclipse.jdt.launching.CLASSPATH_PROVIDER and/or
org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER the application won't start in 
hosted
mode. These values are probable added during some process by M2Eclipse, but that
shouldn't be a problem.

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="in.cypal.studio.gwt.core.launchConfigurationType">
<stringAttribute key="in.cypal.studio.gwt.core.launchModuleName"
value="com.xxx.gwt.test.Test"/>
<stringAttribute key="in.cypal.studio.gwt.core.launchProjectName" value="xxx"/>
<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER"
value="org.maven.ide.eclipse.launchconfig.classpathProvider"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="xxx"/>
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER"
value="org.maven.ide.eclipse.launchconfig.sourcepathProvider"/>
</launchConfiguration>

Original comment by r.f.scho...@gmail.com on 16 Jan 2009 at 10:11

GoogleCodeExporter commented 9 years ago
I have the same problem with the error on GWT module's launch. It really does 
happen
when a project is managed by M2Eclipse.

The only way how to get rid of the error which seems to work now is to delete 
the
module's launch configuration and then create it again (until the next error 
occurs).

Original comment by p.bod...@centrum.cz on 23 May 2009 at 8:02