blocking for the
release?
Oliver
>
> Gary
>
> *
>
> Files with unapproved licenses:
>
> src/test/resources/test.json
> src/test/resources/test.yaml
>
> On Sat, Jul 28, 2018 at 2:38 PM Oliver Heger
&g
Hi,
for the 2.3 release of [configuration] I am trying out the cool release
plugin.
Everything works fine, but I get a build failure when it adds the site
to SVN (see below). Do I have to prepare something in the dist area
before this can be done?
And another question: How can I generate such a
> On Sat, Jul 28, 2018 at 9:21 AM Oliver Heger
> wrote:
>
>> Hi,
>>
>> for the 2.3 release of [configuration] I am trying out the cool release
>> plugin.
>>
>> Everything works fine, but I get a build failure when it adds the site
>> to SVN (
[lang]. I would not want to depend on [collections] just
to use one or two copy methods. And the utility class could support
non-collection types (mainly arrays) as well.
Oliver
>
> Gary
>
> On Wed, Jul 25, 2018, 14:00 Oliver Heger
> wrote:
>
>> +1, Thank you.
>>
>
Am 31.07.2018 um 04:21 schrieb Gary Gregory:
> On Mon, Jul 30, 2018 at 1:29 PM Oliver Heger
> wrote:
>
>> Hi Gary,
>>
>> Am 30.07.2018 um 16:25 schrieb Gary Gregory:
>>> -1
>>>
>>> :-( RAT check fails:
>>> - Unzip src zip
We have fixed quite a few bugs and added some significant enhancements
since Apache Commons Configuration 2.2 was released, so I would like to
release Apache Commons Configuration 2.3.
Apache Commons Configuration 2.3 RC2 is available for review here:
This vote is cancelled because of problems with the RAT report.
Thanks for all reviews.
Oliver
Am 28.07.2018 um 22:38 schrieb Oliver Heger:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Configuration 2.2 was released, so I woul
Am 26.07.2018 um 22:30 schrieb Gary Gregory:
> Hi Oliver,
>
> Once you've released [configuration], I expect you will bring the component
> back to Java 8, right?
Yes, this is the plan.
Oliver
>
> Gary
>
> On Thu, Jul 26, 2018 at 1:39 PM wrote:
>
>> Author: oheger
>> Date: Thu Jul 26
+1, Thank you.
I had planned to create a patch for this issue, but did not find the
time so far.
BTW, I have quite often the need to create defensive copies of arrays or
collections in some variants (e.g. null safe, with wrapping to an
unmodifiable collection, etc.). Could this be an addition to
Hi,
the current codebase for [configuration] has been updated to require
Java 8. However, no Java 8 feature is used so far.
I would therefore like to go back to Java 7 and get a release out.
Afterwards we can switch to Java 8.
Thoughts?
Oliver
The vote to release Apache Commons Configuration 2.3 based on RC2 passed
with the following votes (all are binding):
Gary Gregory: +1
Rob Tompkins: +1
Oliver Heger: +1
Thanks to all reviewers. I will start with the tasks to publish the
release probably tomorrow.
Oliver
Am 04.08.2018 um
+1
Oliver
Am 04.08.2018 um 21:19 schrieb Oliver Heger:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Configuration 2.2 was released, so I would like to
> release Apache Commons Configuration 2.3.
>
> Apache Commons Config
Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.
One minor nit: I was a bit confused by the sentence in the release notes
"Lang 3.0 and onwards now targets Java 5.0...". This sounds as if the
minimum Java requirement was 5.0. A bit later it is correctly stated
, patches, or suggestions for
improvement, see the Apache Commons Configuration website:
http://commons.apache.org/proper/commons-configuration/
Oliver Heger, on behalf of the Apache Commons community
-
To unsubscribe, e-mail
Build works fine on Windows 10 with Java 8. Artifacts and site look good.
+1
I noticed the following things:
* In the first sentence of RELEASE-NOTES.txt the version has a -SNAPSHOT.
* In README.txt it is stated that "DBCP version 2 requires JDK 1.7.".
This is not true for version 2.5.
* I had
backward compatibility
>> changed, we must deprecate the existing classes
>> [ ] release a new version of lang with this new interface and the
>> updated circuit breakers[ ] and either delete the deprecated classes
>> or leave it until for some more releases
>> I won
Am 16.07.2018 um 02:17 schrieb Gary Gregory:
> Thank you for your review; more below.
> '
> On Sun, Jul 15, 2018 at 12:20 PM Oliver Heger
> wrote:
>
>> Build works fine on Windows 10 with Java 8. Artifacts and site look good.
>>
>> +1
>>
>> I no
> Subject: Re: [LANG] Java 9 problems because of dependencies to java.desktop
> (Was: Re: [LANG] Thoughts about Lang 4.0)
>
>
>
> Good spot. I think that means [lang] would have to have its own copy
> of the JDK interfaces. or just deprecate the functionality without
> replacement.
Build works fine with Java 1.8 on Windows 10. Artifacts and site look good.
+1
Only one minor nit: On the site under Project Reports there is an empty
japicmp report.
Oliver
Am 08.07.2018 um 16:04 schrieb Gary Gregory:
> We have fixed quite a few bugs and added some significant enhancements
>
Am 10.07.2018 um 19:13 schrieb Gary Gregory:
> Yeah, I dislike *Util names as well, it's not only a co-out but an
> encouragement to make such classes dumping-grounds/kitchen-sinks.
>
> I was thinking [lang] or maybe [collections] but it's not a collection
> really.
As the implementation is
Build works fine with Java 8 on Windows 10. Artifacts and site look good.
+1
One minor point I noticed is that the release notes say that "Version 2
requires JDK level 1.6 or above", but the minimum JDK for 2.6 is 1.7.
There are also a few checkstyle errors that could be fixed with not too
much
Hi,
Am 11.04.2018 um 10:42 schrieb Claude Warren:
> Greetings,
>
> Is the snapshot packaging for commons configuration2 available for download
> / maven?
AFAIK, there are no nightly builds that are deployed automatically; but
it is possible to deploy snapshot builds manually to the Apache Maven
Hi Claude,
(Note that I have added the component name to the subject because this
is a shared list.)
Am 11.04.2018 um 10:49 schrieb Claude Warren:
> Greetings,
>
> I have been using commons configuration2 for sometime with apache jena.
> The RDF format has many of the same properties of the XML
Am 20.04.2018 um 19:08 schrieb Matt Sicker:
> Wow, us "legacy" projects really need to keep up to date with these
> requirements. GitBox, no CMS (I think we're using svnpubsub everywhere, but
> this could also use gitpubsub with an asf-site branch), etc.
Would it reduce overhead if we converted
Hi,
Am 23.04.2018 um 22:21 schrieb Stefan Bodewig:
> Hi all
>
> I'm trying to resolve COMPRESS-443 which talks about having a regression
> test that fails if we break the OSGi bundle again (has already happened
> three times duing the life of Compress so far). But unfortunately I'm
> getting
+1
Oliver
Am 22.04.2018 um 19:07 schrieb Matt Sicker:
> This is a vote to migrate existing Git repositories from the old git-wip-us
> infrastructure to the new gitbox infrastructure. New Apache projects are
> not allowed to use git-wip-us and are instead directed to use gitbox. As
> such, it
mpkins <chtom...@gmail.com> wrote:
>>
>>>
>>>
>>>> On Apr 21, 2018, at 10:20 AM, Oliver Heger <
>> oliver.he...@oliver-heger.de>
>>> wrote:
>>>>
>>>>
>>>>
>>>> Am 20.04.2018 um 19:08 schrie
Wrong mailing list, guys?
Http Client is not part of Apache Commons.
Oliver
Am 30.03.2018 um 18:44 schrieb Mark Thomas:
> On 30/03/18 12:22, ajs6f wrote:
>> For at least some cases, this wouldn't be good for security.
>
> That is debatable.
>
> Providing exact version information is highly
Am 29.03.2018 um 15:54 schrieb Gary Gregory:
> Done.
>
> Gary
>
> On Wed, Mar 28, 2018 at 2:21 PM, Jochen Wiedmann
> wrote:
>
>> +1
>>
>>
>> On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory
>> wrote:
>>> Hi All:
>>>
>>> I say it is time to
Build works fine with Java 1.7 and 1.8. Artifacts and site look good.
So +1.
Minor nit: The site has a japicmp report which is just an empty page.
Oliver
Am 16.03.2018 um 16:35 schrieb Rob Tompkins:
> Hello all,
>
> This is a [VOTE] for releasing Apache Commons Text 1.3 (from RC1).
>
> Tag
Am 02.03.2018 um 15:45 schrieb Gary Gregory:
> On Fri, Mar 2, 2018 at 7:31 AM, Otto Fowler wrote:
>
>> I don’t understand the options that we are discussing here. Can we
>> clarify?
>>
>> * create a new component from sirota, bringing it into commons ( resurrect
>>
Am 26.04.2018 um 17:37 schrieb Matt Sicker:
> If it helps in design, the most promising approach I found was to integrate
> with the java.nio.file API. However, that turns into a sort of hybrid
> library between VFS and Compress. However, they are rather strongly related
> (if the two libraries
Hi Rob,
build works fine with Java 8 on Windows 10. Artifacts and site look good.
+1
Some remarks:
- When running mvn site it did an SVN checkout to a folder named
site-content. What is the background of this?
- The japicmp report on the site you referenced looks pretty strange -
given the fact
Any chance this guy can be blocked? There has been similar spam like
this for other projects.
Oliver
Am 25.09.2018 um 15:35 schrieb Benedikt Ritter (JIRA):
>
> [
> https://issues.apache.org/jira/browse/COMMONSSITE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
Am 27.09.2018 um 19:27 schrieb Gary Gregory:
> Hi All:
>
> I'd like to update [configuration] from java 7 to Java 8.
Just go on. I think it was consensus that after the latest release the
Java version should be upgraded.
Oliver
>
> Gary
>
Am 27.09.2018 um 20:43 schrieb ggreg...@apache.org:
> Author: ggregory
> Date: Thu Sep 27 18:43:37 2018
> New Revision: 1842139
>
> URL: http://svn.apache.org/viewvc?rev=1842139=rev
> Log:
> [CONFIGURATION-720] Replace use of deprecated Commons Lang string
> substitution code for Commons
+1
Oliver
Am 08.12.2018 um 21:09 schrieb Rob Tompkins:
> Infra stated that we need documented consensus on this. So, let’s have at it.
>
> I propose that we move the following repos over to gitbox:
>
> commons-build-plugin.git 11 weeks ago
> commons-cli.git30 weeks ago
>
+1
Oliver
Am 08.01.19 um 17:25 schrieb Rob Tompkins:
> Vote statement: "I propose we move all ‘proper' svn repos to gitbox."
>
> I went though, and I think these are the ones that need to be migrated:
>
> bcel/
> beanutils/
> bsf/
> chain/
> codec/
> commons-parent/
> commons-skin (???)
>
+1
Oliver
Am 19.02.19 um 22:35 schrieb Marcelo Vanzin:
> I'm opening a vote based on recent discussions about the extra noise
> generated by github updates going to dev@. So please vote:
>
> - +1 to redirect github updates of all commons repos to the issues@ list
> - -1 to keep things as is
>
Am 20.05.19 um 16:19 schrieb sebb:
> On Mon, 20 May 2019 at 14:58, Gary Gregory wrote:
>>
>> On Mon, May 20, 2019 at 9:16 AM Gilles Sadowski
>> wrote:
>>
>>> Le lun. 20 mai 2019 à 14:51, Gary Gregory a
>>> écrit :
Hi All:
Right now, if you uses an 'include' in a
Hi,
BasicThreadFactory has an option to create daemon threads. I assume, you
have found out in the meantime?
Oliver
Am 01.05.19 um 23:07 schrieb Gary Gregory:
> Hi All,
>
> Hard to believe, but we do not have one yet.
>
> https://issues.apache.org/jira/browse/LANG-1455
>
> Assigned to your
Am 02.01.20 um 12:08 schrieb Bruno P. Kinoshita:
> Also not a user of OSGi. But I feel like it is a bug that could be reverted
> and informed in the changelog and release email?
> But not too sure if that's the best option.
> Bruno
>
> Sent from Yahoo Mail on Android
>
> On Thu, 2 Jan
+1
Build works fine with Java 8, artifacts and site look good.
Oliver
Am 09.03.20 um 15:55 schrieb Rob Tompkins:
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Configuration 2.6 was released, so I would like to release
> Apache Commons
processor.
Credit:
This issue was discovered by Daniel Kalinowski of ISEC.pl Research Team
Oliver Heger
on behalf of the Apache Commons PMC
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e
Hi Rob,
many thanks for working on the release.
I also did a check. The builds of the jar and the site were successful
with the configuration below. Artifacts and site look good.
The NOTICE file has still a copyright year of 2019; so if you re-roll
the RC, you should adapt this. Otherwise, I
The form at Mitre was just submitted, so I assume that the issue will be
visible soon.
Oliver
Am 12.03.20 um 19:18 schrieb Gary Gregory:
> Note that https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-1953 is not
> "live" yet.
>
> Gary
>
> On Thu, Mar 12, 2020 at
Hi all,
once we had a discussion (it must be one or two years ago) whether
Commons could support components in other (JVM) languages, too. IIRC,
there were no strong objections, but there has never been a follow up.
For a project in Scala, I needed some limited functionality to process
command
Resending with a different subject to potentially reach a broader audience.
Am 17.09.20 um 21:47 schrieb Oliver Heger:
> Hi all,
>
> once we had a discussion (it must be one or two years ago) whether
> Commons could support components in other (JVM) languages, too. IIRC,
> there
Hi Gilles,
Am 20.09.20 um 19:44 schrieb Gilles Sadowski:
> Hello.
>
> 2020-09-17 21:47 UTC+02:00, Oliver Heger :
>> Hi all,
>>
>> once we had a discussion (it must be one or two years ago) whether
>> Commons could support components in other (JVM) languages, t
Am 22.07.20 um 18:28 schrieb Stefan Bodewig:
> On 2020-07-22, Rob Tompkins wrote:
>
>> I’m happy to merge them….will get to them by tomorrow morning ok?
>
> TBH I'd prefer to turn them off and reject the PRs.
>
> Personally I don't see any value for our downstream users if we update
> our
Am 05.05.21 um 21:54 schrieb Gilles Sadowski:
Le mer. 5 mai 2021 à 20:33, Oliver Heger
a écrit :
Am 05.05.21 um 20:26 schrieb Gilles Sadowski:
Le mer. 5 mai 2021 à 18:57, Gary Gregory a écrit :
IMO the lack of +1s shows the lack of appetite to manage another component
That's
Am 30.06.21 um 14:41 schrieb Gary Gregory:
On Tue, Jun 29, 2021 at 4:24 PM Stefan Bodewig wrote:
Hi
I'm sorry, but I'm unable to see what would or would not work for the
people who chimed in. Short of calling for a vote, lets try with a poll
that could show whether there is some sort of
Am 05.05.21 um 20:26 schrieb Gilles Sadowski:
Le mer. 5 mai 2021 à 18:57, Gary Gregory a écrit :
IMO the lack of +1s shows the lack of appetite to manage another component
That's certainly true.
And nobody is forced to do anything.
When the other CM spin-offs started, there was only
901 - 953 of 953 matches
Mail list logo