geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aman Nanner (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-2818) In-Place deployment does not interpret Manifest Class-Path entries correctly in JAR files
Date Sun, 11 Feb 2007 04:03:06 GMT
In-Place deployment does not interpret Manifest Class-Path entries correctly in JAR files
-----------------------------------------------------------------------------------------

                 Key: GERONIMO-2818
                 URL: https://issues.apache.org/jira/browse/GERONIMO-2818
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: deployment
    Affects Versions: 1.2
         Environment: Windows XP SP2
            Reporter: Aman Nanner
             Fix For: 1.2


>From the mailing list regarding deployment of EARs that contain JARS with a Class-Path
entry in their Manifest files:

----
It seems like the behaviour is different depending on whether I deploy the EAR as "inPlace"
or not.  I was deploying an expanded EAR "inPlace" and it seems that I needed the "../" prefix
before each JAR in my Manifest  classpath.  I tried deploying an EAR containing actual JAR
archives without the "inPlace" attribute, and I had to change my Manifest classpath  references
by removing the "../" prefix to make it work.

My guess is that the deployer creates a different folder hiearchy when deploying an application
without the "inPlace" attribute.
----

To review, using "inPlace" deployment requires that a "../" prefix be used in Manifest class-path
entries to reference library JARs relative to the EAR root.  This is a bug, and it should
be the same as non-inPlace deployment, where library JARs are already relative to the EAR
root.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message