[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jdt-core-dev] Bug in F2??
|
Also, if you deliberately want to work with project cycles, you may want to
uncheck the 'stop building if invalid classpath' settings in the Java
compiler preferences (see Window>Preferences>Java>Compiler>Others>Stop
building when an invalid classpath is detected).
By default, build is prevented under these circumstances, and earlier we
wouldn't check for this issue, and likely build projects with thousands of
errors, when the only real problem was in the classpath.
Jerome_Lanneluc@oti
.com To: jdt-core-dev@xxxxxxxxxxx
Sent by: cc:
jdt-core-dev-admin@ Subject: Re: [jdt-core-dev] Bug in F2??
eclipse.org
06/04/2002 12:29 PM
Please respond to
jdt-core-dev
Christian,
This looks like a bug to me. Please enter a bug into bugzilla against
JDT/Debug.
Jerome
Christian Betz
<betz@xxxxxxxxxxxxxx-wu To:
jdt-core-dev@xxxxxxxxxxx
erzburg.de> cc:
Sent by: Subject:
[jdt-core-dev] Bug in F2??
jdt-core-dev-admin@ecli
pse.org
06/04/2002 10:33 AM
Please respond to
jdt-core-dev
Sorry - maybe this should better be put into bugzilla, but I am not sure
whether it is a bug or only a misfeature...
We do need projects refering to each other:
Project A is our core app and can be build standalone
Project B is a plugin to Project A and needs Project A to be build.
To run Project A with Project B as plugin, I need to add project B to
classpath. The only way I could find is to add it to build path: this
results in a cycle.
In earlier versions (I used build 20020410) this resulted in a warning in
the task-view, but worked well.
In F2, this leads to a stack overflow (see below) - forcing me to exit
eclipse.
So if this is not a bug it's definitely a misfeature. Could anybody tell me
how to work around the problem?
Thanks
Chris
--
Dipl.Inform. Christian Betz Chair for Computer
Science VI
Artificial Intelligence and Applied Computer
Science
University of
Wuerzburg
eMail: betz@xxxxxxxxxxxxxxxxxxxxxxxxxxx phone: +49 931 888
6744
www: http://ki.informatik.uni-wuerzburg.de/~betz/ fax: +49 931 888
6732
.log:
!SESSION Jun 04, 2002 10:13:24.906
---------------------------------------------
java.version=1.4.0-rc
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -os win32 -ws win32 -arch x86 -install
file:D:/programme/Dev/eclipse/
!ENTRY org.eclipse.jdt.launching 2 103 Jun 04, 2002 10:13:24.906
!MESSAGE VM not fully specified in launch configuration KnowME - missing VM
name. Reverting to default VM.
!ENTRY org.eclipse.jdt.launching 2 103 Jun 04, 2002 10:13:24.986
!MESSAGE VM not fully specified in launch configuration KnowME - missing VM
name. Reverting to default VM.
!ENTRY org.eclipse.jdt.launching 2 103 Jun 04, 2002 10:13:25.26
!MESSAGE VM not fully specified in launch configuration KnowME - missing VM
name. Reverting to default VM.
!ENTRY org.eclipse.jdt.launching 2 103 Jun 04, 2002 10:15:37.727
!MESSAGE VM not fully specified in launch configuration KnowME - missing VM
name. Reverting to default VM.
!ENTRY org.eclipse.ui 4 4 Jun 04, 2002 10:15:39.299
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Jun 04, 2002 10:15:39.299
!MESSAGE java.lang.StackOverflowError
!STACK 0
java.lang.StackOverflowError
at
org.eclipse.core.internal.dtree.DataTreeLookup.newLookup(DataTreeLookup.java:65)
at
org.eclipse.core.internal.dtree.DeltaDataTree.lookup(DeltaDataTree.java:710)
at
org.eclipse.core.internal.watson.ElementTree.includes(ElementTree.java:706)
at
org.eclipse.core.internal.resources.Workspace.getResourceInfo(Workspace.java:964)
at
org.eclipse.core.internal.resources.Container.findMember(Container.java:58)
at
org.eclipse.core.internal.resources.Container.findMember(Container.java:51)
at
org.eclipse.jdt.launching.JavaRuntime.expandProject(JavaRuntime.java:936)
at
org.eclipse.jdt.launching.JavaRuntime.expandProject(JavaRuntime.java:969)
at
org.eclipse.jdt.launching.JavaRuntime.expandProject(JavaRuntime.java:969)
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-core-dev
