Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » PDE Build, P2 Metadata and Target Platform Problems
PDE Build, P2 Metadata and Target Platform Problems [message #41087] Tue, 20 January 2009 01:30 Go to next message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

Had been stuck for while on a problem with building my RCP features
based app with PDE Build to include p2 metadata. The setup is based on
Andrew Niefer's Example Headless build for a RCP product with p2 @
http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html

While I got Andrew's demo working with no problem I could not get my
features based RCP product built by the Headless Director
(org.eclipse.equinox.p2.director.app.application to create
zips of the product that contain P2 metadata.)

Here is the exception I kept getting:

[java] Time to load bundles: 38
[java] Starting application: 43688
[java] !SESSION 2009-01-19 09:49:40.096
-----------------------------------------------
[java] eclipse.buildId=M20080911-1700
[java] java.version=1.6.0_05
[java] java.vendor=Sun Microsystems Inc.
[java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
[java] Framework arguments: --launcher.suppressErrors
-application org.eclipse.equinox.p2.director.app.application -flavor
tooling -installIU com.verticon.tracker.editor.Tracker -version
0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
-profileProperties org.eclipse.update.install.features=true -profile
TrackerProfile -metadataRepository
file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
-artifactRepository
file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
-destination
/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
-bundlepool
/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
[java] Command-line arguments: -clean -consoleLog -debug
--launcher.suppressErrors -application
org.eclipse.equinox.p2.director.app.application -flavor tooling
-installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
-version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
-roaming -profileProperties org.eclipse.update.install.features=true
-profile TrackerProfile -metadataRepository
file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
-artifactRepository
file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
-destination
/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
-bundlepool
/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
[java]
[java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
2009-01-19 09:51:57.823
[java] !MESSAGE Error parsing metadata repository
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.823
[java] !MESSAGE Error at line 10, column 91: Missing required
attribute in "repository": url
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.824
[java] !MESSAGE Error at line 10, column 91: Illegal value for
attribute "url" of element "repository": null
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.824
[java] !MESSAGE Error at line 11, column 91: Missing required
attribute in "repository": url
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.824
[java] !MESSAGE Error at line 11, column 91: Illegal value for
attribute "url" of element "repository": null
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.824
[java] !MESSAGE Error at line 12, column 90: Missing required
attribute in "repository": url
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.824
[java] !MESSAGE Error at line 12, column 90: Illegal value for
attribute "url" of element "repository": null
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.825
[java] !MESSAGE Error at line 13, column 90: Missing required
attribute in "repository": url
[java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
09:51:57.825
[java] !MESSAGE Error at line 13, column 90: Illegal value for
attribute "url" of element "repository": null
[java] Installing com.verticon.tracker.editor.Tracker
0.3.1.v200901190943.
[java] Installation failed.
[java]
[java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
09:53:34.418
[java] !MESSAGE An error occurred while collecting items to be
installed
[java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0
2009-01-19 09:53:34.419
[java] !MESSAGE Problems downloading artifact:
osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
[java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
09:53:34.419
[java] !MESSAGE OK
[java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4 4
2009-01-19 09:53:34.419
[java] !MESSAGE File has invalid content: /tmp/signatureFile17624.jar
[java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4 0
2009-01-19 09:53:34.419
[java] !MESSAGE Invalid content: plugin_customization.ini
[java] !STACK 0
[java] org.eclipse.osgi.signedcontent.InvalidContentException: The
file "plugin_customization.ini" in the jar "/tmp/signatureFile17624.jar"
has been tampered!
[java] at
org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
[java] at
org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
[java] at
org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
[java] at
org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
[java] at
org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
[java] at
org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
[java] at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
[java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
09:53:34.421
[java] !MESSAGE OK
[java] Java Result: 13


Got similar errors from the Admin UI when I pointed it at the repo I
created with PDE Build above:
An error occurred while collecting items to be installed
Problems downloading artifact:
osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
File has invalid content: /tmp/signatureFile9067.jar
Invalid content: plugin_customization.ini
The file "plugin_customization.ini" in the jar
"/tmp/signatureFile9067.jar" has been tampered!


Was able to cause Andrew's demo to fail in similar ways by adding the
org.eclipse.platform plugin to the product configuration.

Searching the bugzilla I noticed the similarity with
https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
but because I have very little debug or diagnostic messages I had to
grope in the dark to fix this.

My last grope was successful - I created a fresh target platform from
3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox plugins
that were required by the product.

Since I would hate to have anyone else have to go through this hassle
and am still in the dark on what caused it - Does anyone have any
ideas, and/or suggestions on what might have been happening? Any
troubleshooting techniques for dealing with similar p2 problems would
also be helpful.

thanks for any ideas,

John
Re: PDE Build, P2 Metadata and Target Platform Problems [message #41185 is a reply to message #41087] Tue, 20 January 2009 17:12 Go to previous messageGo to next message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
verification. You basically want to identify where the "corruption" is
being introduced.

In general, to track down this kind of verification error, you want to
run "jarsigner -verify" on the jars in several locations:

1) The jar in your repository
(buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)


2) The jar in the output of the build. (in the example this is
Builder/I.TestBuild/TestBuild-win32.win32.x86.zip

3) The input to the build, ie baseLocation

if (1) passes, then I guess there is a bug in p2 install somewhere
if (2) passes and (1) failed, the bug is in p2 metadata generation.
if (3) passes and (2) failed, the bug is in pde.build
if (3) fails, your input files are corrupt, where did you get them from?
were they ever modified?

Since creating a fresh target fixed things for you, I expect the last
case, somehow the input files got corrupted.

In this particular case, this is complicated by org.eclipse.platform
being a folder shaped bundle, so (2) and (3) both are folders.
jarsigner doesn't verify folders. You can try zipping them into jars
and verifying that. Or, org.eclipse.osgi has experimental API that can
verify folders, so you could write a small tool using
CertificateVerifierFactory. (See as an example
org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)

-Andrew

John E. Conlon wrote:
> Had been stuck for while on a problem with building my RCP features
> based app with PDE Build to include p2 metadata. The setup is based on
> Andrew Niefer's Example Headless build for a RCP product with p2 @
> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>
>
> While I got Andrew's demo working with no problem I could not get my
> features based RCP product built by the Headless Director
> (org.eclipse.equinox.p2.director.app.application to create
> zips of the product that contain P2 metadata.)
>
> Here is the exception I kept getting:
>
> [java] Time to load bundles: 38
> [java] Starting application: 43688
> [java] !SESSION 2009-01-19 09:49:40.096
> -----------------------------------------------
> [java] eclipse.buildId=M20080911-1700
> [java] java.version=1.6.0_05
> [java] java.vendor=Sun Microsystems Inc.
> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> [java] Framework arguments: --launcher.suppressErrors -application
> org.eclipse.equinox.p2.director.app.application -flavor tooling
> -installIU com.verticon.tracker.editor.Tracker -version
> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
> -profileProperties org.eclipse.update.install.features=true -profile
> TrackerProfile -metadataRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -artifactRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -destination
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
> -bundlepool
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>
> [java] Command-line arguments: -clean -consoleLog -debug
> --launcher.suppressErrors -application
> org.eclipse.equinox.p2.director.app.application -flavor tooling
> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
> -roaming -profileProperties org.eclipse.update.install.features=true
> -profile TrackerProfile -metadataRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -artifactRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -destination
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
> -bundlepool
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>
> [java]
> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
> 2009-01-19 09:51:57.823
> [java] !MESSAGE Error parsing metadata repository
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.823
> [java] !MESSAGE Error at line 10, column 91: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 10, column 91: Illegal value for
> attribute "url" of element "repository": null
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 11, column 91: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 11, column 91: Illegal value for
> attribute "url" of element "repository": null
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 12, column 90: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 12, column 90: Illegal value for
> attribute "url" of element "repository": null
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.825
> [java] !MESSAGE Error at line 13, column 90: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.825
> [java] !MESSAGE Error at line 13, column 90: Illegal value for
> attribute "url" of element "repository": null
> [java] Installing com.verticon.tracker.editor.Tracker
> 0.3.1.v200901190943.
> [java] Installation failed.
> [java]
> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
> 09:53:34.418
> [java] !MESSAGE An error occurred while collecting items to be
> installed
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0
> 2009-01-19 09:53:34.419
> [java] !MESSAGE Problems downloading artifact:
> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
> 09:53:34.419
> [java] !MESSAGE OK
> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4 4
> 2009-01-19 09:53:34.419
> [java] !MESSAGE File has invalid content: /tmp/signatureFile17624.jar
> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4 0
> 2009-01-19 09:53:34.419
> [java] !MESSAGE Invalid content: plugin_customization.ini
> [java] !STACK 0
> [java] org.eclipse.osgi.signedcontent.InvalidContentException: The
> file "plugin_customization.ini" in the jar "/tmp/signatureFile17624.jar"
> has been tampered!
> [java] at
> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>
> [java] at
> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>
> [java] at
> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>
> [java] at
> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>
> [java] at
> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>
> [java] at
> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
> 09:53:34.421
> [java] !MESSAGE OK
> [java] Java Result: 13
>
>
> Got similar errors from the Admin UI when I pointed it at the repo I
> created with PDE Build above:
> An error occurred while collecting items to be installed
> Problems downloading artifact:
> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
> File has invalid content: /tmp/signatureFile9067.jar
> Invalid content: plugin_customization.ini
> The file "plugin_customization.ini" in the jar
> "/tmp/signatureFile9067.jar" has been tampered!
>
>
> Was able to cause Andrew's demo to fail in similar ways by adding the
> org.eclipse.platform plugin to the product configuration.
>
> Searching the bugzilla I noticed the similarity with
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
> but because I have very little debug or diagnostic messages I had to
> grope in the dark to fix this.
>
> My last grope was successful - I created a fresh target platform from
> 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox plugins
> that were required by the product.
>
> Since I would hate to have anyone else have to go through this hassle
> and am still in the dark on what caused it - Does anyone have any
> ideas, and/or suggestions on what might have been happening? Any
> troubleshooting techniques for dealing with similar p2 problems would
> also be helpful.
>
> thanks for any ideas,
>
> John
>
>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #41278 is a reply to message #41185] Tue, 20 January 2009 19:55 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

Hi Andrew,

See inline comments...

Andrew Niefer wrote:
> So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
> verification. You basically want to identify where the "corruption" is
> being introduced.
Yes, this is the idea I have been exploring (aka groping) as well.

Before I go further I should point out that to try the tests you
suggested I first attempted to get the thing to fail again.
Unfortunately changing the target platform back to the original one I
first experienced the failures in no longer fails. Ugh! (I failed to
fail so to speak.) Nevertheless...
>
> In general, to track down this kind of verification error, you want to
> run "jarsigner -verify" on the jars in several locations:
>
> 1) The jar in your repository
> (buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)
Have noticed all along that this plugin was a jar and that it failed
verification. And even when the director succeeds in extracting a
product from the repository (like in todays tests) this jar fails to
verify...
[echo] verifying
/home/jconlon/eclipse-workspaces/ganymeade1/Builder/repo/plu gins/org.eclipse.platform_3.3.101.v200809111700.jar
[exec] jarsigner: java.lang.SecurityException: SHA1 digest error
for plugin_customization.ini

>
>
> 2) The jar in the output of the build. (in the example this is
> Builder/I.TestBuild/TestBuild-win32.win32.x86.zip
In the output zip the org.eclipse.platform_3.3.101.v200809111700 is not
a jar it's a folder.

>
> 3) The input to the build, ie baseLocation

Here too org.eclipse.platform_3.3.101.v200809111700 in the baseLocation
(my targetPlatform) is a folder.


4) Let me add a fourth test - the result zip from a successful director
extraction.

Here too org.eclipse.platform_3.3.101.v200809111700 is a folder


> if (1) passes, then I guess there is a bug in p2 install somewhere
> if (2) passes and (1) failed, the bug is in p2 metadata generation.
> if (3) passes and (2) failed, the bug is in pde.build
> if (3) fails, your input files are corrupt, where did you get them from?
> were they ever modified?
>
Results -
(1) failed to verify!
(2) a folder - testing after rejaring validation passes
(3) folder - testing after rejaring validation passes
(4) folder - testing after rejaring validation passes




> Since creating a fresh target fixed things for you, I expect the last
> case, somehow the input files got corrupted.
I hoped this was the case too, but things appear to be more convoluted,
as mentioned above my old targetPlatform now seems to work. It also
has/had a good folder in it.

>
> In this particular case, this is complicated by org.eclipse.platform
> being a folder shaped bundle, so (2) and (3) both are folders. jarsigner
> doesn't verify folders. You can try zipping them into jars and
> verifying that.
As mentioned above I rejared and verified.

Or, org.eclipse.osgi has experimental API that can
> verify folders, so you could write a small tool using
> CertificateVerifierFactory. (See as an example
> org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)
>

Questions:
So Why is the repo jaring up the platform folder? (1)

Why is it corrupting the jar in the process? (1)

And if the repo has a broken platform plugin jared where is the
resulting product created by the director getting the good folder to put
in the result? (4)

Or why doesn't the director now NOT fail with a bad jar in the repo?

Aren't there any diagnostic messages that can log what is going on with
the P2 and the director??


thanks for all your help,
John


> -Andrew
>
> John E. Conlon wrote:
>> Had been stuck for while on a problem with building my RCP features
>> based app with PDE Build to include p2 metadata. The setup is based
>> on Andrew Niefer's Example Headless build for a RCP product with p2 @
>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>>
>>
>> While I got Andrew's demo working with no problem I could not get my
>> features based RCP product built by the Headless Director
>> (org.eclipse.equinox.p2.director.app.application to create
>> zips of the product that contain P2 metadata.)
>>
>> Here is the exception I kept getting:
>> [java] Time to load bundles: 38
>> [java] Starting application: 43688
>> [java] !SESSION 2009-01-19 09:49:40.096
>> -----------------------------------------------
>> [java] eclipse.buildId=M20080911-1700
>> [java] java.version=1.6.0_05
>> [java] java.vendor=Sun Microsystems Inc.
>> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>> [java] Framework arguments: --launcher.suppressErrors
>> -application org.eclipse.equinox.p2.director.app.application -flavor
>> tooling -installIU com.verticon.tracker.editor.Tracker -version
>> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
>> -profileProperties org.eclipse.update.install.features=true -profile
>> TrackerProfile -metadataRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -artifactRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -destination
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>> -bundlepool
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>
>> [java] Command-line arguments: -clean -consoleLog -debug
>> --launcher.suppressErrors -application
>> org.eclipse.equinox.p2.director.app.application -flavor tooling
>> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
>> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
>> -roaming -profileProperties org.eclipse.update.install.features=true
>> -profile TrackerProfile -metadataRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -artifactRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -destination
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>> -bundlepool
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>
>> [java]
>> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
>> 2009-01-19 09:51:57.823
>> [java] !MESSAGE Error parsing metadata repository
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.823
>> [java] !MESSAGE Error at line 10, column 91: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 10, column 91: Illegal value for
>> attribute "url" of element "repository": null
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 11, column 91: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 11, column 91: Illegal value for
>> attribute "url" of element "repository": null
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 12, column 90: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 12, column 90: Illegal value for
>> attribute "url" of element "repository": null
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.825
>> [java] !MESSAGE Error at line 13, column 90: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.825
>> [java] !MESSAGE Error at line 13, column 90: Illegal value for
>> attribute "url" of element "repository": null
>> [java] Installing com.verticon.tracker.editor.Tracker
>> 0.3.1.v200901190943.
>> [java] Installation failed.
>> [java]
>> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
>> 09:53:34.418
>> [java] !MESSAGE An error occurred while collecting items to be
>> installed
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0
>> 2009-01-19 09:53:34.419
>> [java] !MESSAGE Problems downloading artifact:
>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>> 09:53:34.419
>> [java] !MESSAGE OK
>> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4 4
>> 2009-01-19 09:53:34.419
>> [java] !MESSAGE File has invalid content:
>> /tmp/signatureFile17624.jar
>> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4 0
>> 2009-01-19 09:53:34.419
>> [java] !MESSAGE Invalid content: plugin_customization.ini
>> [java] !STACK 0
>> [java] org.eclipse.osgi.signedcontent.InvalidContentException:
>> The file "plugin_customization.ini" in the jar
>> "/tmp/signatureFile17624.jar" has been tampered!
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>>
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>>
>> [java] at
>> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>>
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>>
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>>
>> [java] at
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>> 09:53:34.421
>> [java] !MESSAGE OK
>> [java] Java Result: 13
>>
>>
>> Got similar errors from the Admin UI when I pointed it at the repo I
>> created with PDE Build above:
>> An error occurred while collecting items to be installed
>> Problems downloading artifact:
>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>> File has invalid content: /tmp/signatureFile9067.jar
>> Invalid content: plugin_customization.ini
>> The file "plugin_customization.ini" in the jar
>> "/tmp/signatureFile9067.jar" has been tampered!
>>
>>
>> Was able to cause Andrew's demo to fail in similar ways by adding the
>> org.eclipse.platform plugin to the product configuration.
>>
>> Searching the bugzilla I noticed the similarity with
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
>> but because I have very little debug or diagnostic messages I had to
>> grope in the dark to fix this.
>>
>> My last grope was successful - I created a fresh target platform from
>> 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox plugins
>> that were required by the product.
>>
>> Since I would hate to have anyone else have to go through this hassle
>> and am still in the dark on what caused it - Does anyone have any
>> ideas, and/or suggestions on what might have been happening? Any
>> troubleshooting techniques for dealing with similar p2 problems would
>> also be helpful.
>>
>> thanks for any ideas,
>>
>> John
>>
>>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #41372 is a reply to message #41278] Wed, 21 January 2009 19:24 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

Although I was able to build my product from the repo, I can't do it
from an AdminUI without getting:

An error occurred while collecting items to be installed
Problems downloading artifact:
osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
File has invalid content: /tmp/signatureFile55296.jar
Invalid content: plugin_customization.ini
The file "plugin_customization.ini" in the jar
"/tmp/signatureFile55296.jar" has been tampered!


thanks,
John
John E. Conlon wrote:
> Hi Andrew,
>
> See inline comments...
>
> Andrew Niefer wrote:
>> So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
>> verification. You basically want to identify where the "corruption"
>> is being introduced.
> Yes, this is the idea I have been exploring (aka groping) as well.
>
> Before I go further I should point out that to try the tests you
> suggested I first attempted to get the thing to fail again.
> Unfortunately changing the target platform back to the original one I
> first experienced the failures in no longer fails. Ugh! (I failed to
> fail so to speak.) Nevertheless...
>>
>> In general, to track down this kind of verification error, you want to
>> run "jarsigner -verify" on the jars in several locations:
>>
>> 1) The jar in your repository
>> (buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)
>
> Have noticed all along that this plugin was a jar and that it failed
> verification. And even when the director succeeds in extracting a
> product from the repository (like in todays tests) this jar fails to
> verify...
> [echo] verifying
> /home/jconlon/eclipse-workspaces/ganymeade1/Builder/repo/plu gins/org.eclipse.platform_3.3.101.v200809111700.jar
>
> [exec] jarsigner: java.lang.SecurityException: SHA1 digest error
> for plugin_customization.ini
>
>>
>>
>> 2) The jar in the output of the build. (in the example this is
>> Builder/I.TestBuild/TestBuild-win32.win32.x86.zip
> In the output zip the org.eclipse.platform_3.3.101.v200809111700 is not
> a jar it's a folder.
>
>>
>> 3) The input to the build, ie baseLocation
>
> Here too org.eclipse.platform_3.3.101.v200809111700 in the baseLocation
> (my targetPlatform) is a folder.
>
>
> 4) Let me add a fourth test - the result zip from a successful director
> extraction.
>
> Here too org.eclipse.platform_3.3.101.v200809111700 is a folder
>
>
>> if (1) passes, then I guess there is a bug in p2 install somewhere
>> if (2) passes and (1) failed, the bug is in p2 metadata generation.
>> if (3) passes and (2) failed, the bug is in pde.build
>> if (3) fails, your input files are corrupt, where did you get them
>> from? were they ever modified?
>>
> Results -
> (1) failed to verify!
> (2) a folder - testing after rejaring validation passes
> (3) folder - testing after rejaring validation passes
> (4) folder - testing after rejaring validation passes
>
>
>
>
>> Since creating a fresh target fixed things for you, I expect the last
>> case, somehow the input files got corrupted.
> I hoped this was the case too, but things appear to be more convoluted,
> as mentioned above my old targetPlatform now seems to work. It also
> has/had a good folder in it.
>
>>
>> In this particular case, this is complicated by org.eclipse.platform
>> being a folder shaped bundle, so (2) and (3) both are folders.
>> jarsigner doesn't verify folders. You can try zipping them into jars
>> and verifying that.
> As mentioned above I rejared and verified.
>
> Or, org.eclipse.osgi has experimental API that can
>> verify folders, so you could write a small tool using
>> CertificateVerifierFactory. (See as an example
>> org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)
>>
>
> Questions:
> So Why is the repo jaring up the platform folder? (1)
>
> Why is it corrupting the jar in the process? (1)
>
> And if the repo has a broken platform plugin jared where is the
> resulting product created by the director getting the good folder to put
> in the result? (4)
>
> Or why doesn't the director now NOT fail with a bad jar in the repo?
>
> Aren't there any diagnostic messages that can log what is going on with
> the P2 and the director??
>
>
> thanks for all your help,
> John
>
>
>> -Andrew
>>
>> John E. Conlon wrote:
>>> Had been stuck for while on a problem with building my RCP features
>>> based app with PDE Build to include p2 metadata. The setup is based
>>> on Andrew Niefer's Example Headless build for a RCP product with p2 @
>>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>>>
>>>
>>> While I got Andrew's demo working with no problem I could not get my
>>> features based RCP product built by the Headless Director
>>> (org.eclipse.equinox.p2.director.app.application to create
>>> zips of the product that contain P2 metadata.)
>>>
>>> Here is the exception I kept getting:
>>> [java] Time to load bundles: 38
>>> [java] Starting application: 43688
>>> [java] !SESSION 2009-01-19 09:49:40.096
>>> -----------------------------------------------
>>> [java] eclipse.buildId=M20080911-1700
>>> [java] java.version=1.6.0_05
>>> [java] java.vendor=Sun Microsystems Inc.
>>> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>>> [java] Framework arguments: --launcher.suppressErrors
>>> -application org.eclipse.equinox.p2.director.app.application -flavor
>>> tooling -installIU com.verticon.tracker.editor.Tracker -version
>>> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
>>> -profileProperties org.eclipse.update.install.features=true -profile
>>> TrackerProfile -metadataRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -artifactRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -destination
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>> -bundlepool
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>
>>> [java] Command-line arguments: -clean -consoleLog -debug
>>> --launcher.suppressErrors -application
>>> org.eclipse.equinox.p2.director.app.application -flavor tooling
>>> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
>>> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
>>> -roaming -profileProperties org.eclipse.update.install.features=true
>>> -profile TrackerProfile -metadataRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -artifactRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -destination
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>> -bundlepool
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>
>>> [java]
>>> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
>>> 2009-01-19 09:51:57.823
>>> [java] !MESSAGE Error parsing metadata repository
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.823
>>> [java] !MESSAGE Error at line 10, column 91: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 10, column 91: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 11, column 91: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 11, column 91: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 12, column 90: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 12, column 90: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.825
>>> [java] !MESSAGE Error at line 13, column 90: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.825
>>> [java] !MESSAGE Error at line 13, column 90: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] Installing com.verticon.tracker.editor.Tracker
>>> 0.3.1.v200901190943.
>>> [java] Installation failed.
>>> [java]
>>> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
>>> 09:53:34.418
>>> [java] !MESSAGE An error occurred while collecting items to be
>>> installed
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4
>>> 0 2009-01-19 09:53:34.419
>>> [java] !MESSAGE Problems downloading artifact:
>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>> 09:53:34.419
>>> [java] !MESSAGE OK
>>> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4
>>> 4 2009-01-19 09:53:34.419
>>> [java] !MESSAGE File has invalid content:
>>> /tmp/signatureFile17624.jar
>>> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4
>>> 0 2009-01-19 09:53:34.419
>>> [java] !MESSAGE Invalid content: plugin_customization.ini
>>> [java] !STACK 0
>>> [java] org.eclipse.osgi.signedcontent.InvalidContentException:
>>> The file "plugin_customization.ini" in the jar
>>> "/tmp/signatureFile17624.jar" has been tampered!
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>>>
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>>>
>>> [java] at
>>> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>>>
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>>>
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>>>
>>> [java] at
>>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>> 09:53:34.421
>>> [java] !MESSAGE OK
>>> [java] Java Result: 13
>>>
>>>
>>> Got similar errors from the Admin UI when I pointed it at the repo I
>>> created with PDE Build above:
>>> An error occurred while collecting items to be installed
>>> Problems downloading artifact:
>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>> File has invalid content: /tmp/signatureFile9067.jar
>>> Invalid content: plugin_customization.ini
>>> The file "plugin_customization.ini" in the jar
>>> "/tmp/signatureFile9067.jar" has been tampered!
>>>
>>>
>>> Was able to cause Andrew's demo to fail in similar ways by adding the
>>> org.eclipse.platform plugin to the product configuration.
>>>
>>> Searching the bugzilla I noticed the similarity with
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
>>> but because I have very little debug or diagnostic messages I had to
>>> grope in the dark to fix this.
>>>
>>> My last grope was successful - I created a fresh target platform from
>>> 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox
>>> plugins that were required by the product.
>>>
>>> Since I would hate to have anyone else have to go through this hassle
>>> and am still in the dark on what caused it - Does anyone have any
>>> ideas, and/or suggestions on what might have been happening? Any
>>> troubleshooting techniques for dealing with similar p2 problems would
>>> also be helpful.
>>>
>>> thanks for any ideas,
>>>
>>> John
>>>
>>>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #41436 is a reply to message #41372] Thu, 22 January 2009 00:08 Go to previous message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

John E. Conlon wrote:
> Although I was able to build my product from the repo, I can't do it
> from an AdminUI without getting:
>
> An error occurred while collecting items to be installed
> Problems downloading artifact:
> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
> File has invalid content: /tmp/signatureFile55296.jar
> Invalid content: plugin_customization.ini
> The file "plugin_customization.ini" in the jar
> "/tmp/signatureFile55296.jar" has been tampered!
>
This seems to be related to the other repository I had configured in the
Admin UI - http://download.eclipse.org/eclipse/updates/3.4.x

When I remove it and add a local repository ( a locally installed
Eclipse 3.4.1 SDK) to the the Admin UI, the product now installs in
Profiles.

So is the org.eclipse.platform in the
http://download.eclipse.org/eclipse/updates/3.4.x corrupt?

BTW - I can't add the
http://download.eclipse.org/eclipse/updates/3.4
to my Admin UI for some reason??


thanks for any help or insights,
John



>
> thanks,
> John
> John E. Conlon wrote:
>> Hi Andrew,
>>
>> See inline comments...
>>
>> Andrew Niefer wrote:
>>> So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
>>> verification. You basically want to identify where the "corruption"
>>> is being introduced.
>> Yes, this is the idea I have been exploring (aka groping) as well.
>>
>> Before I go further I should point out that to try the tests you
>> suggested I first attempted to get the thing to fail again.
>> Unfortunately changing the target platform back to the original one I
>> first experienced the failures in no longer fails. Ugh! (I failed to
>> fail so to speak.) Nevertheless...
>>>
>>> In general, to track down this kind of verification error, you want
>>> to run "jarsigner -verify" on the jars in several locations:
>>>
>>> 1) The jar in your repository
>>> (buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)
>>
>>
>> Have noticed all along that this plugin was a jar and that it failed
>> verification. And even when the director succeeds in extracting a
>> product from the repository (like in todays tests) this jar fails to
>> verify...
>> [echo] verifying
>> /home/jconlon/eclipse-workspaces/ganymeade1/Builder/repo/plu gins/org.eclipse.platform_3.3.101.v200809111700.jar
>>
>> [exec] jarsigner: java.lang.SecurityException: SHA1 digest error
>> for plugin_customization.ini
>>
>>>
>>>
>>> 2) The jar in the output of the build. (in the example this is
>>> Builder/I.TestBuild/TestBuild-win32.win32.x86.zip
>> In the output zip the org.eclipse.platform_3.3.101.v200809111700 is
>> not a jar it's a folder.
>>
>>>
>>> 3) The input to the build, ie baseLocation
>>
>> Here too org.eclipse.platform_3.3.101.v200809111700 in the
>> baseLocation (my targetPlatform) is a folder.
>>
>>
>> 4) Let me add a fourth test - the result zip from a successful
>> director extraction.
>>
>> Here too org.eclipse.platform_3.3.101.v200809111700 is a folder
>>
>>
>>> if (1) passes, then I guess there is a bug in p2 install somewhere
>>> if (2) passes and (1) failed, the bug is in p2 metadata generation.
>>> if (3) passes and (2) failed, the bug is in pde.build
>>> if (3) fails, your input files are corrupt, where did you get them
>>> from? were they ever modified?
>>>
>> Results -
>> (1) failed to verify!
>> (2) a folder - testing after rejaring validation passes
>> (3) folder - testing after rejaring validation passes
>> (4) folder - testing after rejaring validation passes
>>
>>
>>
>>
>>> Since creating a fresh target fixed things for you, I expect the last
>>> case, somehow the input files got corrupted.
>> I hoped this was the case too, but things appear to be more
>> convoluted, as mentioned above my old targetPlatform now seems to
>> work. It also has/had a good folder in it.
>>
>>>
>>> In this particular case, this is complicated by org.eclipse.platform
>>> being a folder shaped bundle, so (2) and (3) both are folders.
>>> jarsigner doesn't verify folders. You can try zipping them into jars
>>> and verifying that.
>> As mentioned above I rejared and verified.
>>
>> Or, org.eclipse.osgi has experimental API that can
>>> verify folders, so you could write a small tool using
>>> CertificateVerifierFactory. (See as an example
>>> org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)
>>>
>>
>> Questions:
>> So Why is the repo jaring up the platform folder? (1)
>>
>> Why is it corrupting the jar in the process? (1)
>>
>> And if the repo has a broken platform plugin jared where is the
>> resulting product created by the director getting the good folder to
>> put in the result? (4)
>>
>> Or why doesn't the director now NOT fail with a bad jar in the repo?
>>
>> Aren't there any diagnostic messages that can log what is going on
>> with the P2 and the director??
>>
>>
>> thanks for all your help,
>> John
>>
>>
>>> -Andrew
>>>
>>> John E. Conlon wrote:
>>>> Had been stuck for while on a problem with building my RCP features
>>>> based app with PDE Build to include p2 metadata. The setup is based
>>>> on Andrew Niefer's Example Headless build for a RCP product with p2 @
>>>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>>>>
>>>>
>>>> While I got Andrew's demo working with no problem I could not get my
>>>> features based RCP product built by the Headless Director
>>>> (org.eclipse.equinox.p2.director.app.application to create
>>>> zips of the product that contain P2 metadata.)
>>>>
>>>> Here is the exception I kept getting:
>>>> [java] Time to load bundles: 38
>>>> [java] Starting application: 43688
>>>> [java] !SESSION 2009-01-19 09:49:40.096
>>>> -----------------------------------------------
>>>> [java] eclipse.buildId=M20080911-1700
>>>> [java] java.version=1.6.0_05
>>>> [java] java.vendor=Sun Microsystems Inc.
>>>> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>>>> [java] Framework arguments: --launcher.suppressErrors
>>>> -application org.eclipse.equinox.p2.director.app.application -flavor
>>>> tooling -installIU com.verticon.tracker.editor.Tracker -version
>>>> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
>>>> -profileProperties org.eclipse.update.install.features=true -profile
>>>> TrackerProfile -metadataRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -artifactRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -destination
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>> -bundlepool
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>>
>>>> [java] Command-line arguments: -clean -consoleLog -debug
>>>> --launcher.suppressErrors -application
>>>> org.eclipse.equinox.p2.director.app.application -flavor tooling
>>>> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
>>>> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
>>>> -roaming -profileProperties org.eclipse.update.install.features=true
>>>> -profile TrackerProfile -metadataRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -artifactRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -destination
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>> -bundlepool
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>>
>>>> [java]
>>>> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
>>>> 2009-01-19 09:51:57.823
>>>> [java] !MESSAGE Error parsing metadata repository
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.823
>>>> [java] !MESSAGE Error at line 10, column 91: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 10, column 91: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 11, column 91: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 11, column 91: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 12, column 90: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 12, column 90: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.825
>>>> [java] !MESSAGE Error at line 13, column 90: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.825
>>>> [java] !MESSAGE Error at line 13, column 90: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] Installing com.verticon.tracker.editor.Tracker
>>>> 0.3.1.v200901190943.
>>>> [java] Installation failed.
>>>> [java]
>>>> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
>>>> 09:53:34.418
>>>> [java] !MESSAGE An error occurred while collecting items to be
>>>> installed
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4
>>>> 0 2009-01-19 09:53:34.419
>>>> [java] !MESSAGE Problems downloading artifact:
>>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>>> 09:53:34.419
>>>> [java] !MESSAGE OK
>>>> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4
>>>> 4 2009-01-19 09:53:34.419
>>>> [java] !MESSAGE File has invalid content:
>>>> /tmp/signatureFile17624.jar
>>>> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4
>>>> 0 2009-01-19 09:53:34.419
>>>> [java] !MESSAGE Invalid content: plugin_customization.ini
>>>> [java] !STACK 0
>>>> [java] org.eclipse.osgi.signedcontent.InvalidContentException:
>>>> The file "plugin_customization.ini" in the jar
>>>> "/tmp/signatureFile17624.jar" has been tampered!
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>>>>
>>>> [java] at
>>>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>>> 09:53:34.421
>>>> [java] !MESSAGE OK
>>>> [java] Java Result: 13
>>>>
>>>>
>>>> Got similar errors from the Admin UI when I pointed it at the repo I
>>>> created with PDE Build above:
>>>> An error occurred while collecting items to be installed
>>>> Problems downloading artifact:
>>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>>> File has invalid content: /tmp/signatureFile9067.jar
>>>> Invalid content: plugin_customization.ini
>>>> The file "plugin_customization.ini" in the jar
>>>> "/tmp/signatureFile9067.jar" has been tampered!
>>>>
>>>>
>>>> Was able to cause Andrew's demo to fail in similar ways by adding
>>>> the org.eclipse.platform plugin to the product configuration.
>>>>
>>>> Searching the bugzilla I noticed the similarity with
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
>>>> but because I have very little debug or diagnostic messages I had to
>>>> grope in the dark to fix this.
>>>>
>>>> My last grope was successful - I created a fresh target platform
>>>> from 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox
>>>> plugins that were required by the product.
>>>>
>>>> Since I would hate to have anyone else have to go through this
>>>> hassle and am still in the dark on what caused it - Does anyone
>>>> have any ideas, and/or suggestions on what might have been
>>>> happening? Any troubleshooting techniques for dealing with similar
>>>> p2 problems would also be helpful.
>>>>
>>>> thanks for any ideas,
>>>>
>>>> John
>>>>
>>>>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #588489 is a reply to message #41087] Tue, 20 January 2009 17:12 Go to previous message
Andrew Niefer is currently offline Andrew NieferFriend
Messages: 990
Registered: July 2009
Senior Member
So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
verification. You basically want to identify where the "corruption" is
being introduced.

