[ 
https://issues.apache.org/jira/browse/MEJB-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17966069#comment-17966069
 ] 

Olivier Lamy commented on MEJB-15:
----------------------------------

This project has moved from Jira to GitHub Issues. This issue was migrated to 
[apache/maven-ejb-plugin#67|https://github.com/apache/maven-ejb-plugin/issues/67].
 

> ejb-jar.xml file destroys annotation functionality in EJB3
> ----------------------------------------------------------
>
>                 Key: MEJB-15
>                 URL: https://issues.apache.org/jira/browse/MEJB-15
>             Project: Maven EJB Plugin (Moved to GitHub Issues)
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: EJB3
>            Reporter: Dan Greening
>            Priority: Critical
>         Attachments: MEJB-6-maven-ejb-plugin.patch
>
>
> The EJB3 plugin requires an ejb-jar.xml file.  But EJB3 does not require this 
> file, and WORSE when that file is present, some appealing new annotation 
> features get turned off.  The current EJB plugin is a non-starter for serious 
> EJB3 development.
> A couple of us jointly wrote a patch to look for <ejbVersion>3.0</ejbVersion> 
> as a parameter to the EJB plugin. That patch is in issue MEJB-6.  When 
> ejbVersion is set to 3.*, the patched EJB maven plugin does not require 
> META-INF/ejb-jar.xml, and we can use all the features of EJB3.
> Unfortunately, the JIRA issue where this is discussed is marked "trivial": 
> MEJB-6 (http://jira.codehaus.org/browse/MEJB-6).  The priority cannot be 
> edited by mortals.  The issue and our well-constructed (attached) patch has 
> been ignored for 3 months.  Who knows why Tim originally marked it "trivial", 
> possibly because he wasn't using any of the new EJB3 features, but that poor 
> choice of priority has probably doomed our patch to obscurity.  (Of course, 
> anyone seriously using EJB3 wouldn't think it was trivial.)  Several people 
> have asked for this patch to be applied, including Tim and Todd above, as 
> well as myself and Wayne Fay.  Who is responsible for this plugin?  No one is 
> assigned to fix it.
> There are 10 votes and 7 watchers waiting for the patch to be applied.  
> Therefore I believe it justifies marking this problem "critical".  It 
> certainly is not trivial.
> MEJB-6 documents a full, well-structured patch supporting EJB 3.0, as well as 
> retaining default behavior appropriate for EJB 2.x.  The patch should be 
> applied and a new EJB plugin released.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to