[ http://issues.apache.org/jira/browse/GERONIMO-1365?page=all ]
David Jencks closed GERONIMO-1365.
----------------------------------
Resolution: Won't Fix
As I mentioned earlier, the fix for this is to not have a lib dir or manifest
cp entries but rather a bootstrap repository. Dain has some ideas on this.....
maybe it will happen someday soon.
> JSR-88 Manfest has incorrect Class-Path entries
> -----------------------------------------------
>
> Key: GERONIMO-1365
> URL: http://issues.apache.org/jira/browse/GERONIMO-1365
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 1.0
> Reporter: Aaron Mulder
> Assigned To: David Jencks
> Fix For: Wish List
>
>
> We used to use bin/deployer.jar as our JSR-88 implementation JAR. As a
> result, all the Class-Path entries had the form "../lib/foo.jar" (resolving
> to geronimo/lib/...).
> At some point, that was switched so that
> repository/geronimo/jars/geronimo-deploy-jsr88-1.0.jar became the official
> JSR-88 implementation JAR. However, all the Class-Path entries are still
> "../lib" even though that resolves to "repository/geronimo/lib/..." which is
> not valid.
> Either we need to switch JSR-88 back to bin/deployer.jar or else we need to
> update the Class-Path entries to be relative within the repository.
> Assigning this to David J since he mentioned updating the JSR-88
> implementation JAR, so I suspect he has an opinion on which way to go with
> this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
