On Fri, 2003-01-10 at 13:37, Darryl L. Pierce wrote:
On 2003.01.10 12:00 Joe Phillips wrote:
how's very soon?
Too slow for me. I need it yesterday. :)
I had it yesterday but you didn't ask. 8)
you can find my packages for 3.0.2 + tomcat at
http://debian.innovationsw.com/
I have plans for 3.2 next.
Will it have any impact on my distribution? I'm currently using sarge
and am pulling Java from ibilio.org.
I don't know what you mean by that.
I built my packages on stable (woody) with a j2sdk package of my own
design. I don't use the ibilio.org packages so I don't know how well
they would play with my packages. I suspect they'll work fine.
Currently, my packages include the full JBOSS binary release (including
third-party libraries). Over time, I plan to replace pieces of the
JBOSS binary distro with debian packages. As this happens, I also
expect the JBOSS packages to grow & change.
For example, my JBOSS packages include JARs for log4j. Future packages
will likely make my JBOSS depend on log4j debs and include symlinks to
/usr/share/java/log4j.jar or similar.
I would expect my current packages to work with any java2-compiler on
any Debian release for the following reasons:
1- there are no native dependancies beyond whatever your JVM depends
upon
2- as described above, my packages are self-contained (eg. it has its
own log4j)
3- my packages are essentially a pure repackaging of the JBOSS.org
binary release - if it runs for you, so should my packages
Future revisions, may depend on specific versions of external
libraries. This is where you may have difficulties down the road.
add our site to your sources.list and apt-get install
jboss-server-default to get the default server installation. Then set
your JAVA_HOME in /etc/default/jboss and start it via /etc/init.d/jboss.
If you prefer 'all', install jboss-server-all instead. Likewise with
'minimal'.
enjoy!
-joe