Shall we use this for commons-parent?
Bye, Thomas.
Forwarded Message
Subject: Re: New release distribution checksum policy
Date: Thu, 23 Aug 2018 08:02:45 +0200
From: Hervé BOUTEMY
Reply-To: memb...@apache.org
To: memb...@apache.org
FYI, Apache parent POM 21 has been released
On 17.08.18 18:07, Gary Gregory wrote:
> These are the Maven artifacts and their hashes in Nexus:
>
> #Release SHA-256s
> #Fri Aug 17 09:52:45 MDT 2018
> commons-pool2-2.6.1-bin-zip.asc=c557973fdb9b917eb9bd3aea01db5ec1fd9ba81dc44de3ebbfcf0d30d3034457
My understanding of the new release policy is
On 18.02.18 14:20, Rob Tompkins wrote:
> Not quite because our release process isn’t precisely the same as what maven
> does. Hence, our release plugin strives to be a shim for our site and
> distribution files. But yes, I agree that “mvn deploy” should essentially do
> everything you need.
Do
On 07.02.18 00:28, Gilles wrote:
> Having no idea on how to achieve it, I'd wish that creating
> the "full dist" only requires a custom "goal" like (?)
> $ mvn package:dist
> with no ad-hoc directory/module: all modules specified in the
> top POM would have their artefacts (recursively) bundled in
On 15.12.17 14:05, Romain Manni-Bucau wrote:
> Here what I tested:
>
> 1. svn co
> 2. mvn clean install
> 3. mvn source:jar
>
> => the same trash is here
>
> 4. mvn clean source:jar
>
> => same happens
>
> so I guess something more fishy happens :(
What is wrong with
mvn -Preleas
On 12.12.17 09:14, Romain Manni-Bucau wrote:
> This is the part I really don't understand since it will never work.
Yes, I know. And I agree. But it's the process in commons as of now.
Let's get this out of the door and save the discussion for later.
Please?
Bye, Thomas
On 11.12.17 22:43, Romain Manni-Bucau wrote:
> I can drop the rc2, no problem but can you confirm rc3 will be this exact
> vote with revisions as only change?
yes, and the RC-tag is probably required.
Bye, Thomas.
-
To unsubscri
Hi Romain,
On 20.11.17 09:15, Romain Manni-Bucau wrote:
> do we have a real blocker on the release? Being said having the RC or
> not now is pointless since the tag is there, are we waiting for
> anything particular? Happy to drop the RC if it brings more confusion
> than it helps.
Would you plea
On 16.11.17 21:54, Tim Cronin wrote:
> we have a few webapps running on the same server that use JCS.
>
> when moving the 2.x we started getting the following error on tomcat startup
>
>
>
> javax.management.InstanceAlreadyExistsException:
It looks like you load multiple instances of Composite
On 06.11.17 21:11, Romain Manni-Bucau wrote:
> created
> http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/
> (rev 1814438)
Thanks, Romain. However, the POM file in this RC tag contains now
--8<--
scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/tags/co
On 06.11.17 09:01, Romain Manni-Bucau wrote:
> 2017-11-06 8:59 GMT+01:00 Jochen Wiedmann :
>> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau
>> wrote:
>>
>>> due to the RCx procedure we cant use the maven release plugin, any
>>> plan to make it working with commons release procedure or do we j
On 06.11.17 04:48, Gary Gregory wrote:
> The document http://commons.apache.org/releases/prepare.html clearly shows
> an example of an RC tag being labeled with the "RC1" postfix.
Not in the maven-release-plugin chapter. And with reason. The problem of
the later copy would be, that the tagged pom.
Hi Gary,
On 25.10.17 05:24, Gary Gregory wrote:
> Our process documented here http://commons.apache.org/releases/prepare.html
> makes it pretty clear that the RC tag should be labeled as such and that a
> tag like "commons-jcs-2.2.1" should only be created after a VOTE passes.
as this release is
On 14.10.17 01:22, Gary Gregory wrote:
> Well, crud, when I look at the list of JIRA projects I can administer, I do
> not see Commons JCS.
>
> Anyone else?
I can and I fixed it.
Bye, Thomas
-
To unsubscribe, e-mail: dev-unsubs
On 28.09.17 19:23, Romain Manni-Bucau wrote:
> Do I need to cancel this vote? Cant relaunch a vote before ~2 weeks if so
> (will be travelling) but happy to catch up after if you think it is the way
> to go.
I'm afraid so. You published 2.2.2-SNAPSHOT to the release area. You
probably need to roll
On 27.09.17 21:40, Romain Manni-Bucau wrote:
> Didn't run the site one yet - was planned post vote - but did the others
> without the profile since it is configured to be added automatically. Is it
> an issue?
It might be. I copied these from my actual shell history, so I know them
to work.
Bye,
On 25.09.17 17:47, Gary Gregory wrote:
> -1
>
> The file
> https://dist.apache.org/repos/dist/dev/commons/jcs/source/commons-jcs-dist-2.2.1-src.zip
> does not contain any of the modules folders.
>
Hi Romain,
did you do
mvn -Duser.name=rmannibucau -Prelease release:prepare
mvn -Duser.name=rm
On 25.09.17 17:19, Gary Gregory wrote:
> The recent trunk commits to [JCS] for 3.0-SNAPSHOT break binary
> compatibility.
>
> Will there be upcoming package name and Maven coordinate changes?
If that is unavoidable, yes. Let's first push 2.2.1 out.
Bye, Thomas
-
On 20.09.17 22:12, Romain Manni-Bucau wrote:
> back on the release topic (sorry for the delay, have been very busy
> lately): does it sound ok for everyone if I backport the jcache changes in
> 2.2 and release it from here (Some pointer on which branch I can reuse or
> if I should create one from
: Thomas Vandahl
To: Romain Manni-Bucau
On 08.09.17 16:41, Romain Manni-Bucau wrote:
> So it would be a 3.0. Do we expect anything else in a potential 3.0?
I made an attempt to integrate the ConcurrentLinkedHashMap by Ben Manes.
See
https://svn.apache.org/repos/asf/commons/proper/jcs/branches/jcs-c
On 09.09.17 15:43, Romain Manni-Bucau wrote:
> What does references "perf test" here? something from the project? I'm
> interested in the fact CompositeCache doesn't have this synchronized
> block anymore which could scale way better with multiple threads if we
> ensure nested calls can scale as we
On 06.09.17 20:54, Romain Manni-Bucau wrote:
> Ok so sounds a 2.3 from master for next release is ok, or are you bound
> somehow to 2.2 ans prefer some backports?
It should not have sounded like that. All the mentioned changes in trunk
*break binary compatibility* and require a major version updat
Hi Romain,
On 05.09.17 20:32, Romain Manni-Bucau wrote:
> @Thomas: can you say a word on the diff between 2.3 and 2.2 if you have it
> still in memory please?
1. The CacheEventQueue has been derived from PooledCacheEventQueue and
most of its methods removed. The previous implementation smelled.
2
On 03.09.17 20:17, Romain Manni-Bucau wrote:
> Thanks Thomas
>
> Is it the same for the code? Just realised pom were not up to date too.
I released from a branch as some braking changes are already checked in
into trunk. I'd kindly ask you to do the same if you are planning for a
bugfix release.
On 03.09.17 20:11, Romain Manni-Bucau wrote:
> On the perf thing: isXXXEnabled can be costly by itself - see my last
> commit.
Could you please provide some numbers to this claim?
Bye, Thomas.
-
To unsubscribe, e-mail: dev-uns
On 03.09.17 20:05, Gary Gregory wrote:
> Would that not duplicate what logging facades (like log4j-api) already
> provide?
You mean like commons-logging? Yeah, I understand that's not what is
required here. Otherwise it could stay as it is. I believe that
especially a caching layer should be as li
On 01.09.17 17:23, Romain Manni-Bucau wrote:
> 2.2 is out seems some days and jira seems to not have it yet, is it
> intended or it was just forgotten?
The latter. Fixed it now.
Bye, Thomas
-
To unsubscribe, e-mail: dev-unsubsc
On 03.09.17 09:02, Romain Manni-Bucau wrote:
> Once again the issue is the risk to break users and to ensure the api is
> consistent accross all libs (jcs, openjpa, tomee, cxf, activemq, commons,
> ...). It is clearly not "is it good or bad" and tomee switch from log4j1 to
> jul reduced the number
On 02.09.17 20:04, Romain Manni-Bucau wrote:
> However reworking the logging in JCS can be interesting, current log usage
> is slow and sometimes in synchronized blocks so I guess we can be better.
Could you please mark places where this is the case? I spent quite some
effort to extract logging fr
On 02.09.17 10:41, Romain Manni-Bucau wrote:
> Ok, got the confirmation for the reflection fix.
>
> Now we lock in CompositeCache.get. Wonder if we could have a lock free
> MemoryCache implementation, at least for read side of things. Sounds doable
> using ConcurrentMap like algorithms but can req
The Apache Commons Team is pleased to announce the availability of:
Apache Commons JCS 2.2
Apache Commons JCS is a distributed, versatile caching system.
The release notes can be reviewed at:
http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt
Distribution packages can be downloaded from:
On 02.08.17 15:32, Thomas Vandahl wrote:
> I would like to release the [jcs] component to resolve some overdue bugs
>
> Apache Commons JCS 2.2 RC1 is available for review at:
> https://dist.apache.org/repos/dist/dev/commons/jcs/ (r20728).
Time to wrap up. The following votes w
For some reason, your mail was sent to me personally only.
Bye, Thomas.
Forwarded Message
Subject:Re: [VOTE] Release Apache Commons JCS 2.2 based on RC1
Date: Mon, 14 Aug 2017 13:51:55 -0600
From: Gary Gregory
To: Thomas Vandahl
+1
Tests finally pass (must
On 14.08.17 20:21, Rob Tompkins wrote:
>
>
>> On Aug 14, 2017, at 2:15 PM, Thomas Vandahl wrote:
>>
>> We are one PMC vote short. Please consider voting.
>
> I can get to validating it tonight 8p (UTC-4). That work?
Of
We are one PMC vote short. Please consider voting.
On 02.08.17 15:32, Thomas Vandahl wrote:
> I would like to release the [jcs] component to resolve some overdue bugs
>
> Apache Commons JCS 2.2 RC1 is available for review at:
> https://dist.apache.org/repos/dist/dev/commons/
On 02.08.17 15:32, Thomas Vandahl wrote:
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
Bye, Thomas
-
To unsubscri
I would like to release the [jcs] component to resolve some overdue bugs
Apache Commons JCS 2.2 RC1 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/jcs/ (r20728).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1256 .
The
The Apache Commons Team is pleased to announce the availability of:
Apache Commons JCS 2.1
Apache Commons JCS is a distributed, versatile caching system.
The release notes can be reviewed at:
http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt
Distribution packages can be downloaded from:
On 05.02.17 18:24, Thomas Vandahl wrote:
> I would like to release the [jcs] component to resolve some bugs
>
> Apache Commons JCS 2.1 RC1 is available for review at:
> https://dist.apache.org/repos/dist/dev/commons/jcs/ (r18146).
Time to wrap up. The following votes were cast
Hi Oliver,
On 07.02.17 21:42, Oliver Heger wrote:
> I noticed that OSGi manifests of jars use the same symbolic bundle name,
> e.g. for commons-jcs-core-2.1.jar and
> commons-jcs-jcache-openjpa-2.1.jar. This is likely to cause problems in
> an OSGi container.
Thanks for the hint. I didn't know th
Hi Rob,
On 30.01.17 15:14, Rob Tompkins wrote:
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.0-beta-1 (from RC4).
[...]
Artifacts look good, signatures are ok, site looks good.
My guess would be if you use Eclipse you can iron out most of the
checkstyle errors at once wit
On 05.02.17 18:24, Thomas Vandahl wrote:
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
Bye, Thomas
-
To unsubscribe,
I would like to release the [jcs] component to resolve some bugs
Apache Commons JCS 2.1 RC1 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/jcs/ (r18146).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1235 .
The Subvers
On 18.01.17 17:14, Tim Cronin wrote:
> started getting these errors, have to restart the tomcat server to resolve:
>
> ERROR org.apache.commons.jcs.auxiliary.disk.indexed.IndexedDiskCache –
> Region [DroppedEmailSent] No longer alive so returning false for key =
> hqYRRK
What version did you use
On 03.01.17 20:39, Rob Tompkins wrote:
> Hello all,
>
> I propose that we move [text] to Commons Proper.
>
> --
> [X] +1 Move [text] to Commons Proper
> [ ] +0 I am fine with this move
> [ ] -0 I am not too keen, because ...
> [ ] -1
The Apache Commons Team is pleased to announce the availability of:
Apache Commons JCS 2.0
Apache Commons JCS is a distributed, versatile caching system.
The release notes can be reviewed at:
http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt
Distribution packages can be downloaded from:
On 25.12.16 22:24, Thomas Vandahl wrote:
> I would like to release the [jcs] component.
>
> Apache Commons JCS 2.0 RC1 is available for review at:
> https://dist.apache.org/repos/dist/dev/commons/jcs/ (r17574).
The following votes were cast (in order of appearance):
Thomas Vandah
Hi Jörg,
On 29.12.16 16:57, Jörg Schaible wrote:
> +1
thanks for voting.
> builds from source tarball with my compiler zoo except Java 9 (jar-plugin
> fails, unrelated to jcs).
>
> The layout of the binary tarball is somewhat different compared to other
> commons releases:
> - bin archive ext
On 25.12.16 22:24, Thomas Vandahl wrote:
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
Bye, Thomas
-
To unsubscribe,
I would like to release the [jcs] component.
Apache Commons JCS 2.0 RC1 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/jcs/ (r17574).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1232 .
The Subversion tag is:
https:/
On 19.12.16 20:19, Romain Manni-Bucau wrote:
> If code is asf 2 licensed just fixing licens and notice files in the build
> (referencing the project)
It is ASF2 licensed code. I was planning to copy the file to the JCS
source (it's just one class!)
Still valid?
> Btw, do we have jcs figures showi
jira/browse/JCS-119
> Project: Commons JCS
> Issue Type: Improvement
>Reporter: Romain Manni-Bucau
> Assignee: Thomas Vandahl
> Fix For: jcs-2.1
>
>
> A cache is typically used in a concurrent environment. Since Java 6 using a
> Reent
On 15.12.16 22:17, Romain Manni-Bucau wrote:
> Hi guys,
>
> just wanted to get in touch with you to know if a release is planned and if
> not how we can plan it.
>
> For the background: we got some tomee users requesting it (
> http://tomee-openejb.979440.n4.nabble.com/JCS-beta-2-bug-td4680745.ht
On 16.11.16 14:56, Tim Cronin wrote:
> when will it be accessible via maven/ivy repo?
It already is:
http://repo1.maven.org/maven2/org/apache/commons/commons-jcs-core/2.0-beta-2/
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsub
The Apache Commons Team is pleased to announce the availability of:
Apache Commons JCS 2.0-beta-2
Apache Commons JCS is a distributed, versatile caching system.
The release notes can be reviewed at:
http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt
Distribution packages can be downloaded
On 01.11.16 09:24, Thomas Vandahl wrote:
> I would like to beta-release the [jcs] component.
The following votes were cast (in order of appearance):
Romain Manni-Bucau: +1 (non binding)
Johannes Weberhofer: +1 (non-binding)
Gary Gregory: +1
Thomas Vandahl: +1
Bruno P. Kinoshita: +1
The vote
On 08.11.16 20:07, Gary Gregory wrote:
>> Now how shall we proceed?
>>
>> I'd be willing to change the groupId/package name to
>> org.apache.commons.jcs2 or whatever if you insist that
>> org.apache.commons.jcs has been wasted on 2.0-beta-1.
>>
>
> I think we are good as is, keep org.apache.common
On 08.11.16 10:26, sebb wrote:
> Alpha should be used for unstable API
> Beta would be for unstable Behaviour (i.e. implementation)
That is exactly what happened. JCS actually has only 3 public API
classes, JCS, CacheAccess and CacheGroupAccess. These have been
redesigned for the step from 1.3 to
Hi Oliver,
On 05.11.16 21:18, Oliver Heger wrote:
> It seems that there are many breaking changes between this release and
> beta1; for instance, the clirr report for the core component lists
> numerous errors. Is it not against Commons policy to publish
> incompatible artifacts with the same mave
On 05.11.16 20:24, Gary Gregory wrote:
> Time to tally?
I would like to. However, AFAIK, we are one PMC vote short.
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev
On 01.11.16 09:24, Thomas Vandahl wrote:
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
My vote.
Bye, Thomas
-
To un
I would like to beta-release the [jcs] component.
The issues found with RC1 have been addressed.
Apache Commons JCS 2.0-beta-2 RC2 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16762).
Maven artifacts are at:
https://repository.apache.org/content/repositori
Hi Benedikt,
On 26.10.16 21:35, Benedikt Ritter wrote:
> I have discovered one problem. The release tag and the source archive have
> differing contents:
>
>> diff -wqr commons-jcs-dist-2.0-beta-2 TAG
> Only in TAG: .gitignore
> Only in TAG: .svn
> Only in commons-jcs-dist-2.0-beta-2/: LICENSE
>
On 21.10.16 19:42, Thomas Vandahl wrote:
> I would like to beta-release the [jcs] component.
Ok, I'll check out the problems with the Tomcat library and cut an RC2
Thanks to all the testers.
Bye, Thomas
-
To unsubs
Am 25.10.2016 um 21:38 schrieb Oliver Heger :
> when building on Windows 10 with Java 1.6 I get the error below. The
> build with Java 1.8 is successful.
>
> On the distributions, I found some problems:
> - Both the source and the binary distribution deflate in the same
> folder. Typically, differ
> Am 26.10.2016 um 00:19 schrieb sebb :
> Reminder: releases cannot be vetoed [1]
> They pass if there are at least 3 +1 and more +1 than -1.
>
You're technically right, however -1 votes tend to keep others from voting.
We could need your vote, too.
> However I have just noticed that the dist
Hi Benedikt,
On 24.10.16 08:34, Benedikt Ritter wrote:
> Sorry, if that has been decided, I must have missed it. I'll take another
> look tonight.
Could you please reconsider your vote? I fixed the check sums so give it
one more chance!
Bye, Thomas
---
Hi Romain,
On 24.10.16 12:44, Romain Manni-Bucau wrote:
> +1, thanks Thomas
>
> Side note: the tck module has been deactivated cause of packaging=pom but
> ran it manually and all tests passed so not an issue for the release since
> we don't care of this artifact distribution, just here as a runn
On 21.10.16 19:42, Thomas Vandahl wrote:
> [X] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
My own vote.
Bye, Thomas
-
To un
Hi Benedikt,
On 23.10.16 10:51, Benedikt Ritter wrote:
> Hello Thomas,
>
> The build works with Java 8 and Maven 3.3.9.
>
> But the md5 and SHA1 files are missing in the dist area.
>
> -1
>
I thought the signatures were sufficient. I added the check sums with
r16631. Please check again.
Bye,
I would like to beta-release the [jcs] component.
Apache Commons JCS 2.0-beta-2 RC1 is available for review at:
https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16621).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1211 .
The Subversion tag
On 20.10.16 13:55, Gilles wrote:
> Hi.
>
> Can you point me at a component that has a config supporting
> multiple modules?
You may look at commons-jcs, especially at the commons-jcs-dist module
that builds a complete distribution of all modules.
Bye, Thomas.
--
Hi folks,
On 13.10.16 16:25, t...@apache.org wrote:
> Author: tv
> Date: Thu Oct 13 14:25:04 2016
> New Revision: 1764695
>
> URL: http://svn.apache.org/viewvc?rev=1764695&view=rev
> Log:
> Fix SortedPreferentialArray to actually do what was is supposed to do
>
> Modified:
>
> commons/prope
On 19.06.16 10:47, Benedikt Ritter wrote:
> Hi,
>
> we have failing tests on Jenkins for JCS [1]. Does anybody know what caused
> this?
>
> Regards,
> Benedikt
>
> [1]
> https://builds.apache.org/view/Apache%20Commons/job/commons-jcs/159/org.apache.commons$commons-jcs-core/console
>
The differ
On 13.06.16 20:57, James Carman wrote:
> I'd rather not make it (the OSGi metadata) the "source of truth".
I'm not insisting on OSGi meta data but I strongly believe that one
(single) source of truth is required. Suggest something else.
Bye, Thomas.
-
On 13.06.16 20:54, Jochen Wiedmann wrote:
> On Mon, Jun 13, 2016 at 8:49 PM, Thomas Vandahl wrote:
>> On 05.06.16 20:33, James Carman wrote:
>>> Not quite. OSGi is a special case. It's much more restrictive than simple
>>> J2SE, because it can be. In the general
On 05.06.16 20:33, James Carman wrote:
> Not quite. OSGi is a special case. It's much more restrictive than simple
> J2SE, because it can be. In the general case, the public API for OSGi is
> different from the public API for J2SE. Let's not confuse the two.
My intention was to use the OSGi meta d
On 03.06.16 10:38, sebb wrote:
> On 2 June 2016 at 21:42, Benedikt Ritter wrote:
>> - we must not break BC in a release that could collide with an earlier
>> version. In other words, when we break BC, we have to change package and
>> maven coordinates.
>
> +1, with the proviso that we must not br
On 21.03.16 09:45, Benedikt Ritter wrote:
> [X] +1 Accept Chimera as new Apache Commons Component
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this because...
Bye, Thomas
-
To unsubscribe,
On 16.01.16 16:18, Phil Steitz wrote:
> [ ] +1 I am in favor of this action
> [X] +0 I am OK with this
> [ ] -0 OK, but...
> [ ] -1 I oppose this action because...
Bye, Thomas
-
To unsubscribe, e-mail: dev-unsubscr...@commons.a
On 25.11.15 23:20, Thomas Neidhart wrote:
> [X] +1 Release these artifacts
Bye, Thomas.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 28.03.15 19:40, Wiktor Niesiobedzki wrote:
> Hi,
>
> I'm trying to integrate Commons JCS into Java OpenStreetMap editor
> (http://josm.openstreetmap.de). During tests I see, that from time to
> time IndexedDiskCache is thrown away. I've made a simple unit test
> that detects this situation:
> h
On 19.02.15 14:28, Romain Manni-Bucau wrote:
> Hi
>
> Another try, hopefully right this time (I speak about JCS in a JUG
> next thursday so would be awesome to have a release ;))
>
> - here is the maven repo:
> https://repository.apache.org/content/repositories/orgapachecommons-1083/
> - assembli
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 t
On 26.01.15 12:19, Romain Manni-Bucau wrote:
> if that's the case +1 but anyway it doesnt hurt
>
> @Thomas: before dropping it can you confirm it a last time please?
I don't even know if it actually works with the current code. It was
like this when I got here (TM). I'd suggest to remove the aspe
On 25.01.15 17:00, Romain Manni-Bucau wrote:
> It does AFAIK - was not here and just propagated existing legal text - and
> that is why it is referenced in core and not all artifacts.
> Le 25 janv. 2015 16:55, "sebb" a écrit :
The XEROX license relates to the file
/commons-jcs-core/src/aspect/or
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 (ea8b2b07643dbb1b84b6d16e1f08391b666b
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
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 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 u
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 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:
> s
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 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 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 addition
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
F
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
> no
On 16.10.14 02:06, sebb wrote:
> On 16 October 2014 00:47, Olivier Lamy 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 would be
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 componen
101 - 200 of 287 matches
Mail list logo
