geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <...@geronimo.apache.org>
Subject [jira] Resolved: (GERONIMO-2281) Deploy tool does not work (built from new m2 build)
Date Wed, 09 Aug 2006 00:10:14 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2281?page=all ]

Jason Dillon resolved GERONIMO-2281.
------------------------------------

    Fix Version/s: 1.2
       Resolution: Fixed

I've fixed these properties in the classpath.

We will be switching to use the jar or assembly plugin to generate classpath entries in manifests
soon, which will remove the need for these properties.

> Deploy tool does not work (built from new m2 build)
> ---------------------------------------------------
>
>                 Key: GERONIMO-2281
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2281
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.2
>            Reporter: Bill Dudney
>         Assigned To: Jason Dillon
>             Fix For: 1.2
>
>         Attachments: 2281-online-deployer.patch
>
>
> A fresh build of geronimo from trunk (with m2) does not have a working deployer.
> Tested only with the tomcat install but its likely a bug in all.
> To recreate;
> build with m2 (follow directions on wiki)
> install the g-tomcat-1.2-S.tar.gz 
> start the server with bin/startup.sh
> deploy something with bin/deploy.sh
> fails to find class javax/enterprise/deploy/spi/status/ProgressListener.class
> patch adds to the manifest class path of deployer.jar

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