[PATCH] Only renaming base projects not any sub projects. 384510

Signed-off-by: Fred Bricon <fbricon@gmail.com>
organize imports

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
350414 have a workspace preference (export/import-able) to ignore some lifecycle mappings
This commit contains most of the work for bug 350414.
This includes adding workspace settings to the chain
of lookups for determining lifecycle mappings for m2e
projects. There are changes to existing quickfixes,
and a new workspace preferences page that allows users
to view their workspace mappings and edit the raw text file.

There is partial work done for displaying a table of workspace
lifecycle mappings in the preferences page.  The refactoring
of the project lifecycle mappings table is complete, but I
just don't know how to populate the viewer with workspace
mappings only

For compliance with Eclipse.org's contribution rules:
(1) I (Andrew Eisenberg) wrote 100% of the code;
(2) I have the right to contribute the code to Eclipse;
(3) the file header contains the appropriate License header.

Also, this patch is built on top of the SHA 170c7936da947d28e7824bc1d2375903dbda9b17
suppressed NPE during prerefence store initialization

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
restored lifecycle mapping project properties page

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
387151 do not associate pom editor configuration with all xml files

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Update maven plugin templates

- bumped maven-compiler-plugin version to 2.5.1
- fixed default maven-war-plugin>failOnMissingXml to true

Signed-off-by: Fred Bricon <fbricon@gmail.com>
350414 separate quick-fix for workspace mapping; cleanup

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
cleanup

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
do not modify singleton PluginExecutionMetadata instances

The same shared PluginExecutionMetadata read from installed
m2e extensions, including default m2e mapping metadata, are
used for entire lifespan of m2e instance. Do not modify these
instances, create a clone instead.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
350414 show mapping source in project properties

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
comment cleanup

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
more obvious ways to control lifecycle mappings view

right-click menu was hard to find. to make them easier to fine,
moved all menu actions to separate controls above mapping treeviewer.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
387396 fixed null mapping source for embedded maven plugin metadata

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
No need to look the same instance up 3 times in the same method

Signed-off-by: Fred Bricon <fbricon@gmail.com>
359855 Resolve archetypes using their remote repo

Archetype source repository is now used to resolve archetypes from remote
repos. The fix implies calling LegacySupport to properly set the Maven
session for archetype resolution, which was causing the NPE for local
archetypes with required properties.

Properly setting the remote repo also fixes bug 371775

Signed-off-by: Fred Bricon <fbricon@gmail.com>
cleanup: removed eclipse 3.2 compatibility hack

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
350414 more workspce lifecycle mapping fixes and tweaks

In no particular order
* cache workspace lifecycle mapping metadata for faster
  mapping
* read-modify-write to minimize chance of loosing on-disk
  mapping
* Reload metadata preference button
* Mapping metadata file location is configurable again
* Mapping file location is not validated but missing
  file is gracefully tolerated everywhere

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
Fix for issue 387252: Never rename directory when using MavenImportWizard