Il dom 12 mag 2019, 23:01 Olivier Lamy ha scritto:
> +1
> definitely agree on that let's make it simple
> simple deploy of one build with java8 and voila.
> it's snapshot and NOT a release... so we do not have to jump on every bugs
> immediately.
>
Yes
+1
Enrico
It will be already a great
Hi,
On 12.05.19 23:03, Sylwester Lachiewicz wrote:
Hi,
We have fix for MNG-6626 NullPointerException in DefaultExceptionHandler
https://issues.apache.org/jira/browse/MNG-6626
PR: https://github.com/apache/maven/pull/241
commit:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=36630f6a
Hi,
We have fix for MNG-6069 Migrate to non deprecated parts of Commons CLI -
2nd attempt
https://issues.apache.org/jira/browse/MNG-6069
PR: https://github.com/apache/maven/pull/247
commit:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=b01f861729214e45a1f3754ed5456bcdc1c3b4fc
CI build:
Am 2019-05-12 um 23:03 schrieb Sylwester Lachiewicz:
Hi,
We have fix for MNG-6626 NullPointerException in DefaultExceptionHandler
https://issues.apache.org/jira/browse/MNG-6626
PR: https://github.com/apache/maven/pull/241
commit:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=36630f6
Hi,
We have fix for MNG-6626 NullPointerException in DefaultExceptionHandler
https://issues.apache.org/jira/browse/MNG-6626
PR: https://github.com/apache/maven/pull/241
commit:
https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=36630f6a3d0ac885061cae9d4ebb8c92496e4c0f
CI build:
https://bui
+1
definitely agree on that let's make it simple
simple deploy of one build with java8 and voila.
it's snapshot and NOT a release... so we do not have to jump on every bugs
immediately.
It will be already a great forward to have quick feedback from maven
consumers
On Mon, 13 May 2019 at
IMO, if some patch managed to get to master, it's worth being released,
even if IT test fail.
So I would make the first step being a `mvn deploy` of what[s in master,
before running other tests.
I think this would be much simpler, allow community to test some "master"
snapshot even if it's bugged (
Hi,
The vote has passed with the following result:
+1 : Eric Lilja, Robert Scholte, Olivier Lamy, Hervé Boutemy, Tibor
Digana, Anders Hammar, Karl Heinz Marbaise
PMC quorum: reached.
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
--
Hello!
The Jenkins library revision can be specified in the Jenkinsfile. For exemple,
we can use a specific version of ‘my-shared-library’ with tag 1.0 by putting
the following line at the beginning of the Jenkinsfile:
@Library('my-shared-library@1.0') _
Regards,
Amine TAYEB CHERIF
Le 12
