[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] Director produces unwanted "SDKProfile" profile?
- From: Fredrik Alströmer <roe@xxxxxxx>
- Date: Tue, 17 Mar 2009 15:37:42 +0100
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=Tk/W2tHPYJSQMjZhBQPXvvfN2KYCP3AncpHTHPZHZZbUBH970DktFZI13W6dvsyvFf ZWCcZt7F8EJeO6tc127dQss4zboz12gMGg8t716AIKzwRo91lYhFoUXBffxfKkzRSg+b UEfcDgFceGt1ht/NU8W7JSrKhq/PGHiRyluoM=
Hi, me again,
I got my other problems figured out (was a signature verification
failure due to me having imported a plugin with sources into my
workspace), now I've upgraded to 3.5M6 and I noticed that running the
director to 'bootstrap' an installation creates a profile 'SDKProfile'
in addition to the one I specified on the commandline (-profile), not
my configuration is generated correctly, so my product is launched
with the correct profile.
Why is the SDKProfile-profile created, does it serve a purpose? (It
wasn't created when performing the same steps in M5) Could it be that
something 'accidentally' got installed into the wrong profile?
What's worse, the SDKProfile contains a 'p2.cache' property pointing
to (absolute path) the eclipse installation that I used do the
bootstrap, which it complains about not being able to find at startup.