[ X ] +1 Release these artifacts
Tested from the provided git commit sha, running `mvn clean test site` with:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home:
Not so familiar, more familiar with Jena, but they are related.
If nobody else volunteers, I can try to spend a weekend triaging issues and
seeing if I can catch up with the changes since the last release and volunteer
to cut a new release.
CheersBruno
From: Gary Gregory
ect: Re: [dbcp] update to pool 2.4.3.
On 31/10/2017 00:54, Gary Gregory wrote:
> On Sun, Oct 29, 2017 at 2:09 AM, Mark Thomas <ma...@apache.org> wrote:
>
>> On 29 October 2017 03:54:40 GMT+00:00, "Bruno P. Kinoshita" <
>> brunodepau...@yahoo.com.br.INVALID>
Hi Amitava,
There were still pending issues prior to the 1.0 release, so it was moved to a
branch for further work. If you are interested in using it, perhaps you would
have some suggestions/comments for these tickets:
* Human name parser https://issues.apache.org/jira/browse/TEXT-15
* Make
+1
Sent from Yahoo Mail on Android
On Sat, 19 May 2018 at 7:35, Gary Gregory wrote: Hi
All:
A lot of methods in CollectionUtils are not null-safe and are documented as
such in Javadoc with throwing NPEs.
I'd like to change that.
The change is behavioral and BC
No objections from me. +1
Sent from Yahoo Mail on Android
On Sat, 19 May 2018 at 9:24, Gary Gregory wrote: Hi
All:
Eclipse is moving to SHA-256 to validate downloads [1] alongside MD5.
We just updated to SHA-1 which apparently has been subject to a collision
about this
issue (-:
Bruno
From: Gary Gregory
To: Commons Developers List ; Bruno P. Kinoshita
Sent: Sunday, 10 June 2018 10:56 AM
Subject: Re: [LANG] Java 9 problems because of dependencies to java.desktop
(Was: Re: [LANG] Thoughts about Lang 4.0)
So
Hi all,
There is a patch [1] for LANG-1339 [2] that I would like to merge. The
discussion around this issue can be found in the rest of this e-mail thread.
The patch basically deprecates the existing classes that depend on
java.desktop, and provide alternative implementations. The previous
[ X ] +1 Release these artifacts
Build passing with no errors on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_171, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default
2018 at 22:11, Gilles wrote:
> Hello.
>
> On Sun, 10 Jun 2018 21:34:49 +0200, Oliver Heger wrote:
>>
>> Hi Bruno,
>>
>> Am 10.06.2018 um 00:52 schrieb Bruno P. Kinoshita:
>>>
>>> Hi all,
>>>
>>> There is a patch [1] for LANG-1339
[ X ] +1 Release these artifacts
Building OK from commit d7aa662fbbb99e536ae28c47d0c4e1d51e39d5b9 passing OK on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_171, vendor: Oracle Corporation
Hi Pascal,
Apache OpenNLP uses that approach whenever possible
(http://opennlp.apache.org/using-git.html). I like the way the commit tree
looks after a while. Sometimes it's not practical, especially when receiving
patches from external contributors (developers can still check-out code locally
Hi Gilles,
I've checked out the latest from https://github.com/apache/commons-rng, updated
the pom.xml to use 47 instead of 45, and downloaded JDK 9.
kinow@local:~/Development/java/apache/commons-rng$
JAVA_HOME=/home/kinow/Development/java/jdk-9.0.4/ mvn -v
Apache Maven 3.5.2
[ X ] +1 Release it.
I'm OK with the lazy vote from the other thread, or with this vote process.
Both work fine for me.
And fantastic work! Build from tag passing with `mvn clean test site` on:
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven
[ X ] +1 Create the component
Thanks for working on this!
Bruno
From: Rob Tompkins
To: Commons Developers List
Sent: Friday, 5 January 2018 5:56 AM
Subject: [VOTE] Create new component commons-release-plugin
Hello,
If memory serves me well, some time ago we had a discussion around sanselan &
commons-imaging 1.0. One of the issues with commons-imaging 1.0 was the Debug
class.
https://issues.apache.org/jira/browse/IMAGING-154
I finished the pull request, but Gilles raised an important point, about
>If the fix is confirmed I'd like to cut a 1.16.1 release more or less
>immediately. Any objections?
+1, go for it. Took me a while to spot the difference between the two lines.
Tricky to remember to use := and not = there.
Cheers
B
From: Stefan Bodewig
imaging/blob/7e7f96857df999175bb614732e13272a82f7962a/src/main/java/org/apache/commons/imaging/FormatCompliance.java#L70).
Cheers
Bruno
From: sebb <seb...@gmail.com>
To: Commons Developers List <dev@commons.apache.org>; Bruno P. Kinoshita
<brunodepau...@yaho
without
further comment. Nobody may rely on it in production code, but during
development it might be helpful. With such an approach we might not have
a need to find a better interface to provide this functionality.
Just my 2¢,
Jörg
Am Mon, 05 Feb 2018 12:20:58 + schrieb Bru
Hi Claude,
Quite sure there was similar discussion some time ago. But I can't recall if it
was here in commons, somewhere in the incubator, or labs?
But regarding commons, before the component/jira/mailing list are created, I
think it would have to go either via sandbox or incubator first?
an interface ( perhaps with the current class
> as the
> default implementation ) and be passed in optionally?
>
>
> On February 5, 2018 at 07:21:11, Bruno P. Kinoshita (
> brunodepau...@yahoo.com.br.invalid) wrote:
>
> Hello,
>
> If memory serves me well, some
Hi,
See https://issues.apache.org/jira/browse/LANG-1373 for the ticket history, and
https://github.com/apache/commons-lang/pull/311 for the pull request review &
discussion.
I'm happy with the current design. It builds on top of the existing StopWatch,
giving users the ability to have
Hello,
I couldn't find the tag 2.6 [1], as reported in IO-569 below.
Maybe we skipped some step from "4 Create SCM Tag for the Final Release" in [2]
? Not too sure if that's really OK just to create manually the tag now, or if
I've missed something here.
Any thoughts?
Cheers
Bruno
[1]
I did that only once during a release for commons-csv. But looking at the
documentation for publishing commons sites located here:
https://commons.apache.org/site-publish.html under the section "Components", it
explains how it works. So perhaps you could try:
```
cd commons-email
vim
Having the same issue as before when I was testing commons-pool. Some tests are
hanging and the console is just waiting for some threads to finish.
When I complained about this test failure last week while voting on
commons-pool, I went to work and tested it, and it actually worked. For some
heers
Bruno
From: Gary Gregory <garydgreg...@gmail.com>
To: Commons Developers List <dev@commons.apache.org>; Bruno P. Kinoshita
<brunodepau...@yahoo.com.br>
Sent: Saturday, 23 December 2017 3:50 AM
Subject: Re: [VOTE] Release Apache Commons
ention merely as reassurance that
they will get looked at.
ajs6f
> On Dec 21, 2017, at 1:45 PM, Jörg Schaible <joerg.schai...@gmx.de> wrote:
>
> Hi Bruno,
>
> Am Wed, 13 Dec 2017 09:53:35 + schrieb Bruno P. Kinoshita:
>
> [snip]
>
>> I went throug
[ X ] +1 Release these artifacts
Maven build passing OK from tag + svn revision with environment:
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_171, vendor: Oracle Corporation
Java home:
Hi Andreas!
Happy to hear you successfully used Commons Imaging, and also keen to hear what
features/suggestions you have for the API.
There was a call for 1.0 to be released, but some blockers were found and the
release was called off (e.g. https://issues.apache.org/jira/browse/IMAGING-154).
I
Hi all,
Since Sanselan became Commons Imaging, some work has been done, but there was
never an official release.
The project is using Java7, and I would like to update it to use Java 8. Any
objections?
My plan is to just update to Java8 now and prepare the 1.0 release vote. Then
slowly add
t; >> > Users that use a logging framework can redirect the JUL logging into
> >> their
> >> > log file with the JUL adapter of their logging library.
> >> >
> >> > But that’s just me.
> >> >
> >> > Remko
Builds successfully from tag with `mvn clean test site` on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_181, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default
but is still on
Java 7.
After the release we can update to Java 8 for 1.1.
Cheers,
Pascal
Am 12.08.2018 um 00:46 schrieb Bruno P. Kinoshita:
> Hi all,
>
> Since Sanselan became Commons Imaging, some work has been done, but there was
> never an official release.
>
> The proj
calls to
System.out in there.
Thanks!
Bruno
________
From: Bruno P. Kinoshita
To: Commons Developers List
Sent: Tuesday, 6 February 2018 11:30 PM
Subject: Re: [imaging] IMAGING-154 remove Debug class
Hi sebb,
>Another aspect of debugging is ensuring that methods
: Wednesday, 15 August 2018 11:29 AM
Subject: Re: [lang] preparing for 3.8
> On Aug 14, 2018, at 7:13 AM, Bruno P. Kinoshita
> wrote:
>
> Hi Rob!
>
> Thanks for RM'ing lang 3.8!
>
>
> I think it would be good to fix for LANG-1339, as we get closer to supporting
Congrats! And great to have you back Benedikt!!!
Bruno
Sent from Yahoo Mail on Android
On Fri, 17 Aug 2018 at 2:59, Benedikt Ritter wrote: Hi
all,
I have been pretty quite over the past 12 month. There are a lot of reasons
for this. The most important reasons are:
- I've been Lead
vote should go out
in September!
Thanks!
Bruno
From: Bruno P. Kinoshita
To: Commons Developers List
Sent: Thursday, 16 August 2018 12:26 AM
Subject: Re: [imaging] IMAGING-154 remove Debug class
Hi,
Remko's suggestion sounded good, and the KISS princ
s helps,
>
> Remko
>
> (Shameless plug) Every java main() method deserves http://picocli.info
>
> > On Aug 12, 2018, at 21:21, Gilles wrote:
> >
> > Hello Bruno.
> >
> >> On Sun, 12 Aug 2018 08:56:37 + (UTC), Bruno P. Kinoshita wrote:
> >&g
the middle.
>>>
>>> *Final note*
>>> I would never log to System out, always use system err instead. This
>>> allows programs using your library to pipe output to other programs
>> without
>>> their output getting mixed with your library’s diagnostic ou
2642ecabb3b4ab73df83b1e5982076
From: Gilles
To: dev@commons.apache.org
Sent: Monday, 13 August 2018 12:21 AM
Subject: Re: [imaging] IMAGING-154 remove Debug class
Hello Bruno.
On Sun, 12 Aug 2018 08:56:37 + (UTC), Bruno P. Kinoshita wrote:
> Hi all,
>
diagnostic output.
Hope this helps,
Remko
(Shameless plug) Every java main() method deserves http://picocli.info
> On Aug 12, 2018, at 21:21, Gilles wrote:
>
> Hello Bruno.
>
>> On Sun, 12 Aug 2018 08:56:37 +0000 (UTC), Bruno P. Kinoshita wrote:
>> Hi all,
>>
your library to pipe output to other programs
> without
> > their output getting mixed with your library’s diagnostic output.
> >
> > Hope this helps,
> >
> > Remko
> >
> > (Shameless plug) Every java main() method deserves http://picocli.info
> >
> &g
Logging were
started before SLF4J (and perhaps JUL) were created, I believe.
(Shameless plug) Every java main() method deserves http://picocli.info
> On Aug 13, 2018, at 18:22, Bruno P. Kinoshita
> wrote:
>
> Right now that's where I am standing too. If adding a depende
mons Imaging to Maven
central repo
Den tor. 9. aug. 2018 kl. 09:20 skrev Bruno P. Kinoshita
:
> It should be possible to release a new snapshot, or maybe another
alpha/beta ?
Yes, a alpha/beta release to the maven central now would be very useful!
The API has changed significantly since the
Hi Rob!
Thanks for RM'ing lang 3.8!
I think it would be good to fix for LANG-1339, as we get closer to supporting
Java 9 someday...
I believe the summary from the last comments in the discussion in the mailing
list is that looks like Observable/Observable won't be removed from the JDK,
but
OK for me, RERO after all
Cheers
Bruno
From: Gary Gregory
To: Commons Developers List ; Bruno P. Kinoshita
Sent: Wednesday, 15 August 2018 12:15 AM
Subject: Re: [lang] preparing for 3.8
Not a blocker IMO. We can release 3.8 and work on this for 3.9.
Gary
[ X ] +1 Release these artifacts
Building fine on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_181, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale:
From: Gilles
To: dev@commons.apache.org
Sent: Tuesday, 14 August 2018 11:39 PM
Subject: Re: [lang] preparing for 3.8
Hi.
On Tue, 14 Aug 2018 11:13:48 + (UTC), Bruno P. Kinoshita wrote:
> Hi Rob!
>
> Thanks for RM'ing lang 3.8!
>
>
> I think it would be good to fix for LA
[ X ] +0 OK, but... some issues with RAT in local project site (more below). Or
a +1 if not an issue.
Build passing successfully from git commit on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version:
From: sebb
To: Commons Developers List ; Bruno P. Kinoshita
Sent: Thursday, 23 August 2018 11:23 AM
Subject: Re: [CSV] Inconsistent record separator behavior
On 23 August 2018 at 00:01, Bruno P. Kinoshita
wrote:
>
>>Maybe I'm just not getting it, but it feels pretty
Hi,
All issues for 1.0 are now fixed. Thanks for the reviews/comments and for
putting up with my messages about debug & other pending issues for a 1.0
release (:
It was suggested to cut a 1.0-alpha prior to a full 1.0 release, and I have no
objection for that. So I've created a local branch
[ X ] +1 Release these artifacts
Not much time to review signatures, but tested the build with `mvn clean test
site` against commit sha from git
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version:
Hi,
Will try to look at the code and give a better answer during the weekend. But
risking a silly question, would it mean that users are not able to parse a CSV
unless each CSV row is separated by LF or CRLF? I remember getting a CSV in a
government website some time ago that was formatted in
ust 2018 7:10 AM
Subject: Re: [CSV] Inconsistent record separator behavior
Hi Bruno,
Am Mi., 22. Aug. 2018 um 15:10 Uhr schrieb Bruno P. Kinoshita
:
> Hi,
>
>
> Will try to look at the code and give a better answer during the weekend.
> But risking a silly question, would
ybe internal
only.
Bruno
From: Gilles
To: dev@commons.apache.org
Sent: Friday, 20 July 2018 11:05 AM
Subject: Re: [LANG] Java 9 problems because of dependencies to java.desktop
Hello.
On Mon, 16 Jul 2018 21:30:00 + (UTC), Bruno P. Kinoshita wrote:
>>What about introdu
ly 2018 4:13 AM
Subject: Re: [LANG] Java 9 problems because of dependencies to java.desktop
(Was: Re: [LANG] Thoughts about Lang 4.0)
Am 16.07.2018 um 13:40 schrieb Bruno P. Kinoshita:
> Saw some recent activity around lang 3.8, and remembered about this issue,
> and then look
deprecate the functionality without
replacement.
Stephen
On 10 June 2018 at 22:11, Gilles wrote:
> Hello.
>
> On Sun, 10 Jun 2018 21:34:49 +0200, Oliver Heger wrote:
>>
>> Hi Bruno,
>>
>> Am 10.06.2018 um 00:52 schrieb Bruno P. Kinoshita:
>>>
>>> Hi all,
>
+1
Build passing successfully on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0_172/jre
Default locale: en_NZ, platform encoding: UTF-8
I think you are probably correct about the SVN part being incomplete.
As for the git repository, in a discussion about Apache Sis about moving to
git, I learned that those git-wip repositories are being transitioned into
gitbox (wonder if the wip actually means work-in-progress?). Can't find
[ X ] +1 Release these artifacts
Build passing successfully on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_181, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Hello,
While preparing the release candidate for Imaging, I noticed one entry in the
instructions that seems to be outdated.
Under "Configure the Build to Generate a Complete Set of Release Artifacts"
[1], the list of entries for MANIFEST.MF starts with:
- Extension-Name:
Hi all,
I am almost done following the docs to prepare a release. Didn't struggle as
much as I expected with the release-plugin. Had more trouble getting the
MANIFEST.MF entries corrected.
But now, before I create the dist tag, and upload the zip/tar.gz (this was not
executed by the release
[ X ] +1 Release these artifacts
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_171, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_NZ, platform
Hi Seshadri,
I think Commons Text is a better place for soundex and other phonetic
algorithms.
Bruno
Sent from Yahoo Mail on Android
On Mon, 26 Mar 2018 at 5:38, seshadri n s wrote:
Hi,
I am planning to implement soundex function in StringUtils
I think StopWatch and CircuitBreakers could be moved together to the same
component. However, a circuit breaker can be time-related, or not (e.g. a
circuit breaker for memory size). So probably commons-timing could be a good
place for StopWatch, but maybe not for circuit-breaker. But I think
gmail.com>; Bruno P. Kinoshita
<brunodepau...@yahoo.com.br.invalid>; Commons Developers List
<dev@commons.apache.org>
Sent: Wednesday, 21 March 2018 11:00 AM
Subject: Re: [DISCUSS] new component for timing?
If monitoring was started a new, and not re-viving the old monitor
We could perhaps move some classes from the concurrent package too I think.
Like the circuit breakers. That'd solve our current issue with java.desktop
dependency and java9
Sent from Yahoo Mail on Android
On Sat, 3 Mar 2018 at 3:45, Gary Gregory wrote: On
Fri,
I am canceling this VOTE. Need to re-roll another release candidate to fix the
file signatures, following the new requirements. Will roll a new RC this week.
Thanks
Bruno
From: Gary Gregory
To: Commons Developers List ; Bruno P. Kinoshita
Sent: Monday
: Bruno P. Kinoshita
Sent: Monday, 29 October 2018 2:49 AM
Subject: [site] update release process (Was: Re: [VOTE] Release Commons Imaging
1.0-alpha1 based on RC1)
This is mildly on me for not updating the release docs recently. I’ll put that
on my docket for the week.
PS. @Bruno solid work
Building from tag works fine with `mvn clean test site` on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0_172/jre
Default locale: en_NZ,
- What else would need to be updated? The site perhaps??? Or is it OK to have
>a few places showing 1.0?
Vote e-mail coming in a few minutes (hopefully).
Cheers
Bruno
From: Gary Gregory
To: Commons Developers List ; Bruno P. Kinoshita
Sent: Sunday, 9
We have fixed quite a few bugs and added some significant enhancements since
Sanselan 0.97-incubator was released,
so I would like to release Apache Commons Imaging 1.0-alpha1.
This will be the first release after the project was renamed from Sanselan to
Apache Commons Imaging. This is an alpha
+1 to release as-is and postpone POOL-355, then +1 to Java8 later too
CheersBruno
From: Gary Gregory
To: Commons Developers List
Sent: Tuesday, 30 October 2018 4:17 AM
Subject: Re: [pool] how to move to Java8?
My view is to skip POOL-355 and release the current code still, on Java
/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Bruno P. Kinoshita,
Release Manager (using key
correctly.
Thank you again!!
Bruno
ps: Will look for the Slack link again... I don't have Slack on this
computer... do you know if we have the link for the slack channel somewhere in
the website/twitter/etc?
From: Rob Tompkins
To: Bruno P. Kinoshita
C
s like that).
CheersBruno
From: "thc...@gmail.com"
To: dev@commons.apache.org
Sent: Tuesday, 30 October 2018 10:34 PM
Subject: Re: [VOTE] Release Apache Commons Imaging 1.0-alpha1 based on RC2
Hi.
On 30/10/2018 09:09, Bruno P. Kinoshita wrote:
> We have fixed quite a few
?
Gary
On Wed, Oct 31, 2018 at 11:06 AM Andreas Lehmkuehler
wrote:
> Am 30.10.18 um 10:09 schrieb Bruno P. Kinoshita:
> > We have fixed quite a few bugs and added some significant enhancements
> since Apache Sanselan Incubating 0.97-incubator was released, so I would
> like to
run the build on Java 8, I get Javadoc errors and using
-P jdk8-javadoc does not seem to turn doclint off. Can anyone get the build
to work on Java 8?
Gary
On Wed, Oct 31, 2018 at 11:06 AM Andreas Lehmkuehler
wrote:
> Am 30.10.18 um 10:09 schrieb Bruno P. Kinoshita:
> > We have fixed qu
If anyone would like to take over commons-imaging 1.0-alpha1 release. We had up
to RC2 I think, so there should be little left to do.
I can volunteer around x-mas or January/19 I think.
Bruno
From: Gary Gregory
To: Commons Developers List
Sent: Wednesday, 14 November 2018 8:34 AM
[ X ] +1 Release these artifacts
Build passing with mvn clean test site on
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d;
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0_172/jre
Default
Build passing OK with `mvn clean test site` on
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_NZ,
[ x ] +1 Release it.
Build from tag passing on Ubuntu LTS Java 8 with mvn clean test install site on
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_191, vendor: Oracle Corporation, runtime:
I got confused by vote/cancel threads, but the RC should be good. Will check
what's the latest vote thread, sorry.
And I guess the lack of votes right now is probably due to holidays (:
CheersBruno
From: Maxim Solodovnik
To: Commons Developers List ; Bruno P. Kinoshita
Sent: Sunday
Hi Sukant,
The project is maintained mainly by volunteers. I am indeed working on other
things, including on other issues for [imaging]. Your changes seem interesting,
but I would rather work on the other issues first (including the 1.0 release)
and postpone reviewing your pull request till
>From what I understood from the previous messages & discussion on GitHub, it
>would be more convenient for users to be able to have a List instead of an
>Iterable, or instead of having to call the #toList() or convert to a List in
>some other way.
I commented in the pull request, that I don't
FWIW I had a similar experience, and realized I was doing `git fetch --all`,
but it didn't bring the tags. `git fetch --tags` did the trick. After that I
could `git checkout $tag-name`
Cheers
Bruno
From: Gilles
To: dev@commons.apache.org
Sent: Thursday, 27
[ X ] +1 Release these artifacts
Thanks !
Bruno
From: Rob Tompkins
To: Commons Developers List
Sent: Monday, 24 December 2018 8:23 PM
Subject: [VOTE] Release Apache Commons FileUpload 1.4 based on RC2
We have fixed quite a few bugs and added some
Hi Gilles!
Sorry, just came back from a long holiday, speaking Portuguese only. Semantic,
vocabulary, etc, in English is a bit laggy right now.
>>On Tue, 18 Dec 2018 07:22:00 + (UTC), Bruno P. Kinoshita wrote:
>> From what I understood from the previous messages & discuss
Missed the vote (holiday in Auckland), but my late +1, and thanks for RM'ing
it Gary!
Bruno
On Monday, 28 January 2019, 10:32:53 AM NZDT, Gary Gregory
wrote:
May I get at least one more review please?
Gary
On Sun, Jan 27, 2019, 10:07 Rob Tompkins +1
> signatures good, sha1
Hmm, couldn't build it. Tried from the dist archive, decompressing the .tar.gz
source.
I think the test failing in my case is not listed in your notes about known
failures?(used mvn clean install -e -X)
Results :
Tests in error:
GetContentInfoFunctionalTest.testGetContentInfo:72 »
[ X ] +1 Release these artifacts
Build passing with `mvn clean test install site` on
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)Maven home: /opt/apache-maven-3.5.4Java version:
1.8.0_191, vendor: Oracle Corporation, runtime:
+1 Gary. Will make sure to review and vote on the RC as soon as I see it
coming. Or if I don't vote within the 72hours, feel free to remind me and I
will quickly do so.
Cheers
On Thursday, 21 March 2019, 10:33:47 am NZDT, Gary Gregory
wrote:
Hi All:
I need the fix for BCEL-315
Indeed. I worked in a bank and in a research company, where in both at least
one department was stuck in an old version for issues with the code base or
environment policies/decisions.
Agree not the best choice, but sometimes developers simply cannot immediately
upgrade jvm.
Some managers may
+1
Good idea. I think it should be fine as there are other breaking changes in
sanselan -> imaging.
We loop over data all time in imaging too, some streams/collectors/etc could
make the code more readable. And later maybe make some of the utility code more
functional to be passed around instead
, Gary Gregory
wrote:
On Tue, Mar 26, 2019 at 2:29 PM Bruno P. Kinoshita wrote:
> +1
>
> Good idea. I think it should be fine as there are other breaking changes
> in sanselan -> imaging.
>
> We loop over data all time in imaging too, some streams/collectors/etc
>
+1
Sent from Yahoo Mail on Android
On Sun, 24 Feb 2019 at 2:16, Gary Gregory wrote: Hi
All:
I plan on updating Commons CSV from Java 7 to 8.
Gary
Hi Alex,
Also found the two implementations similar, but confusing.
- The parameter name inconsistency
+1
- The edge case logic inconsistency
+1
- Change to a stepwise charAt comparison
+1 if the behaviour is kept. Right now some crazy characters like those old
latin letters are supported
Thanks for the heads up Rob! Go for it
On Tuesday, 5 March 2019, 3:00:52 pm NZDT, Gary Gregory
wrote:
Thanks Rob!
Gary
On Mon, Mar 4, 2019 at 8:54 PM Rob Tompkins wrote:
> Hello all,
>
> I’m fiddling around with the release plugin and I’m going to commit some
> files to the [text]
T, Gary Gregory
wrote:
IMO, let's stick with 1.0-alpha1. There is no need to rush the new API and
this will make the code available to all through Maven repos. Hopefully
once the code is more easy to use from builds, we will get more feedback.
Gary
On Sun, Nov 4, 2018 at 12:17 AM Bruno P. Kino
Hi Shashwat,
I am not aware of other development happening similar to what you described.
As you have already some changes, I think you can just prepare a pull request
and create a JIRA if you would like to contribute with this new feature.
Have a look at the CONTRIBUTING.md file for the IO
301 - 400 of 597 matches
Mail list logo