date:20170908

[jira] [Commented] (MJAVADOC-496) javadoc:fix creates invalid @param tags for "this"

2017-09-08 Thread Chris Hennick (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159755#comment-16159755
 ] 

Chris Hennick commented on MJAVADOC-496:


It does indeed compile on Java 8; in fact, the Checker Framework relies on
it to know when an instance method (at least a non-final one) is safe to
call from the constructor. "this" isn't an actual parameter, just a place
to attach annotations.




> javadoc:fix creates invalid @param tags for "this"
> --
>
> Key: MJAVADOC-496
> URL: https://issues.apache.org/jira/browse/MJAVADOC-496
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.9.1
> Environment: Ubuntu 14.04.3 LTS
>Reporter: Chris Hennick
>
> I'm using the Checker Framework on Java 8, so I sometimes need to write 
> method declarations in a form like
> {code:java}
>   protected void initTransientFields(
>   @UnknownInitialization AesCounterRandom this) {/*...*/}
> {code}
> When I run mvn javadoc:fix on a code base where I'm doing that, the javadocs 
> of such methods gain tags beginning with {code:java}@param this{code}, which 
> raise an error when mvn javadoc:javadoc tries to process them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MPDF-82) Improve the PDF aggregated title page

2017-09-08 Thread Alex O'Ree (JIRA)

Alex O'Ree created MPDF-82:
--

 Summary: Improve the PDF aggregated title page
 Key: MPDF-82
 URL: https://issues.apache.org/jira/browse/MPDF-82
 Project: Maven PDF Plugin
  Issue Type: Improvement
Reporter: Alex O'Ree


The current setup has two logos, top left and top right of about the same size. 
This is probably ok for some cases but not all. Usually, you want to have some 
kind of a company logo or logo(s) on the top, and a project specific logo dead 
center of the page, followed by the remaining usual content. It would also be 
nice to also have the headers/footers optionally applied to the title page and 
TOC



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPDF-81) Override the copyright footer

2017-09-08 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159675#comment-16159675
 ] 

Alex O'Ree commented on MPDF-81:


that issue was resolved, PR opened at 
https://github.com/apache/maven-plugins/pull/129

> Override the copyright footer
> -
>
> Key: MPDF-81
> URL: https://issues.apache.org/jira/browse/MPDF-81
> Project: Maven PDF Plugin
>  Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex O'Ree
>
> As of right now, it doesn't look possible to override the content of the 
> footer which is on all non-title page pages. It currently reads (c) year - 
> organization All rights reserved.
> I don't see anywhere in the code where this is defined or in any of the 
> resource files. It is in the generated fo files but it's not obvious where 
> the xslt is.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPDF-81) Override the copyright footer

2017-09-08 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159674#comment-16159674
 ] 

ASF GitHub Bot commented on MPDF-81:


GitHub user spyhunter99 opened a pull request:

https://github.com/apache/maven-plugins/pull/129

MPDF-81 merging in the needed doxia modules required for copyright ov…

…errides, Add property based overrides for the copyright headers. Most of 
the real changes were in FoAggregatedSink

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/spyhunter99/maven-plugins feature/MPDF-81

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/129.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #129


commit 27c221e8cece7a5b8574a0aeb593efbd02547ccf
Author: Alex O'Ree 
Date:   2017-09-09T02:14:14Z

MPDF-81 merging in the needed doxia modules required for copyright 
overrides, Add property based overrides for the copyright headers. Most of the 
real changes were in FoAggregatedSink




> Override the copyright footer
> -
>
> Key: MPDF-81
> URL: https://issues.apache.org/jira/browse/MPDF-81
> Project: Maven PDF Plugin
>  Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex O'Ree
>
> As of right now, it doesn't look possible to override the content of the 
> footer which is on all non-title page pages. It currently reads (c) year - 
> organization All rights reserved.
> I don't see anywhere in the code where this is defined or in any of the 
> resource files. It is in the generated fo files but it's not obvious where 
> the xslt is.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPDF-81) Override the copyright footer

2017-09-08 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159658#comment-16159658
 ] 

Alex O'Ree commented on MPDF-81:


part of the difficult here is that doxia plays by different check style rules 
than the maven plugins. grrr. is check style really needed?

> Override the copyright footer
> -
>
> Key: MPDF-81
> URL: https://issues.apache.org/jira/browse/MPDF-81
> Project: Maven PDF Plugin
>  Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex O'Ree
>
> As of right now, it doesn't look possible to override the content of the 
> footer which is on all non-title page pages. It currently reads (c) year - 
> organization All rights reserved.
> I don't see anywhere in the code where this is defined or in any of the 
> resource files. It is in the generated fo files but it's not obvious where 
> the xslt is.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MPDF-81) Override the copyright footer

