Re: [hyades-dev] Anyone else having this build problem?

["Marius Slavescu" <slavescu@xxxxxxxxxx>]

Hi Kim,

The problem can be fixed temporarily by commenting out the following line:

<import plugin="com.ibm.etools.jsse" optional="true"/>

in

/org.eclipse.hyades.execution.local/plugin.xml

then do an Update classpath by selecting all plugins. You will still get
some compile errors in this plugin (org.eclipse.hyades.execution.local),
those errors will not affect the rest of the plugins.

There might be an Eclipse bug also, anyway we will try to fix the
plugin.xml in the next drop.

Thanks !


Marius Slavescu

Friday, August 29, 2003 11:05 PM
To: hyades-dev@xxxxxxxxxxx
cc:
From: Kim Coleman/Cupertino/IBM@IBMUS
Subject: [hyades-dev] Anyone else having this build problem?



A co-worker of mine ran into this problem on Wed. when she pulled all new
Hyades sources. I reproduced it on my PC and on a Solaris box. I assume it
is an Eclipse bug, but I'm curious whether or not any of the other Hyades
developers are running into this:

Launch a suitable Eclipse with a shiny new workspace.
Set up your PD preferences Target Platform and Java Build Path as usual
Check out all the hyades modules from HEAD, as projects
When the autobuild kicks in, you get about 30k errors and eventually a
null pointer exception in Eclipse here:

java.lang.NullPointerException
at
org.eclipse.core.internal.events.BuildManager$1.handleException(BuildManager.java:161)
at
org.eclipse.core.internal.runtime.InternalPlatform.handleException(InternalPlatform.java:450)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:891)
at org.eclipse.core.runtime.Platform.run(Platform.java:413)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:165)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:243)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:212)
at
org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:884)
at
org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1600)
at
org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:85)
at
org.eclipse.team.internal.ccvs.ui.repo.RepositoryManager.run(RepositoryManager.java:796)
at
org.eclipse.team.internal.ccvs.ui.actions.CVSAction$1.run(CVSAction.java:242)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)

The errors are quite bogus - nonsense about being unable to find
org.eclipse.core and such. Presumably the result of whatever caused the
NPE.

I managed to make this go away by not checking out (or else closing)
org.eclipse.hyades.test.* and org.eclipse.hyades.ui.sample projects. (The
sample project just 'cause it had test dependency and so got build errors
when I ripped out the test projects).

I tried increasing the available memory to 256M (-vmargs -Xmx256M),
changing JRE's (flavors of 1.4.0 and 1.4.1), and changing OS's (Windows
and Solaris). I believe it has also been tried with both Eclipse 2.1 and
Eclipse 2.1.1. It is quite stunningly reproducible around here.

I suppose it could still be an out of memory problem, though since I've
been happily functioning with the eclipse default until now, it would
suprise me if 256M was still not enough. Have we been that prolific
lately?

I'll be happy to report it as a bug against Eclipse, but meanwhile, I'm
wondering what we did to the source base recently to tickle this. I hadn't
pulled new source for a week or two. Or does this only happen in
California?

I am about to abrogate my responsibilities by going away on vacation for a
week, so if details are desired, please contact Anandi Krishnamurthy
(anandik@xxxxxxxxxx), the original victim. :-)

Kim Coleman
PurifyPlus Development
IBM Rational Software, Cupertino, CA
kcoleman@xxxxxxxxxx

_______________________________________________
hyades-dev mailing list
hyades-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/hyades-dev