In general, to track down this kind of verification error, you want to
run "jarsigner -verify" on the jars in several locations:

1) The jar in your repository
(buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)


2) The jar in the output of the build. (in the example this is
Builder/I.TestBuild/TestBuild-win32.win32.x86.zip

3) The input to the build, ie baseLocation

if (1) passes, then I guess there is a bug in p2 install somewhere
if (2) passes and (1) failed, the bug is in p2 metadata generation.
if (3) passes and (2) failed, the bug is in pde.build
if (3) fails, your input files are corrupt, where did you get them from?
were they ever modified?

Since creating a fresh target fixed things for you, I expect the last
case, somehow the input files got corrupted.

In this particular case, this is complicated by org.eclipse.platform
being a folder shaped bundle, so (2) and (3) both are folders.
jarsigner doesn't verify folders. You can try zipping them into jars
and verifying that. Or, org.eclipse.osgi has experimental API that can
verify folders, so you could write a small tool using
CertificateVerifierFactory. (See as an example
org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)

-Andrew

John E. Conlon wrote:
> Had been stuck for while on a problem with building my RCP features
> based app with PDE Build to include p2 metadata. The setup is based on
> Andrew Niefer's Example Headless build for a RCP product with p2 @
> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>
>
> While I got Andrew's demo working with no problem I could not get my
> features based RCP product built by the Headless Director
> (org.eclipse.equinox.p2.director.app.application to create
> zips of the product that contain P2 metadata.)
>
> Here is the exception I kept getting:
>
> [java] Time to load bundles: 38
> [java] Starting application: 43688
> [java] !SESSION 2009-01-19 09:49:40.096
> -----------------------------------------------
> [java] eclipse.buildId=M20080911-1700
> [java] java.version=1.6.0_05
> [java] java.vendor=Sun Microsystems Inc.
> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
> [java] Framework arguments: --launcher.suppressErrors -application
> org.eclipse.equinox.p2.director.app.application -flavor tooling
> -installIU com.verticon.tracker.editor.Tracker -version
> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
> -profileProperties org.eclipse.update.install.features=true -profile
> TrackerProfile -metadataRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -artifactRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -destination
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
> -bundlepool
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>
> [java] Command-line arguments: -clean -consoleLog -debug
> --launcher.suppressErrors -application
> org.eclipse.equinox.p2.director.app.application -flavor tooling
> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
> -roaming -profileProperties org.eclipse.update.install.features=true
> -profile TrackerProfile -metadataRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -artifactRepository
> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
> -destination
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
> -bundlepool
> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>
> [java]
> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
> 2009-01-19 09:51:57.823
> [java] !MESSAGE Error parsing metadata repository
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.823
> [java] !MESSAGE Error at line 10, column 91: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 10, column 91: Illegal value for
> attribute "url" of element "repository": null
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 11, column 91: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 11, column 91: Illegal value for
> attribute "url" of element "repository": null
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 12, column 90: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.824
> [java] !MESSAGE Error at line 12, column 90: Illegal value for
> attribute "url" of element "repository": null
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.825
> [java] !MESSAGE Error at line 13, column 90: Missing required
> attribute in "repository": url
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
> 09:51:57.825
> [java] !MESSAGE Error at line 13, column 90: Illegal value for
> attribute "url" of element "repository": null
> [java] Installing com.verticon.tracker.editor.Tracker
> 0.3.1.v200901190943.
> [java] Installation failed.
> [java]
> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
> 09:53:34.418
> [java] !MESSAGE An error occurred while collecting items to be
> installed
> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0
> 2009-01-19 09:53:34.419
> [java] !MESSAGE Problems downloading artifact:
> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
> 09:53:34.419
> [java] !MESSAGE OK
> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4 4
> 2009-01-19 09:53:34.419
> [java] !MESSAGE File has invalid content: /tmp/signatureFile17624.jar
> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4 0
> 2009-01-19 09:53:34.419
> [java] !MESSAGE Invalid content: plugin_customization.ini
> [java] !STACK 0
> [java] org.eclipse.osgi.signedcontent.InvalidContentException: The
> file "plugin_customization.ini" in the jar "/tmp/signatureFile17624.jar"
> has been tampered!
> [java] at
> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>
> [java] at
> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>
> [java] at
> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>
> [java] at
> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>
> [java] at
> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>
> [java] at
> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>
> [java] at
> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
> 09:53:34.421
> [java] !MESSAGE OK
> [java] Java Result: 13
>
>
> Got similar errors from the Admin UI when I pointed it at the repo I
> created with PDE Build above:
> An error occurred while collecting items to be installed
> Problems downloading artifact:
> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
> File has invalid content: /tmp/signatureFile9067.jar
> Invalid content: plugin_customization.ini
> The file "plugin_customization.ini" in the jar
> "/tmp/signatureFile9067.jar" has been tampered!
>
>
> Was able to cause Andrew's demo to fail in similar ways by adding the
> org.eclipse.platform plugin to the product configuration.
>
> Searching the bugzilla I noticed the similarity with
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
> but because I have very little debug or diagnostic messages I had to
> grope in the dark to fix this.
>
> My last grope was successful - I created a fresh target platform from
> 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox plugins
> that were required by the product.
>
> Since I would hate to have anyone else have to go through this hassle
> and am still in the dark on what caused it - Does anyone have any
> ideas, and/or suggestions on what might have been happening? Any
> troubleshooting techniques for dealing with similar p2 problems would
> also be helpful.
>
> thanks for any ideas,
>
> John
>
>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #588519 is a reply to message #41185] Tue, 20 January 2009 19:55 Go to previous message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

