Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 51488 invoked from network); 8 Dec 2008 18:46:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Dec 2008 18:46:26 -0000 Received: (qmail 58473 invoked by uid 500); 8 Dec 2008 18:46:38 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 58130 invoked by uid 500); 8 Dec 2008 18:46:37 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 58119 invoked by uid 99); 8 Dec 2008 18:46:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2008 10:46:37 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [209.86.89.66] (HELO elasmtp-spurfowl.atl.sa.earthlink.net) (209.86.89.66) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2008 18:46:22 +0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=mK03CcU7LefRWlYTc5wjNKH50OrLemmtMLV+igPmFz2pTR04qEd98xGn15QN8gn9; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; Received: from [24.40.200.241] (helo=tetra.local) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from ) id 1L9l7J-00040a-1w for dev@geronimo.apache.org; Mon, 08 Dec 2008 13:46:01 -0500 Message-ID: <493D6B68.8090901@earthlink.net> Date: Mon, 08 Dec 2008 13:46:00 -0500 From: Joe Bohn User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: [DISCUSS] DayTrader 2.1.3 release References: <4935B0AD.3000306@apache.org> <4937324D.2070003@apache.org> <49395F56.3030407@earthlink.net> <493D316E.4080905@apache.org> In-Reply-To: <493D316E.4080905@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ELNK-Trace: c408501814fc19611aa676d7e74259b7b3291a7d08dfec7960993baa7332161d7caf75a4ed8b0c0d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 24.40.200.241 X-Virus-Checked: Checked by ClamAV on apache.org Donald Woods wrote: > Seems to be a maven problem, in that only one of the CARs is being > published.... This will probably take a reorg of the source tree to > fix, like moving the plugin builds into their own /plugins directory > like the server builds and only building one plugin per subdirectory. > > Should I cancel the vote and spend time fixing this, or release what we > have and fix it in trunk for DayTrader 2.2? I'm a bit undecided on this. I guess I'm ok with releasing this "as is" for 2.1.3. It's been a long time since we've had a Daytrader release and it seems that this is providing the primary functionality. And ... after all it is a sample ... so perhaps releasing what we have and fixing it in trunk for Daytrader 2.2 makes the most sense. Joe > > > -Donald > > > Joe Bohn wrote: >> Donald Woods wrote: >>> I was thinking of going with what we have, which is to manually >>> install the app clients. There are instructions in the README on how >>> to do that. >> >> I'm confused by this. The tomcat client plugins *are* built when you >> do a local build (as the README mentions) ... and supposedly they can >> be installed as plugins according to the README as well (I didn't try >> this). >> >> So why are these tomcat client car files not included in the >> staging-repo content that we are voting on? >> >> We're voting on both the source and the artifacts ... so if the source >> when built produces the artifacts it seems like we should be voting on >> those too. >> >> BTW, only the tomcat cars exist as an archive file ... there are jetty >> versions but they only exist in an unpacked form. >> >> Here are the artifacts for the clients produced by the build: >> ./daytrader-jetty/target/repository/org/apache/geronimo/daytrader/daytrader-streamer-client/2.1.3/daytrader-streamer-client-2.1.3.car >> >> ./daytrader-tomcat/target/daytrader-streamer-client-2.1.3.car >> ./daytrader-tomcat/target/repository/org/apache/geronimo/daytrader/daytrader-streamer-client/2.1.3/daytrader-streamer-client-2.1.3.car >> >> ./daytrader-jetty/target/repository/org/apache/geronimo/daytrader/daytrader-ws-client/2.1.3/daytrader-ws-client-2.1.3.car >> >> ./daytrader-tomcat/target/daytrader-ws-client-2.1.3.car >> ./daytrader-tomcat/target/repository/org/apache/geronimo/daytrader/daytrader-ws-client/2.1.3/daytrader-ws-client-2.1.3.car >> >> >> Is there some strange build processing that is creating these which is >> not honored by the mvn release plugin? >> >> Joe >> >>> >>> Maybe we can get them setup as plugins in daytrader/trunk for the 2.2 >>> release. >>> >>> >>> -Donald >>> >>> >>> Lin Sun wrote: >>>> Hi Donald, >>>> >>>> Thanks for getting this out for vote! >>>> >>>> Do we plan to allow users to install the app client as G plugin? If >>>> so, I think there is a manual work, that is to add the app client's >>>> plugin.xml file to the plugin catalog (geronimo-plugins.xml). I think >>>> we've got code to pack the app client car file and copy it onto local >>>> .m2 repo. >>>> >>>> Thanks >>>> >>>> Lin >>>> >>>> On Tue, Dec 2, 2008 at 5:03 PM, Donald Woods wrote: >>>>> I'm working on updating the daytrader/branches/2.1 for a 2.1.3 >>>>> release (will >>>>> rename it to branches/2.1.3 shortly.) Once everything is ready, >>>>> I'll put it >>>>> up for a vote. >>>>> >>>>> BTW - I'm not creating a branches/2.1 for on-going maintenance, as >>>>> if it is >>>>> ever needed, we can copy over the 2.1.3 tag to create it. I'm just >>>>> wanting >>>>> to get this overdue Daytrader 2.1.x out so we can focus on the 2.2 >>>>> release. >>>>> >>>>> >>>>> -Donald >>>>> >>>> >>> >> >> >