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 242016 - Maven-based EAR projects not deployed correctly to WildFly 8.0.0.Final
Summary: Maven-based EAR projects not deployed correctly to WildFly 8.0.0.Final
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.0
Hardware: PC Windows 8
: P1 normal (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 15:44 UTC by RayDeCampo
Modified: 2014-02-26 07:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Example project files (19.54 KB, application/x-zip-compressed)
2014-02-17 15:44 UTC, RayDeCampo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RayDeCampo 2014-02-17 15:44:00 UTC
Created attachment 145315 [details]
Example project files

I have a maven-based EAR project (see attached).  When deploying to WildFly 8.0.0.Final via the WildFly NetBeans plugin version 1.0.6, the EAR structure is not copied correctly to the deployments directory and the EAR is not deployed correctly.

The WAR and EJB JAR files inside the EAR are copied directly to the deployments/ directory instead of being inside the directory for the EAR.

In addition the directory created for the EAR does not have .ear appended to the name.  This causes incorrect treatment of the archive by WildFly.  A work-around is to change the value of the project/build/finalName element in the example/example-ear/pom.xml file to have the .ear extension.  (This is undesirable in that the resulting EAR file created by maven is named example.ear.ear.)

I have been deploying the attached example by right-clicking on the example-ear project and selecting 'Run'.

Information from the NetBeans Help->About dialog:

Product Version: NetBeans IDE 8.0 Beta (Build 201401141042)
Java: 1.7.0_51; Java HotSpot(TM) 64-Bit Server VM 24.51-b03
Runtime: Java(TM) SE Runtime Environment 1.7.0_51-b13
System: Windows 8 version 6.2 running on amd64; Cp1252; en_US (nb)
Comment 1 ehsavoie 2014-02-19 19:28:00 UTC
Are you using deploy on save ?
The extension enables me to determine the type of the project. I think this is used 'before' the plugin's code is called.
Do you reproduce it with Glassfish ?
Comment 2 RayDeCampo 2014-02-19 19:42:54 UTC
I checked the project properties and 'Deploy on Save' is checked for all of them under the 'Run' section (except for the parent project which has no Run section).  I assume this is the default as I did not consciously configure it.  When the deployment was working under WildFly 8.0.0.CR1 on version 1.0.4 of the plugin I did not notice any deploy on save type behavior, I deployed using the 'Run' maven goal on the ear project.

I just tried again with 'Deploy on Save' unchecked for all three projects and the result was the same.

I have not tried on GlassFish, I do not have it installed.
Comment 3 RayDeCampo 2014-02-19 19:58:17 UTC
Addendum to prior comment:  I went back in to the project configurations to re-select deploy on save and I noticed that the ear and ejb projects had it checked already.  Tried to uncheck it for those projects but when I went back in it was checked again.  Not sure if this is a bug in NetBeans or what.
Comment 4 ehsavoie 2014-02-21 16:00:38 UTC
Ok, I've fixed this issue :o)
I just need to check it doesn't break simple applications.
Comment 5 Quality Engineering 2014-02-22 06:13:22 UTC
Integrated into 'main-silver', will be available in build *201402220001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/f9adbe65a371
User: Emmanuel Hugonnet <ehsavoie@netbeans.org>
Log: ng issue #242016 : Maven ear applications didn't deploy correctly.