AW: [VOTE] Increase minimum Java version for Ivy to Java7

2017-05-22 Thread jhm 
> Should we start talking about using HTTP/2? Then we're firmly in Java 8
> territory :-)

While having HTTP/2 support would be a cool thing, I think we should make small 
steps, and one after the other.
So increase minimum Java version from 1.5 to 1.7, apply some changes, make a 
release.
Then we could think about moving to Java8, maybe preparing for Java9 ...

Jan


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

Buildjob: IvyDE

2017-05-22 Thread Jan Matèrne 
I copied the IvyDE buildjob to have github support here.

https://builds.apache.org/view/A/view/Ant/job/IvyDE-GithubPR/

 

I changed IvyDE and IvyDE to not use "Ant latest" instead "Ant 1.9.9", so it
will work on Java<8.

 

I started IvyDE and it gives me an error I could not interpret:

https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console

 

compute-ivy-bundle-version:
[mkdir] Created dir:
/home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/jar
  [get] Getting:

https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifac
t/jars/ivy.jar
  [get] To: /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar
  [get] Error getting

https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifac
t/jars/ivy.jar to
/home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar

 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:561: The following
error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:277:
javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate
DH keypair
at
com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1747)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1708)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.jav
a:1691)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1222)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1199)
at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Abstra
ctDelegateHttpsURLConnection.java:166)
at
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnection
Impl.java:133)
at
org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:737)
at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:650)
at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:640)
Caused by: java.lang.RuntimeException: Could not generate DH keypair
at com.sun.net.ssl.internal.ssl.DHCrypt.(DHCrypt.java:114)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverKeyExchange(ClientHandsh
aker.java:559)
at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshake
r.java:186)
at
com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:943
)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocket
Impl.java:1188)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1215)
... 7 more
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must
be multiple of 64, and can only range from 512 to 1024 (inclusive)
at
com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA13*..)
at
java.security.KeyPairGenerator$Delegate.initialize(KeyPairGenerator.java:627
)
at com.sun.net.ssl.internal.ssl.DHCrypt.(DHCrypt.java:107)
... 14 more

 

 

Jan

[GitHub] ant-ivy issue #20: Fix IVY-1522

2017-05-22 Thread jaikiran 
Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivy/pull/20
  
I've now updated this PR to not focus on the usage of `:` in versions and 
instead test the FileUtil's method itself. 


---
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...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - Buildjobs/PreCommit

2017-05-22 Thread J Pai 
It looks like there might be some issue with the matrix job(s) 
https://builds.apache.org/job/Ivy-GithubPR-Matrix/2/console

