Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313878

Summary:	Can not build rap mail template: AIOOBE in ManifestConsitencyChecker
Product:	[Eclipse Project] PDE	Reporter:	Benno Baumgartner <benno.baumgartner>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	b.muskalla, ruediger.herrmann
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Benno Baumgartner

2010-05-21 04:28:34 EDT

1. Download latest eclipse rcp milestone (m7: http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/helios/M7/eclipse-rcp-helios-M7-win32.zip)
2. Start eclipse
3. New > Project > Plugin Project
4. name the project 'test'
5. Select the 'RAP Mail Template'
6. Finish.
IS: 

eclipse.buildId=I20100429-1549
java.version=1.6.0_18
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
Framework arguments:  -product org.eclipse.epp.package.rcp.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.rcp.product


Error
Fri May 21 10:23:00 CEST 2010
Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".

java.lang.ArrayIndexOutOfBoundsException: 1
	at org.eclipse.pde.internal.core.builders.BundleErrorReporter.validateRequireBundle(BundleErrorReporter.java:496)
	at org.eclipse.pde.internal.core.builders.BundleErrorReporter.validateContent(BundleErrorReporter.java:63)
	at org.eclipse.pde.internal.core.builders.ManifestConsistencyChecker.validateFiles(ManifestConsistencyChecker.java:302)
	at org.eclipse.pde.internal.core.builders.ManifestConsistencyChecker.validateProject(ManifestConsistencyChecker.java:223)
	at org.eclipse.pde.internal.core.builders.ManifestConsistencyChecker.build(ManifestConsistencyChecker.java:157)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Benjamin Muskalla

2010-05-21 05:33:10 EDT

Cannot reproduce this neither with M7 nor RC1 EPP package. Moving to PDE as this seems to be an issue with the manifest builder

Comment 2 Benno Baumgartner

2010-05-21 06:07:59 EDT

For me the eclipse-rcp-helios-M7 build is not usable to develop RAP. The RAP tooling seems to be only partially available. I.e. there is no welcome screen with RAP specific content, hence I can not install the RAP target platform. I had to download the plain eclipse M7 SDK build and install RAP using the update site: http://download.eclipse.org/rt/rap/1.3/tooling which worked fine (I was able to compile and run the mail rap template, but the AIOOBE was still thrown).

I've started eclipse-rcp-helios-M7 with -consolelog and -debug but no warnings or errors concerning missing bundles where logged.

Comment 3 Eclipse Webmaster

2019-09-06 16:19:16 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 4 Julian Honnen

2019-09-09 02:45:36 EDT

Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.