Re: New Branch (report real sys props of forked JVM) SUREFIRE-1360

2017-06-17 Thread Tibor Digana 
I have fixed https://issues.apache.org/jira/browse/SUREFIRE-1302 in branch
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=b9034a3bbb32a27a2d7b66e4d516c2dac61fce29
Tested and made debugging. Forked VM is killed immediately.

On Wed, Apr 26, 2017 at 3:38 AM, Tibor Digana 
wrote:

> If we do not have time for this, can I proceed with pushing both branches
> SUREFIRE-1364 and SUREFIRE-1366?
>
> On Sun, Apr 23, 2017 at 9:50 PM, Tibor Digana  > wrote:
>
>> @Michael,
>>
>> I had to override branch SUREFIRE-1366 because of some old code and
>> generated code had windows ending lines. Usually the branch changes  to
>>  and  to  which is best to see in GitHub view:
>> https://github.com/apache/maven-surefire/commit/5745ba135522
>> dfe2307d67b4cf84a562fe240ac4
>> Sometimes a code was optimized because was reported that if statements
>> could be written in one line, some #equals(Object), and sometimes ignored
>> Javadoc on the top of class with @SuppressWarnings( { "javadoc", "
>> checkstyle:javadoctype" } ), POM's compiler has -Xdoclint:all, enforcer
>> has rule with jdk 1.8, and @see links in Javadoc with external links to
>> Jira, sometimes changed ">" to .
>>
>> On Sun, Apr 23, 2017 at 10:42 AM, Tibor Digana <
>> tibor.dig...@googlemail.com> wrote:
>>
>>> Hi Michael,
>>>
>>> No problem.
>>> I am glad that somebody helps me like you do.
>>>
>>> On Sun, Apr 23, 2017 at 10:36 AM, Michael Osipov 
>>> wrote:
>>>
 Am 2017-04-22 um 11:31 schrieb Tibor Digana:

> Hi,
>
> I would like to push SUREFIRE-1364 and then fix jira issue
> SUREFIRE-1360
> which should help the users to speed up testing on cloud.
> Can we proceed?
>
>
 I will need a day or two to check the branch. Please wait...

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


>>>
>>>
>>> --
>>> Cheers
>>> Tibor
>>>
>>
>>
>>
>> --
>> Cheers
>> Tibor
>>
>
>

[ANN] Apache Maven Shared Component: Maven Shared Utils Version 3.2.0 Released

2017-06-17 Thread Karl Heinz Marbaise 
The Apache Maven team is pleased to announce the release of the 
Apache Maven Shared Component: Maven Shared Utils Version 3.2.0
 
https://maven.apache.org/shared/maven-shared-utils/

You should specify the version in your project:
 

  org.apache.maven.shared
  maven-shared-utils
  3.2.0


You can download the appropriate sources etc. from the download page:
 
https://maven.apache.org/shared/maven-shared-utils/download.cgi
 
Release Notes Maven Shared Utils 3.2.0

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12338026

Bugs:

 * [MSHARED-574] - UT failure on Windows: utils.io.Java7SupportTest 
createAndReadSymlink
 * [MSHARED-610] - PrettyPrintXMLWriter internally uses java.io.PrintWriter 
without checking for any errors.
 * [MSHARED-617] - StreamFeeder should flush OutputStream
 * [MSHARED-618] - CommandLineCallable does not always call the 
'runAfterProcessTermination' runnable.
 * [MSHARED-619] - StreamFeeder silently ignores exceptions.
 * [MSHARED-622] - CommandLineCallable silently ignores exceptions thrown from 
the stdin processor (StreemFeeder).
 * [MSHARED-630] - Javadoc of several classes still references Maven 3.4.0 for 
color support

Improvements:

 * [MSHARED-587] - remove logger level API from MessageBuilder
 * [MSHARED-620] - CommandLineCallable should defer starting threads until 
called.
 * [MSHARED-621] - CommandLineCallable should calculate process timeouts using 
'System.nanoTime' instead of 'System.currentTimeMillis'.
 * [MSHARED-639] - Removed prerequisites cause it is not a plugin

Task:

 * [MSHARED-623] - Deprecation of methods 'close' and 'flush' of class 
'StreamPumper'.

Enjos,
 
-The Apache Maven team

Karl Heinz Marbaise

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

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

2017-06-17 Thread Robert Scholte 

+1, fully agree with Guillaume

There's no real need to make a plugin modular: it won't become a  
dependency and the dependency management as done by Maven is strong enough  
to have a stable plugin (i.e no need to add requires-statements).


In case of experiment if you want to add a module name,  
"org.apache.maven.plugins.site" would be my choice as well.


Robert

On Sat, 17 Jun 2017 16:31:14 +0200, Guillaume Boué   
wrote:



Hi,

There was a link to Stephen Colebourne's blog about naming modules:  
http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html. So what  
about "org.apache.maven.plugins.site" for the module name?


But I don't think it is necessary to make the plugin modular. The error  
means that code launched by the Site plugin is trying to access the  
private "File(String,File)" constructor. Can you turn on stacktraces to  
see what part of the code is doing that? We can perhaps fix the deep  
reflection usage and only rely on public API.


I've also noticed MSITE-789 about a similar error but it was in Findbugs  
code.


Guillaume

Le 17/06/2017 à 15:54, Karl Heinz Marbaise a écrit :

Hi,
currently I'm a bit on testing JDK 9 EA+174..and found the following  
issue:


[INFO]
[INFO] <<< maven-plugin-plugin:3.4:report < process-classes @  
maven-install-plugin <<<

[INFO]
[INFO] 'process-classes' forked phase execution for  
maven-plugin-plugin:report report preparation done
[INFO] configuring report plugin  
org.apache.maven.plugins:maven-invoker-plugin:2.0.0
[INFO]  


[INFO] BUILD FAILURE
[INFO]  


[INFO] Total time: 14.810 s
[INFO] Finished at: 2017-06-17T15:47:38+02:00
[INFO] Final Memory: 57M/256M
[INFO]  

[ERROR] Failed to execute goal  
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on  
project maven-install-plugin: Execution default-site of goal  
org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to  
make private java.io.File(java.lang.String,java.io.File) accessible:  
module java.base does not "opens java.io" to unnamed module @44b002c9  
-> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with  
the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

So based on what I understood at the moment is that the  
maven-site-plugin needs to have a module-info.java file


The first thing which came into my mind was how-to name the module?

module org.apache.maven.plugins.maven.site.plugin {
  requires java.io;
  requires java.base;
}

Do we have any kind of general naming convention for the plugins?

Kind regards
Karl Heinz Marbaise

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




---
L'absence de virus dans ce courrier électronique a été vérifiée par le  
logiciel antivirus Avast.

https://www.avast.com/antivirus


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


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

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

2017-06-17 Thread Enrico Olivelli 
Il sab 17 giu 2017, 16:40 Karl Heinz Marbaise  ha
scritto:

> Hi,
>
> If i correctly understand the error message it would help having a
> module-info.java with a proper name and a require clause to say that we
> need access to java.io.File...
> Currently we have a unnamed module which prevents such access...
>

IMHO The java.base module should give you access, but you cannot change it
and your module cannot request access to internals of other modules, that
would break strong encapsulation, this is the great value of jigsaw, most
of the problems nowadays are due to legacy java code which bypasses
encapsulation by using setAccessible.

Enrico

>
>
>
>
> Kind regards
> Karl Heinz Marbaise
> On 17/06/17 16:31, Enrico Olivelli wrote:
> > Karl,
> > I think that the problem is tha code is trying to access internals of
> > java.io.File.
> > No module descriptor can help.
> > I think you should run with -X, get the stacktrace of the exception and
> > then we need to avoid that reflective call.
> > In the meantime you can use the famous big kill switch.
> > Hope that helps
> > I will be happy to check the problem next week and help if possible
> >
> >
> > Enrico
> >
> > Il sab 17 giu 2017, 15:54 Karl Heinz Marbaise  > > ha scritto:
> >
> > Hi,
> > currently I'm a bit on testing JDK 9 EA+174..and found the following
> > issue:
> >
> > [INFO]
> > [INFO] <<< maven-plugin-plugin:3.4:report < process-classes @
> > maven-install-plugin <<<
> > [INFO]
> > [INFO] 'process-classes' forked phase execution for
> > maven-plugin-plugin:report report preparation done
> > [INFO] configuring report plugin
> > org.apache.maven.plugins:maven-invoker-plugin:2.0.0
> > [INFO]
> >
>  
> > [INFO] BUILD FAILURE
> > [INFO]
> >
>  
> > [INFO] Total time: 14.810 s
> > [INFO] Finished at: 2017-06-17T15:47:38+02:00
> > [INFO] Final Memory: 57M/256M
> > [INFO]
> >
>  
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
> > project maven-install-plugin: Execution default-site of goal
> > org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to
> > make private java.io.File(java.lang.String,java.io.File) accessible:
> > module java.base does not "opens java.io " to
> > unnamed module @44b002c9 ->
> > [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> > -e switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> > [ERROR]
> >
> > So based on what I understood at the moment is that the
> > maven-site-plugin needs to have a module-info.java file
> >
> > The first thing which came into my mind was how-to name the module?
> >
> > module org.apache.maven.plugins.maven.site.plugin {
> > requires java.io ;
> > requires java.base;
> > }
> >
> > Do we have any kind of general naming convention for the plugins?
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
>
-- 


-- Enrico Olivelli

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

2017-06-17 Thread Karl Heinz Marbaise 

Hi,

If i correctly understand the error message it would help having a 
module-info.java with a proper name and a require clause to say that we 
need access to java.io.File...

Currently we have a unnamed module which prevents such access...

Kind regards
Karl Heinz Marbaise
On 17/06/17 16:31, Enrico Olivelli wrote:

Karl,
I think that the problem is tha code is trying to access internals of 
java.io.File.

No module descriptor can help.
I think you should run with -X, get the stacktrace of the exception and 
then we need to avoid that reflective call.

In the meantime you can use the famous big kill switch.
Hope that helps
I will be happy to check the problem next week and help if possible


Enrico

Il sab 17 giu 2017, 15:54 Karl Heinz Marbaise > ha scritto:


Hi,
currently I'm a bit on testing JDK 9 EA+174..and found the following
issue:

[INFO]
[INFO] <<< maven-plugin-plugin:3.4:report < process-classes @
maven-install-plugin <<<
[INFO]
[INFO] 'process-classes' forked phase execution for
maven-plugin-plugin:report report preparation done
[INFO] configuring report plugin
org.apache.maven.plugins:maven-invoker-plugin:2.0.0
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 14.810 s
[INFO] Finished at: 2017-06-17T15:47:38+02:00
[INFO] Final Memory: 57M/256M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
project maven-install-plugin: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to
make private java.io.File(java.lang.String,java.io.File) accessible:
module java.base does not "opens java.io " to
unnamed module @44b002c9 ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

So based on what I understood at the moment is that the
maven-site-plugin needs to have a module-info.java file

The first thing which came into my mind was how-to name the module?

module org.apache.maven.plugins.maven.site.plugin {
requires java.io ;
requires java.base;
}

Do we have any kind of general naming convention for the plugins?

Kind regards
Karl Heinz Marbaise



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

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

2017-06-17 Thread Enrico Olivelli 
Karl,
I think that the problem is tha code is trying to access internals of
java.io.File.
No module descriptor can help.
I think you should run with -X, get the stacktrace of the exception and
then we need to avoid that reflective call.
In the meantime you can use the famous big kill switch.
Hope that helps
I will be happy to check the problem next week and help if possible


Enrico

Il sab 17 giu 2017, 15:54 Karl Heinz Marbaise  ha
scritto:

> Hi,
> currently I'm a bit on testing JDK 9 EA+174..and found the following issue:
>
> [INFO]
> [INFO] <<< maven-plugin-plugin:3.4:report < process-classes @
> maven-install-plugin <<<
> [INFO]
> [INFO] 'process-classes' forked phase execution for
> maven-plugin-plugin:report report preparation done
> [INFO] configuring report plugin
> org.apache.maven.plugins:maven-invoker-plugin:2.0.0
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 14.810 s
> [INFO] Finished at: 2017-06-17T15:47:38+02:00
> [INFO] Final Memory: 57M/256M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
> project maven-install-plugin: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to
> make private java.io.File(java.lang.String,java.io.File) accessible:
> module java.base does not "opens java.io" to unnamed module @44b002c9 ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
>
> So based on what I understood at the moment is that the
> maven-site-plugin needs to have a module-info.java file
>
> The first thing which came into my mind was how-to name the module?
>
> module org.apache.maven.plugins.maven.site.plugin {
>requires java.io;
>requires java.base;
> }
>
> Do we have any kind of general naming convention for the plugins?
>
> Kind regards
> Karl Heinz Marbaise
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --


-- Enrico Olivelli

Re: JDK9: Jigsaw Problem with maven-site-plugin 3.6

2017-06-17 Thread Guillaume Boué 

Hi,

There was a link to Stephen Colebourne's blog about naming modules: 
http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html. So what 
about "org.apache.maven.plugins.site" for the module name?


But I don't think it is necessary to make the plugin modular. The error 
means that code launched by the Site plugin is trying to access the 
private "File(String,File)" constructor. Can you turn on stacktraces to 
see what part of the code is doing that? We can perhaps fix the deep 
reflection usage and only rely on public API.


I've also noticed MSITE-789 about a similar error but it was in Findbugs 
code.


Guillaume

Le 17/06/2017 à 15:54, Karl Heinz Marbaise a écrit :

Hi,
currently I'm a bit on testing JDK 9 EA+174..and found the following 
issue:


[INFO]
[INFO] <<< maven-plugin-plugin:3.4:report < process-classes @ 
maven-install-plugin <<<

[INFO]
[INFO] 'process-classes' forked phase execution for 
maven-plugin-plugin:report report preparation done
[INFO] configuring report plugin 
org.apache.maven.plugins:maven-invoker-plugin:2.0.0
[INFO] 


[INFO] BUILD FAILURE
[INFO] 


[INFO] Total time: 14.810 s
[INFO] Finished at: 2017-06-17T15:47:38+02:00
[INFO] Final Memory: 57M/256M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on 
project maven-install-plugin: Execution default-site of goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to 
make private java.io.File(java.lang.String,java.io.File) accessible: 
module java.base does not "opens java.io" to unnamed module @44b002c9 
-> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

So based on what I understood at the moment is that the 
maven-site-plugin needs to have a module-info.java file


The first thing which came into my mind was how-to name the module?

module org.apache.maven.plugins.maven.site.plugin {
  requires java.io;
  requires java.base;
}

Do we have any kind of general naming convention for the plugins?

Kind regards
Karl Heinz Marbaise

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




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus


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

JDK9: Jigsaw Problem with maven-site-plugin 3.6

2017-06-17 Thread Karl Heinz Marbaise 

Hi,
currently I'm a bit on testing JDK 9 EA+174..and found the following issue:

[INFO]
[INFO] <<< maven-plugin-plugin:3.4:report < process-classes @ 
maven-install-plugin <<<

[INFO]
[INFO] 'process-classes' forked phase execution for 
maven-plugin-plugin:report report preparation done
[INFO] configuring report plugin 
org.apache.maven.plugins:maven-invoker-plugin:2.0.0
[INFO] 


[INFO] BUILD FAILURE
[INFO] 


[INFO] Total time: 14.810 s
[INFO] Finished at: 2017-06-17T15:47:38+02:00
[INFO] Final Memory: 57M/256M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on 
project maven-install-plugin: Execution default-site of goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site failed: Unable to 
make private java.io.File(java.lang.String,java.io.File) accessible: 
module java.base does not "opens java.io" to unnamed module @44b002c9 -> 
[Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

So based on what I understood at the moment is that the 
maven-site-plugin needs to have a module-info.java file


The first thing which came into my mind was how-to name the module?

module org.apache.maven.plugins.maven.site.plugin {
  requires java.io;
  requires java.base;
}

Do we have any kind of general naming convention for the plugins?

Kind regards
Karl Heinz Marbaise

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

Re: Closing issues in JIRA

2017-06-17 Thread Karl Heinz Marbaise 

Hi,

created an INFRA Ticket for that issue.

https://issues.apache.org/jira/browse/INFRA-14380

Kind regards
Karl Heinz Marbaise
On 17/06/17 13:21, Karl Heinz Marbaise wrote:

Hi,

I have checked that I'm unable to do that on Maven Assembly plugin but 
on others for example maven-jar-plugin I'm allowed to do so...


Kind regards
Karl Heinz Marbaise

On 17/06/17 13:18, Karl Heinz Marbaise wrote:

Hi,

it looks at the moment that I'm unable to close (closed as duplicate 
etc.) an issue ?


is this a general problem for others as well or only for me?

Any ideas?

Kind regards
Karl Heinz Marbaise



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

Re: Closing issues in JIRA

2017-06-17 Thread Karl Heinz Marbaise 

Hi,

I have checked that I'm unable to do that on Maven Assembly plugin but 
on others for example maven-jar-plugin I'm allowed to do so...


Kind regards
Karl Heinz Marbaise

On 17/06/17 13:18, Karl Heinz Marbaise wrote:

Hi,

it looks at the moment that I'm unable to close (closed as duplicate 
etc.) an issue ?


is this a general problem for others as well or only for me?

Any ideas?

Kind regards
Karl Heinz Marbaise

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




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

Closing issues in JIRA

2017-06-17 Thread Karl Heinz Marbaise 

Hi,

it looks at the moment that I'm unable to close (closed as duplicate 
etc.) an issue ?


is this a general problem for others as well or only for me?

Any ideas?

Kind regards
Karl Heinz Marbaise

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

[RESULT] [VOTE] Release Apache Maven Shared Component: Maven Shared Utils Version 3.2.0

2017-06-17 Thread Karl Heinz Marbaise 

Hi,

The vote has passed with the following result:

+1 : Hervé Boutemy, Olivier Lamy, Karl Heinz Marbaise

PMC quorum: reqched.

I will promote the artifacts to the central repo.

Kind regards
Karl Heinz Marbaise

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