[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Creating P2's default profile

Hello Anthony, Devs,

thank you very much for the explanation. It helped a lot to understand
what's going on.

I used the target platform editor and on the first launch of my target
a profileRegistry with a weirdly named profile
"TARGET_DEFINITION%58;local%58;1309224216952.target.profile" was
created in my workspace. On the next step, I pointed
eclipse.p2.data.area to the directory of this profile and it was
recognized in the osgi console (appeared in "provlp").

I then tried to install an IU with provinstall "name" "version", which
didn't work because the command complains about a missing profile. I
tried again with provinstall "name" "version" "profileId", which
worked. After calling confapply my IU / plugins are now installed (?)
in the profile (they appear when calling "provlp profileId"). Anyway,
I'm not able to see the new plugins in ss or bundles and couldn't find
a way to start/stop them. Did I do something wrong, or how are bundles
in p2 profiles managed?

Thanks again,

Sebastian


On Mon, Jun 27, 2011 at 4:54 PM, Dahanne, Anthony
<Anthony.Dahanne@xxxxxxxxxxxxx> wrote:
> Hello Sebastian,
> I guess you should rather use an existing p2 profile.
> When you created your target platform, a default profile might have been provisioned.
> If you created it from inside eclipse, using the target platform editor (and set as target button), the p2 profile artifacts should be in ${workspace}/.metadata\.plugins\org.eclipse.pde.core\.p2
> If you created it from a product, then the usual path should be used : ${base directory}/p2
> Once you have located your profile directory, you can reference it from your runtime, using the right VM arguments as seen in [1] :
> -Declipse.p2.data.area=C:/testBuild/eclipse/p2/
> -Declipse.p2.profile=SDKProfile
>
> You can replace SDKProfile with the name of your profile which is PROFILE_NAME:
>  {p2 directory}/org.eclipse.equinox.p2.engine\profileRegistry\{PROFILE_NAME}.profile
>
> Hope it helps !
> Anthony
>
>
>
>
>
>
>
> Le contenu de ce courriel s'adresse au destinataire seulement. Il contient de l'information pouvant être confidentielle. Vous ne devez ni le copier ni l'utiliser ni le divulguer à qui que ce soit à moins que vous soyez le destinataire ou une personne désignée autorisée. Si vous le receviez par erreur, veuillez nous aviser immédiatement et le détruire.
>
> The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
>
>
> De : p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] De la part de Sebastian Schmidt
> Envoyé : 27 juin 2011 09:13
> À : p2-dev@xxxxxxxxxxx
> Objet : [p2-dev] Creating P2's default profile
>
> Hi,
>
> I'm trying to install an IU to P2's default profile using the P2
> console as described here [1]. Unfortunately, the default profile
> isn't created during the first start up of my target platform. I
> searched the mailing lists and tried several ways to achieve this
> (using eclipse.p2.profile and eclipse.p2.data.area arguments for
> example).
>
> Which dependencies are needed for P2 to create the default profile?
> Perhaps I missed to include something. This is the list of running
> bundles on my target platform: [2]. Otherwise, what else can I do to
> debug why the default profile isn't there?
>
> Thanks for any help,
>
> Sebastian
>
> [1] http://wiki.eclipse.org/Equinox_p2_Console_Users_Guide
> [2] http://pastebin.com/BuyC3eCa
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>
>
> _______________________________________________
> p2-dev mailing list
> p2-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/p2-dev
>