Simplified the bnd baseline command so that when
you're in a project directory it runs the project
baseline. I.e. you no longer have to specify the
two jars, it derives them from the project info.
Seems we had some false caching. Less efficient
but also less error by redoing it always. And he,
this is on the client so who cares, enough horse
power there.
Not sure what I had been smoking when writing this class. It was
a total disaster with subsets. Fixed most, added some (but too few)
tests. :-(
Added a facility to add error details to the location
so that the user of bnd can find easy to process
details. Each message has an associated Location
object (Processor.getLocation(msg)). This location
now has a 'details' object. Example where used
is the Baseline, the Baseline.Info is now set
as the details for a baseline error.
Changed the algorithm to find the baseline for
baselining. This is a breaking change since 
I removed functionality. The old way had a boolean
that selected a fallback or not. I think this was
too confusing and should in general not affect 
anybody. However, need to talk to PK about the
consequences because I think he was responsible.

See #356
Ouch, still smoking. Now verified against normal list
Not all repos return a file ...
Still some problems with GenericArray and byte. Seems fixed now
Added a macro that gets a repository digest

A repository digest is a unique digest representing
the contents of a repo. It is calculated by taking the
sha-1 of its contents, sorting them, removing duplicates
and then digesting them with sha-1. The macro
visits all repositories and any repo with a getDigest
method is added to the list.

jim can use this to calculate the dependencies.
adapt Javadoc to implementation: manifest must be set by caller
Added resolution callback API
Additional methods on RepositoryListenerPlugin
Copy locations from sub-builders to higher processor
Issue #355 Allow Metatype annotations to be found on parent interfaces.
Improved null handling in SortedList.toArray
Only complain about having the same version as the baseline when the bundle is actually changed. Using last modified from the baseline and current bundle.
Fixed #359 by making sure that the last modified date of the folders in the class path gets propagated to the target Jar, making sure that class files that have disappeared still trigger the last modified date to be updated.
Add: Get last revision for Release from bndtools
Fix #687: OS version must not be parsed with an OSGi-version parser

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>
Processor: use some predefined strings in the native_capability macro

Signed-off-by: Ferry Huberts <ferry.huberts@pelagic.nl>