You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/03/17 18:42:22 UTC
[jira] Commented: (MEJB-46) classpath entry is missing in ejb
MANIFEST when using Maven 3.0-alpha-7
[ http://jira.codehaus.org/browse/MEJB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214244#action_214244 ]
Benjamin Bentmann commented on MEJB-46:
---------------------------------------
This is a bug in the EJB Plugin (missing @requiresDependencyResolution annotation) that shows up with recent Maven 3.0 alphas due to the fix for MNG-4526.
> classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7
> -----------------------------------------------------------------------
>
> Key: MEJB-46
> URL: http://jira.codehaus.org/browse/MEJB-46
> Project: Maven 2.x EJB Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: Maven 3.0-alpha-7
> Reporter: Julien HENRY
> Priority: Critical
> Attachments: test-bug-maven-ejb-manifest.zip
>
>
> After upgrading from alpha 6 to alpha 7, the classpath entry is missing in the MANIFEST of my ejb module. See the attached project as example.
--
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