[ http://issues.apache.org/jira/browse/GERONIMO-2208?page=all ]
Kevan Miller resolved GERONIMO-2208.
------------------------------------
Fix Version/s: 1.1.1
(was: 1.1.x)
Resolution: Fixed
Updated manifest.mf to include geronimo-util in the deploy-jsr88 classpath.
If you attempt to deploy using deploy-jsr88 to a remote server, you could see
this exception. Our testing doesn't detect this, because our deploys are local.
> bad classpath in geronimo-deploy-jsr88-1.1.jar
> ----------------------------------------------
>
> Key: GERONIMO-2208
> URL: http://issues.apache.org/jira/browse/GERONIMO-2208
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 1.1.x
> Reporter: Ted Kirby
> Assigned To: Kevan Miller
> Fix For: 1.1.1, 1.2
>
>
> When trying to do a remote deploy using geronimo-deploy-jsr88-1.1.jar, got a
> class not found exception on org.apache.geronimo.util.encoders.Base64. This
> class is packaged in geronimo-util-1.1.jar. The classpath in
> geronimo-deploy-jsr88-1.1.jar is suspect. First, it does not include the
> required geronimo-util-1.1.jar. Second, it includes itself, which I think is
> unnecessary.
> My change is to geronimo\modules\deploy-jsr88\src\conf\manifest.mf.
> In the classpath, I changed:
> < ../lib/geronimo-deploy-jsr88-${geronimo_version}.jar
> ---
> > ../lib/geronimo-util-${geronimo_version}.jar
> With that change, my remote deploy was successful.
--
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
