Moin Ralf,
cd to workspace/.metadata/.plugins/org.eclipse.debug.core/.launches
The files should look like this one:
<?xml version="1.0" encoding="UTF-8"?>
<launchConfiguration
type="org.objectstyle.wolips.launching.WOLocalJavaApplication">
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE"
value="Application"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR"
value="HelloWOrld"/>
<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER"
value="org.objectstyle.wolips.launching.WORuntimeClasspathProvider"/>
</launchConfiguration>
If the file does not start with:
<?xml version="1.0" encoding="UTF-8"?>
<launchConfiguration
type="org.objectstyle.wolips.launching.WOLocalJavaApplication">
Ignore it.
Important is the runtime classpath provider.
Ulrich
Am 13.12.2004 um 14:43 schrieb Ralf Liebenow:
> Hallo !
>
> What exactly has to be changed in the launch config to make that work
> (do you have an example ?)
>
> Thanks in advance
> Ralf
>
>> Moin Chuck,
>>
>> some of the launch configurations created by WOLips are invalid. A fix
>> is in the cvs.
>>
>> The fix prevents a buggy config to be launched. It's possible to fix
>> the launch config in the .metadata directory.
>>
>> Ulrich
>> Am 10.12.2004 um 19:04 schrieb Chuck Hill:
>>
>>> On Dec 10, 2004, at 9:13 AM, Ralf Liebenow wrote:
>>>> However, the launch Configuration I created to launch the
>>>> Application
>>>> within Eclipse does not have the right Classpaths setup. NSBundle
>>>> does
>>>> not find its Main Bundle because its X.woa Path is not in the
>>>> classpath.
>>>> It also does not find Resources for the Framework Y, because the
>>>> Y.framework Path is not in its classpath.
>>>>
>>> You need to make the .woa directory the working directory in the run
>>> config. I also usually have to tweak the run config's classpath. I
>>> add the jar from each .framework/Resources/Java directory and move
>>> then in the list before the projects. There is usually (at least for
>>> my projects) a lot of duplication in the default generated classpath.
>>> I like to get rid of this. It makes seeing any problems easier.
>>>
>>>
>>>> The Framework is selected in the Java build Path of the Project
>>>> (which
>>>> is necessary to compile the classes), and the jar-files are
>>>> referenced, so
>>>> the Problem is only in launching because application and frameworks
>>>> base
>>>> paths are not listed in the classpath at launch time (all the jar
>>>> files are).
>>>>
>>>> NSBundle uses the System Properties "java.class.path" and
>>>> "com.webobjects.classpath" to look for classes, Frameworks and
>>>> applications.
>>>>
>>>> "com.webobjects.classpath" is empty, when I launch in eclipse and
>>>> "java.class.path" lists only the necessary jar files, which is OK
>>>> for
>>>> compilation, but for NSBundle the .framework and .woa Paths needed
>>>> to
>>>> be
>>>> in there.
>>>>
>>> I don't know if those are relevant for Eclipse launches. Apps
>>> launched by Eclipse launch differently than apps launched from the
>>> command line. Command line launches use WOBootstrap and the
>>> <x>Classpath.txt files.
>>>
>>> All that said, I've never done this on Linux, but I have pulled out
>>> my
>>> fair share of hair getting complex setups to run.
>>>
>>> HTH
>>> Chuck
>>>
>>>
>>> --
>>> Practical WebObjects - a book for intermediate WebObjects developers
>>> who want to increase their overall knowledge of WebObjects, or those
>>> who are trying to solve specific application development problems.
>>> http://www.global-village.net/products/practical_webobjects
>>>
>>>
>>>
>>
>>
>
> --
> theCode AG
> Oranienstr. 10-11, 10997 Berlin [×]
> fon +49 30 617 897-0 fax -10
> ral..heCo.de http://www.theCo.de
This archive was generated by hypermail 2.0.0 : Mon Dec 13 2004 - 12:31:58 EST