[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] Export problems
|
Hi Wim,
This is very strange.
Since this appears to be some subtle behavior of the IBM compiler under
these conditions (compiler compliance level of 1.5, but javac target of
1.4), I'm going to simply remove the jre.compilation.profile from the
build.properties for that project, do a build, and ask you to try this
again to make sure it doesn't recur. I don't understand why this is
happening, but in the interests of getting our builder working as
desired, lets see if this fixes things...and then we can see if we can
diagnose more carefully later...and report any bugs to jdt, IBM, or
wherever the problem actually lies.
I am doing a new build now, and will notify all of the build number on
the bug as soon as it is ready.
Scott
Wim Jongman wrote:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=315149
While helping Abishek and preparing for a blog I was fighting with
class not found errors in the exported product. After investigating I
found that a bundle cannot be build because of values in the
build.properties file:
jre.compilation.profile = J2SE-1.3
javacTarget=jsr14
results in:
# 5/31/10 11:50:26 PM CEST
# Eclipse Compiler for Java(TM) 0.A54, 3.6.0, Copyright IBM Corp 2000,
2010. All rights reserved.
Target level 'jsr14' is incompatible with source level '1.3'. A source
level '1.5' or better is required
and an empty jar file.
Noticed with project:
org.eclipse.ecf.remoteservice 4.1.0
The error is only noticable if the project is exported standalone. As
part of a product export there is no error only an empty jar which
gives you problems at runtime
Best regards,
Wim
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