Hi Andrew,

See inline comments...

Andrew Niefer wrote:
> So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
> verification. You basically want to identify where the "corruption" is
> being introduced.
Yes, this is the idea I have been exploring (aka groping) as well.

Before I go further I should point out that to try the tests you
suggested I first attempted to get the thing to fail again.
Unfortunately changing the target platform back to the original one I
first experienced the failures in no longer fails. Ugh! (I failed to
fail so to speak.) Nevertheless...
>
> In general, to track down this kind of verification error, you want to
> run "jarsigner -verify" on the jars in several locations:
>
> 1) The jar in your repository
> (buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)
Have noticed all along that this plugin was a jar and that it failed
verification. And even when the director succeeds in extracting a
product from the repository (like in todays tests) this jar fails to
verify...
[echo] verifying
/home/jconlon/eclipse-workspaces/ganymeade1/Builder/repo/plu gins/org.eclipse.platform_3.3.101.v200809111700.jar
[exec] jarsigner: java.lang.SecurityException: SHA1 digest error
for plugin_customization.ini

>
>
> 2) The jar in the output of the build. (in the example this is
> Builder/I.TestBuild/TestBuild-win32.win32.x86.zip
In the output zip the org.eclipse.platform_3.3.101.v200809111700 is not
a jar it's a folder.

>
> 3) The input to the build, ie baseLocation

