date:20170501

[jira] [Updated] (SUREFIRE-1369) No way to output ANSI colors when running under Surefire

2017-05-01 Thread Gili (JIRA)


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

Gili updated SUREFIRE-1369:
---
Description: 
I invoke the following native code from inside a unit test:

{{GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), )}}

It fails with {{GetLastError() == ERROR_INVALID_HANDLE}} indicating that stdout 
has been redirected.

I am blocked by the fact that it isn't possible to use ANSI colors under 
Windows when stdout has been redirected. I tried configuring Surefire with:

{code}
0
false
false
false
{code}

but stdout is still getting redirected. Is it possible to configure Surefire to 
use the default stdout (connected to a terminal) without redirection?

Expected behavior: Surefire shouldn't fork the JVM or redirect stdout when 
{{forkCount}} is zero and {{useFile}} is false.

  was:
I invoke the following native code from inside a unit test:

{{GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), )}}

It fails with {{GetLastError() == ERROR_INVALID_HANDLE}} indicating that stdout 
has been redirected.

I am blocked by the fact that it isn't possible to use ANSI colors under 
Windows when stdout has been redirected. I tried configuring Surefire with:

{code}
0
false
false
false
{code}

but stdout is still getting redirected. Is it possible to configure Surefire to 
use the default stdout (connected to a terminal) without redirection?

 Issue Type: Bug  (was: Improvement)

> No way to output ANSI colors when running under Surefire
> 
>
> Key: SUREFIRE-1369
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1369
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
> Environment: Windows 10 64-bit, 10.0.14393
>Reporter: Gili
>
> I invoke the following native code from inside a unit test:
> {{GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), )}}
> It fails with {{GetLastError() == ERROR_INVALID_HANDLE}} indicating that 
> stdout has been redirected.
> I am blocked by the fact that it isn't possible to use ANSI colors under 
> Windows when stdout has been redirected. I tried configuring Surefire with:
> {code}
>   0
>   false
>   false
>   false
> {code}
> but stdout is still getting redirected. Is it possible to configure Surefire 
> to use the default stdout (connected to a terminal) without redirection?
> Expected behavior: Surefire shouldn't fork the JVM or redirect stdout when 
> {{forkCount}} is zero and {{useFile}} is false.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SUREFIRE-1369) No way to output ANSI colors when running under Surefire

2017-05-01 Thread Gili (JIRA)

Gili created SUREFIRE-1369:
--

 Summary: No way to output ANSI colors when running under Surefire
 Key: SUREFIRE-1369
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1369
 Project: Maven Surefire
  Issue Type: Improvement
  Components: Maven Surefire Plugin
Affects Versions: 2.20
 Environment: Windows 10 64-bit, 10.0.14393
Reporter: Gili


I invoke the following native code from inside a unit test:

{{GetConsoleScreenBufferInfo(GetStdHandle(STD_OUTPUT_HANDLE), )}}

It fails with {{GetLastError() == ERROR_INVALID_HANDLE}} indicating that stdout 
has been redirected.

I am blocked by the fact that it isn't possible to use ANSI colors under 
Windows when stdout has been redirected. I tried configuring Surefire with:

{code}
0
false
false
false
{code}

but stdout is still getting redirected. Is it possible to configure Surefire to 
use the default stdout (connected to a terminal) without redirection?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (DOXIA-556) Add support for macros in vm templates

2017-05-01 Thread Alex O'Ree (JIRA)


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

Alex O'Ree updated DOXIA-556:
-
Summary: Add support for macros in vm templates  (was: Add support for 
macros in vm tempaltes)

> Add support for macros in vm templates
> --
>
> Key: DOXIA-556
> URL: https://issues.apache.org/jira/browse/DOXIA-556
> Project: Maven Doxia
>  Issue Type: Improvement
>Reporter: Alex O'Ree
>
> see also [DOXIA-492]
> The current support for MACROs, such as TOC, appears to not function in 
> templated/filtered documents, such as markdown.md.vm. Would it be possible to 
> enabling MACRO support in .vm templates?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (DOXIA-556) Add support for macros in vm tempaltes

2017-05-01 Thread Alex O'Ree (JIRA)

Alex O'Ree created DOXIA-556:


 Summary: Add support for macros in vm tempaltes
 Key: DOXIA-556
 URL: https://issues.apache.org/jira/browse/DOXIA-556
 Project: Maven Doxia
  Issue Type: Improvement
Reporter: Alex O'Ree


see also [DOXIA-492]

The current support for MACROs, such as TOC, appears to not function in 
templated/filtered documents, such as markdown.md.vm. Would it be possible to 
enabling MACRO support in .vm templates?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991801#comment-15991801
 ] 

Alex O'Ree edited comment on MSITE-748 at 5/2/17 12:30 AM:
---

[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown
{quote}
# title
### something here
## Sub section 1
{quote}

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)


was (Author: spyhunter99):
[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown

# title
### something here
## Sub section 1

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at

[jira] [Comment Edited] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991801#comment-15991801
 ] 

Alex O'Ree edited comment on MSITE-748 at 5/2/17 12:30 AM:
---

[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown
{noformat}
# title
### something here
## Sub section 1
{noformat}

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)


was (Author: spyhunter99):
[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown
{quote}
# title
### something here
## Sub section 1
{quote}

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>

[jira] [Comment Edited] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991801#comment-15991801
 ] 

Alex O'Ree edited comment on MSITE-748 at 5/2/17 12:28 AM:
---

[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown

# title
### something here
## Sub section 1

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)


was (Author: spyhunter99):
[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown

# title

### something here

## Sub section 1

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at

[jira] [Comment Edited] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991801#comment-15991801
 ] 

Alex O'Ree edited comment on MSITE-748 at 5/2/17 12:28 AM:
---

[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown

# title

### something here

## Sub section 1

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)


was (Author: spyhunter99):
[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown

# title

### something here

## Sub section 1

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991801#comment-15991801
 ] 

Alex O'Ree commented on MSITE-748:
--

[~roller_hboutemy] my stack trace is a bit different and does not indicate an 
xdoc issue. (I'm new to the doxia/site stuff but have been digging deep 
lately). For markdown sources, it appears to go from markdown to xhtml, then 
run the macro. Stepping through the debugger, the xhtml does use h4 elements. 
Digging deeper, the xhtml parser ends up calling 
org.apache.maven.doxia.parser.AbstractXmlParser while running some kind of 
indexing mechanism.

In my case, I had the following markdown

# title

### something here

## Sub section 1

The sudden jump of headers seemed to cause the issue. Regardless, fixing that 
part of the markdown resolved my issue and level 4 headers are now working 
(still not with .vm files)

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by:

[jira] [Commented] (SUREFIRE-1366) mvn javadoc:javadoc fails on Javadoc syntax with JDK 1.8

2017-05-01 Thread Hudson (JIRA)


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

Hudson commented on SUREFIRE-1366:
--

