Removed resource warnings
Command execution generated errors during the writing
of the command output. So I changed this to execute
inline with the doIncludeResource handling, seeing
any errors early. It also turned out that the build
got screwed if an exception was raised during write. Fixed
this as well.
New version for testing
Fixes #338 - Parsing of bnd @Component properties cannot handle an array
with a single value
Attempt to support profiles in package command

There were 2 profiles, one for the configurer (not bnd
related) that was set by bnd as "profile" and we have
the standard bnd "-profile" :-( Now will set the
-profile in bnd before packaging so we should see
the profiled properties. Also fixed a bug, the
Did not contain any code, tests are in launcher test
Changed method remove on Consumer Type to be a MAJOR 
event after discussion. Though the provider is not
affected, not only the provider could use this interface.
1) Moved the package code to Project
2) Added a -jpm to package that allows jpm to store the bundles

Will not change existing projects, new functionality
will need some more testing.
The plugin can now accept a -package: jpm option. This
will then not store the jars of the bundles but store
the sha in a header
The paths in the properties file are platform specific
when launched normally. However, with the SHA's we
have generic (/ based) file paths that can contain
macros. Convert a generic path to . If no macro is
present, we assume native, otherwise we convert it
from generic.