From what I understand of that log, it seems like the parent matrix job (the 
one above) is correctly checking out the commit from the submitted PR:

 > Checking out Revision c1765c71ba4394597409de790bf4529ff97e866e (master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c1765c71ba4394597409de790bf4529ff97e866e
 > git rev-parse origin/master^{commit} # timeout=10
 > git rev-list 239bc0b04a95d6c0f82e59c513de36d68c033c6a # timeout=10

However, it then hands off the job execution to individual Windows/Linux jobs 
and those jobs 
https://builds.apache.org/job/Ivy-GithubPR-Matrix/jdk=JDK%201.7%20(latest),os=ubuntu/2/console
 don’t seem to be able to checkout the commit(s) from the PR and fail with 
error like:

> Fetching upstream changes from https://github.com/apache/ant-ivy/

 > git --version # timeout=10
 > git fetch --tags --progress 
https://github.com/apache/ant-ivy/
 +refs/heads/*:refs/remotes/origin/*
Checking out Revision c1765c71ba4394597409de790bf4529ff97e866e (master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c1765c71ba4394597409de790bf4529ff97e866e
FATAL: Could not checkout c1765c71ba4394597409de790bf4529ff97e866e

hudson.plugins.git.GitException
: Command "git checkout -f c1765c71ba4394597409de790bf4529ff97e866e" returned 
status code 128:
stdout: 
stderr: fatal: reference is not a tree: c1765c71ba4394597409de790bf4529ff97e866e

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1866)


-Jaikiran

On 22-May-2017, at 12:25 PM, Jan Matèrne (jhm)  wrote:

>> On a related note, while we are at this - does Apache infra allow the
> jobs to be run against Windows OS Jenkins agents as well? There are a
> few issues specifically reported against Windows OS and having the job
> run against linux and Windows OS should give a decent coverage for the
> upstream code.
> 
> In Jenkins there is the concept of « Matrix » job.
> Here is the ones for Ant:
> https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-
> Windows/  Matrix-1.9.x-Windows/>
> https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-
> Linux/  1.9.x-Linux/>
> AFAIR, it used to be able to do on several different OS. I don’t know
> why they are split.
> 
> And I don’t know if it is possible to do it while pulling a PR from
> github.


New buildjob "Ivy-GithubPR-Matrix". I deactivated the old (so we could easily 
switch back).
https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR-Matrix/
Basically a copy of the old job:
* discard old build jobs (keep 10)
* git merge support: fail the build if push fails
* github project: git://github.com/apache/ant-ivy.git
* git
 -- repository: git://github.com/apache/ant-ivy.git
 -- branches: */master (= default)
 -- clean before checkout
 -- recursively update submodules
 -- build commits submitted for validated merge (= PR support)
* start build: build pull request to the repository (= PR support)
* configuration matrix
 -- JDK: JDK 1.7 (latest), JDK 1.8 (latest), JDK 9 b156 with jigsaw
 -- os: label expression = ["ubuntu", "Windows"]
* abort the build if it's stuck: absolute 20 minutes
* Lock: Ant
* build
 -- ant(standard): clean coverage-report
* publish junit: build/test-report/**


Jan


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



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

Re: Buildjob: IvyDE

2017-05-22 Thread J Pai 
That specific line in the build.xml[1] of the IvyDE project is trying to “get” 
the ivy.jar from a URL. In this case, it’s trying to fetch it from:

> [get] Getting: 
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifact/jars/ivy.jar

Since it’s https backed, there’s a SSL handshake going on via this build 
process which is running on JRE 6 (upgrading to JRE 7 won’t solve the issue) 
and the builds.apache.org system while retrieving the file. It looks like as 
noted here [2] that builds.apache.org is presenting a certificate which JRE 
versions before JRE 8 don’t allow. The workaround presented in that FAQ is to 
switch the settings on the “server” which in this case would be 
builds.apache.org to use a different cipher list.

I’m not sure, if we will be allowed to do that and I’m curious how other builds 
(not necessary Ivy project builds) that need to fetch something from 
builds.apache.org via https and JRE <=7 get past this currently. Either way, I 
think this is something that we will have to ask the Apache infra team for 
their inputs.


[1] https://github.com/apache/ant-ivyde/blob/master/build.xml#L277
[2] http://httpd.apache.org/docs/current/ssl/ssl_faq.html#javadh


-Jaikiran
On 22-May-2017, at 2:04 PM, Jan Matèrne  wrote:

I copied the IvyDE buildjob to have github support here.

https://builds.apache.org/view/A/view/Ant/job/IvyDE-GithubPR/



I changed IvyDE and IvyDE to not use "Ant latest" instead "Ant 1.9.9", so it
will work on Java<8.



I started IvyDE and it gives me an error I could not interpret:

https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console



compute-ivy-bundle-version:
   [mkdir] Created dir:
/home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/jar
 [get] Getting:

https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifac
t/jars/ivy.jar
 [get] To: /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar
 [get] Error getting

https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifac
t/jars/ivy.jar to
/home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar



BUILD FAILED
/home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:561: The following
error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:277:
javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate
DH keypair
   at
com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1747)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1708)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.jav
a:1691)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1222)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1199)
   at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
   at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Abstra
ctDelegateHttpsURLConnection.java:166)
   at
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnection
Impl.java:133)
   at
org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:737)
   at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:650)
   at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:640)
Caused by: java.lang.RuntimeException: Could not generate DH keypair
   at com.sun.net.ssl.internal.ssl.DHCrypt.(DHCrypt.java:114)
   at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverKeyExchange(ClientHandsh
aker.java:559)
   at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshake
r.java:186)
   at
com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
   at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:943
)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocket
Impl.java:1188)
   at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1215)
   ... 7 more
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must
be multiple of 64, and can only range from 512 to 1024 (inclusive)
   at
com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA13*..)
   at
java.security.KeyPairGenerator$Delegate.initialize(KeyPairGenerator.java:627
)
   at com.sun.net.ssl.internal.ssl.DHCrypt.(DHCrypt.java:107)
   ... 14 more





Jan



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For ad

Re: Buildjob: IvyDE

2017-05-22 Thread J Pai 
Is there a chance you could trigger this build to run using Java 7? I read up a 
few JIRA posts for the INFRA project in issues.apache.org and they seem to 
indicate that this probably will work fine with builds that use Java 7. I’m not 
100% sure though.

-Jaikiran
On 22-May-2017, at 6:30 PM, J Pai  wrote:

That specific line in the build.xml[1] of the IvyDE project is trying to “get” 
the ivy.jar from a URL. In this case, it’s trying to fetch it from:

> [get] Getting: 
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifact/jars/ivy.jar

Since it’s https backed, there’s a SSL handshake going on via this build 
process which is running on JRE 6 (upgrading to JRE 7 won’t solve the issue) 
and the builds.apache.org system while retrieving the file. It looks like as 
noted here [2] that builds.apache.org is presenting a certificate which JRE 
versions before JRE 8 don’t allow. The workaround presented in that FAQ is to 
switch the settings on the “server” which in this case would be 
builds.apache.org to use a different cipher list.

I’m not sure, if we will be allowed to do that and I’m curious how other builds 
(not necessary Ivy project builds) that need to fetch something from 
builds.apache.org via https and JRE <=7 get past this currently. Either way, I 
think this is something that we will have to ask the Apache infra team for 
their inputs.


[1] https://github.com/apache/ant-ivyde/blob/master/build.xml#L277
[2] http://httpd.apache.org/docs/current/ssl/ssl_faq.html#javadh


-Jaikiran
On 22-May-2017, at 2:04 PM, Jan Matèrne  wrote:

I copied the IvyDE buildjob to have github support here.

https://builds.apache.org/view/A/view/Ant/job/IvyDE-GithubPR/



I changed IvyDE and IvyDE to not use "Ant latest" instead "Ant 1.9.9", so it
will work on Java<8.



I started IvyDE and it gives me an error I could not interpret:

https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console



compute-ivy-bundle-version:
  [mkdir] Created dir:
/home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/jar
[get] Getting:

https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifac
t/jars/ivy.jar
[get] To: /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar
[get] Error getting

https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/artifac
t/jars/ivy.jar to
/home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar



BUILD FAILED
/home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:561: The following
error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:277:
javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate
DH keypair
  at
com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1747)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1708)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.jav
a:1691)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1222)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1199)
  at
sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
  at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Abstra
ctDelegateHttpsURLConnection.java:166)
  at
sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnection
Impl.java:133)
  at
org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:737)
  at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:650)
  at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:640)
Caused by: java.lang.RuntimeException: Could not generate DH keypair
  at com.sun.net.ssl.internal.ssl.DHCrypt.(DHCrypt.java:114)
  at
com.sun.net.ssl.internal.ssl.ClientHandshaker.serverKeyExchange(ClientHandsh
aker.java:559)
  at
com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshake
r.java:186)
  at
com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
  at
com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:943
)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocket
Impl.java:1188)
  at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java
:1215)
  ... 7 more
Caused by: java.security.InvalidAlgorithmParameterException: Prime size must
be multiple of 64, and can only range from 512 to 1024 (inclusive)
  at
com.sun.crypto.provider.DHKeyPairGenerator.initialize(DashoA13*..)
  at
java.security.KeyPairGen

Re: [VOTE] Increase minimum Java version for Ivy to Java7

2017-05-22 Thread Matt Sicker 
Isn't HTTP 2.0 only in Java 9? Otherwise you need a 3rd party library that
implements the protocol support.

On 22 May 2017 at 02:00, Jan Matèrne (jhm)  wrote:

> > Should we start talking about using HTTP/2? Then we're firmly in Java 8
> > territory :-)
>
> While having HTTP/2 support would be a cool thing, I think we should make
> small steps, and one after the other.
> So increase minimum Java version from 1.5 to 1.7, apply some changes, make
> a release.
> Then we could think about moving to Java8, maybe preparing for Java9 ...
>
> Jan
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>


-- 
Matt Sicker

AW: Buildjob: IvyDE

2017-05-22 Thread jhm 
I changed the buildjobs for IvyDE + IvyDE-Github to use Java7(latest).
But I prefer to use the lowest Java version we have defined as minimum. ;)

Jan

> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 22. Mai 2017 15:09
> An: Ant Developers List
> Betreff: Re: Buildjob: IvyDE
> 
> Is there a chance you could trigger this build to run using Java 7? I
> read up a few JIRA posts for the INFRA project in issues.apache.org and
> they seem to indicate that this probably will work fine with builds
> that use Java 7. I’m not 100% sure though.
> 
> -Jaikiran
> On 22-May-2017, at 6:30 PM, J Pai  wrote:
> 
> That specific line in the build.xml[1] of the IvyDE project is trying
> to “get” the ivy.jar from a URL. In this case, it’s trying to fetch it
> from:
> 
> > [get] Getting:
> >
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/a
> > rtifact/jars/ivy.jar
> 
> Since it’s https backed, there’s a SSL handshake going on via this
> build process which is running on JRE 6 (upgrading to JRE 7 won’t solve
> the issue) and the builds.apache.org system while retrieving the file.
> It looks like as noted here [2] that builds.apache.org is presenting a
> certificate which JRE versions before JRE 8 don’t allow. The workaround
> presented in that FAQ is to switch the settings on the “server” which
> in this case would be builds.apache.org to use a different cipher list.
> 
> I’m not sure, if we will be allowed to do that and I’m curious how
> other builds (not necessary Ivy project builds) that need to fetch
> something from builds.apache.org via https and JRE <=7 get past this
> currently. Either way, I think this is something that we will have to
> ask the Apache infra team for their inputs.
> 
> 
> [1] https://github.com/apache/ant-ivyde/blob/master/build.xml#L277
> [2] http://httpd.apache.org/docs/current/ssl/ssl_faq.html#javadh
> 
> 
> -Jaikiran
> On 22-May-2017, at 2:04 PM, Jan Matèrne  wrote:
> 
> I copied the IvyDE buildjob to have github support here.
> 
> https://builds.apache.org/view/A/view/Ant/job/IvyDE-GithubPR/
> 
> 
> 
> I changed IvyDE and IvyDE to not use "Ant latest" instead "Ant 1.9.9",
> so it will work on Java<8.
> 
> 
> 
> I started IvyDE and it gives me an error I could not interpret:
> 
> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
> 
> 
> 
> compute-ivy-bundle-version:
>   [mkdir] Created dir:
> /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/jar
> [get] Getting:
>  rtifa
> ct/jars/ivy.jar>
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/ar
> tifac
> t/jars/ivy.jar
> [get] To: /home/jenkins/jenkins-
> slave/workspace/IvyDE/work/ivy/ivy.jar
> [get] Error getting
>  rtifa
> ct/jars/ivy.jar>
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/ar
> tifac
> t/jars/ivy.jar to
> /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar
> 
> 
> 
> BUILD FAILED
> /home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:561: The
> following error occurred while executing this line:
> /home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:277:
> javax.net.ssl.SSLException: java.lang.RuntimeException: Could not
> generate DH keypair
>   at
> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
>   at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:174
> 7)
>   at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:170
> 8)
>   at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImp
> l.jav
> a:1691)
>   at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl
> .java
> :1222)
>   at
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl
> .java
> :1199)
>   at
> sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:43
> 4)
>   at
> sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(A
> bstra
> ctDelegateHttpsURLConnection.java:166)
>   at
> sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConne
> ction
> Impl.java:133)
>   at
> org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:737
> )
>   at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:650)
>   at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:640)
> Caused by: java.lang.RuntimeException: Could not generate DH keypair
>   at com.sun.net.ssl.internal.ssl.DHCrypt.(DHCrypt.java:114)
>   at
> com.sun.net.ssl.internal.ssl.ClientHandshaker.serverKeyExchange(ClientH
> andsh
> aker.java:559)
>   at
> com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHand
> shake
> r.java:186)
>   at
> com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593
> )
>   at
> com.sun.net.ssl.in

Re: Buildjob: IvyDE

2017-05-22 Thread Gintautas Grigelionis 
Admins have all rights to stay insist on closing as many CVSS 10 score
holes in JRE as possible ;)

Gintas

2017-05-22 21:24 GMT+02:00 Jan Matèrne (jhm) :

> I changed the buildjobs for IvyDE + IvyDE-Github to use Java7(latest).
> But I prefer to use the lowest Java version we have defined as minimum. ;)
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: J Pai [mailto:jai.forums2...@gmail.com]
> > Gesendet: Montag, 22. Mai 2017 15:09
> > An: Ant Developers List
> > Betreff: Re: Buildjob: IvyDE
> >
> > Is there a chance you could trigger this build to run using Java 7? I
> > read up a few JIRA posts for the INFRA project in issues.apache.org and
> > they seem to indicate that this probably will work fine with builds
> > that use Java 7. I’m not 100% sure though.
> >
> > -Jaikiran
> > On 22-May-2017, at 6:30 PM, J Pai  wrote:
> >
> > That specific line in the build.xml[1] of the IvyDE project is trying
> > to “get” the ivy.jar from a URL. In this case, it’s trying to fetch it
> > from:
> >
> > > [get] Getting:
> > >
> > https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/a
> > > rtifact/jars/ivy.jar
> >
> > Since it’s https backed, there’s a SSL handshake going on via this
> > build process which is running on JRE 6 (upgrading to JRE 7 won’t solve
> > the issue) and the builds.apache.org system while retrieving the file.
> > It looks like as noted here [2] that builds.apache.org is presenting a
> > certificate which JRE versions before JRE 8 don’t allow. The workaround
> > presented in that FAQ is to switch the settings on the “server” which
> > in this case would be builds.apache.org to use a different cipher list.
> >
> > I’m not sure, if we will be allowed to do that and I’m curious how
> > other builds (not necessary Ivy project builds) that need to fetch
> > something from builds.apache.org via https and JRE <=7 get past this
> > currently. Either way, I think this is something that we will have to
> > ask the Apache infra team for their inputs.
> >
> >
> > [1] https://github.com/apache/ant-ivyde/blob/master/build.xml#L277
> > [2] http://httpd.apache.org/docs/current/ssl/ssl_faq.html#javadh
> >
> >
> > -Jaikiran
> > On 22-May-2017, at 2:04 PM, Jan Matèrne  wrote:
> >
> > I copied the IvyDE buildjob to have github support here.
> >
> > https://builds.apache.org/view/A/view/Ant/job/IvyDE-GithubPR/
> >
> >
> >
> > I changed IvyDE and IvyDE to not use "Ant latest" instead "Ant 1.9.9",
> > so it will work on Java<8.
> >
> >
> >
> > I started IvyDE and it gives me an error I could not interpret:
> >
> > https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/console
> >
> >
> >
> > compute-ivy-bundle-version:
> >   [mkdir] Created dir:
> > /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/jar
> > [get] Getting:
> >  > rtifa
> > ct/jars/ivy.jar>
> > https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/ar
> > tifac
> > t/jars/ivy.jar
> > [get] To: /home/jenkins/jenkins-
> > slave/workspace/IvyDE/work/ivy/ivy.jar
> > [get] Error getting
> >  > rtifa
> > ct/jars/ivy.jar>
> > https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/ar
> > tifac
> > t/jars/ivy.jar to
> > /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar
> >
> >
> >
> > BUILD FAILED
> > /home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:561: The
> > following error occurred while executing this line:
> > /home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:277:
> > javax.net.ssl.SSLException: java.lang.RuntimeException: Could not
> > generate DH keypair
> >   at
> > com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
> >   at
> > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:174
> > 7)
> >   at
> > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:170
> > 8)
> >   at
> > com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImp
> > l.jav
> > a:1691)
> >   at
> > com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl
> > .java
> > :1222)
> >   at
> > com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl
> > .java
> > :1199)
> >   at
> > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:43
> > 4)
> >   at
> > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(A
> > bstra
> > ctDelegateHttpsURLConnection.java:166)
> >   at
> > sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConne
> > ction
> > Impl.java:133)
> >   at
> > org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:737
> > )
> >   at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:650)
> >   at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:640)
> > Caused by: java.lang.RuntimeException: Could not generate DH keypair
> >

Re: [VOTE] Increase minimum Java version for Ivy to Java7

2017-05-22 Thread Gintautas Grigelionis 
You're right, full HTTP/2 in JRE is Java 9. What I meant was AEAD crypto
that was introduced in Java 8 JRE. Before that, that's another dependency
on BouncyCastle.

Gintas

2017-05-22 17:42 GMT+02:00 Matt Sicker :

> Isn't HTTP 2.0 only in Java 9? Otherwise you need a 3rd party library that
> implements the protocol support.
>
> On 22 May 2017 at 02:00, Jan Matèrne (jhm)  wrote:
>
> > > Should we start talking about using HTTP/2? Then we're firmly in Java 8
> > > territory :-)
> >
> > While having HTTP/2 support would be a cool thing, I think we should make
> > small steps, and one after the other.
> > So increase minimum Java version from 1.5 to 1.7, apply some changes,
> make
> > a release.
> > Then we could think about moving to Java8, maybe preparing for Java9 ...
> >
> > Jan
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> > For additional commands, e-mail: dev-h...@ant.apache.org
> >
> >
>
>
> --
> Matt Sicker 
>