maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Wilson (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MEJB-7) Transitive Classpath not written to the manifest
Date Thu, 26 Oct 2006 14:23:04 GMT
    [ http://jira.codehaus.org/browse/MEJB-7?page=comments#action_78519 ] 
            
Sam Wilson commented on MEJB-7:
-------------------------------

That seems to solve the issue.

However, given that this is part of the spec, shouldn't this be the default behavior and not
require this sort of archane override?

I went through the homepage for the plugin, the guides as well as the "Better Builds With
Maven" book and found no reference to this property, which would be required for proper deployment
in a compliant container. 

It would be nice to see this referenced in the documentation somewhere, or to have the default
changed to something more appropriate (provided that won't cause other things to brake in
a terrible way).

Thanks for the solution.

> Transitive Classpath not written to the manifest
> ------------------------------------------------
>
>                 Key: MEJB-7
>                 URL: http://jira.codehaus.org/browse/MEJB-7
>             Project: Maven 2.x Ejb Plugin
>          Issue Type: Bug
>            Reporter: Todd Nine
>
> The transitive classpath of all dependencies from the dependencies in an EJB pom are
not added to the MANIFEST.MF classpath. This causes the ejb to not deploy correctly.
> Todd

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message