[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Trying to make sense of agent, installer and director

The installer and the p2agent are both examplary applications that here to show the possibilities offered by p2. That said it worth opening bugs for things that are causing you troubles.
For 1) you need to start the p2agent specifying the location of the profile registry that manages you install contained in c:\foo. You can do this by setting -Declipse.p2.data.area.
For 2) I think this may just be resulting from us forgetting to include the necessary plug-in in the agent product file :)

You are correct, p2agent, installer or eclipse SDK UI, all run the same code behind the scene. They are just variation on where the management can be done, the size, the user experience, etc.
HTH

Inactive hide details for "Torsten Schlabach" ---06/05/2009 04:49:15 AM---Hi again!"Torsten Schlabach" ---06/05/2009 04:49:15 AM---Hi again!


From:

"Torsten Schlabach" <TSchlabach@xxxxxxx>

To:

P2 developer discussions <p2-dev@xxxxxxxxxxx>

Date:

06/05/2009 04:49 AM

Subject:

Re: [p2-dev] Trying to make sense of agent, installer and director




Hi again!

Just one ... sorry ... two more questions:

1. I have created a standalone installation of the SDK into some folder c:\foo using the p2installer. Now I wanted to tell the p2agent about this folder to possibly install additional artifacts into my standalone environment. But I just does not recognize my installation. I have created a new profile and pointed both "Install folder" and "Bundle location" to c:\foo, did a refresh and expected to see my installed artifacts there, but I don't see nothing.

2. I then tried to use the p2agent for a new installation. I am behind an HTTP proxy. While the p2installer obviously recognized my proxy settings automatically (I am on Windows, Vista to be exact) the p2agent is unable to connect to any external http location. I also cannot find any proxy settings in the Preferences dialog. Is this by design or would it make sense filing a bug / enhancement request for that.

I again hope I understood the concept correctly that the directory layout expected by the p2agent is the same as the p2installer creates, as they are basically the same application, isn't it?

Regards,
Torsten

-------- Original-Nachricht --------
> Datum: Thu, 4 Jun 2009 14:56:26 -0400
> Von: Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
> An: P2 developer discussions <p2-dev@xxxxxxxxxxx>
> CC: P2 developer discussions <p2-dev@xxxxxxxxxxx>, p2-dev-bounces@xxxxxxxxxxx
> Betreff: Re: [p2-dev] Trying to make sense of agent, installer and director

>
> This is normal. Becasue the description file is shipped in the SDK and we
> are done with our builds, we had to point at the repository where the
> final
> 3.5.0 bytes will be, but they are just not there yet. Bytes will be
> available there at the release.
> If you want to try, open the installer.properties and point at
>
http://download.eclipse.org/eclipse/updates/3.5-I-builds
>
> PaScaL
>
>
> |------------>
> | From:      |
> |------------>
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
>   |"Torsten Schlabach" <TSchlabach@xxxxxxx>                              
>                                                                    |
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | To:        |
> |------------>
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
>   |P2 developer discussions <p2-dev@xxxxxxxxxxx>                          
>                                                                    |
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Date:      |
> |------------>
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
>   |06/04/2009 02:52 PM                                                    
>                                                                    |
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
> |------------>
> | Subject:   |
> |------------>
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
>   |Re: [p2-dev] Trying to make sense of agent, installer and director    
>                                                                    |
>  
> >-------------------------------------------------------------------------------------------------------------------------------------------|
>
>
>
>
>
> Hi!
>
> Thanks, that explaination makes some sense.
>
> > - the p2-installer can be directed to install anything by modifying
> > the installer.properties.
>
> Well, I would have expected it to be able to install me an SDK if I use
> the
> default settings, but no luck.
>
> I have downloaded the p2installer from Galileo 3.5RC3 on win32 and just
> lauched it.
>
> Result:
>
> > !SESSION 2009-06-04 19:14:49.062 >
> > -----------------------------------------------
> > eclipse.buildId=unknown
> > java.version=1.6.0_13
> > java.vendor=Sun Microsystems Inc.
> > BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
> > Command-line arguments:  -os win32 -ws win32 -arch x86
> >
> > !ENTRY org.eclipse.equinox.p2.installer 4 0 2009-06-04 19:15:25.250
> > !MESSAGE Installable unit not found: org.eclipse.sdk.ide
>
> Shouldn't that work out of the box normally?
>
> As you say, the UI has little options to set.
>
> I also tried to install something using the agent.
>
> There my problem was that it could not find certain required parts in any
> of its repositories.
>
> Did anyone ever successfully install his / her SDK through P2?
>
> I mean: Install from scratch. Not just install some additional features
> into an existing SDK which got installed by unpacking a ZIP file. Or do I
> suffer from a misunderstanding and the p2installer is not at all made for
> that?
>
> Regards,
> Torsten
>
>
> -------- Original-Nachricht --------
> > Datum: Thu, 4 Jun 2009 19:46:36 +0200
> > Von: Henrik Lindberg <henrik.lindberg@xxxxxxxxxxxxxx>
> > An: P2 developer discussions <p2-dev@xxxxxxxxxxx>
> > Betreff: Re: [p2-dev] Trying to make sense of agent, installer and
> director
>
> > In one respect, they are all the same (agent, installer, director) as
> > it is the same code beneath the surface.
> > It is the UI and how you tell it what you want that differs.
> >
> > Some small notes:
> > - the 'director.app' is part of every SDK. There is also a separate
> > headless director.
> > - the p2-installer can be directed to install anything by modifying
> > the installer.properties. It's UI is streamlined as it performs the
> > installs a particular way.
> >
> > Henrik Lindberg
> > henrik.lindberg@xxxxxxxxxxxxxx
> >
> >
> >
> > On Jun 4, 2009, at 5:40 PM, Torsten Schlabach wrote:
> >
> > > Hi all!
> > >
> > > I am currently trying to gain an understanding of how I will manage my
> > > Eclipse SDK and Eclipse based product installations in the future.
> > > This
> > > includes both RCP apps as well as possibly headless installations. I
> > > understand p2 is what I want in the future, for a number of good
> > > reasons.
> > >
> > > Now I am trying to understand what's offered to me at
> > >
> > >
http://download.eclipse.org/equinox/
> > >
> > > I think I am most interested in the sections
> > >
> > > Provisioning
> > > Launchers
> > >
> > > What would be the difference between
> > >
> > > - A launcher for my platform
> > > - An Equinox p2 agent
> > > - An Equinox p2 installer
> > > - The Equinox director which is not listed here at all, but I found it
> > > on the Buckminster update site
> > >
> > > My guess was:
> > >
> > > - The agent can install arbitrary artifacts into arbitrary locations.
> > > This is managed using some kind of profiles.
> > > - The installer is a special purpose agent which can only install
> > > Eclipse SDK?
> > > - The director is the same as the agent, just it can run headless.
> > > - After I will have installed by SDK for example, using either the
> > > agent
> > > or the installer or the director, I will not yet have a launcher
> > > because
> > > Launchers are not installable by using p2.
> > >
> > > Are my guesses about right?
> > >
> > > Regards,
> > > Torsten
> > >
> > > _______________________________________________
> > > 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


GIF image

GIF image