On Sun, 7 Nov 2004, Dain Sundstrom wrote:
God I hope not. I spend a long long long time making sure our code
would work with unpacked archives. People don't want to jar up a
deployment during development. Having the tool jar it up, is a bit
better than no support at all, but the extra
+1
As an aside, the new deployer can not distribute unpacked modules. Is it
intentional?
Thanks,
Gianny
On 7/11/2004 4:35 AM, Aaron Mulder wrote:
I'd like to remove the current deployer.jar tool, remove the
command-line processing logic from the Deployer class, rename
new-deployer.jar to
On Mon, 8 Nov 2004, Gianny Damour wrote:
+1
As an aside, the new deployer can not distribute unpacked modules. Is it
intentional?
JSR-88 doesn't support unpacked modules. If you like, we could
assume any directory is an unpacked module, JAR it, distribute the JAR,
then delete the
+1 from me.
On Sat, 6 Nov 2004 12:35:01 -0500 (EST), Aaron Mulder
[EMAIL PROTECTED] wrote:
I'd like to remove the current deployer.jar tool, remove the
command-line processing logic from the Deployer class, rename
new-deployer.jar to deployer.jar and change the bootstrapper to build