2017-09-08 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MPDF-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159603#comment-16159603
 ] 

Alex O'Ree commented on MPDF-81:


sure thing

> Override the copyright footer
> -
>
> Key: MPDF-81
> URL: https://issues.apache.org/jira/browse/MPDF-81
> Project: Maven PDF Plugin
>  Issue Type: New Feature
>Affects Versions: 1.3
>Reporter: Alex O'Ree
>
> As of right now, it doesn't look possible to override the content of the 
> footer which is on all non-title page pages. It currently reads (c) year - 
> organization All rights reserved.
> I don't see anywhere in the code where this is defined or in any of the 
> resource files. It is in the generated fo files but it's not obvious where 
> the xslt is.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MSHADE-243) Java 8 type-use annotation breaks relocation

2017-09-08 Thread Evgeny Mandrikov (JIRA)


[ 
https://issues.apache.org/jira/browse/MSHADE-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159430#comment-16159430
 ] 

Evgeny Mandrikov commented on MSHADE-243:
-

FWIW the linked issue in ASM has been closed as "invalid", this is actually bug 
in {{javac}} - see https://bugs.openjdk.java.net/browse/JDK-8144185 , there is 
also more recent discussion in ASM - 
http://forge.ow2.org/tracker/?func=detail=100023=317789_id=23

> Java 8 type-use annotation breaks relocation
> 
>
> Key: MSHADE-243
> URL: https://issues.apache.org/jira/browse/MSHADE-243
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4.3
>Reporter: Yegor Borovikov
>  Labels: annotation, asm, java8
> Attachments: mshade-243.zip
>
>
> When relocation tries to examine a class with type-use annotation for 
> remapping it fails in {{org.objectweb.asm.ClassReader.readLabel()}} (in some 
> cases).
> This code can be used to reproduce the issue:
> {code:java}
> import org.jetbrains.annotations.Nullable;
> interface Foo { void foo(V x); }
> class FooImpl implements Foo {
> public void foo(Iterable result) {
> if ("".equals(null)) {
> @Nullable Object o = null;
> o = null; // without a statement here errs at offset 65535 
> instead of 11
> }
> }
> }
> {code}
> Running {{mvn package}} (with {{}} in shade configuration) yields:
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on project 
> asm-bug: Error creating shaded jar: Error in ASM processing class 
> FooImpl.class: 11 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-shade-plugin:2.4.3:shade (default) on 
> project asm-bug: Error creating shaded jar: Error in ASM processing class 
> FooImpl.class
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
>   at 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating 
> shaded jar: Error in ASM processing class FooImpl.class
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:540)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
>   ... 20 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error in ASM 
> processing class FooImpl.class
>   at 
> org.apache.maven.plugins.shade.DefaultShader.addRemappedClass(DefaultShader.java:450)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeSingleJar(DefaultShader.java:219)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shadeJars(DefaultShader.java:179)
>   at 
> org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:104)
>   at 
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:454)
>   ... 22 more
> Caused by:

[jira] [Commented] (SUREFIRE-1331) Bump version number

2017-09-08 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159379#comment-16159379
 ] 

ASF GitHub Bot commented on SUREFIRE-1331:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/141
  
@britter 
I think this was forgotten. Should I process it?


> Bump version number
> ---
>
> Key: SUREFIRE-1331
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1331
> Project: Maven Surefire
>  Issue Type: Task
>Reporter: Benedikt Ritter
> Fix For: 3.0-RC1
>
>
> Currently the version in 3.0-rc1 branch is 2.19.2-SNAPSHOT. We should bump it 
> to 3.0.0-SNAPSHOT.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1391) System Property variables processed twice in calculation of effective properties

2017-09-08 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159367#comment-16159367
 ] 

ASF GitHub Bot commented on SUREFIRE-1391:
--

Github user Tibor17 commented on the issue:

https://github.com/apache/maven-surefire/pull/159
  
@andrew-j-cohen
We do not have rights to close this issue. Please close it!