SUCCESS: Integrated in Jenkins build maven-surefire #1697 (See 
[https://builds.apache.org/job/maven-surefire/1697/])
[SUREFIRE-1366] mvn javadoc:javadoc fails on Javadoc syntax with JDK 1.8 
(tibor17: 
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git=commit=b54e33e68e9c3e13f8fca4b66dbb5c89a0a30715])
* (edit) surefire-integration-tests/src/test/resources/crash-during-test/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/fork-consoleOutputWithErrors/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/surefire-510-testClassPath/pom.xml
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java
* (edit) surefire-integration-tests/src/test/resources/junit-innerClass/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/junit48-single-method/pom.xml
* (edit) surefire-integration-tests/src/test/resources/fork-timeout/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/junit44-method-pattern/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/junit4-runlistener/pom.xml
* (edit) 
maven-failsafe-plugin/src/test/java/org/apache/maven/plugin/failsafe/MarshallerUnmarshallerTest.java
* (edit) 
surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/JUnitCore.java
* (edit) surefire-integration-tests/src/test/resources/fork-mode-testng/pom.xml
* (edit) 
surefire-api/src/main/java/org/apache/maven/surefire/booter/SurefireReflector.java
* (edit) surefire-integration-tests/src/test/resources/testng-groups/pom.xml
* (edit) 
surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/pc/SchedulingStrategy.java
* (edit) 
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/UnicodeTestNamesIT.java
* (edit) 
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/AbstractFailFastIT.java
* (edit) 
surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/ThreadSafe.java
* (edit) 
surefire-integration-tests/src/test/resources/fork-mode-multimodule/module-a/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/testng-single-method/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/plain-old-java-classpath/pom.xml
* (edit) surefire-integration-tests/src/test/resources/aggregate-report/pom.xml
* (edit) surefire-integration-tests/src/test/resources/pojo-simple/pom.xml
* (edit) 
surefire-integration-tests/src/test/resources/argLine-properties/pom.xml
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/BooterSerializer.java
* (delete) 
maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/xmlsummary/ErrorType.java
* (edit) 
surefire-integration-tests/src/test/resources/junit-twoTestCaseSuite/pom.xml
* (edit) 
maven-surefire-common/src/test/java/org/apache/maven/surefire/spi/IDefault.java
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java
* (edit) 
surefire-api/src/main/java/org/apache/maven/surefire/testset/ResolvedTest.java
* (edit) 
surefire-providers/surefire-junit47/src/main/java/org/apache/maven/surefire/junitcore/pc/SchedulingStrategies.java
* (edit) surefire-integration-tests/src/test/resources/result-counting/pom.xml
* (edit) 
surefire-providers/common-junit4/src/main/java/org/apache/maven/surefire/common/junit4/JUnit4RunListener.java
* (edit) 
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire1028UnableToRunSingleIT.java
* (edit) 
surefire-integration-tests/src/test/resources/surefire-570-multipleReportDirectories/pom.xml
* (delete) maven-surefire-plugin/src/site/resources/xsd/bindings.xml
* (edit) surefire-integration-tests/src/test/resources/surefire-1265/pom.xml
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
* (edit) 
surefire-integration-tests/src/test/resources/surefire-1080-parallel-fork-double-test/pom.xml
* (edit) 
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire1265Java9IT.java
* (edit) surefire-integration-tests/src/test/resources/runorder-parallel/pom.xml
* (add) maven-surefire-plugin/src/site/resources/xsd/failsafe-summary.xjb
* (edit) 
surefire-providers/surefire-testng-utils/src/main/java/org/apache/maven/surefire/testng/utils/Stoppable.java
* (edit) 
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkConfiguration.java
* (edit) 
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire1080ParallelForkDoubleTestIT.java
* (edit)

[jira] [Closed] (SUREFIRE-1366) mvn javadoc:javadoc fails on Javadoc syntax with JDK 1.8

2017-05-01 Thread Tibor Digana (JIRA)


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

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

https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=b54e33e68e9c3e13f8fca4b66dbb5c89a0a30715

> mvn javadoc:javadoc fails on Javadoc syntax with JDK 1.8
> 
>
> Key: SUREFIRE-1366
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1366
> Project: Maven Surefire
>  Issue Type: Task
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>  Labels: documentation, javadoc
> Fix For: 2.20.1
>
>
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.9.1:javadoc (default-cli) on 
> project surefire-logger-api: An error has occurred in JavaDocs report 
> generation:
> [ERROR] Exit code: 1 - ConsoleLogger.java:24: error: self-closing element not 
> allowed
> [ERROR]  * 
> [ERROR]^



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (MDOAP-49) Website still points to jira.codehaus.org

2017-05-01 Thread Sebb (JIRA)


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

Sebb reopened MDOAP-49:
---

That commit was 2 years ago, but the website has not yet been updated.

Would it be possible to at least regenerate the website?

> Website still points to jira.codehaus.org
> -
>
> Key: MDOAP-49
> URL: https://issues.apache.org/jira/browse/MDOAP-49
> Project: Maven DOAP Plugin
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Hervé Boutemy
> Fix For: 3.0.0
>
>
> As the subject says



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991688#comment-15991688
 ] 

Alex O'Ree commented on MSITE-748:
--

well maybe this message traffic can stimulate someone to look into it. If doxia 
is the root cause, maybe i'll poke around there, however i don't believe i have 
commit permissions on that repo

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
>   at

[jira] [Commented] (MDEP-471) Java 8 Method references are not detected

2017-05-01 Thread Jonathan Haber (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991601#comment-15991601
 ] 

Jonathan Haber commented on MDEP-471:
-

This is the relevant MSHARED JIRA for reference 
https://issues.apache.org/jira/browse/MSHARED-428

> Java 8 Method references are not detected
> -
>
> Key: MDEP-471
> URL: https://issues.apache.org/jira/browse/MDEP-471
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 2.9
> Environment: Mac OSX 
> 13.3.0 Darwin Kernel Version 13.3.0: Tue Jun  3 21:27:35 PDT 2014; 
> root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
>Reporter: Ben Hardy
>
> It is possible to get the depedency plugin to fail to recognize methods 
> references.
> For example, the following function declaration is the only place in its 
> class where the Guava "Lists" class is referenced (apart from imports):
> public static  SequenceMap forStringKeys() {
> return new SequenceMap<>(Lists::charactersOf);
> }
> We choose to fail when declared dependencies are thought to be unused, and 
> this usage is simply not detected, resulting in the following output and 
> exception:
> [WARNING] Unused declared dependencies found:
> [WARNING]com.google.guava:guava:jar:18.0:compile
> [INFO] 
> 
> Caused by: org.apache.maven.plugin.MojoExecutionException: Dependency 
> problems found
>   at 
> org.apache.maven.plugin.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:187)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> Will try to get a test and patch attached to this once I figure out where 
> your test case class file resources are coming from.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-01 Thread JIRA


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

Hervé Boutemy commented on MNG-6223:


the message is not in java code but in {{mvn}} shell script, in 
{{apache-maven/src/bin}}
it is related to MNG-5889: that's why the IT is in 
https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git, in 
{{core-it-suite/src/test/java/org/apache/maven/it/MavenITmng5889FindBasedir.java}}
 and {{core-it-suite/src/test/resources/mng-5889-find.mvn/}}

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Fix For: 3.5.1
>
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SCM-807) JGit impl check-in fails unless the Maven project is in the working copy root

2017-05-01 Thread Richard DiCroce (JIRA)


[ 
https://issues.apache.org/jira/browse/SCM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991436#comment-15991436
 ] 

