JBIDE-11319: Url for Eclipse-SourceReferences
JBIDE-15316 - Bump Webservices to version 1.6.0
TOOLSDOC-390: Ready docs for 7.1
JBIDE-15175 - Fix for one more validation issue with Simple Web Service
wizard
JBIDE-15402 - Doubled warnings Multiple JAX-RS Activators

Removed the duplicate validation at both the JaxrsApplications level and kept the one
at the JaxrsMetamodel level.
JBIDE-12860 - JAX-RS validation problems are not linked

Added a custom JAXRS_PROBLEM_TYPE attribute in JAX-RS markers.
Those JAX-RS Problem markers are now indexed with Lucene.
Thus, it becomes possible to look for resource that have the same
error as a given resource, even if this later one has been deleted.
(eg: looking for duplicate application problem after an application
has been removed).
When a JAX-RS Element is removed, its associated JAX-RS Markers are
removed from the index *during the validation phase* (the markers
still exist and are still indexed until the validation is performed).
Added some JUnit tests to verify the good behaviour againts the case
where a project has 2 JAX-RS application then one is removed.
JBIDE-15304 - NullPointerExceptions in JAX-RS doesn't report what project is affected

Printing the current java element name and parent project in the existing call to the logger
if the element is known.
JBIDE-15508 - Incorrect problem marker when refactoring a custom Qualifier

Initial problem was that *any* annotation would be taken as a JAX-RS HTTP Method,
which was über wrong.
Added tests cases to verify.
JBIDE-15505 - Exception in JAXRS at startup

Added a check for null metamodel before calling the JaxrsMetamodel#removeListener() method
JBIDE-15599 - Changes on a subresource locator fields are not propagated to the JAX-RS Explorer

Registered the URI Mappings Content Provider (in the UI) when the JAX-RS Web Services node is
expanded. This avoids the case where in some circumstances, the JAX-RS metamodel would have no
listener to notify when JAX-RS endpoints changed.

Also edited the log messages for sake of readability
JBIDE-15428 - No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

Skipping the Java ElementChangeEvents when the Java Project is not open yet. This avoids race conditions during import.
Bonus: import seem to be twice as fast as before ;-)

Other changes:
- Move the call the JaxrsMetamodel#setBuildStatus() to finally{} blocks of JaxrsMetamodel#processXXX() methods
- Adjusted some javadoc, log messages and catch() blocks (avoiding to catch Exception or Throwable)
- Added a ReadWriteLock on all public methods of the JaxrsMetamodel to avoid concurrent access to the metamodel by different threads, for example if an async build
is still running and the validation is started. This avoids the following type of error:

{code}
!ENTRY org.jboss.tools.common 4 0 2013-10-09 18:17:54.307
!MESSAGE
!STACK 0
org.jboss.tools.common.validation.JBTValidationException
	at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)
	at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
	at java.util.HashMap$ValueIterator.next(HashMap.java:822)
	at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validateAll(JaxrsMetamodelValidator.java:268)
	at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:153)
	at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117)
	at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81)
	... 2 more
{code}

- added some tests to increase code coverage
JIBDE-12860 - JAX-RS validation problems are not linked

Fixed the problem where some markers would not be removed from the resource to be validated between
two validation calls, which meant that duplicate markers for the same problem would exist on each
resource.

Also refactored the search/element retrieval: the JaxrsElementIndexationDelegate now not only
deals with the Lucene indexation and searches, but also uses the metamodel to return List of
JAX-RS elements, Endpoints or workspace Resources.
Renamed some marker deletion/undexing methods to use the "remove" verb (eg: "removeMarker()") and be consistent with the
existing "remove()" methods that remove the elements themselves.
Added JUnit tests to covers the fixes.

This patch also fixes:
- JBIDE-15662: Warning Multiple JAX-RS Activators doesn't disappear
- JBIDE-15664: Application path configured in web.xml causes warning
JBIDE-15839 - Exception while saving Provider in JAX-RS application

Fixed the problem which occurred only when the problem severity as set to
'ignore' level. In that particular case, no IMarker would be created, thus
returning a null reference, which lead to NPE.

Added JUnit tests to cover all ways to create JAX-RS Markers.
JBIDE-15908 - Problem decorator is not removed after error was fixed

Bug was that the problemLevel on each JAX-RS Resource Method would not
be reset at the beginning of the validation, and during validation, the
highest problem level is kept. Thus, during the next validation (fixing
the problem), the problem level would remain at its highest (previous)
value.

Added tests to verify the correct behaviour on all validators.