commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: [jcs] jcache support?
Date Mon, 28 Apr 2014 05:02:54 GMT
+1

Open question is jcs-jcache instead of jcs-tck (and jcache tests = tcks). I
think it makes sense to extract it
Le 28 avr. 2014 00:47, "Olivier Lamy" <olamy@apache.org> a écrit :

> BTW the ideal would be to use modules in the build as:
> commons-jcs
>   commons-jcs-core
>   commons-jcs-tck
>
> Any issues with changing the structure?
>
> Olivier
>
> On 28 April 2014 09:32, Olivier Lamy <olamy@apache.org> wrote:
> > Hi,
> > I will have a look at the pr. Then move to defaut maven sources
> directories.
> >
> > *NOTE*: jsr 107 is java 1.7 required. (just before someone complain :-)
> ).
> >
> > Then I agree on moving to incubator.
> >
> >
> >
> > On 27 April 2014 19:10, Romain Manni-Bucau <rmannibucau@gmail.com>
> wrote:
> >> 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 <rmannibucau@gmail.com>:
> >>> 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 <rmannibucau@gmail.com>:
> >>>> 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 <sgoeschl@gmx.at>:
> >>>>> 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 <jeanouii@gmail.com>:
> >>>>>>>
> >>>>>>> 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 <
> rmannibucau@gmail.com>:
> >>>>>>>
> >>>>>>>> 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 <jeanouii@gmail.com
> >:
> >>>>>>>>>
> >>>>>>>>> +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 <tv@apache.org>:
> >>>>>>>>>
> >>>>>>>>>> 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
> >>
> >
> >
> >
> > --
> > Olivier Lamy
> > Ecetera: http://ecetera.com.au
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message