Hi Tamas, we are too fast ;-)
I think we have to cancel the Vote. Please check the GitHub issues, I will
post there. Thx.
On Fri, Nov 2, 2018 at 5:15 PM Tamás Cservenák wrote:
> +1 (binding) works OK on system/openjdk that initially made me report
> SUREFIRE-1588 in the first place.
>
> On Fri,
+1 (binding) works OK on system/openjdk that initially made me report
SUREFIRE-1588 in the first place.
On Fri, Nov 2, 2018 at 5:00 PM Tibor Digana wrote:
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12342871
>
> There are still a
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927=12342871
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
Staging repo:
Cool, just start creating these Jira issues.
The one you've mentioned is probably already covered by MNG-6444[1].
Depending on the set of changes, we can add related issues or just add
them here.
thanks,
Robert
[1] https://issues.apache.org/jira/browse/MNG-6444
On Fri, 02 Nov 2018
Hi Robert,
I'm Alex Porcelli and I work with Max. I can also create some jiras
about things that we couldn't do.
Here's an example (likely my first JIRA):
In our use case, all sources are stored in bare Git repositories and
we manipulate it using NIO2 API [1], if Maven accepted NIO2 Path
Can we add sub-version JDK 1.8.0_192 or JDK 1.8.0_192 to
maven-jenkins-env [1]? Is this JDK already installed on Jenkins by
Infra team?
Latest version should be independent of subversion, but I mean a new
label named "JDK 1.8 (181)" with concrete subversion.
We can introduce an integration test
On Wed, 08 Aug 2018 09:49:17 +0200, Massimiliano Dessì
wrote:
Hi Robert
2018-08-07 18:35 GMT+02:00 Robert Scholte :
Hi Max,
regarding the contribution, I would like to propose the following:
- At least create a JIRA issue for every feature.
Can we start creating these JIRA issues? I'd
