Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)

[sebb]

AFAIK most of the Commons jobs use JDK 1.7 latest and the java-1.n
profiles to choose the appropriate compile/test environment.

These should continue to build OK, assuming that Jenkins is able to
find a suitable version of Java if necessary.

Builds which rely on JDK 7 and which don't use a Java profile will
find that the compile/test now use Java 8.

We need predictable builds so we need to ensure that all Maven builds
use the appropriate java profiles for the target JVM.

Once all the builds use the appropriate Java profiles we should be OK
when Jenkins next change the minimum Java version.

-- Forwarded message --
From: Gavin McDonald 
Date: 27 June 2017 at 08:03
Subject: [JENKINS]  [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
To: bui...@apache.org
Cc: ASF Operations 


ASF Jenkins Master Migration and Upgrade on :-


LocationLocal Time
 Time Zone   UTC Offset
Melbourne (Australia - Victoria)Sunday, 16 July 2017 at
10:00:00 am AESTUTC+10 hours
New York (USA - New York)   Saturday, 15 July 2017 at
8:00:00 pmEDT UTC-4 hours
Corresponding UTC (GMT) Sunday, 16 July 2017 at 00:00:00


Hi All,

A few things are going to happen in just over 2 weeks.

1. Migration of Jenkins to a new host. A Jenkins Master module and
yaml have been puppetized and ready to go.
What we need to do to migrate the Master away from its current
host is turn off the old service. Perform a final
rsync of data and perform the migration tasks.

As we intend to preserve history for jobs this will take some time.
At the same time as doing this migration to a new host, all slave
connections will be updated (see below.)
I have no current estimate of downtime, but it will run into
several hours. We do plan to run this migration on a
Sunday at the lowest part of Jenkins usual usage.

2. Upgrade of Jenkins - Jenkins project released a new LTS release,
version 2.60.1. This is a major release and breaks
Jenkins in terms of Maven jobs for JDK 7 in the same way that it
happened for Maven and JDK 6 a few months back.

The infra team (mainly myself) got quite some feedback on not
supplying advance notice of this breakage. That upgrade
however was necessary due to security fixes that required our
upgrade.  This email serves as advance warning of the
upcoming upgrade of Jenkins, the downtime due to the migration of
the service to a new host; and notice of the breakage
to JDK 7 that the upgrade brings.

Please familiarise yourself with the Jenkins LTS upgrade notes at [1].
In particular please note:-

“…2.60.1 is the first Jenkins LTS release that requires Java 8 to
run. If you're using the Maven Project type, please note that it needs
to use a JDK capable of running Jenkins, i.e. JDK 8 or up. If you
configure an older JDK in a Maven Project, Jenkins will attempt to
find a newer JDK and use that automatically. If your SSH Slaves fail
to start and you have the plugin install the JRE to run them, make
sure to update SSH Slaves Plugin to at least version 1.17 (1.20
recommended).
Changes since 2.60:
Fix for NullPointerException while initiating some SSH connections
(regression in 2.59). (issue 44120
)
Notable changes since 2.46.3:
Jenkins (master and agents) now requires Java 8 to run. (issue 27624
 <>, issue 42709
 <>, pull 2802
, announcement blog
post )

…”

There are over 30 other enhancements/fixes since 2.46.2 which we
currently run so please do take a note of those.

Recap: In just over 2 weeks, downtime for a migration AND upgrade is planned.

Please do not rely on Jenkins at all for that weekend if you use it in
your release workflow.

Please do take this notice back to your dev lists.

Any questions or concerns please email back to bui...@apache.org
 only.

Thanks

Gav…

[1] - https://jenkins.io/changelog-stable/

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/commons-cli/pull/15
  

[![Coverage 
Status](https://:/builds/12154396/badge)](https://:/builds/12154396)

Coverage increased (+0.04%) to 96.287% when pulling 
**3d9587caec7dd23d359bc112c63512e2bc3e0702 on rubin55:master** into 
**c246bd419ee0efccd9a96f9d33486617d5d38a56 on apache:master**.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/commons-cli/pull/15
  

[![Coverage 
Status](https://:/builds/12154396/badge)](https://:/builds/12154396)

Coverage increased (+0.04%) to 96.287% when pulling 
**3d9587caec7dd23d359bc112c63512e2bc3e0702 on rubin55:master** into 
**c246bd419ee0efccd9a96f9d33486617d5d38a56 on apache:master**.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Fwd: [text] - using RandomStringGenerator for alpha numeric

[Amey Jadiye]

Hi All,

With below reference user asked whether he can use alpha numeric string ?
 we can do that easily by overloading .withinRange(char[][])
where my vision is to pass multiple pairs of min max characters. so we can
pas {'0','9'} and {'a','z'}, OR any similar alternative where we can pass
pairs of range.

i.e.

RandomStringGenerator generator = new
RandomStringGenerator.Builder()
.withinRange({'0','9'}, {'a','z'}).build();


What do you guys think  ?

Regards,
Amey

-- Forwarded message --
From: Amey Jadiye 
Date: Tue, Jun 27, 2017 at 10:57 PM
Subject: Re: [text] - using RandomStringGenerator for alpha numeric
To: Commons Users List , gregh3...@gmail.com


Hi Greg,

Thanks for writing to us, as range are the codePoints you can use it like
below.

RandomStringGenerator generator = new
RandomStringGenerator.Builder()
.withinRange('0', 'z').build();

However that will include all the numbers, capital letters, small letters
and some special characters. between (48 to 112)

We are including feature in next release so you can give characters you
want to generate random string, but that will be available in Text 1.2
release.

For now as an alternate you can use below code as well passing it array of
a to z and 0 to 9.

Set characters = Stream.of('a', 'b', '1', '2').map(i -> (int)
i).collect(Collectors.toSet());
String str = new RandomStringGenerator.Builder().filteredBy(i ->
characters.contains(i)).build().generate(5);

Let us know if you need more info.

Regards,
Amey

On Tue, Jun 27, 2017 at 8:03 PM, Greg Huber  wrote:

> ​Hello,
>
> How would I use org.apache.commons.text.RandomStringGenerator to replace
> the RandomStringUtils alpha numeric number?
>
> String text = RandomStringUtils.randomAlphanumeric(num);
>
> The docs only show how to use a-z :
>
> RandomStringGenerator generator = new
> RandomStringGenerator.Builder()
> .withinRange('a', 'z').build();
>
> String text = generator.generate(num);
>
> Cheers
>
> ​
>



-- 

-

To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

For additional commands, e-mail: dev-h...@commons.apache.org



-- 

-

To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

For additional commands, e-mail: dev-h...@commons.apache.org

Re: Things in a POM file that are not probably incorrect

[Benedikt Ritter]

Hello Simon,

> Am 27.06.2017 um 00:02 schrieb Simon Spero :
> 
>1.5
>1.5
>org.apache.commons.functor
> 
> JDK 9 cannot generate or parse class files compiled with -target 1.5  [1].
> 
> Per the JPMS Armistice talks,   "Automatic-Module-Name" header should only
> be added to jars that have been tested under JDK 9 [2].
> 
> Also, javac now supports the new "--release" argument as an alternative to
> source + target.
> Roughly speaking, this option combines -source & -target with a little bit
> of animal sniffing.  JDK 9 includes  signatures for JDK 6,7,8, and 9 (i.e.
> all the releases which jdk9 can compile for).
> This option is supported by maven-compiler-plugin [4] via a 
> element in the plugin  configuration, or by settting the property
> *maven.compiler.release* .

Thank you for the heads up! We should definitely try to use the new release 
option once JDK9 is released and our components require at least Java 1.6.

Cheers,
Benedikt

> 
> Simon
> 
> [1] https://bugs.openjdk.java.net/browse/JDK-8011044
> [2]
> http://openjdk.java.net/projects/jigsaw/spec/minutes/2017-05-18#AutomaticModuleNames--ModuleNameInManifest
> [3] http://openjdk.java.net/jeps/247
> [4]
> https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#release


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Things in a POM file that are not probably incorrect

[Rob Tompkins]

> On Jun 27, 2017, at 7:45 PM, Emmanuel Bourg  wrote:
> 
>> Le 27/06/2017 à 00:02, Simon Spero a écrit :
>> 
>> JDK 9 cannot generate or parse class files compiled with -target 1.5  [1].
> 
> AFAIK Java 9 can still parse 1.5 (and lower) class files.

But it does matter what you declare the target to be: 
http://openjdk.java.net/jeps/182

-Rob


> 
> Emmanuel Bourg
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

Git/Github Access

[Carl Hall]

Hi friends,

I'd like to move commons-dbutils to git rather than continuing to deal with
git-svn.  Could someone point me in the right direction for requesting this
or point me to the right person/group to pose my request?

Thanks,
Carl

Re: Things in a POM file that are not probably incorrect

[Emmanuel Bourg]

Le 27/06/2017 à 00:02, Simon Spero a écrit :

> JDK 9 cannot generate or parse class files compiled with -target 1.5  [1].

AFAIK Java 9 can still parse 1.5 (and lower) class files.

Emmanuel Bourg

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org