Skip to main content

classpathJars property in .lgcfg files

2 replies [Last post]
afishionado
Offline
Joined: 2004-05-26

Alright, can somebody explain to me why nearly all the .lgcfg files in lg3d-incubator have the classpathJars property, while *none* of the .lgcfg files in lg3d-demo-apps do? Does LG3D have some built-in way of recognizing the jars in lg3d-demo-apps?

This has been really tripping me up while I was trying to fix the tutorial. :-P

William

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Krishna Gadepalli

Hi William
This is because ALL the demo apps get packaged into lg3d-demo-apps.jar
(into the lib directory) and this jar is added to the command line class
path when running the LG JVM.
The incubator apps on the other hand are each packaged into their own
jar (and put into ext/app directory) and these jars are NOT specified
in the classpath and are instead dynamically loaded.
-krishna

lg3d@javadesktop.org said the following on 09/21/2006 03:18 PM:
> Alright, can somebody explain to me why nearly all the .lgcfg files in lg3d-incubator have the classpathJars property, while *none* of the .lgcfg files in lg3d-demo-apps do? Does LG3D have some built-in way of recognizing the jars in lg3d-demo-apps?
>
> This has been really tripping me up while I was trying to fix the tutorial. :-P
>
> William
> [Message sent by forum member 'afishionado' (afishionado)]
>
> http://forums.java.net/jive/thread.jspa?messageID=155630
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
> For additional commands, e-mail: interest-help@lg3d.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

paulby
Offline
Joined: 2003-06-13

Use the technique from lg3d-incubator, I'd regard the lg3d-demo-apps as using obsolete api/techniques as far as packaging.