> System Property variables processed twice in calculation of effective 
> properties
> 
>
> Key: SUREFIRE-1391
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1391
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Reporter: Andrew Cohen
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 2.20.1
>
> Attachments: 
> 0001-SUREFIRE-1391-Eliminate-redundant-call-to-process-sy.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> System property variables are processed twice in the calculation of effective 
> properties. There is obviously no adverse impact on behavior, just 
> unnecessary processing.
> {code:java}
> static SurefireProperties calculateEffectiveProperties( Properties 
> systemProperties,
> Map String> systemPropertyVariables,
> Properties 
> userProperties, SurefireProperties props )
> {
> SurefireProperties result = new SurefireProperties();
> result.copyPropertiesFrom( systemProperties );
> result.copyPropertiesFrom( props );
> copyProperties( result, systemPropertyVariables );
> copyProperties( result, systemPropertyVariables );
> // We used to take all of our system properties and dump them in with 
> the
> // user specified properties for SUREFIRE-121, causing SUREFIRE-491.
> // Not gonna do THAT any more... instead, we only propagate those 
> system properties
> // that have been explicitly specified by the user via -Dkey=value on 
> the CLI
> result.copyPropertiesFrom( userProperties );
> return result;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.

2017-09-08 Thread Tibor Digana (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana closed SUREFIRE-1409.
--
Resolution: Fixed

https://git1-us-west.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=67c06d5876dcabc037de9b5f4cc226beeedcb379

> Parallel runner should not drop away runners that have zero children.
> -
>
> Key: SUREFIRE-1409
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1409
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Junit 4.7+ (parallel) support
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> JUnit does not force runners to include all child tests in Description. 
> Therefore Parallel Runner should not throw such tests away.
> For example Spock does not report parametrized tests.
> [https://github.com/spockframework/spock/pull/558]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.

2017-09-08 Thread Tibor Digana (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana updated SUREFIRE-1409:
---
Fix Version/s: (was: 2.20.2)
   2.20.1

> Parallel runner should not drop away runners that have zero children.
> -
>
> Key: SUREFIRE-1409
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1409
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Junit 4.7+ (parallel) support
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> JUnit does not force runners to include all child tests in Description. 
> Therefore Parallel Runner should not throw such tests away.
> For example Spock does not report parametrized tests.
> [https://github.com/spockframework/spock/pull/558]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

2017-09-08 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159306#comment-16159306
 ] 

Tibor Digana commented on SUREFIRE-1408:


[~aonishuk]
Should I use Ubuntu or Fedora?

> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is 
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO] 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE 
> [28:40.637s]
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on 
> project ambari-server: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp 
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp 
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp 
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] 
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter8706425108380679609.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun4 surefire3030080908304903958tmp 
> surefire_5025412729838224505067tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit

[jira] [Comment Edited] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

2017-09-08 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159299#comment-16159299
 ] 

Tibor Digana edited comment on SUREFIRE-1408 at 9/8/17 8:44 PM:


[~aonishuk]
This is my result:

{panel}
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ... SUCCESS [  7.566 s]
[INFO] utility  SUCCESS [  2.017 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 12.307 s]
[INFO] Ambari Server .. FAILURE [  6.704 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 29.626 s
[INFO] Finished at: 2017-09-08T22:40:25+02:00
[INFO] Final Memory: 43M/313M
[INFO] 
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(azuredb-gen) on project ambari-server: Command execution failed.: Cannot run 
program 
"E:\tmp\zmaz12\ambari\ambari-server\src\main\sh\azuredb_create_generator.sh" 
(in directory "E:\tmp\zmaz12\ambari\ambari-server"): CreateProcess error=193, 
%1 is not a valid Win32 application -> [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]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
{panel}


was (Author: tibor17):
[~aonishuk]
This is my result:

{{
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ... SUCCESS [  7.566 s]
[INFO] utility  SUCCESS [  2.017 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 12.307 s]
[INFO] Ambari Server .. FAILURE [  6.704 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 29.626 s
[INFO] Finished at: 2017-09-08T22:40:25+02:00
[INFO] Final Memory: 43M/313M
[INFO] 
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(azuredb-gen) on project ambari-server: Command execution failed.: Cannot run 
program 
"E:\tmp\zmaz12\ambari\ambari-server\src\main\sh\azuredb_create_generator.sh" 
(in directory "E:\tmp\zmaz12\ambari\ambari-server"): CreateProcess error=193, 
%1 is not a valid Win32 application -> [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]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
}}

> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is 
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO] 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE 
> [28:40.637s]
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on 
> project

[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

2017-09-08 Thread Tibor Digana (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159299#comment-16159299
 ] 

Tibor Digana commented on SUREFIRE-1408:


[~aonishuk]
This is my result:

{{
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ... SUCCESS [  7.566 s]
[INFO] utility  SUCCESS [  2.017 s]
[INFO] Ambari Metrics Common .. SUCCESS [ 12.307 s]
[INFO] Ambari Server .. FAILURE [  6.704 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 29.626 s
[INFO] Finished at: 2017-09-08T22:40:25+02:00
[INFO] Final Memory: 43M/313M
[INFO] 
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec 
(azuredb-gen) on project ambari-server: Command execution failed.: Cannot run 
program 
"E:\tmp\zmaz12\ambari\ambari-server\src\main\sh\azuredb_create_generator.sh" 
(in directory "E:\tmp\zmaz12\ambari\ambari-server"): CreateProcess error=193, 
%1 is not a valid Win32 application -> [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]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
}}

> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is 
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO] 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE 
> [28:40.637s]
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on 
> project ambari-server: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp 
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp 
> surefire_5004808314434139002513tmp
> [ERROR] Error

[jira] [Updated] (SUREFIRE-1395) Surefire plugin reports bogus test failure

2017-09-08 Thread Carte Project (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carte Project updated SUREFIRE-1395:

Description: 
Surefire plugin reports a bogus test failure when building and running the 
tests for an open source project. This is the report:

{noformat}
Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.211 s <<< 
FAILURE! - in io.sf.carte.doc.html.DOMNodeTest
compareDocumentPosition1(io.sf.carte.doc.html.DOMNodeTest)  Time elapsed: 0.047 
s  <<< FAILURE!
java.lang.AssertionError: expected:<10> but was:<10>
at 
io.sf.carte.doc.html.DOMNodeTest.compareDocumentPosition1(DOMNodeTest.java:56)
{noformat}

The test is an integer comparison, and completes successfully when launched 
from Eclipse.

If anyone is interested in trying to reproduce it, do the following steps:

1) Download a dependency that is not in the central repository:
[https://sourceforge.net/projects/jclf/files/latest/download]
Run 'maven install' in the root directory of that project and install it on 
your maven local repository.

2) Download the code from 
[https://sourceforge.net/projects/carte/files/css4j/0.36/css4j-0.36.zip/download]
 and run 'mvn' at the directory. Now the error happens.

In principle my software setup is relatively simple, an up-to-date Windows 
10-1607 with latest JDK8.

EDIT: more detailed steps to reproduce the problem.
EDIT 2: Updated link to file download.

  was:
Surefire plugin reports a bogus test failure when building and running the 
tests for an open source project. This is the report:

{noformat}
Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.211 s <<< 
FAILURE! - in io.sf.carte.doc.html.DOMNodeTest
compareDocumentPosition1(io.sf.carte.doc.html.DOMNodeTest)  Time elapsed: 0.047 
s  <<< FAILURE!
java.lang.AssertionError: expected:<10> but was:<10>
at 
io.sf.carte.doc.html.DOMNodeTest.compareDocumentPosition1(DOMNodeTest.java:56)
{noformat}

The test is an integer comparison, and completes successfully when launched 
from Eclipse.

If anyone is interested in trying to reproduce it, do the following steps:

1) Download a dependency that is not in the central repository:
[https://sourceforge.net/projects/jclf/files/latest/download]
Run 'maven install' in the root directory of that project and install it on 
your maven local repository.

2) Download the code from 
[https://sourceforge.net/projects/carte/files/css4j/0.32/css4j-0.32.zip/download]
 and run 'mvn' at the directory. Now the error happens.

In principle my software setup is relatively simple, an up-to-date Windows 
10-1607 with latest JDK8.

EDIT: more detailed steps to reproduce the problem.



> Surefire plugin reports bogus test failure
> --
>
> Key: SUREFIRE-1395
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1395
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.19, 2.20
> Environment: Windows 10 (1607) on x86_64 platform. JRE 1.8.0_141-b15 
> (tested with 1.8.0_131 too).
>Reporter: Carte Project
>
> Surefire plugin reports a bogus test failure when building and running the 
> tests for an open source project. This is the report:
> {noformat}
> Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.211 s <<< 
> FAILURE! - in io.sf.carte.doc.html.DOMNodeTest
> compareDocumentPosition1(io.sf.carte.doc.html.DOMNodeTest)  Time elapsed: 
> 0.047 s  <<< FAILURE!
> java.lang.AssertionError: expected:<10> but was:<10>
>   at 
> io.sf.carte.doc.html.DOMNodeTest.compareDocumentPosition1(DOMNodeTest.java:56)
> {noformat}
> The test is an integer comparison, and completes successfully when launched 
> from Eclipse.
> If anyone is interested in trying to reproduce it, do the following steps:
> 1) Download a dependency that is not in the central repository:
> [https://sourceforge.net/projects/jclf/files/latest/download]
> Run 'maven install' in the root directory of that project and install it on 
> your maven local repository.
> 2) Download the code from 
> [https://sourceforge.net/projects/carte/files/css4j/0.36/css4j-0.36.zip/download]
>  and run 'mvn' at the directory. Now the error happens.
> In principle my software setup is relatively simple, an up-to-date Windows 
> 10-1607 with latest JDK8.
> EDIT: more detailed steps to reproduce the problem.
> EDIT 2: Updated link to file download.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.

2017-09-08 Thread Tibor Digana (JIRA)


 [ 
https://issues.apache.org/jira/browse/SUREFIRE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tibor Digana updated SUREFIRE-1409:
---
Description: 
JUnit does not force runners to include all child tests in Description. 
Therefore Parallel Runner should not throw such tests away.
For example Spock does not report parametrized tests.
[https://github.com/spockframework/spock/pull/558]

> Parallel runner should not drop away runners that have zero children.
> -
>
> Key: SUREFIRE-1409
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1409
> Project: Maven Surefire
>  Issue Type: Improvement
>  Components: Junit 4.7+ (parallel) support
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.20.2
>
>
> JUnit does not force runners to include all child tests in Description. 
> Therefore Parallel Runner should not throw such tests away.
> For example Spock does not report parametrized tests.
> [https://github.com/spockframework/spock/pull/558]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Closed] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

2017-09-08 Thread Robert Scholte (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNGSITE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte closed MNGSITE-317.
--
Resolution: Fixed

Fixed in [r1807783|http://svn.apache.org/viewvc?rev=1807783=rev]

> Typo in developers section of Maven Pom Reference page
> --
>
> Key: MNGSITE-317
> URL: https://issues.apache.org/jira/browse/MNGSITE-317
> Project: Maven Project Web Site
>  Issue Type: Bug
> Environment: All
>Reporter: Michael Huang
>Assignee: Robert Scholte
>Priority: Trivial
>
> The xml email tag in the following section is not closed properly. Just 
> slightly annoying for anyone using this as a reference, and probably worse 
> for new people to maven.
> https://maven.apache.org/pom.html#Developers



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

2017-09-08 Thread Robert Scholte (JIRA)


 [ 
https://issues.apache.org/jira/browse/MNGSITE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte reassigned MNGSITE-317:
--

Assignee: Robert Scholte

> Typo in developers section of Maven Pom Reference page
> --
>
> Key: MNGSITE-317
> URL: https://issues.apache.org/jira/browse/MNGSITE-317
> Project: Maven Project Web Site
>  Issue Type: Bug
> Environment: All
>Reporter: Michael Huang
>Assignee: Robert Scholte
>Priority: Trivial
>
> The xml email tag in the following section is not closed properly. Just 
> slightly annoying for anyone using this as a reference, and probably worse 
> for new people to maven.
> https://maven.apache.org/pom.html#Developers



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

2017-09-08 Thread Michael Huang (JIRA)

Michael Huang created MNGSITE-317:
-

 Summary: Typo in developers section of Maven Pom Reference page
 Key: MNGSITE-317
 URL: https://issues.apache.org/jira/browse/MNGSITE-317
 Project: Maven Project Web Site
  Issue Type: Bug
 Environment: All
Reporter: Michael Huang
Priority: Trivial


The xml email tag in the following section is not closed properly. Just 
slightly annoying for anyone using this as a reference, and probably worse for 
new people to maven.

https://maven.apache.org/pom.html#Developers



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

2017-09-08 Thread Michael Huang (JIRA)


[ 
https://issues.apache.org/jira/browse/MNGSITE-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158813#comment-16158813
 ] 

Michael Huang commented on MNGSITE-317:
---

j...@example.com 
Should be
j...@example.com

> Typo in developers section of Maven Pom Reference page
> --
>
> Key: MNGSITE-317
> URL: https://issues.apache.org/jira/browse/MNGSITE-317
> Project: Maven Project Web Site
>  Issue Type: Bug
> Environment: All
>Reporter: Michael Huang
>Priority: Trivial
>
> The xml email tag in the following section is not closed properly. Just 
> slightly annoying for anyone using this as a reference, and probably worse 
> for new people to maven.
> https://maven.apache.org/pom.html#Developers



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (MSOURCES-91) Added several properties for parameters

2017-09-08 Thread Adam Yen (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Adam Yen updated MSOURCES-91:
-
Comment: was deleted

(was: After trying to debug why this plugin ignores my includes, I found this 
Jira issue. The online document states I can use this since version 2.3. Why 
was it removed for 3.x? My reason to use to plugin is to pacakage non-jar 
source directories and files in non-traditional src/main/java dirs.

https://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html
)

> Added several properties for parameters
> ---
>
> Key: MSOURCES-91
> URL: https://issues.apache.org/jira/browse/MSOURCES-91
> Project: Maven Source Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> Added properties for
>  * {{@Parameter( property = "maven.source.includes" )}}
>  * {{@Parameter( property = "maven.source.excludes" )}}
>  * {{@Parameter( property = "maven.source.useDefaultExcludes", defaultValue = 
> "true" )}}
>  * {{@Parameter( property = "maven.source.useDefaultManifestFile", 
> defaultValue = "false" )}}
>  * {{@Parameter( property = "maven.source.outputDirectory", defaultValue = 
> "$\{project.build.directory\}" )}}
>  * {{@Parameter( property = "maven.source.finalName", defaultValue = 
> "$\{project.build.finalName\}" )}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MSOURCES-91) Added several properties for parameters

2017-09-08 Thread Adam Yen (JIRA)


[ 
https://issues.apache.org/jira/browse/MSOURCES-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158752#comment-16158752
 ] 

Adam Yen commented on MSOURCES-91:
--

After trying to debug why this plugin ignores my includes, I found this Jira 
issue. The online document states I can use this since version 2.3. Why was it 
removed for 3.x? My reason to use to plugin is to pacakage non-jar source 
directories and files in non-traditional src/main/java dirs.

https://maven.apache.org/plugins/maven-source-plugin/jar-mojo.html


> Added several properties for parameters
> ---
>
> Key: MSOURCES-91
> URL: https://issues.apache.org/jira/browse/MSOURCES-91
> Project: Maven Source Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>
> Added properties for
>  * {{@Parameter( property = "maven.source.includes" )}}
>  * {{@Parameter( property = "maven.source.excludes" )}}
>  * {{@Parameter( property = "maven.source.useDefaultExcludes", defaultValue = 
> "true" )}}
>  * {{@Parameter( property = "maven.source.useDefaultManifestFile", 
> defaultValue = "false" )}}
>  * {{@Parameter( property = "maven.source.outputDirectory", defaultValue = 
> "$\{project.build.directory\}" )}}
>  * {{@Parameter( property = "maven.source.finalName", defaultValue = 
> "$\{project.build.finalName\}" )}}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MNG-6240) Duplicate components in plugin extension realm when plugin depends on maven-aether-resolver

2017-09-08 Thread Christoph Amshoff (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158685#comment-16158685
 ] 

Christoph Amshoff commented on MNG-6240:


I'm sorry if this is annoying, but this issue is clearly a blocker since it 
randomly breaks builds, and going back to Maven 3.3.9 is not always an option. 
So what exactly is the reason we can't get some kind of release where this is 
fixed, nearly 3 months after the issue has been marked as closed? 3.5.1-alpha 
or such would be fine in case some other planned issues still need a review.

Moreover, I agree with Jay mann's comment on MDEPLOY-221 that the version 3.5.0 
should be marked as buggy on the Maven homepage, or perhaps even revoked.

Please, don't let Maven users run into this without giving a heads-up, and 
without a chance to get around it!


> Duplicate components in plugin extension realm when plugin depends on 
> maven-aether-resolver
> ---
>
> Key: MNG-6240
> URL: https://issues.apache.org/jira/browse/MNG-6240
> Project: Maven
>  Issue Type: Bug
>  Components: Class Loading
>Affects Versions: 3.5.0
>Reporter: Guillaume Boué
>Assignee: Guillaume Boué
> Fix For: 3.5.1
>
>
> When a plugin extension has a dependency on {{maven-aether-resolver}}, the 
> components of this artifact are added into the plugin realm even though Maven 
> Core already provides them. This is a regression introduced by the rename of 
> this module to {{maven-resolver-provider}} in 3.5.0.
> This rename has kept all the classes of {{maven-aether-resolver}} for 
> compatibility, therefore the old artifact name also needs to be exported by 
> Maven Core in {{extension.xml}}.
> A visible side-effect of this is MDEPLOY-221, where the two 
> {{MetadataGeneratorFactory}} components of {{maven-aether-provider}} (which 
> are {{SnapshotMetadataGeneratorFactory}} and 
> {{VersionsMetadataGeneratorFactory}}) are present twice as Guice bindings, 
> and wrong metadata information is deployed as a consequence. This is due to 
> the Flex Mojos plugin extension which depends on {{maven-aether-resolver}} 
> used in the build.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MJAVADOC-496) javadoc:fix creates invalid @param tags for "this"

2017-09-08 Thread Robert Scholte (JIRA)


[ 
https://issues.apache.org/jira/browse/MJAVADOC-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158659#comment-16158659
 ] 

Robert Scholte commented on MJAVADOC-496:
-

I would be very surprised if this code would compile, {{this}} cannot be a 
valid parameter name.

> javadoc:fix creates invalid @param tags for "this"
> --
>
> Key: MJAVADOC-496
> URL: https://issues.apache.org/jira/browse/MJAVADOC-496
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.9.1
> Environment: Ubuntu 14.04.3 LTS
>Reporter: Chris Hennick
>
> I'm using the Checker Framework on Java 8, so I sometimes need to write 
> method declarations in a form like
> {code:java}
>   protected void initTransientFields(
>   @UnknownInitialization AesCounterRandom this) {/*...*/}
> {code}
> When I run mvn javadoc:fix on a code base where I'm doing that, the javadocs 
> of such methods gain tags beginning with {code:java}@param this{code}, which 
> raise an error when mvn javadoc:javadoc tries to process them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DOXIA-559) Doxia macro fails with markdown headers past level 4

2017-09-08 Thread Steve Loughran (JIRA)


[ 
https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158387#comment-16158387
 ] 

Steve Loughran commented on DOXIA-559:
--

Thanks for looking at this BTW, maybe just mark as cannot-reproduce?

> Doxia macro fails with markdown headers past level 4
> 
>
> Key: DOXIA-559
> URL: https://issues.apache.org/jira/browse/DOXIA-559
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Module - Markdown
>Affects Versions: 1.7
>Reporter: Alex O'Ree
> Attachments: toc-macro-test.md
>
>
> attempting to include the TOC using a markdown file. If you have any headers 
> past level 3, the TOC fails
> using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
> I c'd 
> http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup=1716285#l2
> however no TOC is outputted on a test.md.vm file.
> If I change the file name to test.md (dropping the vm extension), I get a 
> stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm 
> doing wrong
> {noformat}Caused by: java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at 
> org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
> at 
> org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
> at 
> org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
> at 
> org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at 
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at 
> org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
> at 
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at 
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at 
> org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
> at 
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at 
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at 
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at 
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (DOXIA-559) Doxia macro fails with markdown headers past level 4

2017-09-08 Thread Steve Loughran (JIRA)


[ 
https://issues.apache.org/jira/browse/DOXIA-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158386#comment-16158386
 ] 

Steve Loughran commented on DOXIA-559:
--

yeah, it's odd. I've pulled out all level 4 tags in our docs and it has gone 
away...but it wasn't happening on some docs that did have that depth of tag. I 
think maybe it's some depth thing like going from ## to  without an 
intermediate, but, whatever: it's gone away now

> Doxia macro fails with markdown headers past level 4
> 
>
> Key: DOXIA-559
> URL: https://issues.apache.org/jira/browse/DOXIA-559
> Project: Maven Doxia
>  Issue Type: Bug
>  Components: Module - Markdown
>Affects Versions: 1.7
>Reporter: Alex O'Ree
> Attachments: toc-macro-test.md
>
>
> attempting to include the TOC using a markdown file. If you have any headers 
> past level 3, the TOC fails
> using maven site plugin version 3.6, which looks like it's using doxia 1.7.4a
> I c'd 
> http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-modules/doxia-module-markdown/src/test/resources/macro-toc.md?view=markup=1716285#l2
> however no TOC is outputted on a test.md.vm file.
> If I change the file name to test.md (dropping the vm extension), I get a 
> stack dump. "EmtpyStackException" when rendering this file. Not sure what I'm 
> doing wrong
> {noformat}Caused by: java.util.EmptyStackException
> at java.util.Stack.peek(Unknown Source)
> at 
> org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
> at 
> org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
> at 
> org.apache.maven.doxia.sink.impl.SinkAdapter.text(SinkAdapter.java:874)
> at 
> org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBaseParser.java:783)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:254)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at 
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at 
> org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
> at 
> org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractParser.java:136)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlParser.java:268)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlParser.java:233)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlParser.java:263)
> at 
> org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlParser.java:145)
> at 
> org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.java:96)
> at 
> org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.java:356)
> at 
> org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownParser.java:112
> at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:449)
> at 
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at 
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at 
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at 
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

