Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Facing problems in doing installation using p2.director
Facing problems in doing installation using p2.director [message #539932] Mon, 14 June 2010 10:24 Go to next message
Nayna Jain is currently offline Nayna JainFriend
Messages: 23
Registered: July 2009
Junior Member
Hi everybody,

I have some doubts related to creating portable installations using p2.director application which can be zipped and then unzipped anywhere.

The steps which I had done till now are as follows :

#1.. Unzip the eclipse SDK
#2.. Run the p2.director application using existing installed eclipse on my system and and install the cdt in the unzipped SDK directory as the destination.
Command is as below :
$InstallPath/eclipse -vm $vm -nosplash -data $workspace -consolelog -clean \
-application org.eclipse.equinox.p2.director
-metadataRepository http://downloads.eclipse.org/releases/galileo \ -artifactRepository http://downloads.eclipse.org/releases/galileo \ -installIU org.eclipse.cdt.feature.group \
-destination $eclipseroot/eclipse \
-profile SDKProfile \
-profileProperties roaming=true \
-p2.os linux -p2.ws gtk -p2.arch x86 -vmargs -Xms128M -Xmx 256M -XX:Permsize=128M -XX:MaxPermSize=256M

After running this application the feature cdt gets installed.

Now in this eclipse installation, I have the directory structure as below :
eclipse/
p2 /
org.eclipse.equinox.p2.core/
org.eclipse.equinox.p2.engine/
profileRegistry/
SDKProfile.profile/
xxxxxxxx.profile
.settings/ org.eclipse.equinox.p2.artifact.repostiory.prefs, org.eclipse.equinox.p2.metadata.repository.prefs


org.eclipse.equinox.p2.repository

So, after doing the installation, I found the hard coded paths of my installation in the xxxxx.profile files and also in the artifact/metadata repository files.. Even installFolder path is hardcoded.

So, I have the following doubts :

1. What is the use of the profile and .settings directory ? What is the use of these files ? And how the values in these files are used.
2. I have read that -roaming flag makes the installation portable.. But not sure then why am I getting these hard coded paths here.
3. I have read that these are created by p2 engine during various phases of configure, install, uninstall etc.. then how do I tell engine in command line that not to add these hard coded paths
4. what is p2.inf file ? When and how it should be created and used ?
5. What is the meaning of touchpoints ? How touchpoints instructions are used ?

Can someone please help me with these doubts ? I need to resolve this issue urgently.

Thanks & Regards,
- Nayna Jain
Re: Facing problems in doing installation using p2.director [message #540063 is a reply to message #539932] Mon, 14 June 2010 17:28 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
For the -roaming, you still get absolute paths in the p2 data files,
however, when roaming is true, then p2 will check these paths and update
them when eclipse is started (or when the next p2 operation occurs).

You can see that when you unzip the Eclipse SDK and before you run it, it
has paths like:
<property name='org.eclipse.equinox.p2.installFolder'
value='/builds/I201005110800/src/I20100511-0800/p2temp/equin ox.p2.build/sdk.install.linux.gtk.x86_64/eclipse'/ >
<property name='org.eclipse.equinox.p2.cache'
value='/builds/I201005110800/src/I20100511-0800/p2temp/equin ox.p2.build/sdk.install.linux.gtk.x86_64/eclipse'/ >
And these get updated when you run eclipse for the first time.

The stuff under eclipse/p2 is the metadata which specifies what you have
installed. It is read by p2 and does not immediately affect Eclipse itself
except when p2 is doing something. You should be more concerned about
paths in the eclipse.ini, configuration/config.ini and
configuration/org.eclipse.equinox.simpleconfigurator/bundles .info files.

As to your other questions, here are some links that may be useful
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/p2_customizing_metadata.html
http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instruc tions
http://wiki.eclipse.org/Equinox/p2/Customizing_Metadata

Nayna wrote:

> Hi everybody,
>
> I have some doubts related to creating portable installations using
> p2.director application which can be zipped and then unzipped anywhere.
>
> The steps which I had done till now are as follows :
>
> #1.. Unzip the eclipse SDK
> #2.. Run the p2.director application using existing installed eclipse on
> #my system and and install the cdt in the unzipped SDK directory as the
> #destination.
> Command is as below :
> $InstallPath/eclipse -vm $vm -nosplash -data $workspace -consolelog -clean
> \
> -application org.eclipse.equinox.p2.director
> -metadataRepository http://downloads.eclipse.org/releases/galileo \
> -artifactRepository http://downloads.eclipse.org/releases/galileo \
> -installIU org.eclipse.cdt.feature.group \
> -destination $eclipseroot/eclipse \
> -profile SDKProfile \
> -profileProperties roaming=true \
> -p2.os linux -p2.ws gtk -p2.arch x86 -vmargs -Xms128M -Xmx 256M
> -XX:Permsize=128M -XX:MaxPermSize=256M
>
> After running this application the feature cdt gets installed.
>
> Now in this eclipse installation, I have the directory structure as below
> : eclipse/
> p2 /
> org.eclipse.equinox.p2.core/
> org.eclipse.equinox.p2.engine/
>
profileRegistry/
>
SDKProfile.profile/
>
xxxxxxxx.profile
> .settings/
>
org.eclipse.equinox.p2.artifact.repostiory.prefs,
>
org.eclipse.equinox.p2.metadata.repository.prefs
>
>
> org.eclipse.equinox.p2.repository
>
> So, after doing the installation, I found the hard coded paths of my
> installation in the xxxxx.profile files and also in the artifact/metadata
> repository files.. Even installFolder path is hardcoded.
>
> So, I have the following doubts :
>
> 1. What is the use of the profile and .settings directory ? What is the
> use of these files ? And how the values in these files are used. 2. I have
> read that -roaming flag makes the installation portable.. But not sure
> then why am I getting these hard coded paths here. 3. I have read that
> these are created by p2 engine during various phases of configure,
> install, uninstall etc.. then how do I tell engine in command line that
> not to add these hard coded paths 4. what is p2.inf file ? When and how it
> should be created and used ? 5. What is the meaning of touchpoints ? How
> touchpoints instructions are used ?
>
> Can someone please help me with these doubts ? I need to resolve this
> issue urgently.
>
> Thanks & Regards,
> - Nayna Jain
Re: Facing problems in doing installation using p2.director [message #540117 is a reply to message #539932] Tue, 15 June 2010 02:40 Go to previous message
Nayna Jain is currently offline Nayna JainFriend
Messages: 23
Registered: July 2009
Junior Member
Hi Andrew,

Thanks for the response.

I tried as you told..
So, after doing the installation, I started the eclipse and and after appearing of Welcome Page , I closed it without doing any operation, but the hard coded paths still exists.

These paths are hard coded for installFolder, cache property values in the profile files and as repository paths in the artifact files

eclipse/p2/org.eclipse.equinox.p2.engine/.settings/org.eclip se.equinox.p2.artifact.repository.prefs:repositories/file\:_ gsa_ausgsa_projects_i_indiateam_nayna_eclipse_35clean_nexus_ nexus1_eclipse/uri=file\:/gsa/ausgsa/projects/i/indiateam/na yna/eclipse/35clean/nexus/nexus1/eclipse/
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDK Profile.profile/1276540728941.profile: <property name='org.eclipse.equinox.p2.cache' value='/gsa/ausgsa/projects/i/indiateam/nayna/eclipse/35clea n/nexus/nexus1/eclipse'/ >
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDK Profile.profile/1276540728941.profile: <property name='org.eclipse.equinox.p2.installFolder' value='/gsa/ausgsa/projects/i/indiateam/nayna/eclipse/35clea n/nexus/nexus1/eclipse'/ >
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDK Profile.profile/1276540745483.profile: <property name='org.eclipse.equinox.p2.cache' value='/gsa/ausgsa/projects/i/indiateam/nayna/eclipse/35clea n/nexus/nexus1/eclipse'/ >
eclipse/p2/org.eclipse.equinox.p2.engine/profileRegistry/SDK Profile.profile/1276540745483.profile: <property name='org.eclipse.equinox.p2.installFolder' value='/gsa/ausgsa/projects/i/indiateam/nayna/eclipse/35clea n/nexus/nexus1/eclipse'/ >

So, now how to avoid these paths. ?

I have read the touchpoint instructions wiki page but couldn't understand much. I couldn't understand that when and how can I use it especially from command line.

Thanks & Regards
- Nayna Jain
Previous Topic:error with embedded servletbridge.jar
Next Topic:Log service set DEBUG level
Goto Forum:
  


Current Time: Wed Sep 25 02:05:02 GMT 2024

Powered by FUDForum. Page generated in 0.04355 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top