introduced CompositeIndex#identifyAll method

this is useful when local repository index contains partial artifact
information. for example, local repository index may only have details
of the main artifact, while remote index(es) also provide information
about attached sources and javadoc artifacts.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
minor tweaks to m2e.jdt implementaton extensibility

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
guard against NPE in EclipseWorkspaceArtifactRepository

NPE happened for projects that did not have existing output folder

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
introduced new flavour of AbstractProjectConfigurator#addNature

the new flavour accepts updateFlags parameter that allows finer
control over new nature creation.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
394525 explicit configuration of project lifecycleMappingId

Introduced new ResolverConfiguration#lifecycleMappingId attribute.
If the attribute is not null, the ILifecycleMapping with specified
id will be used regardless of any other lifecycle mapping metadata
applicable to the project.

The new attribute is meant for m2e exploiters and is not and most
likely will not be exposed via user-accessible UI.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
395033 allowed maven versions [3.0,) as workspace runtime

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
395433 changed default <runOnIncremental> to false

In order to make m2e less prone to endless workspace builds,
<execute/> lifecycle mapping will only run on full/clean builds by
default. Explicit runOnIncremental=true is required to execute
mapped plugin execution during incremental workspace build.

Existing projects and maven plugins that correctly use old default
baviour will need to be updated... which is not nice, but I think
this is justified by improved overall m2e stability. We should have
made this change in 1.0.100...

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
368212 hide ISourceLookupDirector as a workaround

The problem described in 368212 caused by JDT debug ui unnecessary
and inappropriately handling ISourceLookupDirector implementations.
By wrapping ISourceLookupDirector in a simple ISourceLocator, m2e
suppresses this special handling.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
removed stale snapshot build deploy info

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
moved site publishing to 'install' phase

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
368212 reverted 7580c5cf to expose ISourceLookupDirector

Multiple code paths in jdt.debug only work with ISourceLookupDirector
implementation, so hiding it is not really an option.

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
374742 : limit conversion to specific packagings

AbstractProjectConversionParticipant can now declare a set of supported
Maven packagings, contributed via an extension point.

The conversion manager now checks the requested packaging is compatible
with a given conversion participant. If no restrictions are defined or the
given packaging is listed in the restricted packagings, then it's considered
compatible.

For JDT project conversion, only the jar packaging is
defined by default for org.eclipse.m2e.jdt.javaProjectConversionParticipant.

So if a Java Project is converted to an eclipse-plugin for instance, since
eclipse-plugin is not declared as compatible packaging for
 org.eclipse.m2e.jdt.javaProjectConversionParticipant by default, no
maven-compiler-plugin configuration will be added during the project
conversion.

More compatible packagings can be declared, if necessary, by 3rd party
plugins, using the <conversionParticipantConfiguration> element.
<compatiblePackagings> is optional since the extension point could be used
to add additional restriction policies
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=388981).

It's recommended AbstractProjectConversionParticipant implementations
declare at least one restricted packaging, as 3rd party plugins could
introduce restrictions when none were originally declared.

Signed-off-by: Fred Bricon <fbricon@gmail.com>
394480 Eliminate duplicated MavenUpdateRequests
394480 fixed stale registry recover order, minor cleanups

Signed-off-by: Igor Fedorenko <igor@ifedorenko.com>
395144: The install artifact wizard does not process POM in different location

Changes to be comitted:
	Modified: MavenInstallFileArtifactWizardPage.java

- I wrote 100% of the code
- I have right to contribute Eclipse
- I have updated the header
395396 Non externalized string in Checkout Maven Projects from SCM wizard

- I wrote 100% of the code;
- I have the right to contribute the code to Eclipse;
- The file header contains the appropriate License header
397135 : fix projectConversionParticipants.exsd

Signed-off-by: Fred Bricon <fbricon@gmail.com>
396498 : fix path to m2e refactoring icon

Signed-off-by: Fred Bricon <fbricon@gmail.com>
395147:The data from the pages of New Maven Project wizard is not persisted

Changes to be committed:
	modified: MavenProjectWizardArchetypePage.java

- I wrote 100% of the code
- I have the right to contribute the code to Eclipse
- I have updated the header
removed workaround for long-fixes jdt bug 154071

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