2017-09-08 Thread Andrew Onischuk (JIRA)


[ 
https://issues.apache.org/jira/browse/SUREFIRE-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16158331#comment-16158331
 ] 

Andrew Onischuk commented on SUREFIRE-1408:
---

To build ambari-web a lot of pre-setup staff is needed. [~tibor17] can you 
please this build cmd:
{noformat}
mvn clean test -Dcheckstyle.skip -Drat.skip=true -fae -DambariVersion=1.3.0 -pl 
ambari-views,ambari-metrics/ambari-metrics-common,ambari-server,utility 
-DfailIfNoTests=false
{noformat}
It won't build ambari-web and you should reproduce the actual bug.

> Surefire tests constantly fail due to fork issue.
> -
>
> Key: SUREFIRE-1408
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1408
> Project: Maven Surefire
>  Issue Type: Bug
>Affects Versions: 2.20
>Reporter: Andrew Onischuk
>Assignee: Tibor Digana
>Priority: Blocker
>
> Our project cannot run the tests for some reason we have this error. This is 
> blocking 100% of test runs. A big blocker for our project.
> The tests which fail with this are always random.
> {noformat}
> [WARNING] Tests run: 4830, Failures: 0, Errors: 0, Skipped: 35
> [INFO] 
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Ambari Views .. SUCCESS [4.001s]
> [INFO] utility ... SUCCESS [1.057s]
> [INFO] Ambari Metrics Common . SUCCESS [14.892s]
> [INFO] Ambari Server . FAILURE 
> [28:40.637s]
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 29:01.548s
> [INFO] Finished at: Wed Sep 06 13:53:46 EEST 2017
> [INFO] Final Memory: 49M/583M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-surefire-plugin:2.20:test (default-test) on 
> project ambari-server: There are test failures.
> [ERROR] 
> [ERROR] Please refer to 
> /tmp/ambari_test_java/ambari-server/target/surefire-reports for the 
> individual test results.
> [ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
> [date].dumpstream and [date]-jvmRun[N].dumpstream.
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter7964123771295668464.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun4 surefire3196986160626902066tmp 
> surefire_494835328994998108571tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] org.apache.ambari.server.controller.AmbariServerTest
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter5127210523160415183.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun1 surefire5729106817171066937tmp 
> surefire_5004808314434139002513tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
> /tmp/ambari_test_java/ambari-server/target/surefire/surefirebooter3901662057959462367.jar
>  /tmp/ambari_test_java/ambari-server/target/surefire 
> 2017-09-06T13-25-37_978-jvmRun2 surefire1724459552574953042tmp 
> surefire_5012934123283689072947tmp
> [ERROR] Error occurred in starting fork, check output in log
> [ERROR] Process Exit Code: 1
> [ERROR] Crashed tests:
> [ERROR] 
> org.apache.ambari.server.controller.metrics.ganglia.GangliaPropertyProviderTest
> [ERROR] ExecutionException The forked VM terminated without properly saying 
> goodbye. VM crash or System.exit called?
> [ERROR] Command was /bin/sh -c cd /tmp/ambari_test_java/ambari-server && 
> /usr/local/java/jdk1.8.0_25/jre/bin/java -Xmx2048m -XX:MaxPermSize=1024m 
> -Xms1024m -jar 
>

