Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@www.apache.org Received: (qmail 54923 invoked from network); 4 Sep 2003 12:01:54 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Sep 2003 12:01:54 -0000 Received: (qmail 61334 invoked by uid 500); 4 Sep 2003 12:01:40 -0000 Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 61145 invoked by uid 500); 4 Sep 2003 12:01:38 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 61107 invoked from network); 4 Sep 2003 12:01:37 -0000 Received: from unknown (HELO reason.planet57.com) (202.183.214.4) by daedalus.apache.org with SMTP; 4 Sep 2003 12:01:37 -0000 Received: from coredevelopers.net (localhost [127.0.0.1]) by reason.planet57.com (Postfix) with ESMTP id 259BE4988E6 for ; Thu, 4 Sep 2003 18:24:08 +0700 (ICT) Date: Thu, 4 Sep 2003 18:24:07 +0700 Subject: Re: cvs commit: incubator-geronimo/modules/core/src/java/org/apache/geronimo/console/cli DConfigBeanConfigurator.java Deployer.java Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Jason Dillon To: geronimo-dev@incubator.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <4C3C8701-DECA-11D7-B324-000A9566A360@coredevelopers.net> X-Mailer: Apple Mail (2.552) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N >> My opinion is that these are Twiddle bits and do not belong here. >> Especially not in a console/cli package. > > I put it in there because Dain suggested that package in a message > on the 19th (though now that I look, he did recommend a separate module > from core). If you want it somewhere else, that's fine, but where? I would drop them in command for now. >> I looked at this and almost committed but noticed that it only handled >> jars and was not very happy about that. But I guess it is just the >> start. The deploy commands should be able to deploy anything which is >> deployable IMO. > > Umm, you opted not to commit the patch because it wasn't yet a > fully-functional product? Further, instead of making a comment > describing > the enhancements you felt were required in order for the patch to be > acceptable, you simply ignored the patch for two weeks? Surely you > jest! No I passed it on to Jeremy as he asked to review. > In any case, there's a bit of wiring that needs to happen to > support each module type. Right now only the EJB JAR code is in place > in > JSR-88, so we could offer more options in the deploy client, but it > would > just fail when the commands were passed on to JSR-88, and I thought > I'd be > honest up front instead. If you look at the code, there are todos > next to > each EJB JAR line saying something along the lines of "change this once > JSR-88 supports the other module types." Thats fine. --jason