Ok - so I retraced my steps to see exactly why I ended up in the creek with this, and discovered that it was indeed the Websphere 8.5 Development Tools. When I install it, it provides a more explicit JEE->Maven configuration screen.
The interesting thing is that it provides and option to set all the default paths for JEE applications using Maven standards (ie: src/main/webapp instead of WebContent), but when it comes to the application.xml and archiver files, it only provides the option to set the Maven value to false for generating in the build directory: [image: Inline image 1] A setting of "true" shows a warning that it isn't the recommended value. Shouldn't the recommended value be "true"? Shouldn't the recommended process be to generate them in the build directory? Why is there even the option in the interface? Thanks, Eric On Thu, Feb 18, 2016 at 8:04 PM, Eric B <ebenza...@gmail.com> wrote: > Don't I feel like the NOOB. I can't believe I missed that! Nor can I > believe how much time I wasted reinstalling m2e! I wonder what could have > possibly caused the preference change. > > Thanks for pointing it out. > > On Thu, Feb 18, 2016 at 5:04 PM, Fred Bricon <fbri...@gmail.com> wrote: > >> Try Preferences > Maven > Java EE integration > check `Generate >> application.xml under the build directory` >> >> On Thu, Feb 18, 2016 at 4:08 PM, Eric B <ebenza...@gmail.com> wrote: >> >>> I have no idea what I did to break my m2e/m2e-wtp installation, but my >>> maven project is now generating my application.xml file in my >>> src/main/application/META-INF folder. It used to properly generate it in >>> my target/m2e-wtp/ear-resources/META-INF folder (where it belongs). >>> >>> I've spent half the afternoon uninstalling/reinstalling plugins, but >>> haven't really managed to progress. >>> >>> I've got m2e 1.5.2, with m2e-wtp 1.0.1 (yes - both old version - I know) >>> installed. >>> >>> I _believe_ the issue started after installing the WebSphere 8.5 for >>> Juno plugin via the Eclipse Marketplace, but I have since removed that, and >>> removed my m2e/m2e-wtp and reinstalled them. Including a "-clean" when >>> starting Eclipse. >>> >>> My pom itself hasn't changed. The effective-pom shows: >>> >>> <plugin> >>> <artifactId>maven-ear-plugin</artifactId> >>> <version>2.10.1</version> >>> <executions> >>> <execution> >>> <id>default-ear</id> >>> <phase>package</phase> >>> <goals> >>> <goal>ear</goal> >>> </goals> >>> <configuration> >>> <version>5</version> >>> <defaultLibBundleDir>lib/</defaultLibBundleDir> >>> <skinnyWars>true</skinnyWars> >>> <earSourceExcludes></earSourceExcludes> >>> <modules> >>> <webModule> >>> <groupId>com.sbic</groupId> >>> <artifactId>ComWeb</artifactId> >>> <contextRoot>ComWeb</contextRoot> >>> </webModule> >>> </modules> >>> <useBaseVersion>true</useBaseVersion> >>> <packagingIncludes>**/*</packagingIncludes> >>> <encoding>UTF-8</encoding> >>> </configuration> >>> </execution> >>> <execution> >>> <id>default-generate-application-xml</id> >>> <phase>generate-resources</phase> >>> <goals> >>> <goal>generate-application-xml</goal> >>> </goals> >>> <configuration> >>> <version>5</version> >>> <defaultLibBundleDir>lib/</defaultLibBundleDir> >>> <skinnyWars>true</skinnyWars> >>> <earSourceExcludes></earSourceExcludes> >>> <modules> >>> <webModule> >>> <groupId>com.sbic</groupId> >>> <artifactId>ComWeb</artifactId> >>> <contextRoot>ComWeb</contextRoot> >>> </webModule> >>> </modules> >>> <useBaseVersion>true</useBaseVersion> >>> <packagingIncludes>**/*</packagingIncludes> >>> <encoding>UTF-8</encoding> >>> </configuration> >>> </execution> >>> </executions> >>> <configuration> >>> <version>5</version> >>> <defaultLibBundleDir>lib/</defaultLibBundleDir> >>> <skinnyWars>true</skinnyWars> >>> <earSourceExcludes></earSourceExcludes> >>> <modules> >>> <webModule> >>> <groupId>com.sbic</groupId> >>> <artifactId>ComWeb</artifactId> >>> <contextRoot>ComWeb</contextRoot> >>> </webModule> >>> </modules> >>> <useBaseVersion>true</useBaseVersion> >>> <packagingIncludes>**/*</packagingIncludes> >>> <encoding>UTF-8</encoding> >>> </configuration> >>> </plugin> >>> >>> >>> I've tried removing the maven nature, deleting the .project, target and >>> .settings folders, deleting the project and reimporting it as a maven >>> project. And yet, this issue of generating the application.xml in my src >>> folder continues. >>> >>> Anyone have any clues? >>> >>> Thanks, >>> >>> Eric >>> >>> >>> >>> >>> _______________________________________________ >>> m2e-users mailing list >>> m2e-users@eclipse.org >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >> >> >> >> -- >> "Have you tried turning it off and on again" - The IT Crowd >> And if that fails, then http://goo.gl/tnBgH5 >> >> _______________________________________________ >> m2e-users mailing list >> m2e-users@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > >
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
