RE: MX4J build failure
Hi, > > I received a gump build failure for MX4J. This is due to recent > > commits for new functionalities that have dependencies with > > + servlet.jar (javax.servlet.* classes) hessian-3.0.8.jar > > + (downloadable from http://www.caucho.com), a pair of > protocols released under the ASL. > > Ah, I already added Servlet API and Resin, which I thought > would be needed. > > Hmm, looking closer you also seem to need Burlap in addition > to Hessian, will download that (2.1.12) as well. > > > Let me know if you need further information. > > No dependency on Resin itself, correct? No dependency on Resin. But you should download hessian-3.0.8.jar, which contains both hessian and burlap, not version 2.1.12. http://caucho.com/hessian/ (Download section) Thanks ! Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MX4J build failure
Hi guys, I received a gump build failure for MX4J. This is due to recent commits for new functionalities that have dependencies with + servlet.jar (javax.servlet.* classes) + hessian-3.0.8.jar (downloadable from http://www.caucho.com), a pair of protocols released under the ASL. Let me know if you need further information. Thanks Simon (MX4J project admin)
RE: [Mx4j-devel] MX4J build issue (on Gump)
Hi, > Folks, > > When I configured MX4J for Gump notification I did it in a > way that (I now > see) exposed a Gump bug & didn't get you notified. I'll fix > that bug, but here is another manual notification: > > http://brutus.apache.org/gump/public/mx4j/mx4j/index.html > http://brutus.apache.org/gump/public/mx4j/mx4j/gump_work/build > _mx4j_mx4j.html > > BUILD FAILED > /usr/local/gump/public/workspace/mx4j/build/build.xml:240: > Manifest file: > /usr/local/gump/public/workspace/mx4j/src/etc/MANIFEST.MF > does not exist. Should be fixed now. I guess if we don't hear anything from you, we can assume we did the right fix ;) Thanks ! Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [Mx4j-devel] MX4J and Gump (and another log4j deprecation effect)
Hi Adam, > I don't know if you are aware of Apache Gump, but it is a > continuous integration tool. See: > >http://gump.apache.org Yes, we know gump. >From time to time we get an email similar to this one, and we try to promptly fix the >build. Last time was Axis (they reintroduced the API as deprecated), this time seems Log4J. I am in a busy period now, but I'll try to get the build going as soon as I can, running against the latest stable Log4J (which I thought we were already doing, against 1.2.8 if I remember well). The only thing I'd prefer to avoid is to make our build running against the latest CVS (which are usually unstable), since this is gump's job. If Log4J removed deprecated API, fine for all, but I'd prefer to wait for a stable release of Log4J before modifying MX4J's build. If you think there is a better approach, please let me know. Thanks ! Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