Here too org.eclipse.platform_3.3.101.v200809111700 in the baseLocation
(my targetPlatform) is a folder.


4) Let me add a fourth test - the result zip from a successful director
extraction.

Here too org.eclipse.platform_3.3.101.v200809111700 is a folder


> if (1) passes, then I guess there is a bug in p2 install somewhere
> if (2) passes and (1) failed, the bug is in p2 metadata generation.
> if (3) passes and (2) failed, the bug is in pde.build
> if (3) fails, your input files are corrupt, where did you get them from?
> were they ever modified?
>
Results -
(1) failed to verify!
(2) a folder - testing after rejaring validation passes
(3) folder - testing after rejaring validation passes
(4) folder - testing after rejaring validation passes




> Since creating a fresh target fixed things for you, I expect the last
> case, somehow the input files got corrupted.
I hoped this was the case too, but things appear to be more convoluted,
as mentioned above my old targetPlatform now seems to work. It also
has/had a good folder in it.

>
> In this particular case, this is complicated by org.eclipse.platform
> being a folder shaped bundle, so (2) and (3) both are folders. jarsigner
> doesn't verify folders. You can try zipping them into jars and
> verifying that.
As mentioned above I rejared and verified.

Or, org.eclipse.osgi has experimental API that can
> verify folders, so you could write a small tool using
> CertificateVerifierFactory. (See as an example
> org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)
>

