This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 262589 - Ear module names in deployment
Summary: Ear module names in deployment
Status: RESOLVED INCOMPLETE
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.1
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-27 14:39 UTC by spiewok
Modified: 2017-02-22 15:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description spiewok 2016-06-27 14:39:42 UTC 
When the configuration "<fileNameMapping>no-version</fileNameMapping>" of the maven-ear-plugin is used. Netbeans fails to deploy the project on wildfly. The reason is obviously that the wildfly export doesn't respect the setting and deploys the modules still with the version-number included. If I manually deploy the ear everything works.
Comment 1 spiewok 2016-06-27 14:41:53 UTC 
The same applies if I use "<bundleFileName>xxxxx.jar</bundleFileName>". The maven plugin generates the ear properly, but the wildfly export fails because the name is still default.
Comment 2 ehsavoie 2017-02-22 15:27:46 UTC 
I don't reproduce your issue and the plugin only deploy the full ear thus it doesn't care about the names inside.