<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The real difference we are talking about is:<br>
<br>
unzip something.zip<br>
java -jar something.jar -nogui<br>
<br>
I don't really care about keeping the old zip, but it will change to be
built by the same metadata as the installer with the same breakup of
services. There can only be one source of distribution content, and its
the installer.<br>
<br>
Heiko W. Rupp wrote:
<blockquote cite="mid20060919150000.GA32622@pilhuhn.de" type="cite">
<pre wrap="">On Tue, Sep 19, 2006 at 08:23:31AM -0400, Tom Elrod wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Please do include a zip version as well (makes it a lot easier for
servers without X installed).
</pre>
</blockquote>
<pre wrap=""><!---->
Actually the "pure" zip is a big selling point for jboss for
many users.
This double inclusion of jars can probably also be solved
differently - e.g. in the Unix world by using symlinks
or have one post-download scipt that pulls the required
bits from all configuration and creates the other provided
configurations.
</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
jboss-development mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jboss-development">https://lists.jboss.org/mailman/listinfo/jboss-development</a>
</pre>
</blockquote>
<br>
</body>
</html>