* J�rg Schaible <[EMAIL PROTECTED]> [2004-01-06 00:17:14 +0100]:

> - 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

> 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.

You are right, there are IMO several holes in the ebuild system when it
comes to java.

When it comes to web applications, there is currently a GLEP
(http://www.gentoo.org/proj/en/glep/glep-0011.html) which deals with the
many shortcomings of ebuild for "normal" web applications (basically,
anything running under apache).  Unfortunately, this GLEP doesn't mention
servlets at all (I was planning to send a proposal for servlets, but
never got around to it).  This is a shame, since many of the issues with
apache web applications are the same as for servlets.

Another problem with java ebuilds in general is that the current setup
cannot support slots.  There are many cases when one app requires
java-package-0.5.x, while another package requires 1.0.x.  This wouldn't
be too hard to add by changing the java-config script and the dojar
functions to add a slot number to the jar-files, kind of like what is
done for shared libraries.



Eivind

--
[EMAIL PROTECTED] mailing list

Reply via email to