Hey
>Lots of threads on this issue today. I'm not sure I know all the
>scenarios, but I will comment since it was asked for ;)
>
>I'd appreciate the appearence of the "class-path" in the manifest obeyed
>from the deploy dir. So if you copy it, you can have relative (ie: no
>leading slash) or absolute references. If they are relative, they may not
>be a jar, but a whole directory. It would be difficult to copy them. So
>perhaps fixing the "Class-Path:" by prepending "/path/to/deploy/dir/" to
>the entries. Unix allows "/deploy/dir/../../classes" to
>resolve. hopefully the classloader wouldn't have a problem with this.
>
>But yes, any solution (even a hack) would be appreciated. If it's
>recommended only for use in development cause it's too hackish (which it
>would be used more frequently perhaps?), that would be accetable.
Already fixed. In CVS. I simply extracted all the ClassPath: references and
added the URL's to classpath, and if relative I preffixed with the deploy
dir.
/Rickard
