[jboss-jira] [JBoss JIRA] (WFLY-9968) Provides jboss-deployment-structure.xml for all known applications, or a tool to generate it.

[Brian Stansberry (Jira)]

     [ https://issues.jboss.org/browse/WFLY-9968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry resolved WFLY-9968.
------------------------------------
      Assignee:     (was: Jason Greene)
    Resolution: Won't Do


I'm sorry, I don't see this as something feasible for the WildFly developers to do.

> Provides jboss-deployment-structure.xml for all known applications, or a tool to generate it.
> ---------------------------------------------------------------------------------------------
>
>                 Key: WFLY-9968
>                 URL: https://issues.jboss.org/browse/WFLY-9968
>             Project: WildFly
>          Issue Type: Feature Request
>    Affects Versions: 10.0.0.Final, 11.0.0.Final, 12.0.0.Final
>         Environment: all
>            Reporter: Gaétan QUENTIN
>            Priority: Major
>
> It is very painfull to deploy applications since modules system introduction.
> The modules conflicts  it has introduced is very difficult to understand , and we cannot  afford  to waste so many time to deploy war applications , trying to desactivate some modules or some subsystems and see what happens.
> Exemple? apache archiva. Since wildfly 10, i desesperatly try to integrate it as war in wildfly.
> There is always conflicts: first of one is cxf. But if you exclude it, there are bunch of others problems etc.
> So, couldn't it be possible for you to provide the  jboss-deployment-structure.xml needed for each well known application, or better,  provide a tool which would do it automaticaly?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)