[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] non-OSGi artifact with p2

Dmytro, here is how we do it ourselves in one case.
It is not great: we put the files in a bundle and publish a feature
with a custom p2.inf in charge of setting up those files.


I hope this helps,

On Fri, Feb 11, 2011 at 10:21 AM, Pascal Rapicault <pascal@xxxxxxxxxxxx> wrote:
> On Thu, Feb 10, 2011 at 10:11 AM, Dmytro Pishchukhin
> <dmytro.pishchukhin@xxxxxxxxx> wrote:
>> Hello All,
>> I'd like to add to my product non-OSGi artifact that contains
>> folders/configuration files/JARs that should be added to launcher classpath.
>       Without even p2 involved, I'm not sure that what you are trying to do
> is in fact possible. To add something to the launcher you need to pass
> several arguments to -startup in the eclipse.ini which I don't if it is
> possible. If you tell me in which eclipse file you need to modify (e.g.
> eclipse.ini, config.ini) then I should be able to help more.
>> How should I describe this artifact (as plugin, as zip file)? Which
>> touchpoints should I use to unzip it and change class path options?
>     If they are just a bunch of files, I think you should use a "binary"
> artifact, and the touchpoint action to drive where the unzipping should be
> done. Here is an example of XML for a similar case in the eclipse sdk.
> ATM, the main difficulty with this is that there is no tooling provided out
> of the box with p2 to create such an IU (e.g. no editor like we have for
> features) and you will have to generate the XML as part of your build.
>> Are there any samples/docs that can help me with my requirements?
>> Thank you in advance.
>> Best regards,
>> Dmytro Pishchukhin
>> _______________________________________________
>> 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