this worked before i updated to the latest wolips. so i recommend the code to avoid duplicate jars to be more robust.
ciao frank
________________________________
From: Ulrich Köster [mailto:ulric..bjectstyle.org]
Sent: Thursday, 10. May 2007 14:41
To: woproject-de..bjectstyle.org
Subject: Re: Can not Launch
There is some code to avoid duplicate jars. I'll recommend to rename the jar.
Uli
Am 10.05.2007 um 14:25 schrieb Frank Caputo:
I have a problem launching inside of eclipse. .classpath and classpath in the launchconfiguration both contain the missing jar. it is missing, when i look at System.getProperty("java.class.path"), when the app is launching. the jar is referenced as extended classpath-variable, but this is the same for all other jars.
Ciao Frank
________________________________
From: Mike Schrag [mailto:mschra..dimension.com]
Sent: Thursday, 10. May 2007 14:11
To: woproject-de..bjectstyle.org
Subject: Re: Can not Launch
Assuming you made a regular app and not a wonder app (which automatically has a known folder structure and "just works), make sure to include your custom jar folders in your build script. In build.xml there is something like:
<include name="Add .jar's that should be copied in the framework."/>
which you can add a
<include name="lib/*.jar" />
to and have it pickup your jars. I'm not really sure why the default build script just doesn't have **/*.jar in it -- that's probably a more reasonably default than just not including anything. But that's just me, and I use WonderApplication as my starting point, anyway.
ms
On May 10, 2007, at 7:01 AM, Frank Caputo wrote:
Hi,
I have a problem launching an app. The classpath contains a jar which
starts with the project-name. This jar is missing in the generated
classpath for launching:
Project name: Horst
Jar name: HorstGateway-rel_1_1_0_20070402.jar
Can anyone help?
Ciao Frank
This archive was generated by hypermail 2.0.0 : Thu May 10 2007 - 08:42:59 EDT