On Thursday 18 March 2004 19:37, Philipp Hug wrote: > I built a jboss 3.2.3 package a while ago, but it wasn't compliant > with the debian java policy, because jboss has a lots of jars in > its own directories. Well, we could combine our efforts. What do > you think?
Ok, I'm ccing Daniel Ruoso as well, who is experienced in jboss himself and -from what I understand- would like to help in packaging this beast (and who had some pretty good ideas in his mail!). I'm including some parts: i was thinking about it these days... here goes some of my ideas: * Jboss is a j2ee application server, some applications aren't jboss specific or any other appserver specific, so, it would be nice if they could depend on j2ee-application-server. * Some services that run in jboss aren't part of jboss (I know they distribute together), it would be nice to have these parts as separated packages. Including debconf for each one... * For the above item, it would be necessary something like update-j2ee-application-server-rc.d, so packages that installs something inside de appserver would just use update-...-rc.d to setup links of the services and the applications (using prefix deploy we can setup a sorted start) So, what do you say we set up some project on alioth, put jboss into cvs and start playing, effectively being co-maintainers in this? Unfortunately, I can't really start working on this before Monday as I have to deliver something at work. But we can start planning on how to split work, package implementations etc... Konstantinos
