Re: [fedora-java] axis2: openjdk6 javascript e4x rhino
by Gerry Reno
Oct 28, 2009 04:16:18 PM, greno(a)verizon.net wrote:
Oct 28, 2009 01:17:13 PM, akurtako(a)redhat.com wrote:
> I've been trying to get axis2 built for F11. The newest version that
> meets all the dependencies is axis2 1.3 due to maven2 being only at
> 2.0.4. Axis2 1.3 nearly builds except for failing tests for the Scripting
> Module:
>
You can stop tests from compiling and running with -Dmaven.test.skipt=true.
And maven in F-12 is 2.0.8 so you may have a better luck with Fedora 12.
Regards,
Alex
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.axis2.scripting.convertors.JSOMElementConvertorTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.797 sec
> <<< FAILURE! Running org.apache.axis2.scripting.ScriptReceiverTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.081 sec
> <<< FAILURE!
>
> Results :
>
> Tests in error:
>
> testToAndFromScript(org.apache.axis2.scripting.convertors.JSOMElementConve
> rtorTest)
> testFromScript(org.apache.axis2.scripting.convertors.JSOMElementConvertorT
> est) testInvokeBusinessLogic(org.apache.axis2.scripting.ScriptReceiverTest)
> testAxisService(org.apache.axis2.scripting.ScriptReceiverTest)
>
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
>
> This appears to be related to this bug:
> https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/255149
>
> What is the best way to workaround this rhino problem with openjdk6?
>
> -Gerry
>
Yes, -Dmaven.test.skipt=true would keep the tests from compiling/running. But I think that the underlying problem is not fixed. It appears that rhino is crippled in some way in openjdk6 and if we could use a custom rhino jar then we could substitute it for the crippled system jar. And then the tests would probably pass. This is what I would like help in achieving.
-Gerry
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.
-Gerry
14 years, 5 months
Re: [fedora-java] axis2: openjdk6 javascript e4x rhino
by Gerry Reno
Oct 28, 2009 01:17:13 PM, akurtako(a)redhat.com wrote:
> I've been trying to get axis2 built for F11. The newest version that
> meets all the dependencies is axis2 1.3 due to maven2 being only at
> 2.0.4. Axis2 1.3 nearly builds except for failing tests for the Scripting
> Module:
>
You can stop tests from compiling and running with -Dmaven.test.skipt=true.
And maven in F-12 is 2.0.8 so you may have a better luck with Fedora 12.
Regards,
Alex
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.apache.axis2.scripting.convertors.JSOMElementConvertorTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.797 sec
> <<< FAILURE! Running org.apache.axis2.scripting.ScriptReceiverTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.081 sec
> <<< FAILURE!
>
> Results :
>
> Tests in error:
>
> testToAndFromScript(org.apache.axis2.scripting.convertors.JSOMElementConve
> rtorTest)
> testFromScript(org.apache.axis2.scripting.convertors.JSOMElementConvertorT
> est) testInvokeBusinessLogic(org.apache.axis2.scripting.ScriptReceiverTest)
> testAxisService(org.apache.axis2.scripting.ScriptReceiverTest)
>
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
>
>
> This appears to be related to this bug:
> https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/255149
>
> What is the best way to workaround this rhino problem with openjdk6?
>
> -Gerry
>
Yes, -Dmaven.test.skipt=true would keep the tests from compiling/running. But I think that the underlying problem is not fixed. It appears that rhino is crippled in some way in openjdk6 and if we could use a custom rhino jar then we could substitute it for the crippled system jar. And then the tests would probably pass. This is what I would like help in achieving.
-Gerry
14 years, 5 months
Manifest warning
by Orion Poplawski
Can someone explain this:
deploy:
[jar] Building jar:
/builddir/build/BUILD/javatar-2.5/tar-2.5/jars/tar.jar
[jar] Manifest warning: "Name" attributes should not occur in the
main
section and must be the first element in all other sections: "Name:
"Java Tar""
The manifest file is:
Manifest-Version: 2.3
Main-Class: com.ice.tar.tar
Name: "Java Tar"
Created-By: "Tim Endres <time(a)gjt.org>"
Implementation-Vendor: "com.ice"
Implementation-Title: "Java Tar Release 2.3"
Implementation-Version: "2.3"
Looks like Name: really should be:
Name: com/ice/tar/
looking at other manifests. Is that correct?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years, 5 months
Maven and tomcat
by Mary Ellen Foster
I've started poking into the requirements for building sesame, and I'm
hitting an issue with Tomcat and Maven on Rawhide. This happens every
time I try to rebuild the slf4j SRPM on Rawhide (as well as in other
cases, but this is an easy reproducer):
Here's the error, which I get with both mvn and mvn-jpp:
Project ID: null:servlet-api:jar:5.5.27
Reason: Cannot find parent: tomcat:tomcat-parent for project:
null:servlet-api:jar:5.5.27 for project null:servlet-api:jar:5.5.27
The package tomcat5-servlet-2.4-api *is* installed and includes a
plausible-looking
/usr/share/maven2/poms/JPP-tomcat5-servlet-2.4-api.pom file.
What's going on? What does Maven want that it's not getting?
Eventually I'll learn to understand and love Maven, I'm sure ... :)
MEF
--
Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/
Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab
School of Mathematical and Computer Sciences, Heriot-Watt University
Heriot-Watt University is a Scottish charity registered under charity
number SC000278
14 years, 6 months
Re: [fedora-java] Missing deps for eclipse-ptp
by Orion Poplawski
On 10/14/2009 01:38 PM, Jeff Johnston wrote:
> I have built the parsers into a separate sub-package called
> eclipse-cdt-parsers.
>
> Let me know if there are any problems. You'll probably want to use the
> new Eclipse 3.5.1 as there appears to be a bug in the 3.5.0 UI.
>
> -- Jeff J.
I'm not having much luck. See:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1747631
[eclipse.buildScript] Some inter-plug-in dependencies have not been
satisfied.
[eclipse.buildScript] Bundle org.eclipse.ptp.rdt.core.tests:
[eclipse.buildScript] Missing required plug-in
org.eclipse.cdt.core.tests_5.0.1.
[eclipse.buildScript] Bundle org.eclipse.ptp.pldt.upc:
[eclipse.buildScript] Missing required plug-in
org.eclipse.cdt.core.parser.upc_0.0.0.
[eclipse.buildScript] Bundle org.eclipse.cdt.core.lrparser.xlc:
[eclipse.buildScript] Missing required plug-in
org.eclipse.cdt.core.lrparser_5.1.0.
[eclipse.buildScript] Bundle org.eclipse.cdt.core.lrparser:
[eclipse.buildScript] Missing required plug-in
net.sourceforge.lpg.lpgjavaruntime_1.1.0.
[eclipse.buildScript] Bundle org.eclipse.cdt.core.parser.upc:
[eclipse.buildScript] Missing required plug-in
net.sourceforge.lpg.lpgjavaruntime_1.1.0.
[eclipse.buildScript] Missing required plug-in
org.eclipse.cdt.core.lrparser_5.0.0.
[eclipse.buildScript] Bundle org.eclipse.cdt.managedbuilder.xlupc.ui:
[eclipse.buildScript] Missing required plug-in
org.eclipse.cdt.core.parser.upc_5.0.0.
BUILD FAILED
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/build.xml:35:
The following error occurred while executing this line:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/build.xml:91:
The following error occurred while executing this line:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/templates/package-build/customTargets.xml:19:
The following error occurred while executing this line:
/usr/lib64/eclipse/dropins/sdk/plugins/org.eclipse.pde.build_3.5.1.R35x_20090820/scripts/genericTargets.xml:106:
Bundle org.eclipse.ptp.pldt.upc_0.0.0 failed to resolve.:
Missing required plug-in org.eclipse.cdt.core.parser.upc_0.0.0.
It's still not finding org.eclipse.cdt.core.parser.upc. I've tried
stripping all version information about upc I can find to no avail.
It also complains about lrparser and lpgjavaruntime. Not sure if I
should be adding lpg somehow to the pdebuild script.
Any help would be appreciated.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years, 6 months
