Been looking into this one and it appears that my first guess wasn't
right. Seems to actually be some issue with the ejb linking code.
For some reason the app client is trying to lookup a local view from
the server.
Investigating.
-David
On May 11, 2009, at 11:00 PM, David Blevins wrote:
Hmmm. I seem to recall mid April being the time that we realized we
weren't getting updated openejb snapshots due to the nexus switch.
I suspect it might some left over "must updated the clients to use
the right JNDI name" due to the fix that Manu made a few months back
that made it so the jndi name elements in the openejb-jar.xml worked
again.
-David
On May 11, 2009, at 7:31 PM, Jarek Gawor wrote:
Yep. The 'latest' link is updated when all testsuite test pass.
You can browse the results at:
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/
(under logs-<testtime>-<container> directories).
For example for enterprise-testsuite/sec-tests see
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/logs-2100-tomcat/enterprise-testsuite/sec-tests/sec-ear/target/surefire-reports/org.apache.geronimo.mavenplugins.geronimo.server.RunClientMojo.txt
Jarek
On Mon, May 11, 2009 at 10:07 PM, David Jencks <[email protected]
> wrote:
I strongly suspect that the testsuite has been failing since 15
april, thus
preventing copying to the "latest" location.
Personally I get more and different testsuite failures locally on
my mac,
but I haven't looked very hard into why. Can anyone supply info
on the test
failure that is occurring in the automated builds?
thanks
david jencks
On May 11, 2009, at 6:31 PM, Shawn Jiang wrote:
The trunk binary here was built on 15-Apr-2009 according to
http://people.apache.org/builds/geronimo/server/binaries/trunk/latest/
While the latest binary
here http://people.apache.org/builds/geronimo/server/binaries/trunk/20090511/
indicates
the latest build should be 12-May-2009
Is there any problem with the build system ?
--
Shawn
