| p2 director problems [message #110908] |
Thu, 29 May 2008 12:13  |
Eclipse User |
|
|
|
Originally posted by: turesheim.atmel.com
Hi,
I've (finally) managed to set up my build scripts so that they correctly
creates the p2 metadata and artifact repository. After upgrading to the RC2
builds I was also able to use both the agent and the installer to create
installations using the said repository. But I'm quite unable to create an
installation using the director.
I've checked the options many times and find nothing wrong but still the
director will only create the p2 folder with contents in the installation
location and continue to do absolutely nothing. Any ideas on what might be
wrong? There is no log file in the workspace that could have helped
and "-debug" does nothing.
--
Torkild Ulvøy Resheim
Senior Design Engineer
Atmel Norway AS
|
|
|
|
| Re: p2 director problems [message #110960 is a reply to message #110921] |
Thu, 29 May 2008 19:46  |
| Eclipse User |
|
|
|
Originally posted by: torkildr.resheim.no
Andrew Niefer wrote:
> Torkild,
> If it helps, here is the command line I used just this afternoon with
> build I200805281327, it worked fine and installed everything as expected.
>
> (Broken up for readability:)
> > director/eclipse/eclipse
> -vm /jdk1.5.0_14/jre/bin
> -application org.eclipse.equinox.p2.director.app.application
> -nosplash --launcher.suppressErrors -consoleLog
> -flavor tooling
> -installIU org.eclipse.sdk.ide
> -version 3.4.0.I20080528-1327
> -p2.os win32 -p2.ws win32 -p2.arch x86
> -roaming
> -profile SDKProfile
> -profileProperties org.eclipse.update.install.features=true
> -metadataRepository file:/src/repo
> -artifactRepository file:/src/repo
> -metadataRepositoryName metaName
> -artifactRepositoryName artifactName
> -destination /test/install/eclipse
> -bundlepool /test/install/eclipse
> -vmargs
> -Declipse.p2.data.area=/test/install/eclipse/p2
>
> -Andrew
Thanks again Andrew,
I see that I've not specified -vm, -version, -metadataRepositoryName
and -artifactRepositoryName. I guess that could be the problem (the wiki
page examples does not use these though).
--
Torkild
|
|
|
| Re: p2 director problems [message #111032 is a reply to message #110921] |
Fri, 30 May 2008 08:12 |
| Eclipse User |
|
|
|
Originally posted by: turesheim.atmel.com
Andrew,
Andrew Niefer wrote:
> Torkild,
> If it helps, here is the command line I used just this afternoon with
> build I200805281327, it worked fine and installed everything as expected.
[snip]
So I finally managed to install using the director but I had to build an
eclipse installation similar to what is being done in
org.eclipse.releng.eclipsebuilder. For some reason the Eclipse installation
I normally use for building would just hang.
For reference, this is what I ended up doing:
* Obtain a RCP package (eclipse-RCP-3.4RC2-linux-gtk.tar.gz) and use it
build a new Eclipse installation.
* Check out and build the director (org.eclipse.equinox.p2.director.feature)
feature and plug-ins from CVS. Put the result in the installation.
* Copy the org.eclipse.osgi.services_* and org.eclipse.core.net_* plug-ins
into the installation.
* Overwrite the config.ini in the installation with the version found in
org.eclipse.releng.eclipsebuilder/equinox/buildConfigs/equin ox.prov/files.
I'm not sure why I had to do it this way. I noticed that the director
feature is missing from the SDK zip (RC2), while at least most p2 plug-ins
are there.
--
Torkild Ulvøy Resheim
Senior Design Engineer
Atmel Norway AS
|
|
|
Powered by
FUDForum. Page generated in 0.03382 seconds
] 
Search
Help
Register
Login
Home
