Tom,
My issues were based on the VM that was defined for the run
configuration for my test cases. This was not a Java 5 VM and
therefore I had those UnsupportedClassFileVersionErrors when
org.eclipse.osgi now was compiled against Java 5. Of course this was
easy to solve, thus there is no
Ah, Assuming we are not using any Java5 language features we need to
set the source and target options to Java 1.3 equivalents.
Jeff
Heiko Seeberger wrote:
Tom,
My issues were based on the VM that was defined for the run
configuration for my test cases. This was not a Java 5 VM and
Hi Heiko,
The reason this was added was to avoid compilation errors when importing
org.eclipse.osgi into your workspace as source from the target SDK. The
org.eclipse.osgi project supports the OSGi minimum 1.1 execution
environment but will make use of additional classes from J2SE 1.4 and 1.5
I believe there is a property we can put in the build.properties to
tell PDE which EE to use for compilation purposes. This seems like the
safer and more explicit path regardless of any issues Heiko may be
seeing.
Jeff
Thomas Watson wrote:
Hi Heiko,
The reason this was added was to
Subject:Re: [equinox-dev] org.eclipse.osgi_3.4.2.R34x_v20080826-1230
definesExecutionEnvironment: J2SE-1.5
I believe there is a property we can put in the build.properties to tell
PDE which EE
]
org.eclipse.osgi_3.4.2.R34x_v20080826-1230 defines
ExecutionEnvironment: J2SE-1.5
I believe there is a property we can put in the
build.properties to tell PDE which EE to use for compilation purposes.
This seems like the safer and more explicit path regardless of any
issues