Questions:
So Why is the repo jaring up the platform folder? (1)

Why is it corrupting the jar in the process? (1)

And if the repo has a broken platform plugin jared where is the
resulting product created by the director getting the good folder to put
in the result? (4)

Or why doesn't the director now NOT fail with a bad jar in the repo?

Aren't there any diagnostic messages that can log what is going on with
the P2 and the director??


thanks for all your help,
John


> -Andrew
>
> John E. Conlon wrote:
>> Had been stuck for while on a problem with building my RCP features
>> based app with PDE Build to include p2 metadata. The setup is based
>> on Andrew Niefer's Example Headless build for a RCP product with p2 @
>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>>
>>
>> While I got Andrew's demo working with no problem I could not get my
>> features based RCP product built by the Headless Director
>> (org.eclipse.equinox.p2.director.app.application to create
>> zips of the product that contain P2 metadata.)
>>
>> Here is the exception I kept getting:
>> [java] Time to load bundles: 38
>> [java] Starting application: 43688
>> [java] !SESSION 2009-01-19 09:49:40.096
>> -----------------------------------------------
>> [java] eclipse.buildId=M20080911-1700
>> [java] java.version=1.6.0_05
>> [java] java.vendor=Sun Microsystems Inc.
>> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>> [java] Framework arguments: --launcher.suppressErrors
>> -application org.eclipse.equinox.p2.director.app.application -flavor
>> tooling -installIU com.verticon.tracker.editor.Tracker -version
>> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
>> -profileProperties org.eclipse.update.install.features=true -profile
>> TrackerProfile -metadataRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -artifactRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -destination
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>> -bundlepool
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>
>> [java] Command-line arguments: -clean -consoleLog -debug
>> --launcher.suppressErrors -application
>> org.eclipse.equinox.p2.director.app.application -flavor tooling
>> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
>> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
>> -roaming -profileProperties org.eclipse.update.install.features=true
>> -profile TrackerProfile -metadataRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -artifactRepository
>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>> -destination
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>> -bundlepool
>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>
>> [java]
>> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
>> 2009-01-19 09:51:57.823
>> [java] !MESSAGE Error parsing metadata repository
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.823
>> [java] !MESSAGE Error at line 10, column 91: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 10, column 91: Illegal value for
>> attribute "url" of element "repository": null
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 11, column 91: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 11, column 91: Illegal value for
>> attribute "url" of element "repository": null
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 12, column 90: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.824
>> [java] !MESSAGE Error at line 12, column 90: Illegal value for
>> attribute "url" of element "repository": null
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.825
>> [java] !MESSAGE Error at line 13, column 90: Missing required
>> attribute in "repository": url
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>> 09:51:57.825
>> [java] !MESSAGE Error at line 13, column 90: Illegal value for
>> attribute "url" of element "repository": null
>> [java] Installing com.verticon.tracker.editor.Tracker
>> 0.3.1.v200901190943.
>> [java] Installation failed.
>> [java]
>> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
>> 09:53:34.418
>> [java] !MESSAGE An error occurred while collecting items to be
>> installed
>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4 0
>> 2009-01-19 09:53:34.419
>> [java] !MESSAGE Problems downloading artifact:
>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>> 09:53:34.419
>> [java] !MESSAGE OK
>> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4 4
>> 2009-01-19 09:53:34.419
>> [java] !MESSAGE File has invalid content:
>> /tmp/signatureFile17624.jar
>> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4 0
>> 2009-01-19 09:53:34.419
>> [java] !MESSAGE Invalid content: plugin_customization.ini
>> [java] !STACK 0
>> [java] org.eclipse.osgi.signedcontent.InvalidContentException:
>> The file "plugin_customization.ini" in the jar
>> "/tmp/signatureFile17624.jar" has been tampered!
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>>
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>>
>> [java] at
>> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>>
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>>
>> [java] at
>> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>>
>> [java] at
>> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>>
>> [java] at
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>> 09:53:34.421
>> [java] !MESSAGE OK
>> [java] Java Result: 13
>>
>>
>> Got similar errors from the Admin UI when I pointed it at the repo I
>> created with PDE Build above:
>> An error occurred while collecting items to be installed
>> Problems downloading artifact:
>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>> File has invalid content: /tmp/signatureFile9067.jar
>> Invalid content: plugin_customization.ini
>> The file "plugin_customization.ini" in the jar
>> "/tmp/signatureFile9067.jar" has been tampered!
>>
>>
>> Was able to cause Andrew's demo to fail in similar ways by adding the
>> org.eclipse.platform plugin to the product configuration.
>>
>> Searching the bugzilla I noticed the similarity with
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
>> but because I have very little debug or diagnostic messages I had to
>> grope in the dark to fix this.
>>
>> My last grope was successful - I created a fresh target platform from
>> 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox plugins
>> that were required by the product.
>>
>> Since I would hate to have anyone else have to go through this hassle
>> and am still in the dark on what caused it - Does anyone have any
>> ideas, and/or suggestions on what might have been happening? Any
>> troubleshooting techniques for dealing with similar p2 problems would
>> also be helpful.
>>
>> thanks for any ideas,
>>
>> John
>>
>>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #588547 is a reply to message #41278] Wed, 21 January 2009 19:24 Go to previous message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

