Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A2F511EDA for ; Sun, 27 Apr 2014 09:11:10 +0000 (UTC) Received: (qmail 80294 invoked by uid 500); 27 Apr 2014 09:11:07 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 79619 invoked by uid 500); 27 Apr 2014 09:11:00 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 79598 invoked by uid 99); 27 Apr 2014 09:10:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Apr 2014 09:10:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rmannibucau@gmail.com designates 209.85.216.51 as permitted sender) Received: from [209.85.216.51] (HELO mail-qa0-f51.google.com) (209.85.216.51) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 Apr 2014 09:10:54 +0000 Received: by mail-qa0-f51.google.com with SMTP id ih12so1937632qab.38 for ; Sun, 27 Apr 2014 02:10:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Bj7YmJRaEcUsqznMy2UifC4kr2n5Bpa2EtKzn293QyY=; b=nD9Rd6sHetLKMjS00RnqbBHor2VKkgw2aNRc6nlvjKsJKrVBFXOPv+aWv9Jzv2soaC mws9f+fW9SsGX6DNKxx9S6Zf2OwhGC8CKMjzIOTo8Pm2vL0em+GjfE7yioTEPkh66vOY SRFkTIgexsauuA/VraA295mFLzLqIUqBDBR38euUhOA0poZiqMXdXAeejowB8cbrPuHd nbQy0GBmNLqpTR9N2IltID0nH9aJXwfb6EUchbZRs3qW5VwwEKDCIHUgiY2abMM1EchN Ig9bi0rUIqLRUxCXBEwLI0vD8NlTARHbQvESu8Z5g4a7Bsj9ih2FkqyoiOLg+pnF7qfS 3PFQ== X-Received: by 10.140.101.201 with SMTP id u67mr20696qge.107.1398589831143; Sun, 27 Apr 2014 02:10:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.123.7 with HTTP; Sun, 27 Apr 2014 02:10:11 -0700 (PDT) In-Reply-To: References: <53554D8F.8080503@apache.org> <535565C7.9000507@apache.org> <535A53ED.1070203@gmx.at> From: Romain Manni-Bucau Date: Sun, 27 Apr 2014 11:10:11 +0200 Message-ID: Subject: Re: [jcs] jcache support? To: Commons Developers List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org side note: do we plan - after jcache first support please otherwise merge will be a pain - to align project structure on the default maven one (src/main/java, src/main/resources, src/test/java, src/test/resources)? would surely be easier for any new volunteer. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-04-26 19:31 GMT+02:00 Romain Manni-Bucau : > forked https://github.com/rmannibucau/commons-jcs, > > > still some work to make TCKs passing (first step) then make it usable > (think we'll pass tck in local mode then we need to make them > distributed friendly). > > current status: > Tests run: 465, Failures: 70, Errors: 22, Skipped: 0 > > PS: can be run using tck.sh > > > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > 2014-04-25 15:10 GMT+02:00 Romain Manni-Bucau : >> Ok, will try. >> >> Thanks >> >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau >> >> >> 2014-04-25 14:24 GMT+02:00 Siegfried Goeschl : >>> Hi folks, >>> >>> don't know the official view of things (current ASF Git support) but I use >>> GitHub to work on refactoring since it allows broader contribution (only >>> GitHub account is required) >>> >>> Cheers, >>> >>> Siegfried Goeschl >>> >>> >>> On 25.04.14 09:28, Romain Manni-Bucau wrote: >>>> >>>> yep was the idea. >>>> >>>> promoting jcs to incubator would definively be great. >>>> >>>> The short term question and sandbox reference was more: how can we >>>> work together on tcks. Using patches makes it hard (you need to merge >>>> all patches etc if several people are contributing). >>>> >>>> >>>> >>>> Romain Manni-Bucau >>>> Twitter: @rmannibucau >>>> Blog: http://rmannibucau.wordpress.com/ >>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>> Github: https://github.com/rmannibucau >>>> >>>> >>>> 2014-04-25 9:09 GMT+02:00 Jean-Louis MONTEIRO : >>>>> >>>>> You mean move to the sandbox area to work more easily on JCache >>>>> specification implementation. >>>>> And maybe try to get JCS to incubator and then try to promote to TLP? >>>>> >>>>> Not sure I got all your points. >>>>> >>>>> JLouis >>>>> >>>>> >>>>> 2014-04-25 8:43 GMT+02:00 Romain Manni-Bucau : >>>>> >>>>>> Did some more work ( still attached to >>>>>> https://issues.apache.org/jira/browse/JCS-118 - side note: i didnt >>>>>> recheck defaults tests here so maybe seomthing is broken regarding the >>>>>> configuration I changed a bit as mentionned in a comment ) >>>>>> >>>>>> The question at this point is how to go ahead? My main issue is while >>>>>> we don't have a fully working patch how can we share changes. Not sure >>>>>> patches are the best solution. [sandbox] could be since we are more to >>>>>> have perms. >>>>>> >>>>>> wdyt? >>>>>> >>>>>> >>>>>> Romain Manni-Bucau >>>>>> Twitter: @rmannibucau >>>>>> Blog: http://rmannibucau.wordpress.com/ >>>>>> LinkedIn: http://fr.linkedin.com/in/rmannibucau >>>>>> Github: https://github.com/rmannibucau >>>>>> >>>>>> >>>>>> 2014-04-22 9:41 GMT+02:00 Jean-Louis MONTEIRO : >>>>>>> >>>>>>> +1, that'd be awesome. >>>>>>> I don't think it's a big word/rework. Crossing fingers, it's just a >>>>>> >>>>>> matter >>>>>>> >>>>>>> of some interfaces and an SPI to implement. >>>>>>> >>>>>>> JLouis >>>>>>> >>>>>>> >>>>>>> 2014-04-21 20:39 GMT+02:00 Thomas Vandahl : >>>>>>> >>>>>>>> On 21.04.14 19:06, Romain Manni-Bucau wrote: >>>>>>>>> >>>>>>>>> saw it, I can rephrase the question this way: will tomee be able to >>>>>>>>> rely on jcs or should we directly use ehcache as do cxf already for >>>>>>>>> other needs. >>>>>>>>> >>>>>>>>> I'd like to see an apache product in the box but not sure we'll find >>>>>>>>> enough time to make it real short term >>>>>>>>> >>>>>>>> Me too. I think it should be not too hard and the 2.0 release is >>>>>>>> certainly a good milestone to work on this. At the moment, however, I >>>>>>>> maintain this project pretty much alone and I have no idea what JCache >>>>>>>> means and how it is related to the current architecture of JCS. >>>>>>>> I'm willing to help as much as I can. >>>>>>>> >>>>>>>> Bye, Thomas. >>>>>>>> >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>>>>>>> For additional commands, e-mail: dev-help@commons.apache.org >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Jean-Louis >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>>>>> For additional commands, e-mail: dev-help@commons.apache.org >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Jean-Louis >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>>> For additional commands, e-mail: dev-help@commons.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>> For additional commands, e-mail: dev-help@commons.apache.org >>> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org