Hi,
sorry I was wrong - problem is with something else.
I run tests on Windows/Java7 and i think current configuration at
www.apache.org allows only the following cipher suites:
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_EC
created MNG-6413: Redesign proxies in Settings
On Mon, 21 May 2018 22:53:13 +0200, Stephen Connolly
wrote:
plus the newer java proxy methods allow for different proxies per host...
and at the very least we need to take into account the non-proxy host
requirements
On 21 May 2018 at 20:49,
plus the newer java proxy methods allow for different proxies per host...
and at the very least we need to take into account the non-proxy host
requirements
On 21 May 2018 at 20:49, Michael Osipov wrote:
> Am 2018-05-21 um 21:30 schrieb Robert Scholte:
>
>> So we need a new method: #getActivePro
Am 2018-05-21 um 21:30 schrieb Robert Scholte:
So we need a new method: #getActiveProxy(String protocol) ?
At least that, better yet one proxy can handle multiple protocols. The
proxy design of Java is 15 years old. Back then it was assumed that
companies have different proxies for HTTP and
So we need a new method: #getActiveProxy(String protocol) ?
On Mon, 21 May 2018 20:02:22 +0200, Michael Osipov
wrote:
Am 2018-05-21 um 19:53 schrieb Mark Raynsford:
On 2018-05-21T19:46:26 +0200
"Robert Scholte" wrote:
Of course :)
This is probably a good example:
https://github.com/ap
On 2018-05-21T20:02:22 +0200
Michael Osipov wrote:
>
> It is pretty good that Robert raised the example with the Javadoc mojo
> because it is broken. Our current approach does not scale and the
> Javadoc Mojo will fail if your activ proxy is for HTTP, but the
> resources are HTTPS and vice vers
Am 2018-05-21 um 19:53 schrieb Mark Raynsford:
On 2018-05-21T19:46:26 +0200
"Robert Scholte" wrote:
Of course :)
This is probably a good example:
https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3582
Hah, tha
On 2018-05-21T19:46:26 +0200
"Robert Scholte" wrote:
> Of course :)
>
> This is probably a good example:
> https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3582
Hah, thanks! That's a pretty direct example!
For f
Of course :)
This is probably a good example:
https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L3582
best,
Robert
On Mon, 21 May 2018 19:04:07 +0200, Mark Raynsford
wrote:
I have a plugin that uses URL.openS
I have a plugin that uses URL.openStream to load external content:
https://github.com/io7m/minisite/blob/develop/com.io7m.minisite.maven_plugin/src/main/java/com/io7m/minisite/maven_plugin/MinSiteMojo.java#L362
It seems that although the Maven instance is configured to use a proxy
in .m2/setti
Makes sense, let's push this to another release.
On Mon, 21 May 2018 15:47:45 +0200, Hervé BOUTEMY
wrote:
sorry to be a little late...
I just commented on the issue: before merging, I'd like to have a
clearer view
on what's the benefit that we loose when we get back from Object
interpol
sorry to be a little late...
I just commented on the issue: before merging, I'd like to have a clearer view
on what's the benefit that we loose when we get back from Object interpolation
to String interpolation
and how changing the port type from int to String, with a hand written getter
for com
+1
On Mon, 21 May 2018 12:22:02 +0200, Michael Osipov
wrote:
Folks,
who seconds MNG-6401 for 3.5.4? Both PRs look fine, branches pushed. All
ITs pass here.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apach
Folks,
who seconds MNG-6401 for 3.5.4? Both PRs look fine, branches pushed. All
ITs pass here.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Here is mine +1
Kind regards
Karl Heinz Marbaise
On 19/05/18 14:54, Karl Heinz Marbaise wrote:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317227&version=12343248
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i
guys, please have a look at the build before extrapolating ideas on what may
fail
as I wrote, the issue is not with central, it's with https://www.apache.org/
I'll copy/paste the exception:
Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could
not find resource 'https:
16 matches
Mail list logo