You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/08/08 08:53:13 UTC
[jira] Created: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
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
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
[jira] Commented: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2298?page=comments#action_12426487 ]
David Jencks commented on GERONIMO-2298:
----------------------------------------
The geronimo-deploy-jsr88 manifest works fine. I'd like to see if we can remove some duplication from the deployer.jar (online-deployer) manifest before closing this one.
> 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
[jira] Commented: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2298?page=comments#action_12426490 ]
Jason Dillon commented on GERONIMO-2298:
----------------------------------------
Tell me what the classpath should be... and I will fix.
> 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
[jira] Resolved: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2298?page=all ]
Jason Dillon resolved GERONIMO-2298.
------------------------------------
Fix Version/s: 1.2
Resolution: Fixed
Assignee: David Jencks (was: Jason Dillon)
Updated to include the module's classpath and the custom attribute.
Please verify and close.
> 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
[jira] Commented: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Assigned: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2298?page=all ]
Jason Dillon reassigned GERONIMO-2298:
--------------------------------------
Assignee: Jason Dillon
> 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: Jason Dillon
>
> 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
[jira] Commented: (GERONIMO-2298) geronimo-deploy-jsr88 jar is
missing manifest entries in m2 build
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2298?page=comments#action_12426510 ]
Jason Dillon commented on GERONIMO-2298:
----------------------------------------
Seems like there was some aftermath to this change which needs some poms to be adjusted with some added dependencies.
> 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