[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [p2-dev] How to install the launcher during theinitialprovisioning
|
Hi Helmut,
That was exactly it, thank you very much
Shame on me.... :-(
But I said I only started with P2 ;-)
Note to self: ID's need to have Plugin/Product/App in their name to
distinguish them.
Thanks again and best regards,
CarsteN
On Thu, 16 Jul 2009 15:25:31 +0200, "Haigermoser, Helmut"
<Helmut.Haigermoser@xxxxxxxxxxxxx> wrote:
> In the rcpmail example, the plug-in id is "RCPMail", guess you tried to
> install the plug-in "RCPMail", not the product.
> Try specifying a product id and install that one.. :)
> HTH,
> Ciao, hh
>
> -----Original Message-----
> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Carsten Nikiel
> Sent: Thursday, July 16, 2009 2:35 PM
> To: P2 developer discussions
> Subject: RE: [p2-dev] How to install the launcher during
> theinitialprovisioning
>
>
> Hi Helmut,
>
> please do not laugh, but I can now create a launcher again.
> The only thing I did was to create an empty product configuration, e.g.
> one that was not based on the application I created form the template.
>
> Anyway here is the way to reproduce it (for everything I used the
> default settings, NOTHING was changed):
> 1) Create a new workspace
> 2) Create a new product based on the RCP Mail Template
> 3) Create a product configuration with an empty product configuration
> 4) Make sure the "..native launcher artifacts" is checked
> 5) Choose the RCPMail product and the application from the newly created
> plugin
> 6) In the "Dependencies" tab I selected the new plugin and used "add
> required plugins"
> 7) Used the "Eclipse Product export wizard" to export everything to a
> directly that I can access from my web server.
>
> Once finished I start a small bat file that contains this:
>
> c:\programme\eclipse\eclipse.exe -application
> org.eclipse.equinox.p2.director ^ -metadataRepository
> http://localhost/Test/repository ^ -artifactRepository
> http://localhost/Test/repository ^ -installIU RCPMail ^ -destination
> C:\Temp\Test ^ -bundlePool C:\Temp\Test ^ -profile profile ^
> -profileProperties org.eclipse.update.install.features=true ^ -p2.os
> win32 ^ -p2.ws win32 ^ -p2.arch x86 ^ -consoleLog ^ -roaming ^ -debug ^
> -vmargs ^ -Dosgi.noShutdown=true
>
> This installs all plugins but not the launcher and I have no idea how to
> do that.
> These steps should be reproducable, if not please let me know.
>
> Thanks for the help and cheers,
>
> CarsteN
>
>
> On Thu, 16 Jul 2009 13:51:07 +0200, "Haigermoser, Helmut"
> <Helmut.Haigermoser@xxxxxxxxxxxxx> wrote:
>> Ciao Carsten :)
>> The weird thing here is that the product export result itself is
>> already a p2 installation, so first the repo is created and then the
>> director creates the install.
>> So, the bug probably lies in your invocation of the director, are you
>> maybe not setting os,arch,ws right?
>> HTH,
>> Ciao, hh
>>
>> -----Original Message-----
>> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Carsten Nikiel
>> Sent: Thursday, July 16, 2009 1:24 PM
>> To: P2 developer discussions
>> Subject: RE: [p2-dev] How to install the launcher during
>> theinitialprovisioning
>>
>>
>> Hi Helmut,
>>
>> guess I will have to come back to this issue a bit later. :-( Because
>> now I can not even create the launcher executable in the first place.
>> I tried to start from scratch again to get a step by step approach for
>
>> you to follow, but now I am stuck at creating the launcher.
>>
>> Here is what I did so far. (using eclipse 3.5 by the way).
>> Created a new workspace (clean of everything) Created a new plugin
>> project with the RCP Mail template (default settings nothing changed)
>> Created a product configuration (default settings nothing changed,
>> excpet for the Product ID which needs to be given, made sure the
>> "...native launcher..." checkbox was enabled)
>>
>> Used the "Eclipse Product export wizard" with a directory that is
>> loacted in the public_html of my local webserver, for direct
>> installation by the director application.
>>
>> And now I am stuck with no launcher. Even giving it a specific name
>> did not work.
>> Must have done something different yesterday, as then it worked and I
>> got an eclipse.exe in the export directory.
>>
>> If you should have a quick solution to this I am all ears, otherwise I
>
>> will go back to point zero and try to get the launcher working on my
>> own.
>>
>> To answer your questions:
>> Eclipse 3.5
>> The checkbox was enabled
>> The binary directory did contain (and still does) the launcher files.
>> Just
>> the .exe file (plus the config files) in the main directory is missing
>
>> now.
>>
>> Thanks for your time and help.
>>
>> Cheers,
>>
>> CarsteN
>>
>>
>> On Thu, 16 Jul 2009 10:18:22 +0200, "Haigermoser, Helmut"
>> <Helmut.Haigermoser@xxxxxxxxxxxxx> wrote:
>>> Ciao Carsten :)
>>> Sounds like the export operation is including the launchers, but they
>> do
>>> not end up in the repo.
>>> Some more questions:
>>> - What Eclipse version is this?
>>> - In the product config editor, did you checkmark "The product
>> contains
>>> native launcher artifacts" (@see attached pic)?
>>> - In the repo, do you have a "binary" dir, containing things like
>>> "org.eclipse.equinox.executable_root.carbon.macosx.ppc_<version" or
>>> <product name>.launcher.gtk.linux.x86_<version>?
>>> - If nothing seems to work, can you attach the files
>>> content.[jar|xml] and artifacts.[jar|xml] for us to review?
>>> - Finally, can you wrap up the problem in a simple "Steps to
>> reproduce"?
>>> HTH,
>>> Ciao, hh
>>>
>>> -----Original Message-----
>>> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
>> On
>>> Behalf Of Carsten Nikiel
>>> Sent: Thursday, July 16, 2009 10:08 AM
>>> To: P2 developer discussions
>>> Subject: RE: [p2-dev] How to install the launcher during the
>>> initialprovisioning
>>>
>>>
>>> Hi Helmut,
>>>
>>> Thanks for the answer.
>>>
>>> But I am not sure what you mean.
>>> I do have the delta packs installed, that's why I can export the
>> product
>>> and get a layout like this in the directory I exported to:
>>>
>>> artifacts.xml
>>> configuration/
>>> eclipse.exe
>>> eclipse.ini
>>> p2/
>>> plugins/
>>> repository/
>>>
>>> I used the default settings to export the product itself. To install
>> the
>>> plugins I use the director application and point it to the repository
>
>>> directory. Otherwise it would not even consider installing anything.
>>> In that directory there is no launcher eclipse.exe, so I am wondering
>> if
>>> there is any p2.inf magic that I need to use to get these files
>>> installed too, as they seem to be outside of the repository and I can
>
>>> not get them into this directory.
>>>
>>> Well I am new to p2 and therefore it might very well be possible that
>> I
>>> did some obviously silly error.
>>>
>>> Cheers,
>>> CarsteN
>>>
>>>
>>>
>>> On Thu, 16 Jul 2009 09:36:18 +0200, "Haigermoser, Helmut"
>>> <Helmut.Haigermoser@xxxxxxxxxxxxx> wrote:
>>>> Ciao Carsten :)
>>>> Launchers are included in the deltapack, did you include that one in
>
>>>> your build?
>>>> HTH,
>>>> Ciao, hh
>>>>
>>>> -----Original Message-----
>>>> From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx]
>>>> On Behalf Of Carsten Nikiel
>>>> Sent: Thursday, July 16, 2009 7:41 AM
>>>> To: p2-dev@xxxxxxxxxxx
>>>> Subject: [p2-dev] How to install the launcher during the initial
>>>> provisioning
>>>>
>>>> Hello,
>>>>
>>>> for quite some days now I am trying to setup the simple RCP Mail
>>>> product with P2 and it seems I can't figure out how to include the
>>>> launcher in the repository.
>>>>
>>>> What I got after some fiddling is a repository with all the plugins
>>>> and Jars I need for P2 to allow me to install it from somewhere
> else.
>>
>>>> So far so good.
>>>>
>>>> But I can not get the launcher to be installed alongside the
> plugins.
>>
>>>>
>>>> If I copy the launcher and the companion libs to the newly
>>>> downloaded
>>
>>>> installation everything works.
>>>>
>>>> Is there any documentation (which I am just too blind to find) that
>>>> explains how to include some additional files to the repository and
>>>> have them installed during the normal directory.app installations?
>>>>
>>>> Any help is appreciated.
>>>>
>>>>
>>>> Thanks, Carsten
>>>>
>>>>
>>>> PS: Tried at first the equinox-dev mailing list, but was adviced to
>>>> try here.
>>>>
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> 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