]
Gaétan QUENTIN updated WFLY-9968:
---------------------------------
Summary: Provides jboss-deployment-structure.xml for all known applications, or a tool
to generate it. (was: Provides jboss-deployment-structure.xml for all known
applications)
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
Components: CLI, Documentation
Affects Versions: 10.0.0.Final, 11.0.0.Final, 12.0.0.Final
Environment: all
Reporter: Gaétan QUENTIN
Assignee: Jean-Francois Denise
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?