David,
thanks for the update. The Dali build is passing now with the v20070215
base builder, and I am about to released our code for M5. Concerning
the error messages we don’t get them anymore, and no we are not using
the patched version of JEM.
We are still having a unit test failure due to a timeout, and I am not
sure how to increase the value of it. It is a test that is normally
passing in our development environment, so I guess by increasing the
timeout value, it will also pass in the build.
Thanks again,
-Tran
[java] !ENTRY org.eclipse.osgi 2 0 2007-02-16 14:42:26.107
[java] !MESSAGE While loading class
"org.eclipse.jst.jpa.core.internal.JpaModel$1", thread
"Thread[Worker-1,5,main]" timed out waiting (5000ms) for thread
"Thread[main,5,main]" to finish starting bundle
"update@plugins/org.eclipse.jst.jpa.core_1.0.0.v200702150000.jar
[263]". To avoid deadlock, thread "Thread[Worker-1,5,main]" is
proceeding but "org.eclipse.jst.jpa.core.internal.JpaModel$1" may not
be fully initialized.
[java] !STACK 0
[java] org.osgi.framework.BundleException: State change in
progress for bundle
"update@plugins/org.eclipse.jst.jpa.core_1.0.0.v200702150000.jar" by
thread "main".
[java] at
org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1141)
[java] at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:258)
[java] at
org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400)
[java] at
org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111)
[java] at
org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417)
[java] at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189)
[java] at
org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340)
[java] at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:408)
[java] at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369)
[java] at
org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357)
[java] at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
[java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
[java] at
java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
[java] at
org.eclipse.jst.jpa.core.internal.JpaModel.fill(JpaModel.java:149)
David M Williams wrote:
Tran, for now I can just document
what
I've done on our eclipse.org build machine to get things working as far
as I have.
This is obviously error prone and
not
very re-producible, so glad to work with you to things smoothed out.
(And, I've been working the platform
releng team to help get this smoothed out as well, so maybe some new
developments from them later today
or
monday).
Currently we are using the v20070215
base builder.
I replaced the org.eclipse.pde.build
plugin in there is one I built from HEAD. (exported as non-jarred
deployable
plugin).
I "brute forced" removed the
2.3 version of javax.servlet and 2.0 javax.servlet.jsp from our build
machine
cached copy of
orbitBundles.zip (since, I think,
there's
still issues about the right one getting picked).
I'm not sure about those JEM
messages
.. are you using our patched version of JEM from
http://archive.eclipse.org/webtools/downloads/drivers/JEM-SDK-M20060918_wtp-patch-M4d.zip?
Also, yesterday/last night,
downloads/replications
was disabled on Eclipse, so that might be related.
Hi,
With the builder v20070213 we are starting to get the following errors.
I am not sure what is different in this new builder, and was wondering
if we need to update our build configuration.
Thanks for your help,
-Tran
Eclipse Dali / JPA Tools Development
…
[build-dali-dali] postFetch:
[build-dali-dali] generate:
[build-dali-dali] preGenerate:
[build-dali-dali] allElements:
[build-dali-dali] [echo] Target: generateScript
[build-dali-dali] [echo] basedir:
R:\build\home\builders\v20070213\org.eclipse.releng.basebuilder\plugins\org.eclipse.pde.build\scripts
[build-dali-dali] [echo] buildDirectory:
R:/build/home/build-dali-R2.0-I/workdir
[build-dali-dali] [echo] baseLocation:
R:/build/home/build-dali-R2.0-I/eclipse
[build-dali-dali] [echo] generic target:
R:\build\home\builders\v20070213\org.eclipse.releng.basebuilder\plugins\org.eclipse.pde.build\scripts\genericTargets.xml
[build-dali-dali] init:
[build-dali-dali] generateScript:
[build-dali-dali] [eclipse.buildScript] Some inter-plug-in dependencies
have not been satisfied.
[build-dali-dali] [eclipse.buildScript] Bundle org.eclipse.jst.jpa.db:
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.datatools.sqltools.editor.core_[1.0.0,2.0.0).
[build-dali-dali] [eclipse.buildScript] Bundle com.ibm.etools.emf.event:
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.emf.ecore_[2.2.0,3.0.0).
[build-dali-dali] [eclipse.buildScript] Bundle javax.servlet.jsp:
[build-dali-dali] [eclipse.buildScript] Unsatisfied import
package javax.servlet_2.4.0.
[build-dali-dali] [eclipse.buildScript] Unsatisfied import
package javax.servlet.http_2.4.0.
[build-dali-dali] [eclipse.buildScript] Unsatisfied import
package javax.servlet.resources_2.4.0.
[build-dali-dali] [eclipse.buildScript] Bundle org.eclipse.jem.beaninfo:
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.jem.proxy_[1.2.0,2.0.0).
[build-dali-dali] [eclipse.buildScript] Optional plug-in
com.ibm.etools.emf.event_[3.0.0,4.0.0) is not availble.
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.jem.workbench_[1.2.0,2.0.0).
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.emf.ecore_[2.2.0,3.0.0).
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.jem_[1.2.0,2.0.0).
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.emf.ecore.xmi_[2.2.0,3.0.0).
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.jem.util_[1.2.0,2.0.0).
[build-dali-dali] [eclipse.buildScript] Missing required
plug-in org.eclipse.emf.ecore.change_[2.2.0,3.0.0).
…
[build-dali-dali] BUILD FAILED
[build-dali-dali]
R:\_workspaces_\eclipse-3.3M5-build\releng.wtpbuilder\scripts\build\runbuild.xml:74:
The following error occurred while executing this line:
[build-dali-dali]
R:\build\home\builders\v20070213\org.eclipse.releng.basebuilder\plugins\org.eclipse.pde.build\scripts\build.xml:24:
The following error occurred while executing this line:
[build-dali-dali]
R:\build\home\builders\v20070213\org.eclipse.releng.basebuilder\plugins\org.eclipse.pde.build\scripts\build.xml:64:
The following error occurred while executing this line:
[build-dali-dali]
R:\_workspaces_\eclipse-3.3M5-build\releng.wtpbuilder\components\dali\customTargets.xml:18:
The following error occurred while executing this line:
[build-dali-dali]
R:\build\home\builders\v20070213\org.eclipse.releng.basebuilder\plugins\org.eclipse.pde.build\scripts\genericTargets.xml:82:
Unable to find plug-in: org.eclipse.jst.jpa.db_0.0.0. Please check the
error log for more details.
[build-dali-dali] Total time: 18 seconds
David M Williams wrote:
I was having pretty good local luck with an M5 based build (with an M5
based builder, and changes to avoid startup.jar),
so I am going to promote to our build.eclipse.org builds.
I'll admit there were 117 JUnit's still failing locally, but then I saw
there were 86 failures on eclipse.org ... so .... it's going to be a
long
night
for somebody!
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
|
