[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] p2 Engine

Hi Scott,

Jeff and I had a chat about the issue you were encountering. Did you eventually get that to work?
To wrap up, I would appreciate if you could briefly say what was the problem and the solution you used.

Thx

PaScaL

Inactive hide details for Scott Lewis ---03/30/2009 11:06:46 AM---Hi Pascal, Thanks for the info.  Question:  Where in the engiScott Lewis ---03/30/2009 11:06:46 AM---Hi Pascal, Thanks for the info. Question: Where in the engine commit should the


From:

Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>

To:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

03/30/2009 11:06 AM

Subject:

Re: [p2-dev] p2 Engine




Hi Pascal,

Thanks for the info.  Question:  Where in the engine commit should the
new bundles (those in IU) be detected/added as needing to be written to
the bundles.info?

Thanks,

Scott


Pascal Rapicault wrote:
>
> For bundles to be installed in OSGi, a CU indicating to do so needs to
> be attached to the IU representing the bundle.
> Most of the time, the tooling.osgi.bundle.default CU is all you need
> since it just installs a bundle at start level 4 and does not start it.
> This attachment is represented by a ResolvedIU which has the original
> IU and the additional fragments.
> Note that normally the planned returned by the director will contain
> the proper attachment if of course the CUs had been passed to it.
> Also you should be able to find an example of this in Jeff's code
> presented in the Runtime Revolution talk where the director remotely
> talks to the engine.
>
> HTH
>
> PaScaL
>
> Inactive hide details for Scott Lewis ---03/30/2009 03:13:26 AM---I've
> been sending an IU and invoking the p2 engine from an exScott Lewis
> ---03/30/2009 03:13:26 AM---I've been sending an IU and invoking the
> p2 engine from an external process, in order to install IU
>
>
> From:
> Scott Lewis <slewis@xxxxxxxxxxxxxxxxx>
>
> To:
> P2 developer discussions <p2-dev@xxxxxxxxxxx>
>
> Date:
> 03/30/2009 03:13 AM
>
> Subject:
> [p2-dev] p2 Engine
>
> ------------------------------------------------------------------------
>
>
>
> I've been sending an IU and invoking the p2 engine from an external
> process, in order to install IU's into a running system.
>
> I've determined that the IU that I am attempting to install on the
> remote engine:
>
> 1) Is of type ResolvedInstallableUnit
> 2) The IU's contents get successfully written to the remote profile
> (i.e. the profile gets updated)
> 3) The plugin artifacts get downloaded/written to plugins directory
> 4) The simple configurator manipulator does *not* write the new plugins
> in the IU to the bundles.info (this means that confapply does *not*
> install the plugins in the IU).
> 5) The engine does commit successfully, and I can see that the Eclipse
> touchpoint is calling the simple configurator manipulator to write out
> the new bundleInfos.  But the bundleInfos list that is used by the
> simple configurator does *not* contain the new bundles (those in the
> IU).  It does seem to contain all of the original bundles in the profile.
>
> Does anyone have any pointers to look for why the new bundleInfos does
> not include the new IU's plugins?  Where should one look in the engine
> to determine why the IU's bundles are not being included in the
> bundles.info list?  I can see that it's not ever changing.
>
> Thanks,
>
> Scott
>
>
> _______________________________________________
> 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
>  

_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev


GIF image

GIF image