Richard DiCroce commented on SCM-807:
-

It's been quite a while now since I wrote this patch, but if memory serves, 
that block of code was there to sort out which files are actually tracked by 
Git in order to filter the list of returned files so that it only contains 
files that were really added instead of ALL files in that directory (and 
subdirectories). That is now handled by the block of code I added above the 
loop, right under the comment {code}// we may have tried to add files covered 
by .gitignore (so they weren't actually added){code}

> JGit impl check-in fails unless the Maven project is in the working copy root
> -
>
> Key: SCM-807
> URL: https://issues.apache.org/jira/browse/SCM-807
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.4
>Reporter: Richard DiCroce
> Attachments: scm-807.txt
>
>
> Another problem exposed by maven-release-plugin: the JGit SCM 
> implementation's check-in fails unless the Maven project is in the working 
> copy root because it confuses the working copy's location with the Maven 
> project's location.
> The attached patch resolves the issue. Combined with the patch attached to 
> SCM-806, release:prepare now mostly succeeds with the JGit implementation. 
> There is still a problem with the POM not being transformed correctly, but 
> that's a problem in maven-release-plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6224) Dependency version from test scope leaks into compile scope

2017-05-01 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on MNG-6224:
-

This is more related to MNG-6058. The discussion is more about what has a 
higher priority: scope or distance? Or to put it differently: is it possible to 
have a different version of an artifact on the classpath compared to the 
test-classpath. 
It has always been the definition that for every groupId+artifactId there's 
only one scope and one version(nearest). That explains why 3.0.1 is chosen.

> Dependency version from test scope leaks into compile scope
> ---
>
> Key: MNG-6224
> URL: https://issues.apache.org/jira/browse/MNG-6224
> Project: Maven
>  Issue Type: Bug
>  Components: Dependencies
>Affects Versions: 3.3.9
>Reporter: Andrei Tomashpolskiy
> Attachments: mvn_package.txt
>
>
> Despite test scope being non-transitive [1] it's still used to resolve 
> versions of compile dependencies. This might be causing issues in IDEs that 
> rely on the Dependency plugin to assemble the application's classpath.
> E.g. for the following project configuration *javax.servlet-api* version is 
> resolved to *3.0.1* (using nearest-first strategy to resolve conflicts):
> {noformat}
> project1
> |-- project2:compile
> |..|-- jetty-server:compile
> ||-- javax.servlet-api:3.1.0:compile
> |-- jersey-test-framework-core:test
> |..|-- javax.servlet-api:3.0.1:compile
> {noformat}
> My understanding is that it should rather be resolved to 3.1.0, because 
> version 3.0.1 stems from the test scope and should be ignored (AFAIK Maven 
> Shade plugin works in that way).
> Please see a runnable code example in 
> https://github.com/atomashpolskiy/maven-transitive-test-dependencies
> Thank you!
> [1] 
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-5188) Test scope dependency incorrectly promoted to compile scope

2017-05-01 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on MNG-5188:
-

[~atomashpolskiy] The project to this issue gives the following output, which 
is as expected.  MNG-6224 is a different usecase.
{noformat}
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ module2 ---
[DEBUG] Configuring mojo 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile from plugin realm 
ClassRealm[plugin>org.apache.maven.plugins:maven-compiler-plugin:3.1, parent: 
sun.misc.Launcher$AppClassLoader@1174ec5]
[DEBUG] Configuring mojo 
'org.apache.maven.plugins:maven-compiler-plugin:3.1:compile' with basic 
configurator -->
[DEBUG]   (f) basedir = E:\tmp-help\junit-transitive\module2
[DEBUG]   (f) buildDirectory = E:\tmp-help\junit-transitive\module2\target
[DEBUG]   (f) classpathElements = 
[E:\tmp-help\junit-transitive\module2\target\classes, 
E:\tmp-help\junit-transitive\module1\target\module1-0.0.1-SNAPSHOT.jar, 
d:\maven_repo\.m2\repository\org\apache\openjpa\openjpa\2.1.1\openjpa-2.1.1.jar,
 
d:\maven_repo\.m2\repository\commons-lang\commons-lang\2.4\commons-lang-2.4.jar,
 
d:\maven_repo\.m2\repository\commons-collections\commons-collections\3.2.1\commons-collections-3.2.1.jar,
 d:\maven_repo\.m2\repository\net\sourceforge\serp\serp\1.13.1\serp-1.13.1.jar, 
d:\maven_repo\.m2\repository\org\apache\geronimo\specs\geronimo-jms_1.1_spec\1.1.1\geronimo-jms_1.1_spec-1.1.1.jar,
 
d:\maven_repo\.m2\repository\org\apache\geronimo\specs\geronimo-jta_1.1_spec\1.1.1\geronimo-jta_1.1_spec-1.1.1.jar,
 
d:\maven_repo\.m2\repository\commons-pool\commons-pool\1.5.4\commons-pool-1.5.4.jar,
 
d:\maven_repo\.m2\repository\org\apache\geronimo\specs\geronimo-jpa_2.0_spec\1.1\geronimo-jpa_2.0_spec-1.1.jar]
[DEBUG]   (f) compileSourceRoots = 
[E:\tmp-help\junit-transitive\module2\src\main\java]
[DEBUG]   (f) compilerId = javac
[DEBUG]   (f) debug = true
[DEBUG]   (f) failOnError = true
[DEBUG]   (f) forceJavacCompilerUse = false
[DEBUG]   (f) fork = false
[DEBUG]   (f) generatedSourcesDirectory = 
E:\tmp-help\junit-transitive\module2\target\generated-sources\annotations
[DEBUG]   (f) mojoExecution = 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile {execution: 
default-compile}
[DEBUG]   (f) optimize = false
[DEBUG]   (f) outputDirectory = 
E:\tmp-help\junit-transitive\module2\target\classes
[DEBUG]   (f) projectArtifact = com.example:module2:jar:0.0.1-SNAPSHOT
[DEBUG]   (f) showDeprecation = false
[DEBUG]   (f) showWarnings = false
[DEBUG]   (f) skipMultiThreadWarning = false
[DEBUG]   (f) source = 1.5
[DEBUG]   (f) staleMillis = 0
[DEBUG]   (f) target = 1.5
[DEBUG]   (f) useIncrementalCompilation = true
[DEBUG]   (f) verbose = false
[DEBUG]   (f) mavenSession = org.apache.maven.execution.MavenSession@7557b9e
[DEBUG]   (f) session = org.apache.maven.execution.MavenSession@7557b9e
[DEBUG] -- end configuration --
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories: [E:\tmp-help\junit-transitive\module2\src\main\java]
[DEBUG] Classpath: [E:\tmp-help\junit-transitive\module2\target\classes
 E:\tmp-help\junit-transitive\module1\target\module1-0.0.1-SNAPSHOT.jar
 d:\maven_repo\.m2\repository\org\apache\openjpa\openjpa\2.1.1\openjpa-2.1.1.jar
 d:\maven_repo\.m2\repository\commons-lang\commons-lang\2.4\commons-lang-2.4.jar
 
d:\maven_repo\.m2\repository\commons-collections\commons-collections\3.2.1\commons-collections-3.2.1.jar
 d:\maven_repo\.m2\repository\net\sourceforge\serp\serp\1.13.1\serp-1.13.1.jar
 
d:\maven_repo\.m2\repository\org\apache\geronimo\specs\geronimo-jms_1.1_spec\1.1.1\geronimo-jms_1.1_spec-1.1.1.jar
 
d:\maven_repo\.m2\repository\org\apache\geronimo\specs\geronimo-jta_1.1_spec\1.1.1\geronimo-jta_1.1_spec-1.1.1.jar
 
d:\maven_repo\.m2\repository\commons-pool\commons-pool\1.5.4\commons-pool-1.5.4.jar
 
d:\maven_repo\.m2\repository\org\apache\geronimo\specs\geronimo-jpa_2.0_spec\1.1\geronimo-jpa_2.0_spec-1.1.jar]
[DEBUG] Output directory: E:\tmp-help\junit-transitive\module2\target\classes
[DEBUG] CompilerReuseStrategy: reuseCreated
[DEBUG] useIncrementalCompilation enabled
[DEBUG] Stale source detected: 
E:\tmp-help\junit-transitive\module2\src\main\java\module2\Foo.java
[INFO] Changes detected - recompiling the module!
[DEBUG] Classpath:
[DEBUG]  E:\tmp-help\junit-transitive\module2\target\classes
[DEBUG]  E:\tmp-help\junit-transitive\module1\target\module1-0.0.1-SNAPSHOT.jar
[DEBUG]  
d:\maven_repo\.m2\repository\org\apache\openjpa\openjpa\2.1.1\openjpa-2.1.1.jar
[DEBUG]  
d:\maven_repo\.m2\repository\commons-lang\commons-lang\2.4\commons-lang-2.4.jar
[DEBUG]  
d:\maven_repo\.m2\repository\commons-collections\commons-collections\3.2.1\commons-collections-3.2.1.jar
[DEBUG]  
d:\maven_repo\.m2\repository\net\sourceforge\serp\serp\1.13.1\serp-1.13.1.jar
[DEBUG]

