[p2-dev] changing the configuration area

[Rupert Gratz <rupert.gratz@xxxxxxxxxxxxx>]

Hi There,

We repeatably run into a worrisome issue since we enabled p2 in our product:

What many developers/testers do over here is changing the default
configuration area by passing an option to the startup executable:
"-configuration /tmp/myConfig"

Thats where the problem arise:
some folders/files will be created here:
 @config/../ (which is in the case above: /tmp/ !)

a p2 folder will be created there - Of course we can change that
behavior in the config.ini file.
However when one installs additional software, features/plugins will be
stored here @config/../ anyway no matter where the users p2 folder is
being located.

The only solution for us, so far, is to specify the configuration area
by adding a sub folder: "-configuration /tmp/myConfig/conf"

Is this the only solution to get rid over this problem?
Do we have any possibilities to customize our product in anyway so we
can get rid of this problem?
- we can change the location of the user's p2 folder - OK
- Whats with the artifacts.xml which is being created here @config/../
- and additional installed software  (features/plugins) ??


Thanks for any hints,
Rupert