[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [p2-dev] RE: Installing eclipse from the command line
|
John,
I created the local repos using the p2 mirror
application:
I have tested my mirrors by installing all IUs from them
into vanilla eclipse classic installs. Everything works apart from Eclipse (bug
240302 reported). I have also used successfully used both my Eclipse and
Ganymede mirrors as repositories for installing eclipse with the P2 GUI
installer.
I have tried using the external Eclipse and Ganymede
repositories to install Eclipse using the director application. All attempts
failed in the same way: just a P2 directory and nothing else in the install
destination directory. However, now and again (1 out of 10 attempts) I saw
the following NPE in the console:
[echo] Installing Eclipse:
C:/tmp/eclipseide/3.4/win
[echo] - repo : http://download.eclipse.org/releases/ganymede/
[echo] - todir: C:/tmp/eclipseide/3.4/win
[delete] Deleting directory
C:\tmp\eclipseide\3.4\win
[mkdir] Created dir:
C:\tmp\eclipseide\3.4\win
[exec] Installing org.eclipse.sdk.ide
3.4.0.I20080617-2000.
[exec] Installing org.eclipse.sdk.ide
3.4.0.I20080617-2000.
[exec] Operation completed in 25203
ms.
[exec] java.lang.NullPointerException
[exec] at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.createRepository(MetadataRepositoryManager.java:246)
[exec] at
org.eclipse.equinox.internal.p2.engine.MetadataCache.getRepository(MetadataCache.java:53)
[exec] at
org.eclipse.equinox.internal.p2.engine.MetadataCache$1.notify(MetadataCache.java:81)
[exec] at
org.eclipse.equinox.internal.p2.core.ProvisioningEventBus.dispatchEvent(ProvisioningEventBus.java:86)
[exec] at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
[exec] at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
[echo] Install Eclipse complete!
Any idea what is going on here? (I am going to abandon
using director for installation for now.)
Miles
Your use of the director looks fine,
but how are you creating those local repostories? Does it work if you just point
at the remote Ganymede repository instead of your local copy?
John
"Daffin, Miles \(IT\)"
<Miles.Daffin@xxxxxxxxxxxxxxxxx> Sent by: p2-dev-bounces@xxxxxxxxxxx
08/08/2008 05:45 AM
Please respond
to P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
To
| "P2 developer discussions"
<p2-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [p2-dev] RE: Installing eclipse
from the command line |
|
This was pretty close to what I was already using.
Nevertheless I translated the relevant bits into macrodefs and ran them (see
attached): * Platform: WinXP * JDK: Sun 1.6.0_06 * Ant: 1.7.1 The result was the
same: the install location contains a p2 directory and nothing else:
C:\TMP\ECLIPSEIDE\3.4\WIN
└───p2
├───org.eclipse.equinox.p2.core
│
└───cache
├───org.eclipse.equinox.p2.director
│
└───rollback
├───org.eclipse.equinox.p2.engine
│ └───profileRegistry
│
└───SDKProfile.profile
└───org.eclipse.equinox.p2.metadata.repository
└───cache Script output was as follows: > ant
test-install-eclipse-win
Buildfile: build.xml test-install-eclipse-win:
[echo] Installing Eclipse in
C:/tmp/eclipseide/3.4/win
[delete] Deleting directory
C:\tmp\eclipseide\3.4\win
[mkdir] Created dir:
C:\tmp\eclipseide\3.4\win
[exec] DEBUG OUTPUT: false
[exec] Installing org.eclipse.sdk.ide 3.4.0.I20080617-2000.
[exec] Installing org.eclipse.sdk.ide 3.4.0.I20080617-2000.
[exec] Operation completed in 97469 ms.
[echo] Install Eclipse
complete! BUILD SUCCESSFUL
Total time: 2 minutes 27 seconds
Do you
have any idea what could be going wrong?
Thanks, Miles
Miles
Daffin
Morgan Stanley |
Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14
4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew
Niefer
Sent: 07 August 2008 19:15
To: P2 developer
discussions
Subject: RE: [p2-dev] RE: Installing eclipse from the
command line
Just look in the history, the branch point for R3_4_maintenance would
be the last 3.4.0 version.
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng.eclipsebuilder/equinox/buildConfigs/equinox.prov/run.xml?revision=1.86&view=markup
"Daffin, Miles \(IT\)"
<Miles.Daffin@xxxxxxxxxxxxxxxxx> Sent by:
p2-dev-bounces@xxxxxxxxxxx
08/07/2008 01:08 PM
Please respond
to P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
To
| "P2 developer
discussions" <p2-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [p2-dev] RE: Installing eclipse
from the command line |
|
This file is for
creating 3.5.0 installs. Please excuse my almost limitless ignorance, but should
I be looking at the one for 3.4.0?
Thanks a lot,
Miles
Miles Daffin
Morgan Stanley | Technology
20 Cabot Square |
Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax:
+44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew
Niefer
Sent: 07 August 2008 16:38
To: P2 developer
discussions
Subject: RE: [p2-dev] RE: Installing eclipse from the
command line
The script used to create the eclipse downloads is in CVS, you
can see it here:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng.eclipsebuilder/equinox/buildConfigs/equinox.prov/run.xml?view=markup
-Andrew
"Daffin, Miles \(IT\)"
<Miles.Daffin@xxxxxxxxxxxxxxxxx> Sent by:
p2-dev-bounces@xxxxxxxxxxx
08/07/2008 06:12 AM
Please respond
to P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
To
| "P2 developer
discussions" <p2-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [p2-dev] RE: Installing eclipse
from the command line |
|
John,
Would the simplest approach would be to post the script(s)
used to create the eclipse downloads? I am sure others would find this really
helpful. Could they be attached to the directory wiki page?
http://wiki.eclipse.org/Equinox_p2_director_application
Cheers,
Miles
Miles Daffin
Morgan Stanley | Technology
20 Cabot Square |
Canary Wharf | Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax:
+44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Daffin, Miles
(IT)
Sent: 06 August 2008 18:45
To: P2 developer
discussions
Subject: RE: [p2-dev] RE: Installing eclipse from the
command line
Hi
John,
Thanks for responding. Here is my full command line. Can you spot any
problems?
Thanks,
Miles
---
eclipse.exe
-application
org.eclipse.equinox.p2.director.app.application
-nosplash
--launcher.suppressErrors
-consoleLog
-verbose
-debug
-flavor
tooling
-installIU org.eclipse.sdk.ide
-version
3.4.0.I20080617-2000
-p2.os win32
-p2.ws win32
-p2.arch x86
-roaming
-profile SDKProfile
-profileProperties
org.eclipse.update.install.features=true
-metadataRepository
file:C:/dev/workshop/eclipseide/3.4/mirrors/eclipse
-artifactRepository
file:C:/dev/workshop/eclipseide/3.4/mirrors/eclipse
-metadataRepositoryName
metaName
-artifactRepositoryName artifactName
-destination
C:/tmp/eclipseide/3.4/win
-bundlepool C:/tmp/eclipseide/3.4/win
-vmargs
-Declipse.p2.data.area=C:/tmp/eclipseide/3.4/win/p2
Miles Daffin
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf
| Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20
7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of John
Arthorne
Sent: 06 August 2008 15:23
To: P2 developer
discussions
Subject: Re: [p2-dev] RE: Installing eclipse from the
command line
I've been on holiday
for a couple of weeks and just catching up on this. I can confirm you
should get the same behaviour with the director application as the installer,
since they both under the covers call the same p2 API to perform the install. I
know this works because we use the director application ourselves during the
eclipse project build to produce the zip files you see on the download page.
Perhaps your command line for calling the director is missing something. Can you
send along the exact command line you are using? I think you already know
this, but you should be using the "org.eclipse.sdk.ide" product IU as the root
when performing the install.
John
"Daffin, Miles \(IT\)"
<Miles.Daffin@xxxxxxxxxxxxxxxxx> Sent by:
p2-dev-bounces@xxxxxxxxxxx
08/05/2008 06:03 AM
Please respond
to P2 developer discussions
<p2-dev@xxxxxxxxxxx> |
|
To
| "P2 developer
discussions" <p2-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| [p2-dev] RE: Installing eclipse
from the command line |
|
Folks,
Sorry to keep banging on about this - but does anyone
have any idea why eclipse installation fails using the director
application?
Thanks,
Miles
Miles Daffin
Morgan Stanley
| Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14
4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Daffin, Miles
(IT)
Sent: 28 July 2008 12:26
To: P2 developer
discussions
Subject: [p2-dev] RE: Installing eclipse from the command
line
I should add that I have
tried using the P2 director app as described here:
http://wiki.eclipse.org/Equinox_p2_director_application#Installing_a_complete_product
All I end up with is
a p2 folder with 4 subdirectories containing various bit of metadata:
org.eclipse.equinox.p2.core
org.eclipse.equinox.p2.director
org.eclipse.equinox.p2.engine
org.eclipse.equinox.p2.metadata.repository
I was expecting a
complete, runnable eclipse install. What am I doing wrong?
Thanks,
Miles
Miles Daffin
Morgan Stanley | Technology
20 Cabot Square | Canary Wharf
| Floor 06
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20
7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From: p2-dev-bounces@xxxxxxxxxxx
[mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Daffin, Miles
(IT)
Sent: 28 July 2008 11:58
To: P2 developer
discussions
Subject: [p2-dev] Installing eclipse from the command
line
Hi All,
I have tried the P2 installer to
install eclipse from a local Ganymede mirror. Is it possible to do the same but
non-interactively, without a UI, from a script?
Thanks,
Miles
Miles Daffin
Morgan Stanley
| Technology
20 Cabot Square | Canary Wharf | Floor 06
London, E14
4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in error.
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in error.
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in
error._______________________________________________
p2-dev mailing
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in error.
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in
error._______________________________________________
p2-dev mailing
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in
error._______________________________________________
p2-dev mailing
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in
error._______________________________________________
p2-dev mailing
list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.