[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Rebuild Request: [eclipse-dev] Does your workspace build?
|
This is a regression. JDT debug needs a re-build to address this. The fix
is released and the map is updated/ready.
Darin
Pascal Rapicault/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
11/12/2008 07:33 AM
Please respond to
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
To
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
cc
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>, eclipse-dev-bounces@xxxxxxxxxxx
Subject
Re: [eclipse-dev] Does your workspace build?
Sorry to contradict but there is problem. I agree that there has always
been a warning when the EE was not matching, however in the past it did
not prevent my project to compile. So something has changed in this last
build. I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=255031.
It contains a relatively simple test case.
HTH,
PaScaL
Daniel Megert ---12/11/2008 03:34:15 AM---Hi Pascal, the reported problem
is not new: it was always reported as a warning when
From:
Daniel Megert <daniel_megert@xxxxxxxxxx>
To:
"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx>
Date:
12/11/2008 03:34 AM
Subject:
Re: [eclipse-dev] Does your workspace build?
Hi Pascal,
the reported problem is not new: it was always reported as a warning when
the specified EE (in the manifest) could not be satisfied by any of the
installed JREs/EEs. As you pointed out, the message could be improved (I
filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=254994 to track
this).
For M3 we added a preference (the one you've set to 'Ignore') to control
the severity of that problem because the warning was often not seen (or
ignored) by people which for example resulted in 1.5 code being released
into 1.4 projects, causing build errors in the official build. Of course
we've set the default to be 'Warning'. Now, it seems you encountered a
problem where the problem is accidentally reported as an error. Please
note
though that several projects in the SDK explicitly set this to be an error
in their project specific settings. Also, this problem (even if set to
'Error') will currently not abort the builder i.e. the builder should
still
continue to compile your project. Are you sure the compilation got
aborted?
If so, it looks like a different problem.
If you still see those unexpected errors then please file a bug report
against JDT Debug and cc me.
Dani
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|"General development mailing list of the Eclipse project."
<eclipse-dev@xxxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|12.11.2008 04:29 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[eclipse-dev] Does your workspace build? |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Since I have updated to this week I build (I20081111-0800) a large number
of my projects no longer compile.
Most of them have the following error: "Build path specifies execution
environment CDC-1.1/Foundation 1.1. There are no compatible JREs in the
workspace."
First I would like to understand how to change the level of error down to
be a warning (btw my project and workspace level preferences for "No
strictly compatible JRE for execution" are set to ignore"). Second was it
an intentional change? Third, JREs are not stored in workspaces, they are
referred to from a preference page.
Thx for providing clarifications on that.
PaScaL_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
