Oct 28, 2009 04:43:52 PM, mark(a)klomp.org wrote:
Hi Gerry,
On Wed, 2009-10-28 at 15:21 -0500, greno(a)verizon.net wrote:
And in doing some more searching it appears that this deficiency in
rhino was due to some license issue that openjdk6 did not like so some
code was removed. If I understand correctly that license problem has
been addressed (at least from rhino perspective). So what would be
good is if there could be an update to all openjdk6 that would
incorporate the complete rhino code so javascript would fully work.
Indeed there is no legal issue anymore. And IcedTea/OpenJDK now include
(pick up the system installed) rhino to support javascript. I am not
sure how the tests that you say fail are exactly failing. Do you have
some more logs?
Might you be bitten by this issue?
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=179
"javascript script support through rhino should not be on bootclasspath"
If the issue above comes from using a non-system installed rhino, then
there is a workaround mentioned in the comments of that bug report that
might work for you. But if so, it would also be good to make your
package work against the installed rhino on your fedora system.
Cheers,
Mark
My immediate goal is to try to get an Axis2 package generated for F11 that doesn't
rely on any special "tricks". I guess for now I can disable the maven testing
in my specfile. That just grates on me though. But at least it's an Axis2 package
that should work except for the rhino deficiency in openjdk6.
As far as logs there really wasn't anything else in the logs other than what was on
the console.
And I have a feeling that I'm going to run into this same openjdk6/rhino trouble when
trying to do this for F12 as well.
-Gerry