[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [platform-releng-dev] FW: [eclipse-dev] FW: unable to build eclipse 2.0
|
Dean,
Thanks
again.
> And, in
fact, our build process is not very different at all from the source build.
Good to
know. The closer the source builds get to the "official" build process,
the better, IMO.
> 1) Which source build are you
using.
9/24 (cvs-fetch version)
> 2) What version and vendor of a JDK are you
using.
sun
jdk 1.4.1
>
3) What OS are you building on
w2k pro SP3
> 4) What OS are you
building for
> 5) What are
you issuing at the command line to start your build.
build -os win32 -ws win32
This command works the best so
far. The product is built and will run, but compile errors do occur, and
result in some plugins (PDE) not behaving properly. My current plan is,
when I have time, to dissect the build script and modify it so that it will stop
on the first build error. I will then fix the compile errors locally, one
by one, until the application will build successfully. I have used this
process in the past with other open source products and it works quite
well.
After that, I plan on modifying the script
so that the fetchAll and compile targets work correctly. This will allow
me to stay in sync with cvs using cvs update, while maintaining my own local
patches as needed.
> Also, Sonia tried this at home the
other night and it worked for her. (That is, her home is uncontaminated by
applications, path junk etc that may mask problems).
Very good point - I'm probably not being
very scientific about this... As far as the JVM crashes are concerned, I
am willing to believe that this is a purely local artifact. I am trying
this process on two different machines, and have had significantly fewer JVM
crashes on one of them. I will address the other issues as indicated
above.
Thanks again.
- Matt
Matt,
Hmmm. I'm sorry this is frustrating for
you. However, I know there are people running source builds on a nightly
basis. And, in fact, our build process is not very different at all
from the source build.
Also, Sonia
tried this at home the other night and it worked for her. (That is, her
home is uncontaminated by applications, path junk etc that may mask
problems).
Could you please let us
know the following:
1) Which
source build are you using.
2) What
version and vendor of a JDK are you using.
3) What OS are you building on
4) What OS are you building for
5) What are you issuing at the command line to start your build.
Thanks
...Dean...
| "Matt Munz"
<mmunz@xxxxxxxxxx> Sent by: platform-releng-dev-admin@xxxxxxxxxxx
09/24/2002 11:35 AM Please respond to platform-releng-dev
| To:
<platform-releng-dev@xxxxxxxxxxx> cc:
Subject: RE:
[platform-releng-dev] FW: [eclipse-dev] FW: unable to build eclipse
2.0 |
Sonia,
Thanks again. After several JVM crashes and
incomplete builds, I think
I'm going to give this a rest for a
while.
FYI, I believe that the scripts are malfunctioning.
Not knowing the
design of the scripts, I can't say whether the
effects I'm seeing are
designed or unintentional, but they do conflict with
my expectations.
The most difficult issue is that the build
system reports success even
when compiler errors occur (see test run
exerpts below).
I also had no success whatsoever with the -target
option, which always
complained about misplaced files.
-
Matt
...
D:\programs\eclipse-src-2-0-1-9-24\plugins\org.eclipse.pde.ui\src\org\eclips
e\pde\internal\ui\PDEPerspective.java:28:
cannot resolve symbol
[javac] symbol : variable
JavaUI
[javac] location: class
org.eclipse.pde.internal.ui.PDEPerspective
[javac]
topLeft.addView(JavaUI.ID_PACKAGES);
[javac]
^
[javac]
D:\programs\eclipse-src-2-0-1-9-24\plugins\org.eclipse.pde.ui\src\org\eclips
e\pde\internal\ui\PDEPerspective.java:29:
cannot resolve symbol
[javac] symbol : variable
JavaUI
[javac] location: class
org.eclipse.pde.internal.ui.PDEPerspective
[javac]
topLeft.addView(JavaUI.ID_TYPE_HIERARCHY);
[javac]
^
[javac]
D:\programs\eclipse-src-2-0-1-9-24\plugins\org.eclipse.pde.ui\src\org\eclips
e\pde\internal\ui\PDEPerspective.java:58:
cannot resolve symbol
[javac] symbol : variable
JavaUI
[javac] location: class
org.eclipse.pde.internal.ui.PDEPerspective
[javac]
factory.addActionSet(JavaUI.ID_ACTION_SET);
[javac]
^
[javac]
D:\programs\eclipse-src-2-0-1-9-24\plugins\org.eclipse.pde.ui\src\org\eclips
e\pde\internal\ui\PDEPerspective.java:59:
cannot resolve symbol
[javac] symbol : variable
JavaUI
[javac] location: class
org.eclipse.pde.internal.ui.PDEPerspective
[javac]
factory.addActionSet(JavaUI.ID_ELEMENT_CREATION_ACTION_SET);
[javac]
^
...
BUILD
SUCCESSFUL
Total time: 18 minutes 26 seconds
-----Original
Message-----
From:
platform-releng-dev-admin@xxxxxxxxxxx
[mailto:platform-releng-dev-admin@xxxxxxxxxxx]On
Behalf Of Sonia
Dimitrov
Sent: Monday, September 23, 2002 4:00 PM
To:
platform-releng-dev@xxxxxxxxxxx
Subject: RE: [platform-releng-dev] FW:
[eclipse-dev] FW: unable to build
eclipse 2.0
Source builds
using scripts later than > 0821 should work with a 1.4 level
JDK.
The 1.4 JDK was breaking the source builds previous to that
because
of the following
bugs:
http://bugs.eclipse.org/bugs/show_bug.cgi?id=22369
http://bugs.eclipse.org/bugs/show_bug.cgi?id=22365
I
just ran the source builds successfully with a 1.4 JDK with the
source
build downloads
from:
http://64.38.198.171/downloads/drops/N-N20020923-200209230010/index.php
I
used the following commands:
build -os win32 -ws win32
build -os
linux -ws motif
Sonia
"Matt Munz"
<mmunz@xxxxxxxxxx>
To:
<platform-releng-dev@xxxxxxxxxxx>
Sent by:
cc:
platform-releng-dev-admin@ Subject:
RE:
[platform-releng-dev] FW: [eclipse-dev] FW: unable to
eclipse.org
build eclipse 2.0
09/23/2002 02:52
PM
Please respond to
platform-releng-dev
Dean,
Thanks
a lot. Your answers help significantly. If you could,
please
respond to my follow-ups...
> The vast majority of Eclipse
build scripts are generated automatically by
the the Eclipse PDE
feature.
I assume this is the generation that happens when I
select "Create Plugin
JARs" from the context menu of plugin.xml.
Which ones were created by
hand?
build.xml seems like a likely
candidate, and I assume that the fetch
scripts
are also handmade.
Any others?
> With each binary build we ship a source build
zip file which contains the
CVS fetch scripts and geneated build.xml files
that can build a running
Eclipse using only a JDK 1.3.1.
I
think an update to the install instructions that explains this fully
would
help. Even using the "-bc" argument (pointing to jdk 1.3.x),
it
appears that running the ant scripts with jdk 1.4.1 will not work.
Perhaps
the compile succeeds, but the javadoc
fails?
BTW, perhaps I am missing something. I have assumed
that it is
acceptable
to run Eclipse using the 1.4.1 JRE -- is this not
the case? Is there a
list
of supported platforms for Eclipse?
I thought I had read something about
Windows, Linux, and MacOs with
JDK 1.3+. Perhaps this is not the case.
Could you point me to the
appropriate product specifications information?
> Since Eclipse was
designed with requirements to be able to build plugins
both from within and
externally to Eclipse we did not end up with a build
structure that allows
us to point at a
> CVS repository, do a cvs checkout and a build.sh.
However using the
source build scripts have pretty much this
flavour.
I'm not sure how those things relate. I'm also not
worried about the
"flavor" -- just ease of use, transparency, and
reproducibility. I have no
issues with "bootstrapping" per se, but
the KISS rule & experience tells me
that building Eclipse from the
commandline is a process that is easier to
understand, debug (if
necessary), and automate.
This brings me back to an earlier
question. I'm sure that your nightly
builds are not kicked off by
"build.xml>context menu>run ant". Can you
tell
me how your
nightly builds are run?
> As Eclipse is fixed to be 1.4 compatible
the source builds will likewise
migrate to 1.4. I suspect this is
what is causing you the most problems
right now.
I'm more than
willing to make the modifications needed to compile Eclipse
in 1.4.1.
What's the status of the migration effort?
Thanks
again.
- Matt
-----Original Message-----
From:
platform-releng-dev-admin@xxxxxxxxxxx
[mailto:platform-releng-dev-admin@xxxxxxxxxxx]On
Behalf Of Dean Roberts
Sent: Monday, September 23, 2002 1:41 PM
To:
platform-releng-dev@xxxxxxxxxxx
Subject: RE: [platform-releng-dev] FW:
[eclipse-dev] FW: unable to build
eclipse 2.0
Hi
Matt,
I'll see if I can answer some of your questions.
The vast
majority of Eclipse build scripts are generated automatically by
the the
Eclipse PDE feature. The "builder" consists of some
handwritten
scripts that call the appropriate targets in the generated
scripts for
compiling and packaging
the build. The source build scripts have the
approprite target calls
in them.
With each binary build we ship a source build zip file which
contains the
CVS fetch scripts and geneated build.xml files that can build
a running
Eclipse using only a JDK 1.3.1. Since Eclipse was designed
with
requirements to be able to build plugins both from within and
externally to
Eclipse we did not end up with a build structure that
allows us to point at
a CVS repository, do a cvs checkout and a build.sh.
However using the
source build scripts have pretty much this
flavour.
Currentley Eclipse will not compile under a 1.4 JDK due to
stricter
compiler
contraints in JDK 1.4. As well, SDK currentley
uses somce classes and/or
methods that are no longer in 1.3.1. As
Eclipse is fixed to be 1.4
compatible the source builds will likewise
migrate to 1.4. I suspect this
is what is causing you the most
problems right
now.
...Dean...
What I would
like to have is a process whereby I can
1) download the sources from cvs to
a clean directory
2) type "build all" or a similar command at the command
prompt
3) result with a working version of Eclipse, functionally equivalent
to the
binaries on http://eclipse.org
I would additionally like to
do all of this with jdk 1.4.1.
This is not a criticism or a request for
a feature/enhancement. I am
willing to do the work to make this
happen -- I can't imagine that this is
a
difficult task. What I am
asking for is some help in understanding the
build system. Could
someone help me by answering the following?
1) There are nightly &
release binaries on http://eclipse.org. How,
exactly, are they
built?
2) How, exactly, are the released build scripts generated (by
hand,
generated from project definitions, etc.)?
3) What are the rules,
conventions, design principles, etc. of the current
build
system?
"Matt Munz" <mmunz@xxxxxxxxxx>
Sent by:
platform-releng-dev-admin@xxxxxxxxxxx
09/23/2002 01:02 PM
Please respond
to platform-releng-dev
To:
<platform-releng-dev@xxxxxxxxxxx>
cc:
Subject:
RE: [platform-releng-dev] FW: [eclipse-dev] FW:
unable to build
eclipse 2.0
Sonia & Group,
> Does this
help?
Yes and no. I was able to get this to work partially by
using the
parameters you indicated and by running the scripts from another
instance
of
Eclipse. The result, although functional for some
tasks, lacks some of the
needed help files that are present in the binary
distribution (namely the
API docs).
I think I need to take a new
approach with this, so let me start by
explaining my situation.
I am
a professional developer, exploring the usefulness of
Eclipse-based
solutions for my company. I am primarily interested in
Eclipse as an
application platform, and am not as interested in it as a
java IDE.
My company already uses various open source solutions, so I
have some
experience with the process of integrating external sources into
our
internal integration / build process.
At this stage, I like
Eclipse -- I have seen a lot that I like, and have
been able to do some fun
things with it. I do not yet, however, trust
Eclipse. Trust,
for me, comes when I know that if the application breaks,
I
can go into
the source code and fix it myself. I need to have this
assurance to
move forward with this application, and I am highly motivated
to gain this
assurance.
Who knows, perhaps building Eclipse from the ground up once
is all I'll
ever
have to do. Perhaps the Eclipse team's own
integration processes & QA are
that good. Nevertheless, I'd like
to be able to build the app successfully
just once, at a
minimum.
What I would like to have is a process whereby I can
1)
download the sources from cvs to a clean directory
2) type "build all" or a
similar command at the command prompt
3) result with a working version of
Eclipse, functionally equivalent to the
binaries on
http://eclipse.org
I would additionally like to do all of this with jdk
1.4.1.
This is not a criticism or a request for a feature/enhancement.
I am
willing to do the work to make this happen -- I can't imagine
that this is
a
difficult task. What I am asking for is some help
in understanding the
build system. Could someone help me by answering
the following?
1) There are nightly & release binaries on
http://eclipse.org. How,
exactly, are they built?
2) How, exactly,
are the released build scripts generated (by hand,
generated from project
definitions, etc.)?
3) What are the rules, conventions, design principles,
etc. of the current
build system?
For reference, I look to the JBoss
Group's (http://jboss.org) build system,
that, while by no means perfect,
works quite well. If you are unfamiliar
with it I recommend trying it
out. The following steps will take you from
0
to JBoss in very
little time.
mkdir jboss-src
cd jboss-src
cvs ... co
jboss-all
cd jboss-all
cd build
build
The build process itself
takes 10 minutes or so. If I can get Eclipse to
build this way, I
will be quite happy.
For those who read all of this, thanks. I
look forward to your reply.
- Matt Munz
(mmunz@xxxxxxxxxx)
-----Original Message-----
From:
platform-releng-dev-admin@xxxxxxxxxxx
[mailto:platform-releng-dev-admin@xxxxxxxxxxx]On
Behalf Of Sonia
Dimitrov
Sent: Wednesday, August 07, 2002 2:06 PM
To:
platform-releng-dev@xxxxxxxxxxx
Subject: RE: [platform-releng-dev] FW:
[eclipse-dev] FW: unable to build
eclipse 2.0
I have had
success running the scripts on both linux and win2k using jdk
1.3.1 and Ant
1.4.
Here are a couple of problems that I have encountered and that
have been
reported:
Problem 1. Running out of memory
running the build. This can be
determined by doing a search for
"The system is out of resources" or
"java.lang.OutOfMemoryError" in the
compilelog.txt. I have seen this when
using the -bc switch on linux
in particular when using a 1.3.0 level jdk.
Fix. set the environment
variable ANT_OPTS=-Xmx256m in the build script
Problem 2.
Compiling against a non-compatible rt.jar i.e. version other
than
1.3. This occurs when the JAVA_HOME setting is pointing to a
jdk
version other than 1.3.x and the -bc option is not being used.
Fix
(option 1). set the -bc option when running the build. i.e. build
-os
win32 -ws win32 -bc c:\jdk1.3.1\jre\lib\rt.jar. I would also
suggest
setting the ANT_OPTS=-Xms256m environment variable in this
case.
Fix (option 2). set JAVA_HOME to a 1.3.x version of the jdk,
and switch to
this version in the path settings.
Does this
help?
Sonia
"Matt Munz"
<mmunz@xxxxxxxxxx>
To:
<platform-releng-dev@xxxxxxxxxxx>
Sent by:
cc:
platform-releng-dev-admin@ Subject:
RE:
[platform-releng-dev] FW: [eclipse-dev] FW: unable to build
eclipse 2.0
eclipse.org
08/07/2002 01:34 PM
Please respond to
platform-releng-dev
Sonia,
Thanks for your
reply.
1. which jdk version are you using in trying to run the
build?
I tried it with 1.3 and 1.4.
2. are you trying to
run the build using the build.bat/build script
or using eclipse to run Ant
on the build.xml file directly?
build script. I don't mind
bootstrapping builds, but I'd like to build
eclipse from the ground up (not
using eclipse to build itself) at least
once.
Have you had any
success building the sources? If so, what platform /
configuration?
I'm happy to replicate someone else's process -- trying to
debug what
went wrong in this case isn't a priority for me.
- Matt
-----Original
Message-----
From:
platform-releng-dev-admin@xxxxxxxxxxx
[mailto:platform-releng-dev-admin@xxxxxxxxxxx]On
Behalf Of Sonia
Dimitrov
Sent: Wednesday, August 07, 2002 1:23 PM
To:
platform-releng-dev@xxxxxxxxxxx
Subject: Re: [platform-releng-dev] FW:
[eclipse-dev] FW: unable to build
eclipse 2.0
Hi
Matt,
a few questions:
1.
which jdk version are you using in trying to run the build?
2. are you trying to run the build using the build.bat/build
script
or using eclipse to run Ant on the build.xml file
directly?
Sonia
"Matt Munz"
<mmunz@xxxxxxxxxx>
To:
<platform-releng-dev@xxxxxxxxxxx>
Sent by:
cc:
platform-releng-dev-admin@
Subject:
[platform-releng-dev] FW: [eclipse-dev] FW: unable to
build
eclipse.org
eclipse 2.0
08/07/2002 01:08 PM
Please respond to
platform-releng-dev
Hi all,
The following
thread has been diverted from eclipse-dev because
apparently
this topic
is more appropriate on this list. In a nutshell, I am having
trouble
getting the build to work on my machine and am looking for some
pointers
from people who have any luck at all with this. Details
below.
TIA.
- Matt Munz
-----Original Message-----
From:
eclipse-dev-admin@xxxxxxxxxxx
[mailto:eclipse-dev-admin@xxxxxxxxxxx]On
Behalf Of Matt Munz
Sent: Wednesday, August 07, 2002 11:32 AM
To:
Eclipse Developers
Subject: [eclipse-dev] FW: unable to build eclipse
2.0
Hi again,
Can anyone out there help me with this?
Has anyone used the build system
at all? If not, how are you
building the sources?
- Matt
-----Original Message-----
From:
Matt Munz [mailto:mmunz@xxxxxxxxxx]
Sent: Wednesday, July 31, 2002 2:55
PM
To: Eclipse Developers
Subject: unable to build eclipse
2.0
HI all,
Thanks again to those who created a build system
so that those of us who
want to build eclipse from the source code
can.
I am unable to build either eclipse 2.0 (release) or the
Integration
build
from 7/23. Is there some known issue I should be
aware of? My build
target
is win32. The build script
terminates with the following message.
BUILD SUCCESSFUL
Total time:
10 minutes 45 seconds
This is inaccurate, however, as I have found
compiler errors in the
compile.log, like the
following.
D:
\programs\eclipse-fetchbuild-2\plugins\org.eclipse.pde.ui\src\org\eclipse\
pde\internal\ui\editor\SelectionProvider.java:7:
package
org.eclipse.jface.viewers does not exist
[javac] import
org.eclipse.jface.viewers.*;
[javac] ^
The compile log and
console output are too verbose to be useful for me
right now -- I just
don't know where to start in wading through all that
text (more than 3
MB).
Could someone who has been able to get this to work submit their
process
to this list? I would be very greatful for that assistance.
My eclipse
startup log is included below.
-
Matt
!SESSION Jul 31, 2002
14:37:55.302
---------------------------------------------
java.version=1.4.1-beta
java.vendor=Sun
Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32,
NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
-install
file:D:/programs/eclipse-fetchbuild-2/
!ENTRY
org.eclipse.core.runtime 4 2 Jul 31, 2002 14:37:55.312
!MESSAGE Plug-in
org.eclipse.ui was unable to load
class
org.eclipse.ui.internal.Workbench.
!STACK
0
java.lang.ClassNotFoundException:
org.eclipse.ui.internal.Workbench
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(Delegating
URLClassLoader.java:734)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension
(PluginDescriptor.java:130)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension
(PluginDescriptor.java:167)
at
org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExten
sion(ConfigurationElement.java:102)
at
org.eclipse.core.internal.runtime.InternalPlatform.loaderGetRunnable(Interna
lPlatform.java:463)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
org.eclipse.core.internal.boot.InternalBootLoader.getRunnable(InternalBootLo
ader.java:440)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:771)
at
org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
org.eclipse.core.launcher.Main.basicRun(Main.java:248)
at
org.eclipse.core.launcher.Main.run(Main.java:698)
at
org.eclipse.core.launcher.Main.main(Main.java:534)
!ENTRY
org.eclipse.core.runtime 4 2 Jul 31, 2002 14:37:55.342
!MESSAGE Plug-in
org.eclipse.ui was unable to load
class
org.eclipse.ui.internal.Workbench.
!STACK
0
java.lang.ClassNotFoundException:
org.eclipse.ui.internal.Workbench
at
org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(Delegating
URLClassLoader.java:734)
at
java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension
(PluginDescriptor.java:130)
at
org.eclipse.core.internal.plugins.PluginDescriptor.createExecutableExtension
(PluginDescriptor.java:167)
at
org.eclipse.core.internal.plugins.ConfigurationElement.createExecutableExten
sion(ConfigurationElement.java:102)
at
org.eclipse.core.internal.runtime.InternalPlatform.loaderGetRunnable(Interna
lPlatform.java:463)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
org.eclipse.core.internal.boot.InternalBootLoader.getRunnable(InternalBootLo
ader.java:440)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:771)
at
org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
org.eclipse.core.launcher.Main.basicRun(Main.java:248)
at
org.eclipse.core.launcher.Main.run(Main.java:698)
at
org.eclipse.core.launcher.Main.main(Main.java:534)
!SESSION
-------------------------------------------------------------------
---
!ENTRY
org.eclipse.core.launcher 4 0 Jul 31, 2002 14:37:55.372
!MESSAGE Exception
launching the Eclipse
Platform:
!STACK
java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at
java.lang.reflect.Method.invoke(Method.java:324)
at
org.eclipse.core.launcher.Main.basicRun(Main.java:248)
at
org.eclipse.core.launcher.Main.run(Main.java:698)
at
org.eclipse.core.launcher.Main.main(Main.java:534)
Caused by:
java.lang.IllegalArgumentException: Application not
found:
org.eclipse.ui.workbench.
at
org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.jav
a:773)
at
org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
... 7
more
_______________________________________________
eclipse-dev
mailing
list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev
mailing
list
platform-releng-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-releng-dev