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] release?
Date Wed, 15 Oct 2014 19:41:46 GMT
@thomas: right forgot about CacheAccess, sorry

Since that will be the first release from commons (and the first
commons-jcs* artifacts) org.apache.commons:commons-jcs* is fine IMHO
and it will avoid this pain (and broken pattern) which is double
versioning. This convention can make sense at package level (for
classloader even if even here we could discuss) but clearly doesn't
make any sense at maven level (it is even the opposite cause it makes
research of last version less obvious).

So basically the proposal is to keep it like it accepting jcs has an
history before commons.

wdyt?



Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau


2014-10-15 20:51 GMT+02:00 Thomas Vandahl <tv@apache.org>:
> 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.
>
>
>
> ---------------------------------------------------------------------
> 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


Mime
View raw message