Although I was able to build my product from the repo, I can't do it
from an AdminUI without getting:

An error occurred while collecting items to be installed
Problems downloading artifact:
osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
File has invalid content: /tmp/signatureFile55296.jar
Invalid content: plugin_customization.ini
The file "plugin_customization.ini" in the jar
"/tmp/signatureFile55296.jar" has been tampered!


thanks,
John
John E. Conlon wrote:
> Hi Andrew,
>
> See inline comments...
>
> Andrew Niefer wrote:
>> So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
>> verification. You basically want to identify where the "corruption"
>> is being introduced.
> Yes, this is the idea I have been exploring (aka groping) as well.
>
> Before I go further I should point out that to try the tests you
> suggested I first attempted to get the thing to fail again.
> Unfortunately changing the target platform back to the original one I
> first experienced the failures in no longer fails. Ugh! (I failed to
> fail so to speak.) Nevertheless...
>>
>> In general, to track down this kind of verification error, you want to
>> run "jarsigner -verify" on the jars in several locations:
>>
>> 1) The jar in your repository
>> (buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)
>
> Have noticed all along that this plugin was a jar and that it failed
> verification. And even when the director succeeds in extracting a
> product from the repository (like in todays tests) this jar fails to
> verify...
> [echo] verifying
> /home/jconlon/eclipse-workspaces/ganymeade1/Builder/repo/plu gins/org.eclipse.platform_3.3.101.v200809111700.jar
>
> [exec] jarsigner: java.lang.SecurityException: SHA1 digest error
> for plugin_customization.ini
>
>>
>>
>> 2) The jar in the output of the build. (in the example this is
>> Builder/I.TestBuild/TestBuild-win32.win32.x86.zip
> In the output zip the org.eclipse.platform_3.3.101.v200809111700 is not
> a jar it's a folder.
>
>>
>> 3) The input to the build, ie baseLocation
>
> Here too org.eclipse.platform_3.3.101.v200809111700 in the baseLocation
> (my targetPlatform) is a folder.
>
>
> 4) Let me add a fourth test - the result zip from a successful director
> extraction.
>
> Here too org.eclipse.platform_3.3.101.v200809111700 is a folder
>
>
>> if (1) passes, then I guess there is a bug in p2 install somewhere
>> if (2) passes and (1) failed, the bug is in p2 metadata generation.
>> if (3) passes and (2) failed, the bug is in pde.build
>> if (3) fails, your input files are corrupt, where did you get them
>> from? were they ever modified?
>>
> Results -
> (1) failed to verify!
> (2) a folder - testing after rejaring validation passes
> (3) folder - testing after rejaring validation passes
> (4) folder - testing after rejaring validation passes
>
>
>
>
>> Since creating a fresh target fixed things for you, I expect the last
>> case, somehow the input files got corrupted.
> I hoped this was the case too, but things appear to be more convoluted,
> as mentioned above my old targetPlatform now seems to work. It also
> has/had a good folder in it.
>
>>
>> In this particular case, this is complicated by org.eclipse.platform
>> being a folder shaped bundle, so (2) and (3) both are folders.
>> jarsigner doesn't verify folders. You can try zipping them into jars
>> and verifying that.
> As mentioned above I rejared and verified.
>
> Or, org.eclipse.osgi has experimental API that can
>> verify folders, so you could write a small tool using
>> CertificateVerifierFactory. (See as an example
>> org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)
>>
>
> Questions:
> So Why is the repo jaring up the platform folder? (1)
>
> Why is it corrupting the jar in the process? (1)
>
> And if the repo has a broken platform plugin jared where is the
> resulting product created by the director getting the good folder to put
> in the result? (4)
>
> Or why doesn't the director now NOT fail with a bad jar in the repo?
>
> Aren't there any diagnostic messages that can log what is going on with
> the P2 and the director??
>
>
> thanks for all your help,
> John
>
>
>> -Andrew
>>
>> John E. Conlon wrote:
>>> Had been stuck for while on a problem with building my RCP features
>>> based app with PDE Build to include p2 metadata. The setup is based
>>> on Andrew Niefer's Example Headless build for a RCP product with p2 @
>>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>>>
>>>
>>> While I got Andrew's demo working with no problem I could not get my
>>> features based RCP product built by the Headless Director
>>> (org.eclipse.equinox.p2.director.app.application to create
>>> zips of the product that contain P2 metadata.)
>>>
>>> Here is the exception I kept getting:
>>> [java] Time to load bundles: 38
>>> [java] Starting application: 43688
>>> [java] !SESSION 2009-01-19 09:49:40.096
>>> -----------------------------------------------
>>> [java] eclipse.buildId=M20080911-1700
>>> [java] java.version=1.6.0_05
>>> [java] java.vendor=Sun Microsystems Inc.
>>> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>>> [java] Framework arguments: --launcher.suppressErrors
>>> -application org.eclipse.equinox.p2.director.app.application -flavor
>>> tooling -installIU com.verticon.tracker.editor.Tracker -version
>>> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
>>> -profileProperties org.eclipse.update.install.features=true -profile
>>> TrackerProfile -metadataRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -artifactRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -destination
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>> -bundlepool
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>
>>> [java] Command-line arguments: -clean -consoleLog -debug
>>> --launcher.suppressErrors -application
>>> org.eclipse.equinox.p2.director.app.application -flavor tooling
>>> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
>>> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
>>> -roaming -profileProperties org.eclipse.update.install.features=true
>>> -profile TrackerProfile -metadataRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -artifactRepository
>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>> -destination
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>> -bundlepool
>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>
>>> [java]
>>> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
>>> 2009-01-19 09:51:57.823
>>> [java] !MESSAGE Error parsing metadata repository
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.823
>>> [java] !MESSAGE Error at line 10, column 91: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 10, column 91: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 11, column 91: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 11, column 91: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 12, column 90: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.824
>>> [java] !MESSAGE Error at line 12, column 90: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.825
>>> [java] !MESSAGE Error at line 13, column 90: Missing required
>>> attribute in "repository": url
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>> 09:51:57.825
>>> [java] !MESSAGE Error at line 13, column 90: Illegal value for
>>> attribute "url" of element "repository": null
>>> [java] Installing com.verticon.tracker.editor.Tracker
>>> 0.3.1.v200901190943.
>>> [java] Installation failed.
>>> [java]
>>> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
>>> 09:53:34.418
>>> [java] !MESSAGE An error occurred while collecting items to be
>>> installed
>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4
>>> 0 2009-01-19 09:53:34.419
>>> [java] !MESSAGE Problems downloading artifact:
>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>> 09:53:34.419
>>> [java] !MESSAGE OK
>>> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4
>>> 4 2009-01-19 09:53:34.419
>>> [java] !MESSAGE File has invalid content:
>>> /tmp/signatureFile17624.jar
>>> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4
>>> 0 2009-01-19 09:53:34.419
>>> [java] !MESSAGE Invalid content: plugin_customization.ini
>>> [java] !STACK 0
>>> [java] org.eclipse.osgi.signedcontent.InvalidContentException:
>>> The file "plugin_customization.ini" in the jar
>>> "/tmp/signatureFile17624.jar" has been tampered!
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>>>
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>>>
>>> [java] at
>>> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>>>
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>>>
>>> [java] at
>>> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>>>
>>> [java] at
>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>>>
>>> [java] at
>>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>> 09:53:34.421
>>> [java] !MESSAGE OK
>>> [java] Java Result: 13
>>>
>>>
>>> Got similar errors from the Admin UI when I pointed it at the repo I
>>> created with PDE Build above:
>>> An error occurred while collecting items to be installed
>>> Problems downloading artifact:
>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>> File has invalid content: /tmp/signatureFile9067.jar
>>> Invalid content: plugin_customization.ini
>>> The file "plugin_customization.ini" in the jar
>>> "/tmp/signatureFile9067.jar" has been tampered!
>>>
>>>
>>> Was able to cause Andrew's demo to fail in similar ways by adding the
>>> org.eclipse.platform plugin to the product configuration.
>>>
>>> Searching the bugzilla I noticed the similarity with
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
>>> but because I have very little debug or diagnostic messages I had to
>>> grope in the dark to fix this.
>>>
>>> My last grope was successful - I created a fresh target platform from
>>> 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox
>>> plugins that were required by the product.
>>>
>>> Since I would hate to have anyone else have to go through this hassle
>>> and am still in the dark on what caused it - Does anyone have any
>>> ideas, and/or suggestions on what might have been happening? Any
>>> troubleshooting techniques for dealing with similar p2 problems would
>>> also be helpful.
>>>
>>> thanks for any ideas,
>>>
>>> John
>>>
>>>
Re: PDE Build, P2 Metadata and Target Platform Problems [message #588569 is a reply to message #41372] Thu, 22 January 2009 00:08 Go to previous message
Eclipse UserFriend
Originally posted by: jconlon.apache.org

John E. Conlon wrote:
> Although I was able to build my product from the repo, I can't do it
> from an AdminUI without getting:
>
> An error occurred while collecting items to be installed
> Problems downloading artifact:
> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
> File has invalid content: /tmp/signatureFile55296.jar
> Invalid content: plugin_customization.ini
> The file "plugin_customization.ini" in the jar
> "/tmp/signatureFile55296.jar" has been tampered!
>
This seems to be related to the other repository I had configured in the
Admin UI - http://download.eclipse.org/eclipse/updates/3.4.x

When I remove it and add a local repository ( a locally installed
Eclipse 3.4.1 SDK) to the the Admin UI, the product now installs in
Profiles.

So is the org.eclipse.platform in the
http://download.eclipse.org/eclipse/updates/3.4.x corrupt?

BTW - I can't add the
http://download.eclipse.org/eclipse/updates/3.4
to my Admin UI for some reason??


thanks for any help or insights,
John



>
> thanks,
> John
> John E. Conlon wrote:
>> Hi Andrew,
>>
>> See inline comments...
>>
>> Andrew Niefer wrote:
>>> So, org.eclipse.platform,3.3.101.v200809111700 is failing signature
>>> verification. You basically want to identify where the "corruption"
>>> is being introduced.
>> Yes, this is the idea I have been exploring (aka groping) as well.
>>
>> Before I go further I should point out that to try the tests you
>> suggested I first attempted to get the thing to fail again.
>> Unfortunately changing the target platform back to the original one I
>> first experienced the failures in no longer fails. Ugh! (I failed to
>> fail so to speak.) Nevertheless...
>>>
>>> In general, to track down this kind of verification error, you want
>>> to run "jarsigner -verify" on the jars in several locations:
>>>
>>> 1) The jar in your repository
>>> (buildDirectory/repo/plugins/org.eclipse.platform_3.3.101.v2 00809111700.jar)
>>
>>
>> Have noticed all along that this plugin was a jar and that it failed
>> verification. And even when the director succeeds in extracting a
>> product from the repository (like in todays tests) this jar fails to
>> verify...
>> [echo] verifying
>> /home/jconlon/eclipse-workspaces/ganymeade1/Builder/repo/plu gins/org.eclipse.platform_3.3.101.v200809111700.jar
>>
>> [exec] jarsigner: java.lang.SecurityException: SHA1 digest error
>> for plugin_customization.ini
>>
>>>
>>>
>>> 2) The jar in the output of the build. (in the example this is
>>> Builder/I.TestBuild/TestBuild-win32.win32.x86.zip
>> In the output zip the org.eclipse.platform_3.3.101.v200809111700 is
>> not a jar it's a folder.
>>
>>>
>>> 3) The input to the build, ie baseLocation
>>
>> Here too org.eclipse.platform_3.3.101.v200809111700 in the
>> baseLocation (my targetPlatform) is a folder.
>>
>>
>> 4) Let me add a fourth test - the result zip from a successful
>> director extraction.
>>
>> Here too org.eclipse.platform_3.3.101.v200809111700 is a folder
>>
>>
>>> if (1) passes, then I guess there is a bug in p2 install somewhere
>>> if (2) passes and (1) failed, the bug is in p2 metadata generation.
>>> if (3) passes and (2) failed, the bug is in pde.build
>>> if (3) fails, your input files are corrupt, where did you get them
>>> from? were they ever modified?
>>>
>> Results -
>> (1) failed to verify!
>> (2) a folder - testing after rejaring validation passes
>> (3) folder - testing after rejaring validation passes
>> (4) folder - testing after rejaring validation passes
>>
>>
>>
>>
>>> Since creating a fresh target fixed things for you, I expect the last
>>> case, somehow the input files got corrupted.
>> I hoped this was the case too, but things appear to be more
>> convoluted, as mentioned above my old targetPlatform now seems to
>> work. It also has/had a good folder in it.
>>
>>>
>>> In this particular case, this is complicated by org.eclipse.platform
>>> being a folder shaped bundle, so (2) and (3) both are folders.
>>> jarsigner doesn't verify folders. You can try zipping them into jars
>>> and verifying that.
>> As mentioned above I rejared and verified.
>>
>> Or, org.eclipse.osgi has experimental API that can
>>> verify folders, so you could write a small tool using
>>> CertificateVerifierFactory. (See as an example
>>> org.eclipse.pde.build.tests/PDETestCase#assertJarVerifies)
>>>
>>
>> Questions:
>> So Why is the repo jaring up the platform folder? (1)
>>
>> Why is it corrupting the jar in the process? (1)
>>
>> And if the repo has a broken platform plugin jared where is the
>> resulting product created by the director getting the good folder to
>> put in the result? (4)
>>
>> Or why doesn't the director now NOT fail with a bad jar in the repo?
>>
>> Aren't there any diagnostic messages that can log what is going on
>> with the P2 and the director??
>>
>>
>> thanks for all your help,
>> John
>>
>>
>>> -Andrew
>>>
>>> John E. Conlon wrote:
>>>> Had been stuck for while on a problem with building my RCP features
>>>> based app with PDE Build to include p2 metadata. The setup is based
>>>> on Andrew Niefer's Example Headless build for a RCP product with p2 @
>>>> http://aniefer.blogspot.com/2008/06/example-headless-build-f or-rcp-product.html
>>>>
>>>>
>>>> While I got Andrew's demo working with no problem I could not get my
>>>> features based RCP product built by the Headless Director
>>>> (org.eclipse.equinox.p2.director.app.application to create
>>>> zips of the product that contain P2 metadata.)
>>>>
>>>> Here is the exception I kept getting:
>>>> [java] Time to load bundles: 38
>>>> [java] Starting application: 43688
>>>> [java] !SESSION 2009-01-19 09:49:40.096
>>>> -----------------------------------------------
>>>> [java] eclipse.buildId=M20080911-1700
>>>> [java] java.version=1.6.0_05
>>>> [java] java.vendor=Sun Microsystems Inc.
>>>> [java] BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
>>>> [java] Framework arguments: --launcher.suppressErrors
>>>> -application org.eclipse.equinox.p2.director.app.application -flavor
>>>> tooling -installIU com.verticon.tracker.editor.Tracker -version
>>>> 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86 -roaming
>>>> -profileProperties org.eclipse.update.install.features=true -profile
>>>> TrackerProfile -metadataRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -artifactRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -destination
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>> -bundlepool
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>>
>>>> [java] Command-line arguments: -clean -consoleLog -debug
>>>> --launcher.suppressErrors -application
>>>> org.eclipse.equinox.p2.director.app.application -flavor tooling
>>>> -installIU com.verticon.tracker.editor.Tracker -debug -consoleLog
>>>> -version 0.3.1.v200901190943 -p2.os win32 -p2.ws win32 -p2.arch x86
>>>> -roaming -profileProperties org.eclipse.update.install.features=true
>>>> -profile TrackerProfile -metadataRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -artifactRepository
>>>> file:/home/jconlon/eclipse-workspaces/tracker-TRUNK/com.vert icon.tracker.builder/buildDirectory/repo
>>>> -destination
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>> -bundlepool
>>>> /home/jconlon/eclipse-workspaces/tracker-TRUNK/com.verticon. tracker.builder/buildDirectory/result/tmp/eclipse
>>>>
>>>> [java]
>>>> [java] !ENTRY org.eclipse.equinox.p2.metadata.repository 2 0
>>>> 2009-01-19 09:51:57.823
>>>> [java] !MESSAGE Error parsing metadata repository
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.823
>>>> [java] !MESSAGE Error at line 10, column 91: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 10, column 91: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 11, column 91: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 11, column 91: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 12, column 90: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.824
>>>> [java] !MESSAGE Error at line 12, column 90: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.825
>>>> [java] !MESSAGE Error at line 13, column 90: Missing required
>>>> attribute in "repository": url
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.core 2 0 2009-01-19
>>>> 09:51:57.825
>>>> [java] !MESSAGE Error at line 13, column 90: Illegal value for
>>>> attribute "url" of element "repository": null
>>>> [java] Installing com.verticon.tracker.editor.Tracker
>>>> 0.3.1.v200901190943.
>>>> [java] Installation failed.
>>>> [java]
>>>> [java] !ENTRY org.eclipse.equinox.p2.engine 4 4 2009-01-19
>>>> 09:53:34.418
>>>> [java] !MESSAGE An error occurred while collecting items to be
>>>> installed
>>>> [java] !SUBENTRY 1 org.eclipse.equinox.p2.artifact.repository 4
>>>> 0 2009-01-19 09:53:34.419
>>>> [java] !MESSAGE Problems downloading artifact:
>>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>>> 09:53:34.419
>>>> [java] !MESSAGE OK
>>>> [java] !SUBENTRY 2 org.eclipse.equinox.p2.artifact.repository 4
>>>> 4 2009-01-19 09:53:34.419
>>>> [java] !MESSAGE File has invalid content:
>>>> /tmp/signatureFile17624.jar
>>>> [java] !SUBENTRY 3 org.eclipse.equinox.p2.artifact.repository 4
>>>> 0 2009-01-19 09:53:34.419
>>>> [java] !MESSAGE Invalid content: plugin_customization.ini
>>>> [java] !STACK 0
>>>> [java] org.eclipse.osgi.signedcontent.InvalidContentException:
>>>> The file "plugin_customization.ini" in the jar
>>>> "/tmp/signatureFile17624.jar" has been tampered!
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. verifyDigests(DigestedInputStream.java:102)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.DigestedInputStream. read(DigestedInputStream.java:129)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.baseadaptor.bundlefile.BundleEntry.getBytes (BundleEntry.java:102)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.SignedContentImpl$Si gnedContentEntryImpl.verify(SignedContentImpl.java:167)
>>>>
>>>> [java] at
>>>> org.eclipse.osgi.internal.signedcontent.SignedContentFile.ge tSignedEntries(SignedContentFile.java:51)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verifyContent(SignatureVerifier.java:82)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.verify(SignatureVerifier.java:59)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.Signatur eVerifier.close(SignatureVerifier.java:100)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.reportStatus(SimpleArtifactRepositor y.java:815)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.downloadArtifact(SimpleArtifactRepos itory.java:442)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:515)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transferSingle(MirrorRequest.java:162)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.transfer(MirrorRequest.java:146)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.MirrorRe quest.perform(MirrorRequest.java:94)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.S impleArtifactRepository.getArtifact(SimpleArtifactRepository .java:504)
>>>>
>>>> [java] at
>>>> org.eclipse.equinox.internal.p2.artifact.repository.simple.D ownloadJob.run(DownloadJob.java:64)
>>>>
>>>> [java] at
>>>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
>>>> [java] !SUBENTRY 2 org.eclipse.core.runtime 0 0 2009-01-19
>>>> 09:53:34.421
>>>> [java] !MESSAGE OK
>>>> [java] Java Result: 13
>>>>
>>>>
>>>> Got similar errors from the Admin UI when I pointed it at the repo I
>>>> created with PDE Build above:
>>>> An error occurred while collecting items to be installed
>>>> Problems downloading artifact:
>>>> osgi.bundle,org.eclipse.platform,3.3.101.v200809111700.
>>>> File has invalid content: /tmp/signatureFile9067.jar
>>>> Invalid content: plugin_customization.ini
>>>> The file "plugin_customization.ini" in the jar
>>>> "/tmp/signatureFile9067.jar" has been tampered!
>>>>
>>>>
>>>> Was able to cause Andrew's demo to fail in similar ways by adding
>>>> the org.eclipse.platform plugin to the product configuration.
>>>>
>>>> Searching the bugzilla I noticed the similarity with
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=241596
>>>> but because I have very little debug or diagnostic messages I had to
>>>> grope in the dark to fix this.
>>>>
>>>> My last grope was successful - I created a fresh target platform
>>>> from 3.4.1 EMF-all-in-one, RCP-delta-pack, and a handful of Equinox
>>>> plugins that were required by the product.
>>>>
>>>> Since I would hate to have anyone else have to go through this
>>>> hassle and am still in the dark on what caused it - Does anyone
>>>> have any ideas, and/or suggestions on what might have been
>>>> happening? Any troubleshooting techniques for dealing with similar
>>>> p2 problems would also be helpful.
>>>>
>>>> thanks for any ideas,
>>>>
>>>> John
>>>>
>>>>
Previous Topic:Possible to have multiple features in one project?
Next Topic:Drag and Drop between 2 opened editors
Goto Forum:
  


Current Time: Fri Jun 18 04:00:58 GMT 2021

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

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

Back to the top