You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Julien HENRY (JIRA)" <ji...@codehaus.org> on 2010/03/17 16:44:23 UTC

[jira] Created: (MNG-4596) [regression] classpath entry is missing in ejb MANIFEST

[regression] classpath entry is missing in ejb MANIFEST
-------------------------------------------------------

                 Key: MNG-4596
                 URL: http://jira.codehaus.org/browse/MNG-4596
             Project: Maven 2 & 3
          Issue Type: Bug
    Affects Versions: 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

        

[jira] Commented: (MEJB-46) classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7

Posted by "Julien HENRY (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEJB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214247#action_214247 ] 

Julien HENRY commented on MEJB-46:
----------------------------------

Thanks Benjamin

> 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
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>             Fix For: 2.2.1
>
>         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

        

[jira] Moved: (MEJB-46) [regression] classpath entry is missing in ejb MANIFEST

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEJB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann moved MNG-4596 to MEJB-46:
--------------------------------------------

           Complexity:   (was: Intermediate)
    Affects Version/s:     (was: 3.0-alpha-7)
                       2.2
                  Key: MEJB-46  (was: MNG-4596)
              Project: Maven 2.x EJB Plugin  (was: Maven 2 & 3)

> [regression] classpath entry is missing in ejb MANIFEST
> -------------------------------------------------------
>
>                 Key: MEJB-46
>                 URL: http://jira.codehaus.org/browse/MEJB-46
>             Project: Maven 2.x EJB Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            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

        

[jira] Closed: (MEJB-46) classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEJB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann closed MEJB-46.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.1
         Assignee: Benjamin Bentmann

Fixed in [r924384|http://svn.apache.org/viewvc?view=revision&revision=924384].

> 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
>            Assignee: Benjamin Bentmann
>            Priority: Critical
>             Fix For: 2.2.1
>
>         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

        

[jira] Updated: (MEJB-46) classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEJB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MEJB-46:
----------------------------------

    Environment: Maven 3.0-alpha-7
        Summary: classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7  (was: [regression] classpath entry is missing in ejb MANIFEST)

> 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

        

[jira] Commented: (MEJB-46) classpath entry is missing in ejb MANIFEST when using Maven 3.0-alpha-7

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
    [ 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