Do we want to keep the JCS name or switch to a more generic name like
commons-cache or commons-caching?
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@common
ok so it means we are ready to release?
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2014-10-16 2:06 GMT+02:00 sebb :
> On 16 October 2014 00:47, Olivier Lamy wrote:
>> +1
>> as the groupId has changed org.apache.jcs -
Working on Imaging to get out 1.0 is on my list when I have more time for
commons again. Nice to see some activity here.
2014-10-16 7:08 GMT+02:00 Damjan Jovanovic :
> Thank you :).
>
> There's lots of issues to close first, and I think 0.98 would be more
> appropriate.
>
> The API also needs big
Go for it!
2014-10-15 22:12 GMT+02:00 Oliver Heger :
> Hi,
>
> there are currently a few fixes available for [beanutils] related to
> changes introduced with the 1.9.x releases. In order to stabilize this
> series, I would like to push out a new release - there has already been
> a corresponding
Thank you :).
There's lots of issues to close first, and I think 0.98 would be more
appropriate.
The API also needs big, breaking changes, to handle multi-image file
formats, copy/rewrite metadata losslessly, and other things...
Damjan
On Thu, Oct 16, 2014 at 7:01 AM, Gary Gregory wrote:
> Goo
Good to see you pop up!
What are your thoughts on getting to 1.0?
Gary
-- Forwarded message --
From:
Date: Thu, Oct 16, 2014 at 12:49 AM
Subject: svn commit: r1632210 -
/commons/proper/imaging/trunk/src/main/java/org/apache/commons/imaging/formats/jpeg/decoder/Dct.java
To: comm.
On 16 October 2014 00:47, Olivier Lamy wrote:
> +1
> as the groupId has changed org.apache.jcs -> org.apache.commons.jcs.
No, the groupId is now org.apache.commons
ArtifactId: jcs => commons-jcs
Also the package name has changed:
org.apache.jcs -> org.apache.commons.jcs
> Perso I don' get the
+1
as the groupId has changed org.apache.jcs -> org.apache.commons.jcs.
Perso I don' get the point to use this version number at the end of
the artifactId
On 16 October 2014 09:26, Romain Manni-Bucau wrote:
> Same here (no version)
> Le 16 oct. 2014 00:02, "Emmanuel Bourg" a écrit :
>
>> Le 15/
Same here (no version)
Le 16 oct. 2014 00:02, "Emmanuel Bourg" a écrit :
> 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 th
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 technically required.
Emmanuel Bourg
-
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.
Gary
Original message From: Romain Manni-Bucau
Date:10/15/2014 16:14 (GMT-05:00)
To: Commons Developers List
Subject: Re: [JCS] release?
Meant fin
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38384&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 15 Oct 2014 20:20:08 +
Finished at: Wed 15 Oct 2014 20:22:03 +
Total time: 1m 55s
Build Trigger: Sched
Meant finally current status seems ok right?
Le 15 oct. 2014 22:12, "Gary Gregory" a écrit :
> On Wed, Oct 15, 2014 at 3:41 PM, Romain Manni-Bucau >
> wrote:
>
> > @thomas: right forgot about CacheAccess, sorry
> >
> > Since that will be the first release from commons (and the first
> > commons-
On Wed, Oct 15, 2014 at 3:41 PM, Romain Manni-Bucau
wrote:
> @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
Hi,
there are currently a few fixes available for [beanutils] related to
changes introduced with the 1.9.x releases. In order to stabilize this
series, I would like to push out a new release - there has already been
a corresponding request.
So if anybody wants to add some stuff, this is a good op
@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 packag
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38381&projectId=65
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 15 Oct 2014 19:20:03 +
Finished at: Wed 15 Oct 2014 19:21:57 +
Total time: 1m 53s
Build Trigger: Sched
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 15.10.14 20:21, Gary Gregory wrote:
> On Wed, Oct 15, 2014 at 1:58 PM, Thomas Vandahl 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, and
>>>
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38378&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 15 Oct 2014 18:20:26 +
Finished at: Wed 15 Oct 2014 18:25:32 +
Total time: 5m 5s
Build Trigger: Sched
On Wed, Oct 15, 2014 at 1:58 PM, Thomas Vandahl 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, and
> > commons-collection4.
>
> -1
>
> JCS has not b
If the library is going to be called version 2 then personally it should be
commons-jcs2. Otherwise the original version from Jakarta should be dropped
altogether, and the doc changed so this is treated as version 1.
Whilst the later makes sense from the perspective that this is the first Apache
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 do
FYI: The sandbox filecache module does not compile.
Gary
On Tue, Oct 14, 2014 at 4:23 PM, Romain Manni-Bucau
wrote:
> Hello guys,
>
> seems we are good regarding dependencies now
>
> do we try a release this week? 2.0-alpha-1? Anything blocking?
>
>
> Romain Manni-Bucau
> @rmannibucau
> http://
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.
Gary
On Wed, Oct 15, 2014 at 1:45 PM, Thomas Vandahl wrote:
> On 15.10.14 00:58, Romain Manni-Bucau wrote:
> > about api: public api
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 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 binar
Online report :
https://continuum-ci.apache.org/continuum/buildResult.action?buildId=38375&projectId=286
Build statistics:
State: Failed
Previous State: Failed
Started at: Wed 15 Oct 2014 17:20:27 +
Finished at: Wed 15 Oct 2014 17:25:25 +
Total time: 4m 57s
Build Trigger: Sche
On Wed, Oct 15, 2014 at 11:35 AM, Thomas Neidhart wrote:
> On Wed, Oct 15, 2014 at 5:14 PM, Gary Gregory
> wrote:
>
> > On Wed, Oct 15, 2014 at 11:05 AM, Thomas Neidhart <
> > thomas.neidh...@gmail.com
> > > wrote:
> >
> > > Hi Gary,
> > >
> > > thanks for the changes, but see my comments below:
On Wed, Oct 15, 2014 at 5:14 PM, Gary Gregory
wrote:
> On Wed, Oct 15, 2014 at 11:05 AM, Thomas Neidhart <
> thomas.neidh...@gmail.com
> > wrote:
>
> > Hi Gary,
> >
> > thanks for the changes, but see my comments below:
> >
> > On Wed, Oct 15, 2014 at 4:44 PM, wrote:
> >
> > > Author: ggregory
>
On Wed, Oct 15, 2014 at 11:05 AM, Thomas Neidhart wrote:
> Hi Gary,
>
> thanks for the changes, but see my comments below:
>
> On Wed, Oct 15, 2014 at 4:44 PM, wrote:
>
> > Author: ggregory
> > Date: Wed Oct 15 14:44:54 2014
> > New Revision: 1632060
> >
> > URL: http://svn.apache.org/r1632060
>
Hi Gary,
thanks for the changes, but see my comments below:
On Wed, Oct 15, 2014 at 4:44 PM, wrote:
> Author: ggregory
> Date: Wed Oct 15 14:44:54 2014
> New Revision: 1632060
>
> URL: http://svn.apache.org/r1632060
> Log:
> [EMAIL-143] Update Apache Commons Logging from 1.1.3 to 1.2.
>
I fail
I'm done with my updates now... we can call it 1.3.4; or 1.4 to note the
new APIs in the (util) MIME parser and updated deps.
Any RMs out there?
Gary
On Wed, Oct 15, 2014 at 4:29 AM, Thomas Neidhart
wrote:
> Hi,
>
> there have only been 2 small changes since the last release but I would
> like
Hi,
there have only been 2 small changes since the last release but I would
like to see them in an official release.
Maybe somebody interested in email wants to jump in and volunteer as RM?
I can offer help and guidance in making a release.
Thomas
Le 14/10/2014 20:14, Ole Ersoy a écrit :
>
>
> On 10/14/2014 12:32 PM, Luc Maisonobe wrote:
>> Le 14/10/2014 17:46, Ole Ersoy a écrit :
>>> Hi,
>>>
>>> I have 1 open pull request for MathIllegalStateException (Simple update
>>> to description - Gilles approved) that has been sitting for a while,
35 matches
Mail list logo
