geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1365) JSR-88 Manfest has incorrect Class-Path entries
Date Thu, 15 Dec 2005 17:54:46 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1365?page=comments#action_12360518 ] 

David Jencks commented on GERONIMO-1365:
----------------------------------------

My intention in setting the manifest classpath entries as I did was that when used directly
as the jsr-88 implementation jar, the jar would be placed in the bin directory, possibly with
a simpler name.  In this case, the manifest classpath entries would be correct.  I don't think
that asking people to find a jar in the geronimo repository in order to use jsr-88 is appropriate.

I think this issue illustrates that we are using manifest classpath too much and that it is
not appropriate for large scale software.  Unfortuneately I don't have a solution in mind.

> JSR-88 Manfest has incorrect Class-Path entries
> -----------------------------------------------
>
>          Key: GERONIMO-1365
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1365
>      Project: Geronimo
>         Type: Bug
>   Components: deployment
>     Versions: 1.0
>     Reporter: Aaron Mulder
>     Assignee: David Jencks
>      Fix For: 1.1

>
> 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


Mime
View raw message