[jira] [Created] (MJAVADOC-496) javadoc:fix creates invalid @param tags for "this"

2017-09-08 Thread Chris Hennick (JIRA)

Chris Hennick created MJAVADOC-496:
--

 Summary: javadoc:fix creates invalid @param tags for "this"
 Key: MJAVADOC-496
 URL: https://issues.apache.org/jira/browse/MJAVADOC-496
 Project: Maven Javadoc Plugin
  Issue Type: Bug
Affects Versions: 2.9.1
 Environment: Ubuntu 14.04.3 LTS
Reporter: Chris Hennick


I'm using the Checker Framework on Java 8, so I sometimes need to write method 
declarations in a form like

{code:java}
  protected void initTransientFields(
  @UnknownInitialization AesCounterRandom this) {/*...*/}
{code}

When I run mvn javadoc:fix on a code base where I'm doing that, the javadocs of 
such methods gain tags beginning with {code:java}@param this{code}, which raise 
an error when mvn javadoc:javadoc tries to process them.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (MJAVADOC-496) javadoc:fix creates invalid @param tags for "this"

[jira] [Created] (MPDF-82) Improve the PDF aggregated title page

[jira] [Commented] (MPDF-81) Override the copyright footer

[jira] [Commented] (MPDF-81) Override the copyright footer

