[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [hyades-dev] Anyone else having this build problem?
|
Anandi,
Marcelo is
right, the problem is actually generated by the JET builder. I've been misled by
the fact that all Hyades plugins have also the jars beside of the source code
and in my quick test I've been able to run the workspace (after I commented out
that line). We might need to remove the runtime jars from CVS (this will also
reduce the amount of time required to extract the projects), the runtime
jars should be packaged only in Hyades Runtime zip
file.
Thanks
!
Marius Slavescu
Tuesday, September 02, 2003 2:36
PM
To: hyades-dev@xxxxxxxxxxx
cc: Frank Budinsky/Toronto/IBM@IBMCA, Ed
Merks/Toronto/IBM@IBMCA
From: Marcelo
Paternostro/Toronto/IBM@IBMCA
Subject: Re: [hyades-dev] Anyone else having
this build problem?
Hi,
I've did a couple tests and it seems that
this problem is caused by the following plugins: - org.eclipse.hyades.test.http - org.eclipse.hyades.test.java - org.eclipse.hyades.test.manual This is happening because of the jet nature of
those projects. The Jet Engine is an EMF facility that allows code
generation from "JSP like" templates. There are 2 workarounds to avoid the
problem: 1. Close the 3 projects
or 2. Delete the jet builder entry in
the .project file of each project By copying Frank and Ed: I am
pasting here the exception that is thrown when the "Build All" is executed -
everything works fine if each project is build separately. Do you know
what is causing this? 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)
FYI we are using the EMF version that comes
with the wswb 2.1.1 driver (20030620_1105VL)
Best regards,
Marcelo Paternostro
IBM Toronto Lab
Voice:
1-905-413-3942
Fax: 1-905-413-4920
internet: marcelop@xxxxxxxxxx
|
| Anandi
Krishnamurthy/Cupertino/IBM@IBMUS
Sent by: hyades-dev-admin@xxxxxxxxxxx
02/09/2003 02:07 PM
Please respond to hyades-dev
|
To:
hyades-dev@xxxxxxxxxxx
cc:
Subject:
Re: [hyades-dev] Anyone else having this build
problem?
|
Marius,
>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
The plugin change above
did not fix our build problem.
Kim experimented by building subsets of the hyades
plugins.
Currently, we are able to build if we do "Close Projects" on
org.eclipse.hyades.test.* and org.eclipse.hyades.ui.sample
by selecting these projects,
right-clicking on "Close Project".
We do not believe it is a jre problem, since it
happens with
1.3.1... and 1.4.1...
Kim also reproduced it on a Solaris machine, so it
is not a
Windows
XP patch level problem.
Could it be running out of mem? I tried it with -Vmargs -Xmx1024M and
still got
the
error.
Any
other suggestions? I am able to proceed with the "Close Project"
workaround.
But
it sure will be nice to see this fixed.
Anandi
