[pkg-jboss-maintainer] Re: Bug#238411: ITP: JBoss -- J2EE based application server

[Philipp Hug]

btw: the list address was wrong.

well, I think 1 and 3 are too extreme. I think we should go with something
like 2:

how about this package layout:
libjboss3-client (contains jboss/client directory only; can be used without
jboss installation)
jboss3-doc (jboss/doc)
jboss3-server (contains stuff from jboss/lib jboss/bin and depends on
packages that contain the minimal configuration)

packages for the individual components: (maybe separated into j2ee compliant
and jboss specific packages; I guess there aren't many j2ee compliant
packages at least not in the jboss distribution)
jboss3-$SOMEPREFIX$-tomcat4/5 (conflicting packages, but for now we should
just build the jboss default)
jboss3-$SOMEPREFIX$-hsqldb
jboss3-$SOMEPREFIX$-clustering
jboss3-$SOMEPREFIX$-jms
jboss3-$SOMEPREFIX$-http-invoker
jboss3-$SOMEPREFIX$-mangement
...

One more thing about the .war and .sar files: I think they should be
installed extracted as we probably need to modify some files in them. But is
this debian policy compliant? Config files should be in /etc

tomcat: I guess we cannot use the existing debian package for tomcat,
because we need additional jboss specific files. but maybe it's possible to
use the jars from the tomcat package and depend on it.

philipp
----- Original Message ----- 
From: "Konstantinos Margaritis" <markos@debian.gr>
To: "Philipp Hug" <philipp@hug.cx>; "Daniel Ruoso" <daniel@ruoso.com>
Cc: <pkg-jboss-maintainer-request@lists.alioth.debian.org>
Sent: Friday, March 26, 2004 8:30 PM
Subject: Re: Bug#238411: ITP: JBoss -- J2EE based application server


> (cc'ing to the list as well, just a test)
>
> Hi,
>   I just did a checkout. As I see it we have a few alternatives in
> packaging this beast:
>
> 1. package everything in a single package (not really my idea)
> 2. make groups of packages (how and which should be discussed),
>     perhaps use the minimal/default/all package grouping?
> 3. package each directory in each own package:
>
> These are directories (excl. build and debian)
>
> cache   cluster  common  compatible  connector  console
> ejb  iiop  j2ee  jboss.net  jmx  jmx-remoting  management
> messaging  naming  remoting  security  server  system
> testsuite  thirdparty  tomcat  tools  transaction  varia
>
> First of all, I think that we're going to have a licensing problem. In
> the thirdparty folder, there are some sun jars, which I doubt are
> DFSG free. What I mean, even if we ever manage to run jboss with gij,
> or sablevm, kaffe, whatever, so that we don't have to depend on j2sdk
> from sun, even then the inclusion of the thirdparty non-free software
> in the source package, could pose problems. But please, correct me if
> I'm wrong.
>
> Also, we have tomcat41 and tomcat5 folders. Which one do we build by
> default (both and offer conflicting packages)?
>
> Imho, it's possible to create groups of packages, for example I find
> it unlikely for someone to use jboss without j2ee, console, system,
> server, jmx, so these might go into a single package, but jboss-net,
> messaging, security might go in another package. Of course, tomcat is
> a different case. Maybe we should use the existing Debian package if
> possible, in which case I suggest we contact the tomcat package
> maintainers.
>
> Also, I think I might try to run jboss using some free java vm (gij,
> sablevm, kaffe) so that we might not need to depend on a Sun JDK.
>
> That's all for now...
>
> Konstantinos
>
>
>