Hi folks,
I spent quite some time to introduce generics in JCS. Now I finally
managed to reintegrate the changes into trunk. I would kindly ask for
reviewers. All improvements are welcome as I am no generics-expert.
Thanks in advance.
Bye, Thomas.
On 31.05.12 03:09, sebb wrote:
DoubleLinkedList looks incomplete.
It is parameterised by the node type (which must extend
DoubleLinkedListNode), but the node content type is not specified.
Unfortunately, I don't know how to fix this as I am no generics expert either.
Yeah, I failed on this
On 01.06.12 06:31, Bruno P. Kinoshita wrote:
Hi,
[jcs] seems very interesting :-) and maybe I could use it in some
applications too (or at least knowing about it may help).
Thanks, I'm trying to pull things straight to make it usable it current
environments. I use the old version a lot.
On 27.06.12 10:29, Mark Thomas wrote:
It looks like the commons-developers group has not been added to the
admin role for those projects.
I have granted you the admin role for those additional Jira projects.
While you are at it, could you please add me as an admin for JCS?
TIA.
Bye, Thomas.
On 06.08.12 00:12, sebb wrote:
On 4 August 2012 15:23, t...@apache.org wrote:
Author: tv
Date: Sat Aug 4 14:23:36 2012
New Revision: 1369332
URL: http://svn.apache.org/viewvc?rev=1369332view=rev
Log:
- Fixed lots of warnings and FindBugs issues
- Introduced carefully crafted
On 09.10.12 15:12, Simone Tripodi wrote:
So, I'm here to call for a vote for Commons PMC be the BeanShell
Sponsor, please cast your votes
[X] +1
Bye, Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 14.11.2012 08:40, Luc Maisonobe wrote:
Please, could someone who knows what to do step up?
Just a quick note that sites created by Maven can be published with
svnpubsub using the SCM Publish Maven Plugin
(http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/). I guess
this may
On 30.04.2013 00:01, Gilles wrote:
If someone doesn't develop a Commons component, he is not in the
developer
category for that component.
If his app _uses_ a Commons component, he is a user of that component.
This kind of users should indeed be encouraged to test snapshots, and
report
problems
On 06.07.2013 16:10, Benedikt Ritter wrote:
This may or may not be a problem when for creation of a git mirror by
infra. But the question is, do we really need this directory or can we
remove it?
We can surely remove it. The reason I kept the tempbuilds so far was
that they correspond to
On 08.07.2013 10:36, sebb wrote:
On 8 July 2013 09:12, Thomas Vandahl t...@apache.org wrote:
We can surely remove it. The reason I kept the tempbuilds so far was that
they correspond to release-versions in changes.xml and it may have been
useful to reproduce that a certain problem has been
Hi folks,
On the JCS site, the mailing list page still points to the old Jakarta
lists. I saw that a Mailing List page can be generated for a commons
component using some maven plugin. How would I add the pointers to the
old mailing lists to such a page?
Bye, Thomas.
On 08.11.11 20:59, Raffaele P. Guidi wrote:
Are you guys interested in merging efforts on this?
Yes, absolutely. I, however, would need some introduction into the
subject to understand how this is supposed to work. I can assure my
support for the integration into the JCS code.
Bye, Thomas.
On 09.11.11 00:10, Raffaele P. Guidi wrote:
This is not so different from an indexed file, just it is in memory - maybe
you could take a look at the code (which is fairly simple) and get back to
us with some more targeted questions.
I understand that the plugin is supposed to be added as an
On 19.11.11 09:43, Raffaele P. Guidi wrote:
It depends on what JCS requires to manage. If it handles the key-value
mapping on its own (as I suppose it does) you shouldn't need to use DM's
CacheService (it would be a waste of memory) which does the same.
CacheService puts KV mapping on top of
On 18.06.11 18:45, Rahul Akolkar wrote:
On Fri, Jun 17, 2011 at 4:09 AM, Henri Yandell flame...@gmail.com wrote:
Just code on its own = -1. As long as committers are coming, +1.
snip/
Proposal is to give existing committers karma (some have it). In
addition, there seems some new folks
On 22.07.11 11:33, Henri Yandell wrote:
Anyone adverse to me svn moving JCS over from Jakarta? It will mean
someone needing to update the site (which they should do while moving
that over).
I'd be willing to help, just need some directions.
I did some larger modifications to the code base
On 23.07.11 08:17, Henri Yandell wrote:
If you want to get the code committed, it makes life fractionally
easier for you rather than figuring out how to svn switch over. I'm
happy to wait on your nod before doing the svn move.
It's ok as it is now.
How is the policy here concerning larger
Hi folks,
I finished the updates to JDK 5 generics and concurrent and updated the
maven-2 build. Still some tests fail, others should never have passed. I
would like to ask for close review because I basically touched
everything. I tried to fix some obvious problems and typos on the way.
My
On 28.07.11 08:55, Henri Yandell wrote:
Mind if I upgrade JCS to Lang 3.0?
No problem, go ahead. Only that JCS doesn't use the new features.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 01.08.11 09:08, Stefan Bodewig wrote:
I've added a dependency on velocity-tools-view to the Gump descriptor
which may or may not fix the problem (velocity-tools-view currently
doesn't build itself in Gump and unless I managed to fix that as well,
JCS will simply not be built at all).
On 04.08.11 01:08, Rahul Akolkar wrote:
On Wed, Jul 27, 2011 at 3:54 PM, Rahul Akolkar rahul.akol...@gmail.com
wrote:
I cp -R'ed the site over, but it should be republished more gracefully.
Sorry for the delay, I still need to find the time to move the site to
Maven-2. Will re-publish when
Hi folks,
I finally managed to move the site generation to Maven2. The new site
derives the commons layout. Please check if something is missing.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 11.08.11 00:00, sebb wrote:
Only missing item is a logo for the component.
Well, then, I hereby declare the contest open. Your contributions are
welcome. :-)
Bye, Thomas.
-
To unsubscribe, e-mail:
Hi folks,
this special generics case is beyond my skills. Please see
org.apache.jcs.utils.struct.DoubleLinkedList. The DoubleLinkedListNode
needs to be generified. However I was not able to find a solution that
makes the compiler happy.
Any suggestions how to solve this?
Bye, Thomas.
On 12.08.11 08:41, Stefan Bodewig wrote:
Hi,
while looking through the Gump setup for JCS I realized the artifactId
inside the POM had been changed to commons-jcs while the groupId still
is org.apache.jcs. Does it make sense to keep the old groupId when
you change the artifactId anyway?
I
On 27.08.2013 22:31, sebb wrote:
On 25 August 2013 16:22, t...@apache.org wrote:
Author: tv
Date: Sun Aug 25 15:22:17 2013
New Revision: 1517307
URL: http://svn.apache.org/r1517307
Log:
Update commons-parent POM to version 30
Why not update to CP32?
Yeah, why not. 30 was all my Eclipse
Hi Sebb,
On 27.08.2013 22:58, s...@apache.org wrote:
Author: sebb
Date: Tue Aug 27 20:58:00 2013
New Revision: 1517984
URL: http://svn.apache.org/r1517984
Log:
IOException(String, Throwable) is Java 1.6+
Thanks for reviewing the code. I you see other issues, please jump in.
I'm planning to
Hi folks,
I'd like to ask for suggestions for a problem solution regarding the
typesafe handling of cache keys in JCS.
Previously, JCS was not aware of key and value types. So it was possible
to mix cache elements having different key types within the same cache
instance. This feature was abused
On 03.10.13 13:30, Thomas Vandahl wrote:
Hi folks,
I'd like to ask for suggestions for a problem solution regarding the
typesafe handling of cache keys in JCS.
Previously, JCS was not aware of key and value types. So it was possible
to mix cache elements having different key types within
On 10.10.13 16:50, James Carman wrote:
All,
We have had some great discussions about moving our SCM to Git. I
think it's time to put it to a vote. So, here we go:
+1 - yes, move to Git
-1 - no, do not move to Git
-1
I don't see any advantages.
Bye, Thomas.
On 24.10.13 10:52, Henning Schmiedehausen wrote:
[X] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Signatures are fine. Build an test with Java 1.6.0_65 on Mac OS X 10.6
works fine.
Henning, it's good to see you again
Hi Benedikt,
On 28.10.13 12:53, Benedikt Ritter wrote:
Trunk already contains 2.0-SNAPSHOT so it looks like someone intended to
roll out a new major release.
Yep, that was me. And yes, this is my intention. The said issue must be
fixed first, however. And I'm planning to add some JMX
Hi Luc,
On 22.11.13 15:19, Luc Maisonobe wrote:
I would like to thank Gary for accepting the position and to all of you
for your help during my term.
Thanks for serving us, Luc. You did a great job.
Bye, Thomas.
-
To
Hi Sebastian,
On 09.01.14 14:01, sebb wrote:
I had to update the JCS build to 1.6 on Continuum
Thanks for fixing this. How would I get access to the build settings to
maintain this myself next time?
It then ran, but the test was still running after 35 mins so I killed it
Unfortunately the log
Hi folks,
I'd like to attempt a JCS release of version 2.0. I volunteer as the
release manager. However as this will be my first release within Commons
and I don't want to spoil it, I could need some mentoring. Anyone
willing to support me?
Bye, Thomas.
Hi Benedikt,
On 29.03.14 16:58, Benedikt Ritter wrote:
I've released [lang] a few times. I can help. Feel free to drop any issues
here in the list, of get in touch with me in our IRC channel.
Thanks a lot. Indeed, I already have two questions.
- How is the download plugin supposed to work?
On 31.03.14 23:56, sebb wrote:
The Continuum build reports lots of test failures.
For example:
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=28476projectId=286
The tests are very noisy when run interactively.
This makes it difficult to pick out the test failures.
On 01.04.14 00:06, sebb wrote:
Just been looking at the dependencies.
Some of these are obsolete, for example commons-httpclient 3.0.1
What do you mean by obsolete? Use 4.x? Or remove the dependency
completely?
Bye, Thomas.
On 01.04.14 00:25, sebb wrote:
Also, there is a source tree called auxiliary-builds/jdk14.
Since the code now targets 1.6, I assume this is no longer needed?
No. The source tree contains features (such as the JGroups cache) that
have not made it (yet) into the main code base. I had a hard time
On 02.04.14 12:13, sebb wrote:
On 2 April 2014 07:42, Thomas Vandahl t...@apache.org wrote:
On 01.04.14 00:06, sebb wrote:
Just been looking at the dependencies.
Some of these are obsolete, for example commons-httpclient 3.0.1
What do you mean by obsolete?
No longer supported.
Use 4.x
On 02.04.14 12:23, sebb wrote:
However I assume the tests are still noisy on MacOS.
Once the unnecessary output is removed, can look at adding temporary
additional debug for the failing test cases in Continuum.
Yes, I directed logging to a log file and removed some of the chatter.
We'll see if
On 04.04.14 02:32, sebb wrote:
The FileDiskCacheUnitTest was failing because the tests were dependent
on the file timestamp resolution, so the cache did not always treat
the first created file as the oldest.
Adding pauses as necessary fixed this.
I inherited the code. Personally, I'd throw
On 07.04.14 21:38, sebb wrote:
Indeed. It also has some peculiar behaviour in that it allows the
storage directory to be changed after initialisation.
Looks like the directory can be anywhere so it might use a directory
with existing files in it that are not actually cache files.
Seems rather
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:
Hi Siggi,
On 18.04.14 20:47, Siegfried Goeschl wrote:
Hi folks,
so judging from the conversation we have volunteers for Apache Commons VFS :-)
Reclaiming the message thread - who else would like to present his/her pet
component?
Well, I'd talk about JCS a bit but that would require that
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
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.
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
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
On 01.05.14 09:52, Mark Struberg wrote:
Hi folks!
I've moved the TCK run into an own profile. You can activate it via
$ mvn clean install -PjcacheTck
We should also activate it by default during a release.
Btw, why is this project target 1.7? We do not use anything from java7 right?
On 02.05.14 10:13, Jean-Louis MONTEIRO wrote:
He he, sure :)
Here is the error even in Java 7.
ERROR]
/Users/jlmonteiro/devs/asf/commons/proper/jcs/trunk/commons-jcs-jcache/src/main/java/org/apache/commons/jcs/jcache/JCSCache.java:[92,129]
cannot find symbol
symbol: class
Hi folks,
I took some time to look over the code of the JCache implementation and
I have some suggestions for simplification (under the assumption that I
understood the intention correctly).
- JCS does not implement the same model of cache element expiry, however
a few more existing features
On 05.05.14 19:40, Benedikt Ritter wrote:
Hi,
we have a pull request at github for [lang] which proposes to introduce new
methods in NumberUtils that take varargs as input parameters instead of
arrays [1]. I think a better solution would be to change those old methods
to use varargs instead
On 06.05.14 08:31, Romain Manni-Bucau wrote:
Hi guys,
few questions about jcs:
1) I played a bit with remote cache server etc and didn't find a lot
of use cases, do we keep it this way (linked to 4) )?
The features of JCS are quite comprehensive. Not everything is useful
for everybody. So
On 06.05.14 13:27, Romain Manni-Bucau wrote:
Here some pseudo-core details about my first mail:
New internals:
* NetworkTopology
* EntryRepartitor: compute the index of the
* Node (LocalNode which is current impl and RemoteNode which is just a
remote facade relying Network)
On 06.05.14 22:39, Romain Manni-Bucau wrote:
That's my experience too. So let's go for the concurrenthashmap impl
(patch on jira) and then see how we do the invalidation stuff in a
2.1?
Again, I'd like to kindly ask to evaluate the already existing features
of JCS. It might appear to you as an
On 11.05.14 14:43, rmannibu...@apache.org wrote:
Author: rmannibucau
Date: Sun May 11 12:43:07 2014
New Revision: 1593785
URL: http://svn.apache.org/r1593785
Log:
adding API CacheEvictor
Hi Romain,
AFAICS, you are currently creating several JCache replacements for
already existing JCS
On 11.05.14 11:22, sebb wrote:
In which case, why do we need to bother to change the source?
The compiler only has the byte-code as reference when compiling source
that uses the method.
Yeah, well, there is a slight difference in the method meta data. The
isVarArgs() method will return true
Hi Romain,
On 11.05.14 20:33, Romain Manni-Bucau wrote:
actually I evaluated JCS and found several issues (why ATM JCache
doesn't rely on it anymore):
Well, then what does the project have to do with JCS? The initial idea
was to provide JCache compatibility to JCS, IIRC.
1) about network
On 07.05.14 12:03, Raffaele P. Guidi wrote:
Talking about next steps, have you ever considered a second level of (off
heap) cache? My question is of course not so casual, being the PMC of
DirectMemory :) I think there are a lot of potential synergies, here. I
include DM's dev list to gather
On 12.05.14 22:24, Romain Manni-Bucau wrote:
Hi
why using org.apache.commons.jcs.utils.struct.DoubleLinkedListNode and
not a synchronized java.util.LinkedList ?
BTW I'd be happy if we can get rid of this synchronized structure
There are some benchmark tests in the test directory that
Hello Romain,
On 07.05.14 23:30, Romain Manni-Bucau wrote:
Any objection (mainly on the fact we don't rely on jcs-core)?
Yes, I object. I expressed a number of concerns regarding your approach,
your modifications of the main API, the re-implementation of existing
features etc. You chose not to
On 17.05.14 05:41, Bernd Eckenfels wrote:
Hello,
what is it about those JCS Build Failures. They happen for quite some
time. Is this a known problem? Is it worked upon?
I would like to fix it, but I cannot reproduce the problem on any of the
systems I have access to. My guess is a network
Hi Romain,
sorry, I only find time to look at my mail once a week.
On 16.05.14 23:40, Romain Manni-Bucau wrote:
Hi Thomas, is it an old mail or not?
It is not.
If not can you detail the changes you dislike please?
- Removing Serializable from the key and value types. This is required
for
On 22.05.14 19:24, Romain Manni-Bucau wrote:
About eviction: is it still the case? Thought I removed it when merged with
jcs backend
I have no idea. I lost track when I needed to merge my changes with your
reformatted imports (That was one thing I forgot). Why was that necessary?
Not sure I
Am 24.05.2014 um 19:42 schrieb Phil Steitz phil.ste...@gmail.com:
I don't know anything really about [jcs], but what I think those who
are interested in working on this thing need to do is come to
consensus on what a new modular structure will look like, what
changes make sense, what
Hi Romain,
On 24.05.14 20:16, Romain Manni-Bucau wrote:
basically I respected all remarks, only pendings ones are:
1) modules
Ok, right now, I see the following modules
- commons-jcs-core
- commons-jcs-jcache
- commons-jcs-jcache-extras
- commons-jcs-jcache-openjpa
- commons-jcs-tck-tests
I
On 25.05.14 17:18, Romain Manni-Bucau wrote:
Extras is a set of useful basic classes for JCache usage. OpenJPA is JCache
support for L2 cache in openjpa.
The goal is to make what we propose with jcache module as usable as
possible and avoid glue code as much as possible in application code.
On 25.05.14 17:45, Phil Steitz wrote:
On 5/25/14, 8:18 AM, Romain Manni-Bucau wrote:
And please consider reacting to Phils comment on the removal of
synchronized keywords. It took years to pinpoint the race issues in the
JCS code. I don't claim the current situation to be perfect but at least
On 26.05.14 22:05, Romain Manni-Bucau wrote:
the point is putIfAbsent is costly but globally once (can be done
concurrently but this is ignorable at runtime). Only important thing is to
ensure then the system uses a single instance.
Right, but what if the instance creates a file, socket or
On 26.05.14 21:53, Romain Manni-Bucau wrote:
Globally agree
Next question is: do we plan a 2.0.0-alpha without it (said otherwise I'd
like JCache to be out ASAP and avoid what we live @BVal taking soon 1 year
to release) or do we wait to be very stable to do a proper 2.0.0?
My primary goal
On 28.05.14 13:47, Romain Manni-Bucau wrote:
I'm convinced of it (why the comment was this way). I'll try to rework it
this week based on the LockFactory we spoke about in another thread.
Please try to make sure that your conviction is proven by some unit test.
Bye, Thomas.
: https://github.com/rmannibucau
2014-05-29 10:44 GMT+02:00 Thomas Vandahl t...@apache.org:
On 28.05.14 19:15, Romain Manni-Bucau wrote:
Hi
any objection to use debug level for first log message
in org.apache.commons.jcs.engine.control.CompositeCache#dispose(boolean)?
It prints
On 02.06.14 17:02, Romain Manni-Bucau wrote:
actually these logs are really debug log not intended to be activated in
prod excepted if there is a big issue (@thomas: if you can confirm it would
be great).
Yes, logging is for debugging purposes mostly. But if you remove them:
how would you do
On 01.06.14 21:26, Romain Manni-Bucau wrote:
Hi
I have two main point to discuss regarding the logging:
1) LogHelper stuffI committed. Idea was to cache isDebugEnabled to get a if
(boolean) complexity and not go through the logging framework which can
imply several layers (filter, appender,
On 29.06.14 16:12, s...@apache.org wrote:
Remove my attribution entries
Why? These were issues created by you.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
On 29.06.14 16:08, sebb wrote:
+/**
+ * Get the naming url used for RMI registration
+ *
+ * @param registryHost
+ * @param registryPort
+ * @param serviceName
+ * @return
Does this need @since marker?
It might. However this would be true for a lot of API
These are leftovers from the hurried project reorganization. I don't remember
the original state but it is probably sufficient to look into the 1.3 tag. I'll
check this.
Bye, Thomas.
Am 29.06.2014 um 21:34 schrieb sebb seb...@gmail.com:
The test/conf/ and test/test-conf/ directories seem
Hi Romain,
On 19.08.14 19:14, Romain Manni-Bucau wrote:
From my experience snapshot = rc = alpha = beta (all are considered
unstable from users).
I'll wait Thomas' feedback and if everybody is happy I can try to
release next week.
I did a quick review of the open JIRA issues and updated a
Hi folks,
On 20.08.14 16:41, Romain Manni-Bucau wrote:
trying to make it complete:
Solutions are:
1) [logging] - think it is deprecated too
2) log4j2: not integrated at all with anything so a bit early but we
*need* to be compatible
3) slf4j: broken in hierarchical classloaders
4) JUL:
On 20.08.14 15:37, Gary Gregory wrote:
On Wed, Aug 20, 2014 at 9:28 AM, sebb seb...@gmail.com wrote:
On 20 August 2014 14:04, Gary Gregory garydgreg...@gmail.com wrote:
Moving discussion about logging from [JCS-122] to this dev ML.
Why not use Log4j 2, uses can redirect logging to other
On 14.10.14 23:04, Gary Gregory wrote:
It looks like the Maven coords have changed which means the package name
must change, probably to ...jcs2, which means the artifact ID could
probably stand to be post-fixed with a 2 as well.
Did the Maven coords change because version 2 breaks binary
On 15.10.14 00:58, Romain Manni-Bucau wrote:
about api: public api shouldn't be broken (well the one which is
broken shouldn't be used in code but only in config/properties files).
The public API has changed substantially. We use CacheAccess now instead
of JCS. See the docs.
Bye, Thomas.
On 15.10.14 19:55, Gary Gregory wrote:
I propose that we use commons-jcs2 instead of commons-jcs, which what we've
done with other components like commons-math3, commons-lang4, and
commons-collection4.
-1
JCS has not been released from Commons yet. The latest release was from
Jakarta. We
On 15.10.14 20:21, Gary Gregory wrote:
On Wed, Oct 15, 2014 at 1:58 PM, Thomas Vandahl t...@apache.org wrote:
On 15.10.14 19:55, Gary Gregory wrote:
I propose that we use commons-jcs2 instead of commons-jcs, which what
we've
done with other components like commons-math3, commons-lang4
On 15.10.14 19:56, Gary Gregory wrote:
FYI: The sandbox filecache module does not compile.
Yes, this is to be expected. That's why it's called a sandbox. The code
is a fragment that has been removed from the core. It is supposed to be
added back when it has been rewritten.
Bye, Thomas.
On 16.10.14 02:06, sebb wrote:
On 16 October 2014 00:47, Olivier Lamy ol...@apache.org wrote:
Perso I don' get the point to use this version number at the end of
the artifactId
The idea is that if the package name has to be changed again, i.e. to
org.apache.commons.jcs2, then the artifactId
On 16.10.14 00:02, Emmanuel Bourg wrote:
Le 15/10/2014 23:54, Gary Gregory a écrit :
Hm, no, the last item to agree on is the artifact Id. So... Some folks like
me like commons-jcs2 and other(s?) commons-jcs.
My preference goes to commons-jcs without the version appended. That's
not
On 16.10.14 08:35, Romain Manni-Bucau wrote:
ok so it means we are ready to release?
As far As I'm concerned: Go ahead.
Please check JIRAs and docs.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
On 16.10.14 11:19, Romain Manni-Bucau wrote:
If everybody is ok with a 2.0-alpha-1 can someone create this version
on jira please?
Done.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 16.10.14 12:17, Romain Manni-Bucau wrote:
seems I can't do anything on jira,
here few action to do:
1) resolved as won't fix JCS-132 (we have to use java 7 for this tck module)
2) move JCS-130, JCS-119, JCS-116, JCS-16 to alpha2
Done.
Bye, Thomas.
On 16.10.14 12:17, Romain Manni-Bucau wrote:
seems I can't do anything on jira,
I have added you as committer to the project.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands,
On 22.10.14 21:07, Romain Manni-Bucau wrote:
hi
since recently i get:
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single
(source-release-assembly) on project commons-jcs: Error reading
assemblies: Error locating assembly descriptor:
On 23.10.14 20:54, Romain Manni-Bucau wrote:
right, I expected a whole project assembly, don't we do it?
I believe that the different modules will be released independently.
So we need separate assemblies.
Bye, Thomas.
-
To
On 26.10.14 17:18, Romain Manni-Bucau wrote:
Why? I expect them to stay aligned for at least the first year.
I don't expect this. That's just what experience tells me. However, I
have been wrong before.
Bye, Thomas.
-
To
On 27.10.14 12:42, Romain Manni-Bucau wrote:
Any issue if we keep it like it for the first release at least then
we'll change when the lifecycle will be different Thomas?
Do as you please. Let's see how it goes. I'll do my best to help if I can.
Bye, Thomas.
On 30.10.14 16:06, Romain Manni-Bucau wrote:
Hello,
I'd like to release Apache JCS 2.0-alpha-1.
Here is the staging repo:
https://repository.apache.org/content/repositories/orgapachecommons-1053/
My key can be found here:
http://svn.apache.org/repos/asf/commons/proper/jcs/trunk/KEYS
On 12.11.14 10:23, Romain Manni-Bucau wrote:
Hi
I'm trying to align on commons standards this time.
- here is the maven repo:
https://repository.apache.org/content/repositories/orgapachecommons-1061/
Builds and tests run fine.
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
On 28.01.15 20:39, Benedikt Ritter wrote:
Hello Romain,
I've looked at the RC.
- Signs and hashes are good
- builds find with maven 3.2.5 and Java 6 and 7, although the build of the
core takes forever... The build fails with Java 8 (I've run mvn clean
verify). It looks like it's trying
1 - 100 of 274 matches
Mail list logo
