On Tue, 23 Mar 2004, Adam Jack <[EMAIL PROTECTED]> wrote: > Can we find a community e-mail address that would possible be > willing to 'hear' these, and approach them?
Difficult, the issues are too diverse. Let's look at them case by case >> [EMAIL PROTECTED]: webwork/webwork failed At least one missing dependcy. We just build this project as a detector for some Apache projects. I doubt that they are aware that Gump is building the project. >> [EMAIL PROTECTED]: mx4j/mx4j-tools-from-packaged-jetty failed The top item on my TODO list. A real API compatibility problem between mx4j and Axis. >> [EMAIL PROTECTED]: freemarker/freemarker failed Uses old jdom API. Same as webwork. >> [EMAIL PROTECTED]: jakarta-tapestry/ognl failed Tapestry is a problem in itself, since the Gump descriptor is inside the tapestry module. A manual nag together with a patch to the descriptor may help. Number two on my TODO list, helping hands welcome 8-) >> [EMAIL PROTECTED]: javasrc/javasrc failed Nag! >> [EMAIL PROTECTED]: xml-xerces/xml-xerces1 failed Simply needs 1.4.2_04 on LSD, not a problem with the project. >> [EMAIL PROTECTED]: jakarta-turbine-tdk/jakarta-turbine-tdk-docs failed Odd. Works fine on gump.covalent.net. We should work this out before we nag anybody. >> [EMAIL PROTECTED]: eyebrowse/eyebrowse failed Missing Mysql JDBC driver. Similar to webwork (they don't know what we are doing with their project). >> [EMAIL PROTECTED]: castor/castor failed Missing <work> entry. Similar to webwork, but this time we really need to build it since some of "our" projects (jetspeed, pluto) depend on it. >> [EMAIL PROTECTED]: jrefactory/jrefactory failed See webwork. It would probably suffice to turn the pretty printer it into an installed package. >> [EMAIL PROTECTED]: jgen/jgen failed Hasn't upgraded to later released versions of FOP in years (looks more or less dead[1]), will probably never build. Only project that depends on it is Turbine 3 which itself hasn't built since years. Could be turned into an installed package. On the other hand it is quite possible that they've never been told that jgen doesn't build against any recent FOP version. We could ask the FOP people for advice and send a patch to the jgen list to bring them up to FOP 0.20.5. Low on my personal priority list. Stefan Footnotes: [1] http://sourceforge.net/mailarchive/forum.php?forum_id=2500 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