[jira] [Commented] (MNG-5899) Reactor is no longer using the dependency reduced pom created by maven-shade-plugin

2017-05-01 Thread Robert Scholte (JIRA)


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

Robert Scholte commented on MNG-5899:
-

I think we should revise this *after* splitting up the build-pom and 
consumer-pom. I can imagine that during the construction of a buildplan the 
dependencies to a reactor module don't have to be fully resolved yet. That can 
be done after that module has been build or actually when it is required by 
another module. In the end the result must be the same as using that dependency 
from the local repsoitory.

> Reactor is no longer using the dependency reduced pom created by 
> maven-shade-plugin
> ---
>
> Key: MNG-5899
> URL: https://issues.apache.org/jira/browse/MNG-5899
> Project: Maven
>  Issue Type: Bug
>Affects Versions: 3.3.1, 3.3.3
>Reporter: Trask Stalnaker
>
> This works with maven 3.2.5 and prior, but does not work with the latest 
> releases (3.3.1 and 3.3.3), or master (tested against 3.3.7-SNAPSHOT).
> I did some bisecting and found the commit that caused the breakage:
> https://github.com/apache/maven/commit/be3fb200326208ca4b8c41ebf16d5ae6b8049792
> In particular, this commit introduced some code to not rebuild the model if 
> it was already loaded during reactor resolution.
> This is causing maven not to use the dependency reduced pom created by the 
> maven-shade-plugin.
> Removing this code fixes the situation.  I'm hoping that code was just 
> introduced as a performance optimization, and that I haven't broken anything 
> functionally by removing it (the tests still pass at least).
> I will submit a pull request with the change for review.
> Here is the original maven-shade-plugin issue as reported by the Apache Storm 
> team: https://issues.apache.org/jira/browse/MSHADE-206



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-01 Thread Charles Gould (JIRA)


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

Charles Gould commented on MNG-6223:


[~hboutemy] Yesterday I grepped [Maven 
Core|https://git-wip-us.apache.org/repos/asf/maven.git] for the warning 
message, but I couldn't find it. Was I looking in the wrong repo?

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Fix For: 3.5.1
>
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MDOAP-49) Website still points to jira.codehaus.org

2017-05-01 Thread Robert Scholte (JIRA)


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

Robert Scholte closed MDOAP-49.
---
   Resolution: Fixed
 Assignee: Hervé Boutemy
Fix Version/s: 3.0.0

Already fixed in [1671465|http://svn.apache.org/viewvc?rev=1671465=rev] as 
part of the codehaus to asf migration. Will be updated with the next release.

> Website still points to jira.codehaus.org
> -
>
> Key: MDOAP-49
> URL: https://issues.apache.org/jira/browse/MDOAP-49
> Project: Maven DOAP Plugin
>  Issue Type: Bug
>Reporter: Sebb
>Assignee: Hervé Boutemy
> Fix For: 3.0.0
>
>
> As the subject says



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SCM-807) JGit impl check-in fails unless the Maven project is in the working copy root

2017-05-01 Thread Robert Scholte (JIRA)


[ 
https://issues.apache.org/jira/browse/SCM-807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991214#comment-15991214
 ] 

Robert Scholte commented on SCM-807:


Having unittests would indeed help. 
And I'm a bit woried about the complete removal of the last block with the 
comment: {{// if a specific fileSet is given, we have to check if the file is 
really tracked}}. Not familiar with that piece of code, so can't say if it can 
be removed safely.

> JGit impl check-in fails unless the Maven project is in the working copy root
> -
>
> Key: SCM-807
> URL: https://issues.apache.org/jira/browse/SCM-807
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.4
>Reporter: Richard DiCroce
> Attachments: scm-807.txt
>
>
> Another problem exposed by maven-release-plugin: the JGit SCM 
> implementation's check-in fails unless the Maven project is in the working 
> copy root because it confuses the working copy's location with the Maven 
> project's location.
> The attached patch resolves the issue. Combined with the patch attached to 
> SCM-806, release:prepare now mostly succeeds with the JGit implementation. 
> There is still a problem with the POM not being transformed correctly, but 
> that's a problem in maven-release-plugin.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-01 Thread Robert Scholte (JIRA)


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

Robert Scholte updated MNG-6223:

Fix Version/s: (was: 3.5.1-candidate)
   3.5.1

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Fix For: 3.5.1
>
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MPMD-236) Honor pmd:pmd/cpd config in pmd:check/cpd-check goals

2017-05-01 Thread Alex Rentz (JIRA)


[ 
https://issues.apache.org/jira/browse/MPMD-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991100#comment-15991100
 ] 

Alex Rentz commented on MPMD-236:
-

In addition, it doesn't seem to be possible to fail builds based on violations 
in test code.

