|Re: Force p2 materializer to always create and activate a new target platform [message #629575 is a reply to message #629567]
||Tue, 28 September 2010 14:29
| Thomas Hallgren
Registered: July 2009
The easiest way to accomplish this is to create an empty directory and
then do setpref targetPlatformPath=<empty dir>. This ensures that you
have an empty, and active, target platform.
Combine that with an mspec that doesn't have an install location set and
it will default to the currently active target platform. Alternatively,
don't use an mspec at all and control what goes where using
source="true/false" in the RMAP providers. The result is the same, p2
materialized components end up in the active TP.
On 09/28/2010 07:59 PM, Markus Alexander Kuppe wrote:
> is it somehow possible to force the p2 materializer in a .mspec to
> always create a fresh target platform and set it to active irregardless
> of the currently active TP?
Powered by FUDForum
. Page generated in 0.10289 seconds