Is it possible for an ebuild guru to create an ebuild for Axis, I have tried for many hours but failed unfortunately. Thanks a lot in advance for your support. Apache Axis is an implementation of the SOAP ("Simple Object Access Protocol"). Reproducible: Always Steps to Reproduce:
JohnHerdy: would you mind posting up your initial attempts anyway?
Unfortunately I don't have my work anymore, because I tried it a long time ago. I grabbed the /usr/portage/skel.ebuild and filled it in. I can't remember the errors. If you want I can do it again and post the ebuild.
If there are not any other takers I will give this a try. I have a small amount of experience with Axis so I should be able to get it done with few problems. This will give me a chance to focus on a particular Gentoo project.
If you and magnet can work together that would be great. chuck
let's go.
Sounds good to me :D
Any updates?
I have started one. magnet now has internet access at home, so we need to start working together more.
Created attachment 30782 [details] The src_compile stuff for an Axis ebuild axis-1.1.ebuild This has all of the correct dependancies for Axis (which I've added to the tree), and the src_compile() function completed. I'm uncertain of how Axis should be installed on a system. After dependancies are installed, and before you build axis, you also need to run some variation on this command: java-config -A ant,jaf,avalon-logkit,junit,log4j,commons-discovery,commons-logging,activation,servletapi-2.4,pdflib,javamail,wsdl4j then update your environment so Axis can find everything it needs.
Created attachment 30844 [details] src_compile portion of an ebuild I took robbat2's src_compile portion of an ebuild and extended it a little more. I have hit a snag with the gnu-javamail package. It is required to compile axis. Right now it is masked and I am having trouble getting it to work. Ah I also had to make a small patch for gnu-javamail just to get it to start compiling.
Java devs, can you shed any light on this? Thanks chuck
Created attachment 31518 [details] src_compile completed ebuild The compiling problems were fixed with tickets #50206, #50928, and #50932. I create a couple of simple patches to fix the issues. Now I am stuck trying to figure out how to install Axis.
Any update on this?
That ebuild is as far as I got with the Java version. I talked to some Java folk a little while back and it seems this is an ebuild they tried some time back. They gave up on it because of all the integrated pieces and the lack of significant user need. I know there is also a c++ version of the application that magnet has been fighting with to compile. Maybe the c++ app is a better direction. All depends on if there is enough need for this application.
the C++ version's ebuild is not finished yet.I need to make the src_install part and to test it.
Any update?
nop , I'm stick in the installation process.
Created attachment 42653 [details] Working e-build (compile and installation) I fixed up the previous e-build so the dependencies were correct and it installed after compiling. It seems to work fine at least on my system.
Created attachment 43993 [details] Updated e-build to use wsdl4j rather than wsdl4j-bin
Created attachment 45205 [details] axis-1.1.ebuild the axis package is needed in portage because squirrel-sql depends on various lib's of axis. i was searching for an ebuild of axis and found this bug. this ebuild doesnt makes use of packed jars any longer, we delete the packed jars in src_unpack and replace them with java-pkg_jar-from <packagename>. i've also added ~amd64 because it works there, too.
Created attachment 46862 [details] axis-lib-1.2_rc2.ebuild it would be possible to divide the axis package into two parts. one could be called axis-lib. this one contains the libraries (axis.jar, jaxrpc.jar etc). this ebuild should fit the requirements for that package. i've removed all packed jar issues from it and it doesn't modifies the CLASSPATH directly any longer. there are different packages that make use of libraries that axis provides. those packages don't need the other things installed which would make the axis package complete. these things could go into a package called axis-server for example. that package provides startup scripts or whatever is needed besides the libraries.
Created attachment 46863 [details, diff] axis-1.2-gentoo.patch a patch for 1.2, adds thing to the classpath etc
any news about this? what do you think, should we split it? it would be nice to have axis itself in the tree and another aspect is that a bunch of open java bugs could be closed if this is going to be added to the tree.
I think the split up might be a good idea. However you mention startup scripts for the "Axis Server" and I fail to see where those should be needed for (afaik there is no *real* axis-server, it is used within a application server). So I think in the most ideal situation this could be handled by a USE flag (again ideally virtual/application-server or something along those lines). Please correct me if I am talking gibberish :-)
ok, that's also possible. :)
ok, commited. axis now available as 'www-servers/axis' for testing. feedback, suggestions and enhancements very welcome.
Created attachment 53028 [details] This ebuild will install axis inside tomcat. I took the previous ebuild as a base. I don't know what the previous patch was about, and I removed what I don't need. I don't know if any-one need something I removed. Now I get axis installed inside tomcat, working. Need more work to install examples, doc ... etc It is something, though. Require this patch file: --- xmls/properties.xml.orig 2005-03-09 11:22:17.000000000 +0100 +++ xmls/properties.xml 2005-03-09 11:22:37.000000000 +0100 @@ -49,7 +49,7 @@ <property name="commons-discovery.jar" location="${lib.dir}/commons-discovery.jar"/> <property name="commons-httpclient.jar" location="${lib.dir}/commons-httpclient.jar"/> <property name="commons-net.jar" location="${lib.dir}/commons-net-1.0.0-dev.jar"/> -<property name="log4j-core.jar" location="${lib.dir}/log4j-1.2.8.jar"/> +<property name="log4j-core.jar" location="${lib.dir}/log4j.jar"/> <property name="junit.jar" location="${lib.dir}/junit.jar"/> <property name="jimi.jar" location="${lib.dir}/JimiProClasses.zip"/> <property name="activation.jar" location="${lib.dir}/activation.jar"/>