> Honor pmd:pmd/cpd config in pmd:check/cpd-check goals
> -
>
> Key: MPMD-236
> URL: https://issues.apache.org/jira/browse/MPMD-236
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Reporter: Alex Rentz
>
> In the PMD plugin, it seems that configuration for the pmd:pmd and cpd:cpd 
> goals that are executed transitively by way of the pmd:check and 
> cpd:cpd-check goals are not honored. For example, here's the specific issue I 
> am seeing.
> Let's say I need to run pmd on tests and want to fail the build. Intuitively 
> you'd think I could do pmd:check and set includeTests=true. However, this 
> doesn't work because pmd:check doesn't support includeTests. I am not 
> interested in generating the report, and per the site documentation for the 
> plugin, pmd:check generates the report anyway. However, it doesn't support 
> the configuration associated with pmd:pmd.
> What I would like to do is this (which doesn't work):
> {code:xml}
> 
> pmd-check
> 
> check
> 
> verify
> 
> ${pmd.includeTests}
> 
> {code}
> What I have is this:
> {code:xml}
> 
> pmd-check
> 
> check
> pmd 
> 
> verify
> 
> ${pmd.includeTests}
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Roman Ivanov (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991044#comment-15991044
 ] 

Roman Ivanov commented on MSITE-748:


sad, it is not a workaround for me

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
>   at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
>   at 
>

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15991033#comment-15991033
 ] 

Alex O'Ree commented on MSITE-748:
--

I'm using markdown and the fix for me was to
a) not use .vm templates
b) not use anything past ###, or 3 headers. Using 4 headers failures to produce 
the TOC

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
>   at

[jira] [Comment Edited] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-01 Thread JIRA


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

Hervé Boutemy edited comment on MNG-6223 at 5/1/17 4:24 PM:


nice finding: yes, looks like the shell script does not check when argument is 
a directory instead of a file

there is MNG-5889 core IT to improve to add this case, in addition to fixing 
the script itself, so this bug does never gets reintroduced: do you want to try 
to do the fix?


was (Author: hboutemy):
nice finding: yes, looks like the shell script does not check when argument is 
a directory instead of a file

there is MNG-5889 to improve to add this case: do you want to try to do the fix?

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Fix For: 3.5.1-candidate
>
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-01 Thread JIRA


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

Hervé Boutemy updated MNG-6223:
---
Fix Version/s: 3.5.1-candidate

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Fix For: 3.5.1-candidate
>
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6223) mvn -f outputs invalid error when specifying POM directory

2017-05-01 Thread JIRA


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

Hervé Boutemy commented on MNG-6223:


nice finding: yes, looks like the shell script does not check when argument is 
a directory instead of a file

there is MNG-5889 to improve to add this case: do you want to try to do the fix?

> mvn -f outputs invalid error when specifying POM directory
> --
>
> Key: MNG-6223
> URL: https://issues.apache.org/jira/browse/MNG-6223
> Project: Maven
>  Issue Type: Bug
>  Components: Command Line
>Affects Versions: 3.5.0-alpha-1, 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T15:39:06-04:00)
> Maven home: /Users/cgould/dev/tools/apache-maven-3.5.0
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>Reporter: Charles Gould
>Priority: Minor
> Attachments: alternate-pom.zip
>
>
> Basic multi-module project: common, client, and server modules.
>  
> {noformat}
> $ mvn -f client package
> POM file client specified with the -f/--file command line argument does not 
> exist
> [INFO] Scanning for projects...
> [INFO]
> [INFO] 
> 
> [INFO] Building alternate-pom-client 1.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/main/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> alternate-pom-client ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
> alternate-pom-client ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory 
> /Users/cgould/dev/personal/alternate-pom/client/src/test/resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
> alternate-pom-client ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ 
> alternate-pom-client ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ alternate-pom-client ---
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 0.764 s
> [INFO] Finished at: 2017-04-29T14:03:22-04:00
> [INFO] Final Memory: 11M/309M
> [INFO] 
> 
> {noformat}
> There is an error message, but the client module proceeds to build 
> nonetheless.
> I don't see the error message when I run:
> {noformat}
> $ mvn -f client/pom.xml package
> {noformat}
> I've verified it doesn't happen on 3.3.9, but it does happen on 3.5.0 and 
> 3.5.0-alpha-1.
> Sample project attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MPMD-230) Required class missing: org/apache/commons/io/IOUtils

2017-05-01 Thread JIRA


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

Hervé Boutemy updated MPMD-230:
---
Priority: Minor  (was: Blocker)

> Required class missing: org/apache/commons/io/IOUtils
> -
>
> Key: MPMD-230
> URL: https://issues.apache.org/jira/browse/MPMD-230
> Project: Maven PMD Plugin
>  Issue Type: Wish
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.8
>
>
> if MNG-6135 gets implemented without MNG-5739, test-scoped direct 
> dependencies will be removed from compile scope, causing execution issues 
> since compile scope requires these transitive dependencies
> removing the {{test}} scope on direct dependencies is a workaround for 
> MNG-5739, because the dependencies are not really direct compile 
> dependencies: if MNG-5739 gets implemented, we'll be able to put back the 
> {{test}} scope for the direct dependencies, since this is the real requirement



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MPMD-230) Required class missing: org/apache/commons/io/IOUtils

2017-05-01 Thread JIRA


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

Hervé Boutemy updated MPMD-230:
---
Issue Type: Wish  (was: Bug)

> Required class missing: org/apache/commons/io/IOUtils
> -
>
> Key: MPMD-230
> URL: https://issues.apache.org/jira/browse/MPMD-230
> Project: Maven PMD Plugin
>  Issue Type: Wish
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Blocker
> Fix For: 3.8
>
>
> if MNG-6135 gets implemented without MNG-5739, test-scoped direct 
> dependencies will be removed from compile scope, causing execution issues 
> since compile scope requires these transitive dependencies
> removing the {{test}} scope on direct dependencies is a workaround for 
> MNG-5739, because the dependencies are not really direct compile 
> dependencies: if MNG-5739 gets implemented, we'll be able to put back the 
> {{test}} scope for the direct dependencies, since this is the real requirement



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MPMD-230) Required class missing: org/apache/commons/io/IOUtils

2017-05-01 Thread JIRA


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

Hervé Boutemy updated MPMD-230:
---
Description: 
if MNG-6135 gets implemented without MNG-5739, test-scoped direct dependencies 
will be removed from compile scope, causing execution issues since compile 
scope requires these transitive dependencies

removing the {{test}} scope on direct dependencies is a workaround for 
MNG-5739, because the dependencies are not really direct compile dependencies: 
if MNG-5739 gets implemented, we'll be able to put back the {{test}} scope for 
the direct dependencies, since this is the real requirement

> Required class missing: org/apache/commons/io/IOUtils
> -
>
> Key: MPMD-230
> URL: https://issues.apache.org/jira/browse/MPMD-230
> Project: Maven PMD Plugin
>  Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Blocker
> Fix For: 3.8
>
>
> if MNG-6135 gets implemented without MNG-5739, test-scoped direct 
> dependencies will be removed from compile scope, causing execution issues 
> since compile scope requires these transitive dependencies
> removing the {{test}} scope on direct dependencies is a workaround for 
> MNG-5739, because the dependencies are not really direct compile 
> dependencies: if MNG-5739 gets implemented, we'll be able to put back the 
> {{test}} scope for the direct dependencies, since this is the real requirement



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Roman Ivanov (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990951#comment-15990951
 ] 

Roman Ivanov commented on MSITE-748:


but how to force site plugin or doxia to generate different H tag for "section" 
?

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
>   at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
>   at 
>

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990915#comment-15990915
 ] 

Alex O'Ree commented on MSITE-748:
--

