doc fix to indicate comma seperation
On ant warnings/errors, add which project it is related to
Ouch, runfw was not handled correctly.
#381: Reinstated the 999999 version when the directory only contains a latest.
The bnd internal cache needs this feature to find the launcher
and the junit tester. If there is at least one version in the file repo
it will not show the 99999
Offline we build 1.5 but the eclipse settings were
still jsr14. Unfortunately, this made Java 1.8 say 
that it could not FIND (not load, FIND, idiots)
the aQute.launcher.Launcher.

It would be nice if (BJ?) someone could use the same
trick as we do in the osgi build, get the properties
from the .settings.
Do not run OSGi tests unless the Test-Cases macro is set
When starting baselining, I made the release
repo the same as the baseline repo and that is wrong.
Merge pull request #402 from derheld42/docfix

Doc update on -runvm arguments being comma seperated
Merge pull request #400 from derheld42/addwarningserrors

Add project name to ant warnings/errors
Allow a URL to be used as argument to put
These reps should not be there, they should come from
bnd itself.
Add two properties project.junit and project.junit.osgi
to indicate if junit tests and/or OSGi junit tests can
be run. The default is that junit tests depend on
the test src directory and the junit OSGi tests depend
on the Test-Cases macro. Despite their presence, it
is possible to not run them with -nojunit and -nojunitosgi
properties set to true.
New urls
Also downloading repoindex
Wrong property name
Get rid of warning