There is zero tests to run because you have globally specified a "groups"
but there are no tests annotated with such group in your project
hadoop-hdfs.
Try to come over this issue by specifying empty groups in this child.
Let's go back to your three questions.
1. The pluginManagement should be in
Hi,
Recently in our hadoop project, we added maven-surefire-plugin for running
unit tests by categories.
in hadoop root pom.xml:
junit
junit
4.11
:
:
org.apache.hadoop.classification.TestJUnitCategory$AllTests
4.11
org.apache.mave
Hi,
We solved 18 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341563
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCOMPILER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DES
Based on the -1 ..
I cancel the VOTE...
Kind regards
Karl Heinz Marbaise
On 25/07/18 22:18, Karl Heinz Marbaise wrote:
Hi,
We solved 18 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341563
There are still a couple of issues left in JIRA:
https:
Good point about the release number there though. I'd be +1 for 3.8.0 as
well.
On Thu, Jul 26, 2018 at 1:37 PM Robert Scholte
wrote:
> -1, changing the default for source/ target should not be fixed with a
> patch number. Should be 3.8.0.Probably my fault that I didn't update the
> version, but
+1
Thanks,
S.
On Wed, Jul 25, 2018 at 10:18 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 18 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341563
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/
Den tors 26 juli 2018 17:17Anders Hammar skrev:
> -1, I agree with Robert. Looks som docs (and code) also states 1.8.0 for
> this change.
>
Should say 3.8.0 of course.
/A
> /Anders (mobile)
>
> Den tors 26 juli 2018 14:37Robert Scholte
> skrev:
>
>> -1, changing the default for source/ targe
-1, I agree with Robert. Looks som docs (and code) also states 1.8.0 for
this change.
/Anders (mobile)
Den tors 26 juli 2018 14:37Robert Scholte skrev:
> -1, changing the default for source/ target should not be fixed with a
> patch number. Should be 3.8.0.Probably my fault that I didn't update
-1, changing the default for source/ target should not be fixed with a patch
number. Should be 3.8.0.Probably my fault that I didn't update the version,
but I wanted to verify some other small things first.
Will be back on Sunday from (J)Crete,Robert
Verzonden vanaf mijn Samsung Galaxy-smartph
-1, changing the default for source/ target should not be fixed with a patch
number. Should be 3.8.0.Probably my fault that I didn't update the version,
but I wanted to verify some other small things first.
Will be back on Sunday from (J)Crete,Robert
Verzonden vanaf mijn Samsung Galaxy-smartph
Tests ok:
- built from source with Oracle JDK8 and Oracle JDK10 on Fedora 26, all
tests passed.
- Apache RAT ok
Unfortunately I guess I should give a -1 (non-binding) because my GPG
reports that the key used for signing has expired
gpg: assuming signed data in
`maven-compiler-plugin-3.7.1-source-
+1 (non-binding)
Thanks !
regards
François
François Papon
fpa...@apache.org
Le 26/07/2018 à 00:18, Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 18 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341563
>
>
> There are still a couple of issues
12 matches
Mail list logo