Am I correct in assuming that the work around is to not use header level 4s?

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
>   at org.apache.maven.doxia.index.IndexingSink.text(IndexingSink.java:239)
>   at 
>

[jira] [Commented] (MSITE-748) EmptyStackException on xdoc toc macro usage

2017-05-01 Thread Alex O'Ree (JIRA)


[ 
https://issues.apache.org/jira/browse/MSITE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990912#comment-15990912
 ] 

Alex O'Ree commented on MSITE-748:
--

https://issues.apache.org/jira/browse/DOXIA-492?focusedCommentId=15990798=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15990798

Just ran into this issue myself. 

> EmptyStackException on xdoc toc macro usage
> ---
>
> Key: MSITE-748
> URL: https://issues.apache.org/jira/browse/MSITE-748
> Project: Maven Site Plugin
>  Issue Type: Bug
>Affects Versions: 3.4
> Environment: Ubuntu 12.04 64bit
>Reporter: Roman Ivanov
>Priority: Minor
>
> repository https://github.com/checkstyle/checkstyle
> update src/xdocs/config.xml, to add Content section conrtaining toc macro 
> like this:
> {code}
>   
> 
>   
> 
> 
>   
> 
> 
> {code}
> build a site by command:
> {code}
> mvn -X clean site -Dlinkcheck.skip=true -Dmaven.javadoc.skip=true -DskipTests 
> -DskipITs -Dpmd.skip=true -Dfindbugs.skip=true -Dcobertura.skip=true 
> -Dcheckstyle.ant.skip=true
> {code}
> Exception:
> {code}
> [DEBUG] Generating 
> /home/rivanov/java/git-others/checkstyle/checkstyle/target/site/config.html
> [DEBUG] Validating: 
> /home/rivanov/java/git-others/checkstyle/checkstyle/src/xdocs/config.xml
> [DEBUG] Validating the content...
> [WARNING]  was already defined in , ignored  in 
> .
> [DEBUG] Unrecognized xdoc tag:  at [17:70]
> [DEBUG] Unrecognized xdoc tag:  at [18:76]
> [warn]  was already defined in , ignored  in .
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 27.049s
> [INFO] Finished at: Wed Jun 24 21:34:25 PDT 2015
> [INFO] Final Memory: 59M/472M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project 
> checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed. 
> EmptyStackException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on 
> project checkstyle: Execution default-site of goal 
> org.apache.maven.plugins:maven-site-plugin:3.4:site failed.
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
>   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:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   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:497)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>   at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution 
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.4:site 
> failed.
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   ... 19 more
> Caused by: java.util.EmptyStackException
>   at java.util.Stack.peek(Stack.java:102)
>   at org.apache.maven.doxia.index.IndexingSink.peek(IndexingSink.java:292)
>   at

[jira] [Created] (MPMD-236) Honor pmd:pmd/cpd config in pmd:check/cpd-check goals

2017-05-01 Thread Alex Rentz (JIRA)

Alex Rentz created MPMD-236:
---

 Summary: Honor pmd:pmd/cpd config in pmd:check/cpd-check goals
 Key: MPMD-236
 URL: https://issues.apache.org/jira/browse/MPMD-236
 Project: Maven PMD Plugin
  Issue Type: Improvement
  Components: CPD, PMD
Reporter: Alex Rentz


In the PMD plugin, it seems that configuration for the pmd:pmd and cpd:cpd 
goals that are executed transitively by way of the pmd:check and cpd:cpd-check 
goals are not honored. For example, here's the specific issue I am seeing.
Let's say I need to run pmd on tests and want to fail the build. Intuitively 
you'd think I could do pmd:check and set includeTests=true. However, this 
doesn't work because pmd:check doesn't support includeTests. I am not 
interested in generating the report, and per the site documentation for the 
plugin, pmd:check generates the report anyway. However, it doesn't support the 
configuration associated with pmd:pmd.

What I would like to do is this (which doesn't work):
{code:xml}

pmd-check

check

verify

${pmd.includeTests}

{code}

What I have is this:
{code:xml}

pmd-check

check
pmd 

verify

${pmd.includeTests}

{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (MNG-6123) detect self references in POM and fail fast

2017-05-01 Thread Karl Heinz Marbaise (JIRA)


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

Karl Heinz Marbaise commented on MNG-6123:
--

Currently the following IT's:
{code}
org.apache.maven.it.MavenITmng4293RequiresCompilePlusRuntimeScopeTest.testit
org.apache.maven.it.MavenITmng4293RequiresCompilePlusRuntimeScopeTest.testit
org.apache.maven.it.MavenITmng4293RequiresCompilePlusRuntimeScopeTest.testit
org.apache.maven.it.MavenITmng4293RequiresCompilePlusRuntimeScopeTest.testit
{code}
are failing based on the implemented check.

> detect self references in POM and fail fast
> ---
>
> Key: MNG-6123
> URL: https://issues.apache.org/jira/browse/MNG-6123
> Project: Maven
>  Issue Type: Improvement
>  Components: Bootstrap & Build, Dependencies
>Affects Versions: 3.3.9
> Environment: Oracle JDK 1.8.0_111 on Linux 4.8 x64
>Reporter: Gregor B. Rosenauer
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>  Labels: build, easyfix
> Fix For: 3.5.1-candidate
>
>
> Maven does not detect self references in a POM and tries to download the 
> artifact it is about to build, which makes no sense and should result in an 
> early error and abort of the build.
> E.g. sample POM:
> {code}
> org.my.acme
> my-module
> 1.2.3
> 
> ...
> 
> ${project.groupId}
> my-module
> ${project.version}
> 
> 
> {code}
> Maven tries to download my-module.jar but obviously fails...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DOXIA-492) Add support for doxia macros in markdown documents.

2017-05-01 Thread Alex O'Ree (JIRA)


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

Alex O'Ree commented on DOXIA-492:
--

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:87
4)
at org.apache.maven.doxia.parser.XhtmlBaseParser.handleText(XhtmlBasePar
ser.java:783)
at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlP
arser.java:254)
at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlPars
er.java:145)
at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.j
ava:96)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.jav
a:356)
at org.apache.maven.doxia.macro.toc.TocMacro.execute(TocMacro.java:117)
at org.apache.maven.doxia.parser.AbstractParser.executeMacro(AbstractPar
ser.java:136)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.processMacro(XhtmlPar
ser.java:268)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.handleComment(XhtmlPa
rser.java:233)
at org.apache.maven.doxia.parser.AbstractXmlParser.parseXml(AbstractXmlP
arser.java:263)
at org.apache.maven.doxia.parser.AbstractXmlParser.parse(AbstractXmlPars
er.java:145)
at org.apache.maven.doxia.parser.XhtmlBaseParser.parse(XhtmlBaseParser.j
ava:96)
at org.apache.maven.doxia.module.xhtml.XhtmlParser.parse(XhtmlParser.jav
a:356)
at org.apache.maven.doxia.module.markdown.MarkdownParser.parse(MarkdownP
arser.java:112)
at org.apache.maven.doxia.DefaultDoxia.parse(DefaultDoxia.java:65)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocumen
t(DefaultSiteRenderer.java:449)
at org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocum
ent(DoxiaDocumentRenderer.java:53)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Defaul
tSiteRenderer.java:337)
at org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(Si
teMojo.java:262)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.j
ava:168)
at org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:1
32)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:134)
... 21 more

