You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2022/10/18 14:47:00 UTC

[jira] [Updated] (MEAR-309) Support JakartaEE 10

     [ https://issues.apache.org/jira/browse/MEAR-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Slawomir Jaranowski updated MEAR-309:
-------------------------------------
    Issue Type: New Feature  (was: Improvement)

> Support JakartaEE 10
> --------------------
>
>                 Key: MEAR-309
>                 URL: https://issues.apache.org/jira/browse/MEAR-309
>             Project: Maven EAR Plugin
>          Issue Type: New Feature
>    Affects Versions: 3.2.0
>            Reporter: Wolfgang Knauf
>            Assignee: Slawomir Jaranowski
>            Priority: Major
>             Fix For: 3.3.0
>
>
> Please add support for JakartaEE 10, so that a valid "application.xml" can be created.
> As WildFly 27 defaults to JakartaEE 10, I am in the process of updating the archetype for a blank WildFly EAR project. And to keep it clean, I want the maven-ear-plugin to create a JakartaEE 10 "application.xml" instead of the JavaEE8 version.
>  
> In the moment, I think I will switch off generating this file ("<generateApplicationXml>false</generateApplicationXml>") in order  to avoid confusion.
>  
> I see that [https://issues.apache.org/jira/projects/MEAR/issues/MEAR-302] already added support for JakartaEE9, so I could even try to send a similar pull request for 10.



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