Btw, fixed a few broken tests yesterday night, fixed the broken pom and added a
few ALv2 license headers.
Now all builds fine on my local box (w java8).
LieGrue,
strub
On Tuesday, 29 April 2014, 22:20, Mark Struberg strub...@yahoo.de wrote:
plz folks do a full build before committing stuff
well submitted a patch yesterday fixing 1 failling test (due to j7 or
j8) in core and fixing jcache module (my previous patch was not
totally applied), hopefully it is the same fix but here is the patch
https://issues.apache.org/jira/browse/JCS-120
when I updated this morning it was still broken
Well, the TCK profile only gets activated on java7 - but I use java8 by default
already...
Another point. The module needs to ALWAYS be included. And _inside_ the
commons-jcs-tck-tests module we can just skip the tests if the 'tck' profile
doesn't get activated. Otherwise we would screw up
On 30.04.14 08:45, Romain Manni-Bucau wrote:
when I updated this morning it was still broken
Sorry, I needed to keep pace with Olivier structural changes and that's
why it probably slipped thru.
Thanks to all the contributors, I really appreciate your help.
Romain, I think that some of the
Yep, think stats for instance can be merged (would be great since ATM
we have local stats only).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-30 19:34 GMT+02:00
ok, Olivier did a refactoring of maven structure and it seems the best
we can do now. Here a little patch fixing some dependencies (mainly
cleanup): https://gist.github.com/rmannibucau/40f4bcf03dbcf17b8448
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn:
On 28.04.14 20:55, Emmanuel Bourg wrote:
Le 28/04/2014 20:44, Thomas Vandahl a écrit :
This throws me out of the game. My Snow Leopard MacBook is 1.6 only.
You can't upgrade it to Mavericks and install Java 7?
No I can't. MacBook One 32bit, you know.
Bye, Thomas.
plz folks do a full build before committing stuff next time.
Will fix the hamcrest deps now.
LieGrue,
strub
On Tuesday, 29 April 2014, 20:58, Thomas Vandahl t...@apache.org wrote:
On 28.04.14 20:55, Emmanuel Bourg wrote:
Le 28/04/2014 20:44, Thomas Vandahl a écrit :
This throws me out of
+1 Olivier
Thx
2014-04-28 7:02 GMT+02:00 Romain Manni-Bucau rmannibu...@gmail.com:
+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 ol...@apache.org a écrit :
BTW the ideal would be to
On 28.04.14 01:32, Olivier Lamy 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 :-) ).
This throws me out of the game. My Snow Leopard MacBook is 1.6 only.
Bye, Thomas.
On 28.04.14 01:46, Olivier Lamy wrote:
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?
Could we keep the core at 1.6-compatibility?
Bye, Thomas.
my thought was:
core: 1.6
jcache: 1.6
tck: run under java 7
think j6 is a constraint for 1-2 years but tck only runs on j7
@Thomas: in all cases some help on the produced code would be awesome
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn:
Le 28/04/2014 20:44, Thomas Vandahl a écrit :
This throws me out of the game. My Snow Leopard MacBook is 1.6 only.
You can't upgrade it to Mavericks and install Java 7?
Emmanuel Bourg
-
To unsubscribe, e-mail:
Jvm doesnt need to be linked to os btw, i try to avoid it to not get
upgrade surprises ;)
Le 28 avr. 2014 19:56, Emmanuel Bourg ebo...@apache.org a écrit :
Le 28/04/2014 20:44, Thomas Vandahl a écrit :
This throws me out of the game. My Snow Leopard MacBook is 1.6 only.
You can't upgrade it
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:
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 rmannibu...@gmail.com wrote:
side note: do we plan -
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 ol...@apache.org wrote:
Hi,
I will have a look at the pr. Then move to defaut maven sources directories.
+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 ol...@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
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
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
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 rmannibu...@gmail.com:
Did some more work (
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:
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
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 sgoes...@gmx.at:
Hi folks,
don't know the official view
+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 t...@apache.org:
On 21.04.14 19:06, Romain Manni-Bucau wrote:
saw it, I can rephrase the question
Hi
will jcs support jcache? Is it planned?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
-
To
On 21.04.14 13:51, Romain Manni-Bucau wrote:
Hi
will jcs support jcache? Is it planned?
See http://commons.apache.org/proper/commons-jcs/JCSandJCACHE.html for
comments on this topic.
Bye, Thomas.
-
To unsubscribe, e-mail:
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
Romain Manni-Bucau
Twitter:
opened https://issues.apache.org/jira/browse/JCS-118 to at least track it
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-04-21 19:06 GMT+02:00 Romain Manni-Bucau
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
Great Thomas,
Ill try to setup tck in the week then.we can see how far we are.
EE side should bring some more people so it can be important for jcs too.
Le 21 avr. 2014 19:39, Thomas Vandahl t...@apache.org a écrit :
On 21.04.14 19:06, Romain Manni-Bucau wrote:
saw it, I can rephrase the
31 matches
Mail list logo
