There used to be Windows Jenkins slaves. I had them configured for Log4j
here: https://builds.apache.org/job/Log4jWindows/
Not sure if they're working properly, but I see 3 nodes:
https://builds.apache.org/label/Windows/
On 26 September 2017 at 17:52, Bruno P. Kinoshita wrote:
Hi Benedikt,
Benedikt Ritter wrote:
[snip]
>> AFAICS we have only commons-logging. The other artifacts have not been
>> part of any release in the last decade.
>
> It looks like those artifacts have been published to maven central under
> commons-logging:commons-logging coordinates [1].
I
Le 26/09/2017 à 23:34, Stephen Colebourne a écrit :
> I would suggest being extra cautious when releasing, as a newer
> version of maven may have changed some of the config, and you don't
> want to release the two extra jars to maven central. (In fact, why not
> just delete their creation in
I wonder if we have some windows jenkins slaves. It would be nice to identify
these regressions earlier.
Bruno
Sent from Yahoo Mail on Android
On Wed, 27 Sep 2017 at 8:16, Gary Gregory wrote:
This test fails on Windows:
org.apache.commons.io.FileUtilsTestCase
This test fails on Windows:
org.apache.commons.io.FileUtilsTestCase
FileUtilsTestCase
org.apache.commons.io.FileUtilsTestCase
testContentEqualsIgnoreEOL(org.apache.commons.io.FileUtilsTestCase)
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at
Great new! Thanks!
Am 26.09.2017 um 22:48 schrieb Benedikt Ritter:
Hey,
I’m going through the list of components I happen to work with and make them
ready for Java 9. Since I’m blocked in the release process of collections
because of the Windows test failures, I’m going to cut a RC for IO
The contents of pom.xml look OK. I can't seem to browse to see if you
changed anything else in that commit.
I would suggest being extra cautious when releasing, as a newer
version of maven may have changed some of the config, and you don't
want to release the two extra jars to maven central. (In
> Am 26.09.2017 um 22:54 schrieb Stephen Colebourne :
>
> On 26 September 2017 at 18:48, Jörg Schaible wrote:
>> AFAICS we have only commons-logging. The other artifacts have not been part
>> of any release in the last decade.
>
> Simple then!
On 26 September 2017 at 18:48, Jörg Schaible wrote:
> AFAICS we have only commons-logging. The other artifacts have not been part
> of any release in the last decade.
Simple then!
Stephen
-
To
Go for it! :-)
Gary
On Tue, Sep 26, 2017 at 2:48 PM, Benedikt Ritter wrote:
> Hey,
>
> I’m going through the list of components I happen to work with and make
> them ready for Java 9. Since I’m blocked in the release process of
> collections because of the Windows test
Hey,
I’m going through the list of components I happen to work with and make them
ready for Java 9. Since I’m blocked in the release process of collections
because of the Windows test failures, I’m going to cut a RC for IO 2.6 probably
tomorrow night.
Regards,
Benedikt
Hello Jörg,
> Am 26.09.2017 um 19:48 schrieb Jörg Schaible :
>
> Hi Stephen,
>
> Stephen Colebourne wrote:
>
>> On 26 September 2017 at 16:06, Benedikt Ritter wrote:
>>> commons-logging.jar
>>> commons-logging-adapters.jar
>>> commons-logging-api.jar
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, the other one
contains some warnings which
On travis-ci there are three unit test failures for the build of the tag:
ZipFileObjectTestCase.testReadingFilesInZipFile
ZipFileObjectTestCase.testReadingOneAfterClosingAnotherFile
ZipFileObjectTestCase.testReadingOneAfterClosingAnotherStream:see:
My +1
Gary
On Sat, Sep 23, 2017 at 10:43 AM, Gary Gregory wrote:
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons VFS 2.1 was released, so I would like to release
> Apache Commons VFS 2.2.
>
> Apache Commons VFS 2.2 RC1 is
Github user ameyjadiye commented on the issue:
https://github.com/apache/commons-text/pull/62
Hi @chtompki , do you see more places to improvement or its good now ?
---
-
To unsubscribe, e-mail:
On Tue, Sep 26, 2017 at 11:48 AM, Jörg Schaible
wrote:
> Hi Stephen,
>
> Stephen Colebourne wrote:
>
> > On 26 September 2017 at 16:06, Benedikt Ritter
> wrote:
> >> commons-logging.jar
> >> commons-logging-adapters.jar
> >> commons-logging-api.jar
>
Hi Stephen,
Stephen Colebourne wrote:
> On 26 September 2017 at 16:06, Benedikt Ritter wrote:
>> commons-logging.jar
>> commons-logging-adapters.jar
>> commons-logging-api.jar
>>
>> All jars have org.apache.commons.logging as root package, so if I
>> understand correctly we
On 26 September 2017 at 16:06, Benedikt Ritter wrote:
> commons-logging.jar
> commons-logging-adapters.jar
> commons-logging-api.jar
>
> All jars have org.apache.commons.logging as root package, so if I understand
> correctly we can’t do the Automatic-Module-Name trick,
Hi again,
> Am 26.09.2017 um 16:54 schrieb Benedikt Ritter :
>
> Hello,
>
> since LOGGING-165 [1] has been raised, I’m planning to add the
> Automatic-Module-Name to logging and get a new release out of the door.
Looks like I was a bit over enthusiastic here… The logging
Hello,
since LOGGING-165 [1] has been raised, I’m planning to add the
Automatic-Module-Name to logging and get a new release out of the door.
Regards,
Benedikt
[1] https://issues.apache.org/jira/browse/LOGGING-165
-
To
Github user asfgit closed the pull request at:
https://github.com/apache/commons-io/pull/44
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Hi,
Jenkins Jobs for Commons Lang started to fail a while ago. The build log said,
that Maven can not be found. I raised and issue yesterday [1]. Solution was to
use Maven (latest) and JDK 1.8.
Cheers,
Benedikt
[1] https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-15167
23 matches
Mail list logo