> Add support for doxia macros in markdown documents.
> ---
>
> Key: DOXIA-492
> URL: https://issues.apache.org/jira/browse/DOXIA-492
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Module - Markdown
>Affects Versions: 1.4
>Reporter: Juergen Kellerer
>Assignee: Hervé Boutemy
> Fix For: 1.7
>
> Attachments: maven-site-plugin-integration-test.patch, screen.png
>
>
> It would be nice if doxia macros could be supported also inside markdown 
> documents (similar to APT).
> Existing macros (especially snippet) is very useful, however with the power 
> of maven there's the ability to register own macros for a build process which 
> enables reuse of resources and improves dryness in general.
> A syntax which may work could be the following:
> * Block Level
> {noformat}
>#`??MACRO_NAME MACRO_ARGS`
> {noformat}
> * Inline
> {noformat}
> `??MACRO_NAME MACRO_ARGS`
> {noformat}
> Reference: 
> http://hackage.haskell.org/packages/archive/yesod-markdown/0.0/doc/html/Yesod-Markdown-Macros.html
> E.g. using "Texts" it works just from the Editor:
> !screen.png!
> When macros are not interpreted, they fallback to a code block, thus it's 
> easy to edit these sort of documents with one of the existing nice markdown 
> editors.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (DOXIA-492) Add support for doxia macros in markdown documents.

2017-05-01 Thread Alex O'Ree (JIRA)


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

Alex O'Ree commented on DOXIA-492:
--

I'm still having some issues with this. TOC is not being generated...
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

> Add support for doxia macros in markdown documents.
> ---
>
> Key: DOXIA-492
> URL: https://issues.apache.org/jira/browse/DOXIA-492
> Project: Maven Doxia
>  Issue Type: Improvement
>  Components: Module - Markdown
>Affects Versions: 1.4
>Reporter: Juergen Kellerer
>Assignee: Hervé Boutemy
> Fix For: 1.7
>
> Attachments: maven-site-plugin-integration-test.patch, screen.png
>
>
> It would be nice if doxia macros could be supported also inside markdown 
> documents (similar to APT).
> Existing macros (especially snippet) is very useful, however with the power 
> of maven there's the ability to register own macros for a build process which 
> enables reuse of resources and improves dryness in general.
> A syntax which may work could be the following:
> * Block Level
> {noformat}
>#`??MACRO_NAME MACRO_ARGS`
> {noformat}
> * Inline
> {noformat}
> `??MACRO_NAME MACRO_ARGS`
> {noformat}
> Reference: 
> http://hackage.haskell.org/packages/archive/yesod-markdown/0.0/doc/html/Yesod-Markdown-Macros.html
> E.g. using "Texts" it works just from the Editor:
> !screen.png!
> When macros are not interpreted, they fallback to a code block, thus it's 
> easy to edit these sort of documents with one of the existing nice markdown 
> editors.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (SUREFIRE-1263) No class name in log when running tests in parallel with parameterized tests

2017-05-01 Thread Tibor Digana (JIRA)


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

Tibor Digana closed SUREFIRE-1263.
--
Resolution: Duplicate

> No class name in log when running tests in parallel with parameterized tests
> 
>
> Key: SUREFIRE-1263
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1263
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
>
> Hello,
> Using surefire and Junit, the class names are not displayed in the output log 
> when the tests are run in parallel with parameterized tests.
> According to this [small 
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1], in 
> parallel mode:
> {noformat}
> ---
>  T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec - 
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec - 
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 7.799 s
> [INFO] Finished at: 2016-07-27T15:03:37+02:00
> [INFO] Final Memory: 18M/213M
> [INFO] 
> 
> {noformat}
> Without parallel mode (we have the 'Running #classname#' in the output):
> {noformat}
> ---
>  T E S T S
> ---
> Running com.appnexus.viewability.core.surefireJunitTests.ATest
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.085 sec - 
> in com.appnexus.viewability.core.surefireJunitTests.ATest
> Running com.appnexus.viewability.core.surefireJunitTests.BTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - 
> in com.appnexus.viewability.core.surefireJunitTests.BTest
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> It would be great to have the classname displayed when running tests in 
> parallel.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SUREFIRE-1264) Some tests can be lost when running in parallel with parameterized tests

2017-05-01 Thread Tibor Digana (JIRA)


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

Tibor Digana updated SUREFIRE-1264:
---
Fix Version/s: 2.20.1

> Some tests can be lost when running in parallel with parameterized tests
> 
>
> Key: SUREFIRE-1264
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1264
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.19.1
> Environment: Maven 3.3.9
> Java 1.8.0_45 (Oracle)
> System: OS X
> Reproduced on Linux too, with both OpenJDK 7 and Java 7 from Oracle.
>Reporter: Jean-Luc Derrien
>Assignee: Tibor Digana
> Fix For: 2.20.1
>
>
> Hello,
> It appears some tests can be lost when using the parallel mode with 
> parameterized tests. Here is a [small 
> project|https://github.com/jderrien/surefire-junit-tests/tree/simple-1] I've 
> used to try to reproduce the issue we have seen.
> This is not something that happens on every run, but it's quite frequent.
> With this loop, the problem should appear in less than 2 minutes, maybe on 
> the first run when (un)lucky:
> {code}
> time while true; do mvn clean test > last.log ; tail -25 last.log ; if [ 
> "$(grep -c 'Tests run: 12' last.log)" == "0" ]; then break; fi ; done
> {code}
> Normal run:
> {noformat}
> ---
>  T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => stop
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => stop
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.006 sec - 
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec - 
> in [p2]
> Results :
> Tests run: 12, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> When tests have been lost (here one test lost according to the output):
> {noformat}
> ---
>  T E S T S
> ---
> Running [p2]
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p0] - p0 - 
> sleeptime = 5 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p2] - p2 - 
> sleeptime = 1 => start
> com.appnexus.viewability.core.surefireJunitTests.ATest.methodA1[p1] - p1 - 
> sleeptime = 2 => start
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec - 
> in [p2]
> Running [p2]
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - 
> in [p2]
> Results :
> Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
> {noformat}
> Note: there are 3 test classes and 18 tests on the [master 
> branch|https://github.com/jderrien/surefire-junit-tests/tree/master] and it's 
> even more frequent/easy to reproduce.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MPMD-234) Support incremental analysis cache

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel closed MPMD-234.
---

> Support incremental analysis cache
> --
>
> Key: MPMD-234
> URL: https://issues.apache.org/jira/browse/MPMD-234
> Project: Maven PMD Plugin
>  Issue Type: New Feature
>  Components: PMD
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
> Fix For: 3.8
>
>
> PMD 5.6.0 supports an incremental analysis cache, which speeds up the PMD 
> run. Only changed files need to be checked again.
> In m-pmd-p, a new property should be added to configure the location of the 
> cache file (preferrably {{analysisCacheLocation=target/pmd/pmd.cache}}) and 
> another property to enable/disable this feature (e.g. {{analysisCache=true}}).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MPMD-232) Enable typeResolution by default

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel closed MPMD-232.
---

