Axis2 is a totally separate project to Axis v1.x. Hence since I needed the Axis2 package for a university course I made up the following ebuild with a basic structure for it. It currently uses packaged jars which is not recommended but the relevant packages can be put into the tree gradually prior to this being released. It is my first major ebuild project and although it is based on the tomcat-5.5.17-r7 ebuild, which itself has not been migrated to Generation 2 java building, it could be migrated easily I think. It has a few complicated elements which I have not attempted to get around in my first go. Any comments would be helpful.
Created attachment 94200 [details] Ebuild for www-servers/axis2-bin-1.0
Created attachment 94201 [details] BZ2 Tarball of the axis2-bin directory This contains the above ebuild with extra files for init scripts, conf files and env files as well as an initial WSDL2Java.sh file.
Sorry, but we're not adding new binary Java packages to the tree. If you can create a 'from source' ebuild it would be great.
(In reply to comment #3) > Sorry, but we're not adding new binary Java packages to the tree. If you can > create a 'from source' ebuild it would be great. > Okay, However, this program compiles using Maven, and if I am not wrong there is no system in place for source compiling Maven-based programs in ebuilds yet? Get back to me when there is a system if not already.
Due to: * bug in maven 2.0.4 * maven forcing to download deps from repository It will not be possible until 2.0.5 comes out or they implement <file> in dependecies. For now it's possible to use ant:ant to get build.xml.
If its using maven-1, then you can use the ant plugin to generate a build.xml. It will need slight tweaking, in particular, to disable fetching of dependencies. If its maven-2, the ant plugin may or may not generate a build.xml to fully reproduce the maven build... if it doesn't, then we'll need to have proper support for building maven packages.
