commit | 10499440c010096072234d08d5a33aad8c462940 | [log] [tgz] |
---|---|---|
author | Fred Bricon <fbricon@gmail.com> | Tue Aug 13 21:02:21 2013 +0200 |
committer | Fred Bricon <fbricon@gmail.com> | Wed Aug 14 00:46:35 2013 +0200 |
tree | 1cc7db663202abb64c37326596a0771cd33c8bf8 | |
parent | 1dec88e1012c5b68931986ca3c2ab956094c2cc5 [diff] |
413925 : regen. application.xml after clean build The fix allows the application.xml to be regen'd after a Maven 'Project Update...' with the clean flag enabled (Using the Alt-F5 shortcut). However, for some reason, the ear-resources folder is not refreshed properly, i.e. disappears from the 'Deployed Resources' node. It's sometimes correctly refreshed, but it's rare. A simple refresh (F5) on the project root is enough to refresh the 'Deployed Resources' node with the gen'd resources. Removing the ProjectUtils.hideM2eclipseWtpFolder(mavenProject, project) call from EarProjectConfiguratorDelegate.configure() doesn't change anything. Web projects don't suffer from the same issue. Signed-off-by: Fred Bricon <fbricon@gmail.com>
Maven Integration for Eclipse WTP, a.k.a m2e-wtp, aims at providing a tight integration between Maven Integration for Eclipse (a.k.a m2e) and the Eclipse Web Tools Project (WTP) .
m2eclipse-wtp provides a set of m2e connectors used for the configuration of Java EE projects in WTP. It features :
Note that m2e-wtp requires m2e > 1.0. You must make sure m2e's update site (http://download.eclipse.org/technology/m2e/releases/) is defined in : Window > Preferences > Install / Update > Available Software Sites Since m2e 1.0 is incompatible with previous versions, you may have to uninstall old m2e and m2e-wtp versions before proceeding with the installation.