> Enable typeResolution by default
> 
>
> Key: MPMD-232
> URL: https://issues.apache.org/jira/browse/MPMD-232
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: PMD
>Reporter: Juan Martín Sotuyo Dodero
>Assignee: Andreas Dangel
> Fix For: 3.8
>
>
> For some time now PMD has supported type resolution, allowing PMD rules to 
> make better decisions by having knowledge of all classes in both the project, 
> and the classpath.
> However, when using PMD through the Maven plugin, the auxclasspath for type 
> resolution is not populated by default. There is a property to control this 
> behavior, but it's set to false by default. See 
> https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#typeResolution
> I believe there is no reason to have it off by default (actually, I don't 
> think there is any valid reason to have it off at all!). Type resolution 
> means better and more accurate analysis results. If there are no rules 
> configured requiring type resolution, the type resolution analysis is skipped 
> completely, meaning there is no performance impact either.
> I've not checked, but just in case the classpath passed to PMD should include:
> - all dependencies
> - the .class files generated by compiling the project's source code



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MPMD-233) Upgrade to PMD 5.6.1

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel closed MPMD-233.
---

> Upgrade to PMD 5.6.1
> 
>
> Key: MPMD-233
> URL: https://issues.apache.org/jira/browse/MPMD-233
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Affects Versions: 3.7
>Reporter: Matt Nelson
>Assignee: Andreas Dangel
> Fix For: 3.8
>
>
> PMD-5.6.x introduced non-passive API changes
> https://github.com/pmd/pmd/pull/131
> {quote}
> 00:56:58 [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-pmd-plugin:3.7:pmd (pmd) on project 
> maven-base-pom-test: Execution pmd of goal 
> org.apache.maven.plugins:maven-pmd-plugin:3.7:pmd failed: An API 
> incompatibility was encountered while executing 
> org.apache.maven.plugins:maven-pmd-plugin:3.7:pmd: 
> java.lang.NoSuchMethodError: 
> net.sourceforge.pmd.RuleSetFactory.setMinimumPriority(Lnet/sourceforge/pmd/RulePriority;)V
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (MPMD-231) Upgrade to PMD 5.5.6

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel closed MPMD-231.
---

> Upgrade to PMD 5.5.6
> 
>
> Key: MPMD-231
> URL: https://issues.apache.org/jira/browse/MPMD-231
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Affects Versions: 3.7
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (MPMD-231) Upgrade to PMD 5.5.6

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel resolved MPMD-231.
-
Resolution: Duplicate

> Upgrade to PMD 5.5.6
> 
>
> Key: MPMD-231
> URL: https://issues.apache.org/jira/browse/MPMD-231
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Affects Versions: 3.7
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MPMD-231) Upgrade to PMD 5.5.6

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel updated MPMD-231:

Fix Version/s: (was: 3.8)

> Upgrade to PMD 5.5.6
> 
>
> Key: MPMD-231
> URL: https://issues.apache.org/jira/browse/MPMD-231
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Affects Versions: 3.7
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (MPMD-231) Upgrade to PMD 5.5.6

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel reopened MPMD-231:
-

> Upgrade to PMD 5.5.6
> 
>
> Key: MPMD-231
> URL: https://issues.apache.org/jira/browse/MPMD-231
> Project: Maven PMD Plugin
>  Issue Type: Improvement
>  Components: CPD, PMD
>Affects Versions: 3.7
>Reporter: Andreas Dangel
>Assignee: Andreas Dangel
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (MPMD-235) Javadoc errors when building with java8

2017-05-01 Thread Andreas Dangel (JIRA)


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

Andreas Dangel updated MPMD-235:

Priority: Minor  (was: Major)

> Javadoc errors when building with java8
> ---
>
> Key: MPMD-235
> URL: https://issues.apache.org/jira/browse/MPMD-235
> Project: Maven PMD Plugin
>  Issue Type: Bug
>  Components: CPD, PMD
>Affects Versions: 3.8
>Reporter: Andreas Dangel
>Priority: Minor
>
> For example
> {noformat}
> [INFO] [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs) on 
> project maven-pmd-plugin: MavenReportException: Error while generating 
> Javadoc:
> [INFO] [ERROR] Exit code: 1 - 
> /home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdReport.java:286:
>  warning: no description for @throws
> [INFO] [ERROR] * @throws java.io.IOException
> [INFO] [ERROR] ^
> [INFO] [ERROR] 
> /home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:275:
>  warning: no description for @param
> [INFO] [ERROR] * @param item
> [INFO] [ERROR] ^
> [INFO] [ERROR] 
> /home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:277:
>  warning: no @param for severity
> [INFO] [ERROR] protected abstract void printError( D item, String severity );
> [INFO] [ERROR] ^
> [INFO] [ERROR] 
> /home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:282:
>  warning: no description for @param
> [INFO] [ERROR] * @param analisysFile
> [INFO] [ERROR] ^
> [INFO] [ERROR] 
> /home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:283:
>  warning: no description for @throws
> [INFO] [ERROR] * @throws XmlPullParserException
> [INFO] [ERROR] ^
> [INFO] [ERROR] 
> /home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:284:
>  warning: no description for @throws
> [INFO] [ERROR] * @throws IOException
> [INFO] [ERROR] ^
> ...
> {noformat}
> Just run with java8:
> {noformat}mvn clean verify javadoc:javadoc{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (MPMD-235) Javadoc errors when building with java8

2017-05-01 Thread Andreas Dangel (JIRA)

Andreas Dangel created MPMD-235:
---

 Summary: Javadoc errors when building with java8
 Key: MPMD-235
 URL: https://issues.apache.org/jira/browse/MPMD-235
 Project: Maven PMD Plugin
  Issue Type: Bug
  Components: CPD, PMD
Affects Versions: 3.8
Reporter: Andreas Dangel


For example

{noformat}
[INFO] [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:2.10.3:jar (attach-javadocs) on 
project maven-pmd-plugin: MavenReportException: Error while generating Javadoc:
[INFO] [ERROR] Exit code: 1 - 
/home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdReport.java:286:
 warning: no description for @throws
[INFO] [ERROR] * @throws java.io.IOException
[INFO] [ERROR] ^
[INFO] [ERROR] 
/home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:275:
 warning: no description for @param
[INFO] [ERROR] * @param item
[INFO] [ERROR] ^
[INFO] [ERROR] 
/home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:277:
 warning: no @param for severity
[INFO] [ERROR] protected abstract void printError( D item, String severity );
[INFO] [ERROR] ^
[INFO] [ERROR] 
/home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:282:
 warning: no description for @param
[INFO] [ERROR] * @param analisysFile
[INFO] [ERROR] ^
[INFO] [ERROR] 
/home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:283:
 warning: no description for @throws
[INFO] [ERROR] * @throws XmlPullParserException
[INFO] [ERROR] ^
[INFO] [ERROR] 
/home/andreas/projects/programming/apache.org/releases/maven-pmd-plugin/target/checkout/src/main/java/org/apache/maven/plugin/pmd/AbstractPmdViolationCheckMojo.java:284:
 warning: no description for @throws
[INFO] [ERROR] * @throws IOException
[INFO] [ERROR] ^
...
{noformat}

Just run with java8:

{noformat}mvn clean verify javadoc:javadoc{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

50 matches

Mail list logo