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 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 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
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
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 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
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
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
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
+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
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
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
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
+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
>
+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 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
>
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
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
>
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
> ]
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
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
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
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:
the quick reply.
Just checked that a click on the md5 file on [lang]'s download page
gives me a 404.
But for newly released components the download pages generated
automatically will then be correct.
Regards
Oliver
>
> Gary
>
> On Fri, Aug 3, 2018 at 10:01 AM Oliver Heger
>
Hi all,
one question regarding release preparation:
Download pages now link to sha checksums rather than outdated md5
hashes. Thus, the commons-build plugin generates the corresponding links.
There are some components, however, that list multiple versions on their
download pages, e.g. the new
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 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
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
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 RC1 is available for review here:
> 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 (
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
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
[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.
>>
>
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
+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
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
> 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.
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
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
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 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
>
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
+1
Commons Configuration could be built successfully with CP 47.
Oliver
Am 28.06.2018 um 15:21 schrieb Rob Tompkins:
> We have fixed quite a few bugs and added some significant enhancements since
> Apache Commons Parent 46 was released, so I would like to release Apache
> Commons Parent 47.
>
Hi all,
I tried to update the pom of [configuration] to commons-parent 46. When
I build the site I get the error below.
[configuration] has a number of dependencies marked marked as
true. These are obviously not added to the
classpath. I tried to follow the suggestion in the error message to
java.desktop (Was:
> Re: [LANG] Thoughts about Lang 4.0)
>
>
>
>
>> Am 25.05.2017 um 18:23 schrieb Oliver Heger :
>>
>>
>>
>> Am 24.05.2017 um 13:55 schrieb Stephen Colebourne:
>>> On 23 May 2017 at 17:17, sebb wrote:
>>>>
Build works fine on Windows 10 with Java 1.7 and 1.8. Artifacts and site
look good.
+1
Oliver
Am 31.05.2018 um 14:57 schrieb Stefan Bodewig:
> Hi all,
>
> I would like to release Compress 1.17.
>
> Compress 1.17 RC1 is available for review here:
>
Am 12.05.2018 um 20:36 schrieb Gary Gregory:
> Hi All:
>
> Commons DBCP still has an Ant build. Should we drop it?
No objections from me. I think we already dropped support for Ant for
most of our components.
Oliver
>
> Gary
>
Am 12.05.2018 um 20:16 schrieb Gary Gregory:
> On Sat, May 12, 2018 at 10:37 AM, Oliver Heger <oliver.he...@oliver-heger.de
>> wrote:
>
>> Build works fine with Java 1.7 and 1.8 - even the ant build seems to
>> work. Artifacts and site look good.
>&
Build works fine with Java 1.7 and 1.8 - even the ant build seems to
work. Artifacts and site look good.
The only problem I noticed is that the release notes refer to version
"2.3.0-SNAPSHOT", which is confusing.
Do you think this requires a new RC or can we live with that?
Oliver
Am 09.05.2018
Hi Matt,
Am 29.04.2018 um 20:30 schrieb Matt Sicker:
> On 26 April 2018 at 14:38, Oliver Heger <oliver.he...@oliver-heger.de>
> wrote:
>
>> Recently I had a closer look at streaming libraries like Akka Streams.
>> So I had the idea to model the problem in a similar
Am 29.04.2018 um 19:08 schrieb Stefan Bodewig:
> Hi all
>
> I've introduced a whole lot of infrastructure code with
>
> https://github.com/apache/commons-compress/commit/f62c523154dfedcf49a87a865db545bb8c55e795
>
> but the interface now looks nicer to me, in particual see
>
> try
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,
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
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 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
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
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 10.02.2018 um 09:55 schrieb Stefan Bodewig:
> On 2018-02-10, Simon Spero wrote:
>
>> Writing tests for osgi modules is painless... the second time :-P
>
> I said I "was pointed into a direction for writing a test ..." that's
> been your and Bertrand's input. :-)
>
>> The key to making
Build works fine with Java 1.7 and 1.8 on Windows 10. With the site
build on Java 8 I get the same error as for 1.16 (see below, not
blocking). Artifacts and site look good.
+1
Oliver
[warn] No new version specified and file
Hi,
build works fine with Java 1.7 and 1.8 on Windows 10. When building the
site I get the same error as mentioned by sebb. Artifacts and site look
good.
+1
Oliver
Am 02.02.2018 um 19:14 schrieb Stefan Bodewig:
> As indicated I think it is time to get Compress 1.16 out.
>
> Compress 1.16 RC1
+1
Oliver
Am 02.02.2018 um 18:54 schrieb Mark Thomas:
> Hello all,
>
> I propose that we create a new component [commons-signing].
>
> The scope of the component is code signing utilities including, but not
> limited to, Ant and Maven plugins for the Symantec code signing service
> that a
Am 24.01.2018 um 14:29 schrieb Gilles:
> Ping?
>
> More opinions, please (to avoid rehashing the issue at
> vote time).
>
> Thanks,
> Gilles
>
> On Mon, 15 Jan 2018 22:14:03 +0100, Gilles wrote:
>> On Mon, 15 Jan 2018 09:49:44 -0700, Gary Gregory wrote:
>>> Hi All,
>>>
>>> There are some many
Am 15.01.2018 um 18:04 schrieb Oliver Heger:
> Hi,
>
> Am 14.01.2018 um 00:33 schrieb Bindul Bhowmik:
>> Hello,
>>
>> It seems notifications from the commons-configuration GitHub mirror
>> are not setup to go to any commons mailing list.
>>
>> I o
Hi,
Am 14.01.2018 um 00:33 schrieb Bindul Bhowmik:
> Hello,
>
> It seems notifications from the commons-configuration GitHub mirror
> are not setup to go to any commons mailing list.
>
> I opened a trivial pull request - #10 [1], but I don't see any emails
> on any commons lists for this pull
Am 13.01.2018 um 15:36 schrieb Gilles:
> On Sat, 13 Jan 2018 08:48:19 -0500, Rob Tompkins wrote:
>> Given that right now we don’t have sufficient votes to release the
>> plugin, do folks want me to cancel this vote in leu of the lazy vote
>> process cleaning up the nits that folks have found?
+1
Great work, Rob! Many thanks!
Oliver
Am 04.01.2018 um 17:56 schrieb Rob Tompkins:
> Hello all,
>
> I propose that we create a new component [commons-release-plugin] to be
> managed in the same fashion as the commons-build-plugin, and by that I mean:
>
> * Use COMMONSSITE as the jira area
Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.
+1
Oliver
Am 16.12.2017 um 23:35 schrieb Gary Gregory:
> We have fixed quite a few bugs and added some enhancements since Apache
> Commons Pool 2.4.3 was released, so I would like to release Apache Commons
>
Am 19.12.2017 um 17:27 schrieb Gary Gregory:
> I keep on copying this from project to project and it seems fitting for
> Commons Lang:
In the concurrent package, there is the BasicThreadFactory class. Could
this class satisfy your needs or can it be extended?
Oliver
>
> import
Am 14.12.2017 um 01:38 schrieb Gary Gregory:
> On Wed, Dec 13, 2017 at 2:03 PM, Oliver Heger <oliver.he...@oliver-heger.de>
> wrote:
>
>> Hi,
>>
>> thank you for your patience.
>>
>> Build works fine with Java 1.7 on Windows 10 (because of the Java
Hi,
thank you for your patience.
Build works fine with Java 1.7 on Windows 10 (because of the Java 8
Javadoc errors I built the site with 1.7).
I have some minor findings:
- As Bruno already noticed, the release notes contain this strange text.
- In README.md the current version for the
Hi,
build works fine with Java 8 on Windows 10. Artifacts look good.
I am still not able to build the site locally; I get the error below.
Can you somehow provide a zip with the site for inspection?
Thanks
Oliver
[INFO]
ation section on index.html.
There are some checkstyle and findbugs finding, but I assume nothing new
or critical.
So +1
Oliver
>>
>> On Sun, Dec 3, 2017 at 1:44 PM, Oliver Heger <oliver.he...@oliver-heger.de
>>> wrote:
>>
>>> Here is the stack trace:
>>>
t; Gary
>
> On Dec 3, 2017 08:33, "Oliver Heger" <oliver.he...@oliver-heger.de> wrote:
>
>> Hi,
>>
>> when building on Windows 10 with both Java 1.7 and 1.8 I get the test
>> failure below. Does anybody else see this?
>>
>> Oliver
&
Hi,
when building on Windows 10 with both Java 1.7 and 1.8 I get the test
failure below. Does anybody else see this?
Oliver
Results :
Tests in error:
JDKGenericDumpTestCase.data:82->findJavaHomes:87->findJavaHomesOnWindows:97->addAllJavaHomesOnWindows:65
▒ Win32
Tests run: 107, Failures: 0,
Hi Sergio,
build works fine with Java 1.8 on Windows 10. However, the site build
fails for me with the following error:
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Commons RDF
rded message ------
> From: Oliver Heger (JIRA) <j...@apache.org>
> Date: Sat, Nov 11, 2017 at 8:24 AM
> Subject: [jira] [Resolved] (CONFIGURATION-675) Add .gitignore file
> To: iss...@commons.apache.org
>
>
>
> [ https://issues.apache
Hi,
thanks for your contribution. See below...
Am 06.11.2017 um 12:48 schrieb mingleizhang:
> Hello experts
>
>
> I implemented a tool that can directly read a file name by its current
> classloader read an Inputstream and returns a java.util.Properties and
> created two JIRA for this issue
Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.
+1
Oliver
Am 04.11.2017 um 19:50 schrieb Gary Gregory:
> We have fixed a few bugs since Apache Commons Lang 3.6 was released, so I
> would like to release Apache Commons Lang 3.7.
>
> Apache Commons Lang 3.7
ive him some more time.
Do you know him in person, Bruno? Or did you have contact with him in
the past?
Thanks
Oliver
>
> From: Oliver Heger <oliver.he...@oliver-heger.de>
> To: Commons Developers List <dev@commons.apache.org>
> Sent: Thursday, 2 November 2017
On 04.11.2017 17:58, Bernd Eckenfels wrote:
> I like the idea (and prefer Commons Testing), for example a method to list
> all non-daemon threads after a test run (to see there is no resource leak)
> can be used independent of the Unit Test Framework.
We already had a Commons Test project. It
Hi,
recently I did some work to get the Jelly site build with Maven running.
As this is experimental, I created my own fork of the project for this
purpose [1].
An important part of the documentation is the Jellydoc, an automatically
generated documentation for the standard tag libs shipped with
Build works fine with Java 1.6 and 1.8 on Windows 10, artifacts and site
look good.
One problem I found in the release notes: they refer to "the
commons-codec-1.11-SNAPSHOT release". This is confusing, but probably
not a blocker.
So +1
Oliver
Am 17.10.2017 um 20:30 schrieb Gary Gregory:
> Hi
RC1 and RC2 are:
> - Worked on the design of the ByteOrderParser class
> - Fixed IO-546
> - Fixed IO-553
>
> The changes between RC2 and RC3 are:
> - RC2 contained cobertura instrumented class files (thanks to Oliver Heger to
> catching this one!)
>
> Commons IO 2.6 RC3
Build works fine with Java 1.7 and 1.8 on Windows 10. Artifacts and site
look good.
+1
Oliver
Am 14.10.2017 um 15:45 schrieb Stefan Bodewig:
> Hi all
>
> this is mostly a bugfix release but it was about time for a new release.
>
> Compress 1.15 RC1 is available for review here:
>
>>
>> The changes between RC2 and RC3 are:
>> - RC2 contained cobertura instrumented class files (thanks to Oliver Heger
>> to catching this one!)
>>
>> Commons IO 2.6 RC3 is available for review here:
>> https://dist.apache.org/repos/dist/dev/common
Hi Benedikt,
it seems that the binary artifact does not contain the real classes, but
classes manipulated by Cobertura. commons-io-2.6.jar contains a
cobertura.properties file, and opening a class in a decompiler shows
some Cobertura-specific initialization code.
Can you please double-check?
instructions on how to submit bug reports, 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
Am 11.10.2017 um 23:04 schrieb Gary Gregory:
> Can you release from Nexus ASAP SVP?
Done.
Oliver
>
> Gary
>
> On Oct 11, 2017 14:24, "Oliver Heger" <oliver.he...@oliver-heger.de> wrote:
>
>> The vote to release Commons Configuration 2.2 based on
The vote to release Commons Configuration 2.2 based on RC1 passed with
the following binding votes:
Bruno P. Kinoshita: +1
Gary Gregory: +1
Rob Tompkins: +1
Oliver Heger: +1
No other votes were cast.
Thanks to all who took the time to review the RC. I will start the
release
My own +1
Oliver
Am 08.10.2017 um 22:24 schrieb Oliver Heger:
> Hi all,
>
> there was a request for a new release on the ML, so here we go.
>
> Configuration 2.2 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/configuration/ (rev. 22170)
&g
Hi all,
there was a request for a new release on the ML, so here we go.
Configuration 2.2 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/configuration/ (rev. 22170)
The tag is here:
Hi,
same comments as for the last time:
Build works fine with Java 1.7 and 1.8 on Windows 10 (I don't get any
test failures). Artifacts and site look good.
Some findings:
- Both source and binary distribution use the same top-level folder.
- The site has two checkstyle reports. One is empty,
1 - 100 of 953 matches
Mail list logo