Hi gang, since I need a new Cocoon release for another package, I created a new ebuild for it for current release 2.1.3 (my first ebuild at all). I just took the old version for 2.0.2 and adjusted it for the current needs. While it went fine, I am not too happy with it at all. Basically the old ebuild just build the cocoon.war and installed it into an existing Tomcat release. This has following problems:
- my next package is build upon Cocoon, but anything left by the ebuild are the docs and the war file in Tomcat - cocoon runs into multiple servlet containers, we have in portage Tomcat, Resin, jBoss and j2eesdk - cocoon can run standalone - cocoon is not reported as a java-package by java-config Therefore I would like to: - build Cocoon into /usr/share/cocoon - provide a package.env - support USE-flags for installation of Cocoon into existing servlet containers or have a global virtual/servlet-container where cocoon is installed Looking at the ant ebuilds I can see the inherited java-pkg, but I am not sure, what this really means or if there is any documentation. Additionally I did not found the location of the eclasses (possibly an oversight in the docs). Also I am not sure about the strategy for the servlet container problem. If there is a default servlet container in the virtuals, Cocoon could be installed automatically, but I wonder if this is really what a user wants. Cocoon itself just is a "library" with samples. The generated webapp is of no use and mainly an example how to build your own webpp. It is fine, if after installation you can test the running Cocoon, but that's all. Any thoughts and hints welcome! Regards, J�rg -- [EMAIL PROTECTED] mailing list
