[ http://issues.apache.org/jira/browse/GERONIMO-2298?page=comments#action_12426497 ] David Jencks commented on GERONIMO-2298: ----------------------------------------
basically we should be able to leave out anything that is in the geronimo-deploy-jsr88 manifest classpath from the deployer.jar manifest classpath, in particular the spec jar-- this is why the onlne deployer used to work even without the correct spec jar name :-) > geronimo-deploy-jsr88 jar is missing manifest entries in m2 build > ----------------------------------------------------------------- > > Key: GERONIMO-2298 > URL: http://issues.apache.org/jira/browse/GERONIMO-2298 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem > Affects Versions: 1.2 > Reporter: David Jencks > Assigned To: David Jencks > Fix For: 1.2 > > > The m1 build has an explicit manifest.mf file for this jar. We can generate > an appropriate manifest in m2. The m1 manifest has classpath entries > starting with ../lib/ which can be removed since all jars involved are in > lib. The dependencies in the pom.xml need to be adjusted to match the > explicit manifest used in the m1 build. > After this is done most likely the online-deployer won't need so many > manifest classpath entries. -- 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
