Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344054 - [eclipse] IAE while upgrading to newer platform milestone
Summary: [eclipse] IAE while upgrading to newer platform milestone
Status: CLOSED WORKSFORME
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 18:27 EDT by Benjamin Muskalla CLA
Modified: 2011-05-18 10:19 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Muskalla CLA 2011-04-27 18:27:27 EDT 
What steps will reproduce the problem?
1. Used http://download.eclipse.org/eclipse/updates/3.7milestones to upgrade an M1 install

-- Error Details --
Date: Thu Apr 28 00:19:37 CEST 2011
Message: An error occurred while processing the JVM argument.
Severity: Error
Product: Eclipse SDK 3.7.0.v201008051700 (org.eclipse.sdk.ide)
Plugin: org.eclipse.equinox.p2.touchpoint.eclipse
Session Data:
eclipse.buildId=I20100805-1700
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86


Exception Stack Trace:
java.lang.IllegalArgumentException: Invalid format for byte argument: 768m .
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.AddJVMArgumentAction.getByteValue(AddJVMArgumentAction.java:168)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.AddJVMArgumentAction.compareSize(AddJVMArgumentAction.java:137)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.AddJVMArgumentAction.setToMax(AddJVMArgumentAction.java:123)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.AddJVMArgumentAction.addByteArg(AddJVMArgumentAction.java:81)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.AddJVMArgumentAction.addArg(AddJVMArgumentAction.java:53)
at org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.AddJVMArgumentAction.execute(AddJVMArgumentAction.java:34)
at org.eclipse.equinox.internal.p2.engine.ParameterizedProvisioningAction.execute(ParameterizedProvisioningAction.java:35)
at org.eclipse.equinox.internal.p2.engine.Phase.mainPerform(Phase.java:149)
at org.eclipse.equinox.internal.p2.engine.Phase.perform(Phase.java:78)
at org.eclipse.equinox.internal.p2.engine.PhaseSet.perform(PhaseSet.java:44)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:73)
at org.eclipse.equinox.internal.p2.engine.Engine.perform(Engine.java:44)
at org.eclipse.equinox.p2.operations.ProvisioningSession.performProvisioningPlan(ProvisioningSession.java:174)
at org.eclipse.equinox.p2.operations.ProfileModificationJob.runModal(ProfileModificationJob.java:79)
at org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:177)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Pascal Rapicault CLA 2011-05-17 20:08:39 EDT 
Do you remember your starting point for this? An SDK, a platform download? What were you upgrading to?
Thx
Comment 2 Benjamin Muskalla CLA 2011-05-18 06:16:00 EDT 
Used an Eclipse Platform SDK 3.7 M1 (classic) as base
Comment 3 Pascal Rapicault CLA 2011-05-18 10:19:44 EDT 
the M1 download is no longer available. I suspect that this could have been an issue with the metadata.