[
https://issues.jboss.org/browse/WFLY-7708?page=com.atlassian.jira.plugin....
]
Gregor Rosenauer updated WFLY-7708:
-----------------------------------
Description:
There is often a need to change the name of a deployment, e.g. the EAR, from the default
name to a stable name.
The problem is that common Maven practice mandates a version suffix, generating a fully
versioned EAR. Wildfly by default (which is only changable from CLI/management console)
takes the full name without the extension.
This leads to clunky and brittle code, e.g. JNDI lookups *have* to use the full name
including version, which is most often undesirable.
Sadly, Wildfly completely ignores the <earName> (was it?) attribute in the
application.xml.
Generally, there should be an option to strip versions of deployments so e.g. JNDI lookup
is stable and not version dependent.
I know there can be a scenario where this would make sense, but it's a 0.0001% use
case imho.
As suggested in
https://developer.jboss.org/thread/213914 I am creating this issue now,-)
In the meantime, the best way for me was to configure the maven-ear-plugin to change the
module names like suggested in
http://stackoverflow.com/a/27442584/160799 and to override
the finalName of the modules in the module POMs.
was:
There is often a need to change the name of a deployment, e.g. the EAR, from the default
name to a stable name.
The problem is that common Maven practice mandates a version suffix, generating a fully
versioned EAR. Wildfly by default (which is only changable from CLI/management console)
takes the full name without the extension.
This leads to clunky and brittle code, e.g. JNDI lookups *have* to use the full name
including version, which is most often undesirable.
As suggested in
https://developer.jboss.org/thread/213914 I am creating this issue now,-)
support specifying the runtime-name in the deployment descriptor
----------------------------------------------------------------
Key: WFLY-7708
URL:
https://issues.jboss.org/browse/WFLY-7708
Project: WildFly
Issue Type: Enhancement
Components: EE
Affects Versions: 9.0.2.Final
Environment: Java EE 7
Reporter: Gregor Rosenauer
Priority: Minor
Labels: EE, deployment, descriptor
There is often a need to change the name of a deployment, e.g. the EAR, from the default
name to a stable name.
The problem is that common Maven practice mandates a version suffix, generating a fully
versioned EAR. Wildfly by default (which is only changable from CLI/management console)
takes the full name without the extension.
This leads to clunky and brittle code, e.g. JNDI lookups *have* to use the full name
including version, which is most often undesirable.
Sadly, Wildfly completely ignores the <earName> (was it?) attribute in the
application.xml.
Generally, there should be an option to strip versions of deployments so e.g. JNDI lookup
is stable and not version dependent.
I know there can be a scenario where this would make sense, but it's a 0.0001% use
case imho.
As suggested in
https://developer.jboss.org/thread/213914 I am creating this issue
now,-)
In the meantime, the best way for me was to configure the maven-ear-plugin to change the
module names like suggested in
http://stackoverflow.com/a/27442584/160799 and to override
the finalName of the modules in the module POMs.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)