[jira] [Commented] (MPDF-81) Override the copyright footer

[jira] [Commented] (MPDF-81) Override the copyright footer

[jira] [Commented] (MSHADE-243) Java 8 type-use annotation breaks relocation

[jira] [Commented] (SUREFIRE-1331) Bump version number

[jira] [Commented] (SUREFIRE-1391) System Property variables processed twice in calculation of effective properties

[jira] [Closed] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.

[jira] [Updated] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.

[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

[jira] [Comment Edited] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

[jira] [Updated] (SUREFIRE-1395) Surefire plugin reports bogus test failure

[jira] [Updated] (SUREFIRE-1409) Parallel runner should not drop away runners that have zero children.

[jira] [Closed] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

[jira] [Assigned] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

[jira] [Created] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

[jira] [Commented] (MNGSITE-317) Typo in developers section of Maven Pom Reference page

[jira] [Issue Comment Deleted] (MSOURCES-91) Added several properties for parameters

[jira] [Commented] (MSOURCES-91) Added several properties for parameters

[jira] [Commented] (MNG-6240) Duplicate components in plugin extension realm when plugin depends on maven-aether-resolver

[jira] [Commented] (MJAVADOC-496) javadoc:fix creates invalid @param tags for "this"

[jira] [Commented] (DOXIA-559) Doxia macro fails with markdown headers past level 4

[jira] [Commented] (DOXIA-559) Doxia macro fails with markdown headers past level 4

[jira] [Commented] (SUREFIRE-1408) Surefire tests constantly fail due to fork issue.

[jira] [Created] (MJAVADOC-496) javadoc:fix creates invalid @param tags for "this"

28 matches

Site Navigation

Mail list logo

Footer information