[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375933005
 
 
   The current surefire documentation references `@CucumberOptions`. I believe 
this to be sufficient. Any thing more would create a rather tight coupling 
between the documentation of Cucumber and Surefire.
   
   Using `--step-notifications` will result in 
https://github.com/cucumber/cucumber-jvm/issues/263 and 
https://github.com/cucumber/cucumber-jvm/issues/577. So I also believe the 
current defaults to be correct.
   
   Admittedly the documentation of `@CucumberOptions` could stand to be 
improved but this was covered in [the release announcement for cucumber 
2.0](https://cucumber.io/blog/2017/08/29/announcing-cucumber-jvm-2-0-0).
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375933005
 
 
   The current surefire documentation references `@CucumberOptions`. I believe 
this to be sufficient. Any thing more would create a rather tight coupling 
between the documentation of Cucumber and Surefire.
   
   Using `--step-notifications` will result in 
https://github.com/cucumber/cucumber-jvm/issues/263 and 
https://github.com/cucumber/cucumber-jvm/issues/577. So I also believe the 
current defaults to be correct.
   
   Admittedly the documentation of `@CucumberOptions` could stand to be 
improved but this was covered in [the release announcement for cucumber 
2.0](https://cucumber.io/blog/2017/08/29/announcing-cucumber-jvm-2-0-0).
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375933005
 
 
   The current surefire documentation references `@CucumberOptions`. I believe 
this to be sufficient. Any thing more would create a rather tight coupling 
between the documentation of Cucumber and Surefire.
   
   Using `--step-notifications` will result in 
https://github.com/cucumber/cucumber-jvm/issues/263 and 
https://github.com/cucumber/cucumber-jvm/issues/577. So I also believe the 
current defaults to be correct.
   
   Admittedly the documentation of `@CucumberOptions` could stand to be 
approved but this was covered in [the release announcement for cucumber 
2.0](https://cucumber.io/blog/2017/08/29/announcing-cucumber-jvm-2-0-0).
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375933005
 
 
   The current surefire documentation references `@CucumberOptions`. I believe 
this to be sufficient. Any thing more would create a rather tight coupling 
between the documentation of Cucumber and Surefire.
   
   Using `--step-notifications` will result in 
https://github.com/cucumber/cucumber-jvm/issues/263 and 
https://github.com/cucumber/cucumber-jvm/issues/577. So I also believe the 
current defaults to be correct.
   
   Admittedly the documentation of `@CucumberOptions` could stand to be 
approved but this was covered in [the release announcement for cucumber 
2.0](https://cucumber.io/blog/2017/08/29/announcing-cucumber-jvm-2-0-0).
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Closed] (MSHADE-199) What is the effect of promoteTransitiveDependencies=true ?

[Michael Osipov (JIRA)]

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

Michael Osipov closed MSHADE-199.
-
   Resolution: Invalid
Fix Version/s: (was: waiting-for-feedback)

If you are seeking for help, go to the users mailing list.

> What is the effect of promoteTransitiveDependencies=true ?
> --
>
> Key: MSHADE-199
> URL: https://issues.apache.org/jira/browse/MSHADE-199
> Project: Maven Shade Plugin
>  Issue Type: Bug
>Affects Versions: 2.4
> Environment: Win 8.1 Pro 64bit, Eclipse Mars, Java 8 64bit
>Reporter: Shoji Kuzukami
>Priority: Major
>  Labels: documentation
>
> I have some experiments on my project building to use the Shade Plugin. But  
> there is no effect under 'promoteTransitiveDependencies=true' even if the 
> dependencies in project has many transitive dependencies.
> Although I've looked for the evidence of effect by debugging the source code 
> and seeing the tests of plugin, I fell that there is no clear difference 
> between 'promoteTransitiveDependencies=true' and '=false'. Because  
> origDeps.equals(transitiveDeps)  is true in all cases for me under the code 
> below in the ShadeMojo.java, and all tests using the parameter doesn't 
> emphasize the difference of parameter .
> if ( promoteTransitiveDependencies )
> {
> origDeps = transitiveDeps;
> }
> It may be true that merely I cannot find a correct test or document for the 
> parameter because I'm new to this project. If it is, close this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6290) java.security.InvalidAlgorithmParameterException with java 9

[Michael Osipov (JIRA)]

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

Michael Osipov closed MNG-6290.
---
   Resolution: Incomplete
Fix Version/s: (was: waiting-for-feedback)

No further information given. This seems to be an issue in your jdk distro. Not 
a Haven issue.

> java.security.InvalidAlgorithmParameterException with java 9
> 
>
> Key: MNG-6290
> URL: https://issues.apache.org/jira/browse/MNG-6290
> Project: Maven
>  Issue Type: Bug
>  Components: Dependencies
>Affects Versions: 3.5.0
> Environment: Ubuntu
>Reporter: Greg Wilkins
>Priority: Major
>
> Using 
> {{
> openjdk version "9"
> OpenJDK Runtime Environment (build 9+181)
> OpenJDK 64-Bit Server VM (build 9+181, mixed mode)
> }}
> with some missing dependencies results in 
> {{
> [ERROR] Plugin org.apache.maven.plugins:maven-failsafe-plugin:2.20.1 or one 
> of its dependencies could not be resolved: Failed to read artifact descriptor 
> for org.apache.maven.plugins:maven-failsafe-plugin:jar:2.20.1: Could not 
> transfer artifact org.apache.maven.plugins:maven-failsafe-plugin:pom:2.20.1 
> from/to central (https://repo.maven.apache.org/maven2): 
> java.lang.RuntimeException: Unexpected error: 
> java.security.InvalidAlgorithmParameterException: the trustAnchors parameter 
> must be non-empty -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
> }}
> switching back to java 8 allows the dependencies to be resolved and then mvn 
> appears to work fine in java 9.
> removing the dependency makes the failure re-occur.  In my case the missing 
> dependency is {{ 
> org/apache/maven/plugins/maven-failsafe-plugin/2.20.1/maven-failsafe-plugin-2.20.1.jar}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6292) Add to the settings.xml file

[Michael Osipov (JIRA)]

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

Michael Osipov closed MNG-6292.
---
   Resolution: Incomplete
Fix Version/s: (was: waiting-for-feedback)

No reaction for six months.

> Add  to the settings.xml file
> -
>
> Key: MNG-6292
> URL: https://issues.apache.org/jira/browse/MNG-6292
> Project: Maven
>  Issue Type: Improvement
>  Components: Deployment
>Affects Versions: 3.5.0
>Reporter: zosrothko
>Priority: Major
>
> Hi
> Currently, the  element can be specified only in a 
> pom. It would be interesting also to factorize this element into a 
> settings.xml file. This would avoid to repeat this element when one manages 
> many independent Maven projects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MNG-6289) The ability to add a new phase to default lifecycle

[Michael Osipov (JIRA)]

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

Michael Osipov closed MNG-6289.
---
   Resolution: Incomplete
Fix Version/s: (was: waiting-for-feedback)

No reaction for six months.

> The ability to add a new phase to default lifecycle
> ---
>
> Key: MNG-6289
> URL: https://issues.apache.org/jira/browse/MNG-6289
> Project: Maven
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 3.5.0
>Reporter: Rami Ojares
>Priority: Major
>
> At the moment there is no way to add a phase to the default lifecycle.
> The best one can do is to create a new lifecycle with one or more phases.
> Then a phase can be bound to a goal.
> And in the Mojo that implements the goal one can fork the default lifecycle's 
> phase say install or deploy.
> But the default lifecycle is always executed forked.
> This means that the information that the package phase adds to the maven 
> project for example about the attached artifacts is lost because it is 
> executed forked.
> The simplest way to remedy this situation would be to add possibility in the 
> @Execute annotation to run a phase not-forked.
> Eg. @Execute (phase = LifecyclePhase.INSTALL, forked = false)
> This way I could create a new lifecycle but run the default lifecycle first 
> as a requirement within the same MavenProject.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MDEP-603) dependency:analyse fail on JDK 9

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise commented on MDEP-603:
--

We have to wait until the VOTE is done of the 
maven-dependency-anlyzer..Afterwards we can update to the version 1.9 which 
will solve this issue.

> dependency:analyse fail on JDK 9
> 
>
> Key: MDEP-603
> URL: https://issues.apache.org/jira/browse/MDEP-603
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.1.0
>
>
> {code}
> Running mvn dependency:analyze fails with the follwing exception:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
> (default-cli) on project utils: Execution default-cli of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze failed.:
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
> (default-cli) on project utils: Execution default-cli of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at
> org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass(DependencyClassFileVisitor.java:65)
> at
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass(ClassFileVisitorUtils.java:163)
> at
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory(ClassFileVisitorUtils.java:143)
> at
> org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept(ClassFileVisitorUtils.java:71)
> at
> org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze(ASMDependencyAnalyzer.java:50)
> at
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:211)
> at
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:198)
> at
> org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze(DefaultProjectDependencyAnalyzer.java:74)
> at
> org.apache.maven.plugins.dependency.analyze.AbstractAnalyzeMojo.checkDependencies(AbstractAnalyzeMojo.java:298)
> at
> 

[jira] [Created] (MSHARED-709) Upgrade maven 3.X only

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MSHARED-709:
---

 Summary: Upgrade maven 3.X only
 Key: MSHARED-709
 URL: https://issues.apache.org/jira/browse/MSHARED-709
 Project: Maven Shared Components
  Issue Type: Dependency upgrade
Affects Versions: maven-dependency-analyzer-1.8
Reporter: Karl Heinz Marbaise
 Fix For: maven-dependency-analyzer-3.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375922092
 
 
   Just writing a comment as you did here with @JeneJasper in it...that 
triggers an email to those ...


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375922092
 
 
   Just writing a comment as you did here with @JeneJasper in it...that 
triggers an email to those ...


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375921964
 
 
   What is a ping?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375921964
 
 
   What is a ping?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (MJAVADOC-521) Add documentation information for GitHub

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJAVADOC-521:


 Summary: Add documentation information for GitHub
 Key: MJAVADOC-521
 URL: https://issues.apache.org/jira/browse/MJAVADOC-521
 Project: Maven Javadoc Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375916227
 
 
   Can you please remove the comments about the other projects here cause they 
do not belong here..a ping on the other projects would have worked also...


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375914890
 
 
   Would like to shameless plug two other pull requests
   
   - https://github.com/mojohaus/extra-enforcer-rules/pull/36
   - https://github.com/mojohaus/build-helper-maven-plugin/pull/32


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

khmarbaise closed pull request #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: https://github.com/apache/maven-javadoc-plugin/pull/1
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java 
b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
index 24ea1b9..487bb0f 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
@@ -3782,7 +3782,7 @@ private void setFJavadocVersion( File jExecutable )
 throw new MavenReportException( "Unable to parse javadoc 
version: " + e.getMessage(), e );
 }
 
-if ( javadocRuntimeVersion != jVersion && getLog().isWarnEnabled() 
)
+if ( javadocRuntimeVersion.compareTo( jVersion ) != 0 && 
getLog().isWarnEnabled() )
 {
 getLog().warn( "Are you sure about the  
parameter? It seems to be " + jVersion );
 }


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375920302
 
 
   So now is integrated into master...Thanks for your patch.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375920302
 
 
   So now is integrated into master...Thanks for your patch.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] khmarbaise closed pull request #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

khmarbaise closed pull request #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: https://github.com/apache/maven-javadoc-plugin/pull/1
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git 
a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java 
b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
index 24ea1b9..487bb0f 100644
--- a/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
+++ b/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java
@@ -3782,7 +3782,7 @@ private void setFJavadocVersion( File jExecutable )
 throw new MavenReportException( "Unable to parse javadoc 
version: " + e.getMessage(), e );
 }
 
-if ( javadocRuntimeVersion != jVersion && getLog().isWarnEnabled() 
)
+if ( javadocRuntimeVersion.compareTo( jVersion ) != 0 && 
getLog().isWarnEnabled() )
 {
 getLog().warn( "Are you sure about the  
parameter? It seems to be " + jVersion );
 }


 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Closed] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MJAVADOC-512.

Resolution: Fixed

Done in 
[7c75ad532da90be55a8ec9c0cbc66c6638e3c1cd|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=7c75ad532da90be55a8ec9c0cbc66c6638e3c1cd]
Issue during merge: 
[c6113300e2480a2cd9919fb82985ebca15fe203c|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=c6113300e2480a2cd9919fb82985ebca15fe203c]

> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375916227
 
 
   Can you please remove the comments about the other projects here cause they 
do not belong here..a ping on the other projects would have worked also...


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375914890
 
 
   Would like to shameless plug two other pull requests
   
   - https://github.com/mojohaus/extra-enforcer-rules/pull/36
   - https://github.com/mojohaus/build-helper-maven-plugin/pull/32


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Closed] (MSHARED-708) Upgrade org.ow2.asm:asm:6.0 to 6.1 JDK 10 issues

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MSHARED-708.
---
Resolution: Fixed

Done in 
[7dc7802bf4a8e5aa1f5909e648bf7a879e7e1ce9|https://gitbox.apache.org/repos/asf?p=maven-dependency-analyzer.git;a=commitdiff;h=7dc7802bf4a8e5aa1f5909e648bf7a879e7e1ce9]

> Upgrade org.ow2.asm:asm:6.0 to 6.1 JDK 10 issues
> 
>
> Key: MSHARED-708
> URL: https://issues.apache.org/jira/browse/MSHARED-708
> Project: Maven Shared Components
>  Issue Type: Dependency upgrade
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.8
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: maven-dependency-analyzer-1.9
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[Hudson (JIRA)]

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

Hudson commented on MJAVADOC-512:
-

Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » master #31

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/31/

> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSHARED-708) Upgrade org.ow2.asm:asm:6.0 to 6.1 JDK 10 issues

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHARED-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412759#comment-16412759
 ] 

Hudson commented on MSHARED-708:


Build succeeded in Jenkins: Maven TLP » maven-dependency-analyzer » master #6

See 
https://builds.apache.org/job/maven-box/job/maven-dependency-analyzer/job/master/6/

> Upgrade org.ow2.asm:asm:6.0 to 6.1 JDK 10 issues
> 
>
> Key: MSHARED-708
> URL: https://issues.apache.org/jira/browse/MSHARED-708
> Project: Maven Shared Components
>  Issue Type: Dependency upgrade
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.8
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: maven-dependency-analyzer-1.9
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSHARED-707) Upgrade parent to 31

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MSHARED-707.
---
Resolution: Fixed

Done in 
[ef5d6974dc4d62523640a75038f4ced6e3229cff|https://gitbox.apache.org/repos/asf?p=maven-dependency-analyzer.git;a=commitdiff;h=ef5d6974dc4d62523640a75038f4ced6e3229cff]

> Upgrade parent to 31
> 
>
> Key: MSHARED-707
> URL: https://issues.apache.org/jira/browse/MSHARED-707
> Project: Maven Shared Components
>  Issue Type: Dependency upgrade
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.8
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-dependency-analyzer-1.9
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-519) IT detectLinks fails on Windows

[Hudson (JIRA)]

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

Hudson commented on MJAVADOC-519:
-

Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » master #30

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/30/

> IT detectLinks fails on Windows
> ---
>
> Key: MJAVADOC-519
> URL: https://issues.apache.org/jira/browse/MJAVADOC-519
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.1
>
> Attachments: failing-javadoc-it.log
>
>
> [Currently|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]
>  the following IT is failing:
> {code}
> [windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] The following builds failed:
> [windows-jdk9] [WARNING] *  detectLinks\pom.xml
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] Ignoring that 1 build failed.
> [windows-jdk9] [INFO] 
> 
> [windows-jdk9] [INFO] BUILD SUCCESS
> [windows-jdk9] [INFO] ---
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSHARED-707) Upgrade parent to 31

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MSHARED-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412752#comment-16412752
 ] 

Hudson commented on MSHARED-707:


Build succeeded in Jenkins: Maven TLP » maven-dependency-analyzer » master #5

See 
https://builds.apache.org/job/maven-box/job/maven-dependency-analyzer/job/master/5/

> Upgrade parent to 31
> 
>
> Key: MSHARED-707
> URL: https://issues.apache.org/jira/browse/MSHARED-707
> Project: Maven Shared Components
>  Issue Type: Dependency upgrade
>  Components: maven-dependency-analyzer
>Affects Versions: maven-dependency-analyzer-1.8
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-dependency-analyzer-1.9
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MDEP-603) dependency:analyse fail on JDK 9

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MDEP-603:


 Summary: dependency:analyse fail on JDK 9
 Key: MDEP-603
 URL: https://issues.apache.org/jira/browse/MDEP-603
 Project: Maven Dependency Plugin
  Issue Type: Bug
Affects Versions: 3.0.2
Reporter: Karl Heinz Marbaise
 Fix For: 3.1.0


{code}
Running mvn dependency:analyze fails with the follwing exception:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
(default-cli) on project utils: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze failed.:
IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze
(default-cli) on project utils: Execution default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.2:analyze failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.IllegalArgumentException
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at org.objectweb.asm.ClassReader.(Unknown Source)
at
org.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass(DependencyClassFileVisitor.java:65)
at
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass(ClassFileVisitorUtils.java:163)
at
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory(ClassFileVisitorUtils.java:143)
at
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.accept(ClassFileVisitorUtils.java:71)
at
org.apache.maven.shared.dependency.analyzer.asm.ASMDependencyAnalyzer.analyze(ASMDependencyAnalyzer.java:50)
at
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:211)
at
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.buildDependencyClasses(DefaultProjectDependencyAnalyzer.java:198)
at
org.apache.maven.shared.dependency.analyzer.DefaultProjectDependencyAnalyzer.analyze(DefaultProjectDependencyAnalyzer.java:74)
at
org.apache.maven.plugins.dependency.analyze.AbstractAnalyzeMojo.checkDependencies(AbstractAnalyzeMojo.java:298)
at
org.apache.maven.plugins.dependency.analyze.AbstractAnalyzeMojo.execute(AbstractAnalyzeMojo.java:250)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command

mvn --verison
Apache Maven 3.5.0 

[jira] [Commented] (MNG-5689) Checksum policy for mirrors

[Christopher Tubbs (JIRA)]

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

Christopher Tubbs commented on MNG-5689:


I had a mirror with broken artifacts in it... which is what motivated me to 
create this. Maven was perfectly happy downloading the broken artifacts, 
warning about them (the default behavior), and then putting the broken 
artifacts on the class path when I built my application. It was a pain to 
figure out why my builds were failing. A strict "fail" checksum policy would 
have made it obvious.

> Checksum policy for mirrors
> ---
>
> Key: MNG-5689
> URL: https://issues.apache.org/jira/browse/MNG-5689
> Project: Maven
>  Issue Type: Improvement
>  Components: Settings
>Affects Versions: 3.2.3
>Reporter: Christopher Tubbs
>Priority: Major
>  Labels: security-issue
>
> It does not appear that there is any way to configure a checksum policy for 
> mirrors in the settings.xml file.
> In particular, I'd love to enforce a "strict" checksum policy on maven 
> central. I can configure a mirrorOf central, but I cannot set the checksum 
> policy. This seems like a big oversight.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSHARED-708) Upgrade org.ow2.asm:asm:6.0 to 6.1 JDK 10 issues

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MSHARED-708:
---

 Summary: Upgrade org.ow2.asm:asm:6.0 to 6.1 JDK 10 issues
 Key: MSHARED-708
 URL: https://issues.apache.org/jira/browse/MSHARED-708
 Project: Maven Shared Components
  Issue Type: Dependency upgrade
  Components: maven-dependency-analyzer
Affects Versions: maven-dependency-analyzer-1.8
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: maven-dependency-analyzer-1.9






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSHARED-707) Upgrade parent to 31

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MSHARED-707:
---

 Summary: Upgrade parent to 31
 Key: MSHARED-707
 URL: https://issues.apache.org/jira/browse/MSHARED-707
 Project: Maven Shared Components
  Issue Type: Dependency upgrade
  Components: maven-dependency-analyzer
Affects Versions: maven-dependency-analyzer-1.8
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: maven-dependency-analyzer-1.9






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJAVADOC-512:
-
Fix Version/s: 3.0.1

> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise reassigned MJAVADOC-512:


Assignee: Karl Heinz Marbaise

> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[Hudson (JIRA)]

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

Hudson commented on MJAVADOC-512:
-

Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-512 #2

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-512/2/

> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Priority: Minor
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJAVADOC-512:
-
Comment: was deleted

(was: JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375914890
 
 
   Would like to shameless plug two other pull requests
   
   - https://github.com/mojohaus/extra-enforcer-rules/pull/36
   - https://github.com/mojohaus/build-helper-maven-plugin/pull/32


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
)

> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Priority: Minor
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375916227
 
 
   Can you please remove the comments about the other projects here cause they 
do not belong here..a ping on the other projects would have worked also...


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Priority: Minor
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

khmarbaise commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375916227
 
 
   Can you please remove the comments about the other projects here cause they 
do not belong here..a ping on the other projects would have worked also...


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375914890
 
 
   Would like to shameless plug two other pull requests
   
   - https://github.com/mojohaus/extra-enforcer-rules/pull/36
   - https://github.com/mojohaus/build-helper-maven-plugin/pull/32


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Priority: Minor
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375914890
 
 
   Would like to shameless plug two other pull requests
   
   - https://github.com/mojohaus/extra-enforcer-rules/pull/36
   - https://github.com/mojohaus/build-helper-maven-plugin/pull/32


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MJAVADOC-512) Even when 1.8.0 matches there still is a warning.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-512:
-

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375912303
 
 
   Rebased and changed message of pull request and commit.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Even when 1.8.0 matches there still is a 
> warning.
> --
>
> Key: MJAVADOC-512
> URL: https://issues.apache.org/jira/browse/MJAVADOC-512
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 3.0.0
>Reporter: Jene Jasper
>Priority: Minor
>
> Even when {{1.8.0}} matches there still is 
> the following log message:
> {quote}[WARNING] Are you sure about the parameter? It seems to be 1.8.0.
> {quote}
>  
> See [https://github.com/apache/maven-javadoc-plugin/pull/1]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 1.8.0 matches there still is a warning.

[GitBox]

JeneJasper commented on issue #1: [MJAVADOC-512] - Even when 
1.8.0 matches there still is a warning.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375912303
 
 
   Rebased and changed message of pull request and commit.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Closed] (MARCHETYPES-60) switch to Git

[JIRA]

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

Hervé Boutemy closed MARCHETYPES-60.

Resolution: Fixed
  Assignee: Hervé Boutemy

> switch to Git
> -
>
> Key: MARCHETYPES-60
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-60
> Project: Maven Archetype Bundles
>  Issue Type: Task
>Affects Versions: maven-archetype-quickstart-1.2
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 1.3
>
>
> see INFRA-16087



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

Tibor17 commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375906501
 
 
@mpkorstanje  Should we change something
   in Surefire documentation? It seems we should according to this discussion.
   
   On Sat, Mar 24, 2018 at 2:38 PM, adarshkv  wrote:
   
   > @mpkorstanje  -- Any idea how we can
   > embed screenshot to XML report (surefire-XML report ?)... At present I am
   > attaching/ embedding the failed screenshot to html report.. *but I want
   > to embed the screenshot to surefire-maven XML report TEST.(.*).XML*
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > ,
   > or mute the thread
   > 

   > .
   >
   
   
   
   -- 
   Cheers
   Tibor
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] Tibor17 commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

Tibor17 commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375906501
 
 
@mpkorstanje  Should we change something
   in Surefire documentation? It seems we should according to this discussion.
   
   On Sat, Mar 24, 2018 at 2:38 PM, adarshkv  wrote:
   
   > @mpkorstanje  -- Any idea how we can
   > embed screenshot to XML report (surefire-XML report ?)... At present I am
   > attaching/ embedding the failed screenshot to html report.. *but I want
   > to embed the screenshot to surefire-maven XML report TEST.(.*).XML*
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > ,
   > or mute the thread
   > 

   > .
   >
   
   
   
   -- 
   Cheers
   Tibor
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Closed] (MRELEASE-1007) Rework usage workingDirectory and commonBasedir

[Robert Scholte (JIRA)]

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

Robert Scholte closed MRELEASE-1007.

   Resolution: Fixed
Fix Version/s: 3.0.0

Fixed in 
[9ea29a796d0e6191bebdf9accf4338fde541195d|https://gitbox.apache.org/repos/asf?p=maven-release.git;a=commit;h=9ea29a796d0e6191bebdf9accf4338fde541195d]

> Rework usage workingDirectory and commonBasedir
> ---
>
> Key: MRELEASE-1007
> URL: https://issues.apache.org/jira/browse/MRELEASE-1007
> Project: Maven Release Plugin
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0
>
>
> All over the code are recalculations based on commonbasedir and 
> workingdirectory. Add several places the usage is unclear and is the 
> intention hard to read. Quite often they're simply the same.
> Better to use the commonbasedir as the workingdirectory and calculate the 
> pomFile(s) relative to the working directory.
> This step is required to better control the plugin when using an aggregator 
> to do multiple releases at once. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRELEASE-1007) Rework usage workingDirectory and commonBasedir

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412677#comment-16412677
 ] 

Hudson commented on MRELEASE-1007:
--

Build succeeded in Jenkins: Maven TLP » maven-release » master #42

See https://builds.apache.org/job/maven-box/job/maven-release/job/master/42/

> Rework usage workingDirectory and commonBasedir
> ---
>
> Key: MRELEASE-1007
> URL: https://issues.apache.org/jira/browse/MRELEASE-1007
> Project: Maven Release Plugin
>  Issue Type: Improvement
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
>
> All over the code are recalculations based on commonbasedir and 
> workingdirectory. Add several places the usage is unclear and is the 
> intention hard to read. Quite often they're simply the same.
> Better to use the commonbasedir as the workingdirectory and calculate the 
> pomFile(s) relative to the working directory.
> This step is required to better control the plugin when using an aggregator 
> to do multiple releases at once. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSHARED-698) Change the package to org.apache.maven.shared.transfer.*

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MSHARED-698:

Summary: Change the package to org.apache.maven.shared.transfer.*  (was: 
Change the package to org.apache.maven.shared.(artifact.?)transfer)

> Change the package to org.apache.maven.shared.transfer.*
> 
>
> Key: MSHARED-698
> URL: https://issues.apache.org/jira/browse/MSHARED-698
> Project: Maven Shared Components
>  Issue Type: Task
>  Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.10.0
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-0.10.0
>
>
> We should change the package from {{org.apache.maven.shared}} to 
> {{org.apache.maven.shared.transfer.*}} to be in line with other shared 
> components.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSHARED-698) Change the package to org.apache.maven.shared.(artifact.?)transfer

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MSHARED-698:

Description: We should change the package from {{org.apache.maven.shared}} 
to {{org.apache.maven.shared.transfer.*}} to be in line with other shared 
components.  (was: We should change the package from 
{{org.apache.maven.shared}} to {{org.apache.maven.shared.artifact.transfer}} or 
maybe {{org.apache.maven.shared.transfer}}.)

> Change the package to org.apache.maven.shared.(artifact.?)transfer
> --
>
> Key: MSHARED-698
> URL: https://issues.apache.org/jira/browse/MSHARED-698
> Project: Maven Shared Components
>  Issue Type: Task
>  Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.10.0
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-0.10.0
>
>
> We should change the package from {{org.apache.maven.shared}} to 
> {{org.apache.maven.shared.transfer.*}} to be in line with other shared 
> components.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375890028
 
 
   @mpkorstanje  -- Any idea how we can embed screenshot to XML report 
(surefire-XML report ?)... At present I am attaching/ embedding the failed 
screenshot to html report.. **but I want to embed the screenshot to 
surefire-maven XML report TEST.(.*).XML**


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375890028
 
 
   @mpkorstanje  -- Any idea how we can embed screenshot to XML report 
(surefire-XML report ?)... At present I am attaching/ embedding the failed 
screenshot to html report.. **but I want to embed the screenshot to 
surefire-maven XML report TEST.(.*).XML**


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375889645
 
 
   Thanks a lot @mpkorstanje ... My issue is fixed with this change  


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375889645
 
 
   Thanks a lot @mpkorstanje ... My issue is fixed with this change  


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Assigned] (MJAVADOC-519) IT detectLinks fails on Windows

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise reassigned MJAVADOC-519:


Assignee: Karl Heinz Marbaise

> IT detectLinks fails on Windows
> ---
>
> Key: MJAVADOC-519
> URL: https://issues.apache.org/jira/browse/MJAVADOC-519
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.1
>
> Attachments: failing-javadoc-it.log
>
>
> [Currently|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]
>  the following IT is failing:
> {code}
> [windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] The following builds failed:
> [windows-jdk9] [WARNING] *  detectLinks\pom.xml
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] Ignoring that 1 build failed.
> [windows-jdk9] [INFO] 
> 
> [windows-jdk9] [INFO] BUILD SUCCESS
> [windows-jdk9] [INFO] ---
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJAVADOC-519) IT detectLinks fails on Windows

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJAVADOC-519:
-
Summary: IT detectLinks fails on Windows  (was: IT's detectLinks fails on 
Windows)

> IT detectLinks fails on Windows
> ---
>
> Key: MJAVADOC-519
> URL: https://issues.apache.org/jira/browse/MJAVADOC-519
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.1
>
> Attachments: failing-javadoc-it.log
>
>
> [Currently|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]
>  the following IT is failing:
> {code}
> [windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] The following builds failed:
> [windows-jdk9] [WARNING] *  detectLinks\pom.xml
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] Ignoring that 1 build failed.
> [windows-jdk9] [INFO] 
> 
> [windows-jdk9] [INFO] BUILD SUCCESS
> [windows-jdk9] [INFO] ---
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375887187
 
 
   Try `@CucumberOptions(junit = "--step-notifications")`. Forgot to remove the 
*-no* before copying.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 
>
> Key: SUREFIRE-1372
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1372
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: Maven Surefire Plugin
>Affects Versions: 2.20
>Reporter: M.P. Korstanje
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 2.21.0
>
>
> When using surefire to rerun failing tests created by a Runner that uses 
> {noformat}Description#createSuiteDescription{noformat} with a human readable 
> name rather then a class name the following stack trace occurs:
> {code}
> org.apache.maven.surefire.testset.TestSetFailedException: Unable to create 
> test class 'Scenario: Fail when running'
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:385)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> Caused by: java.lang.ClassNotFoundException: Scenario: Fail when running
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeFailedMethod(JUnit4Provider.java:379)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:292)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

mpkorstanje commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375887187
 
 
   Try `@CucumberOptions(junit = "--step-notifications")`. Forgot to remove the 
*-no* before copying.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Updated] (MJAVADOC-519) IT's detectLinks fails on Windows

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJAVADOC-519:
-
Attachment: failing-javadoc-it.log

> IT's detectLinks fails on Windows
> -
>
> Key: MJAVADOC-519
> URL: https://issues.apache.org/jira/browse/MJAVADOC-519
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.1
>
> Attachments: failing-javadoc-it.log
>
>
> [Currently|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]
>  the following IT is failing:
> {code}
> [windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] The following builds failed:
> [windows-jdk9] [WARNING] *  detectLinks\pom.xml
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] Ignoring that 1 build failed.
> [windows-jdk9] [INFO] 
> 
> [windows-jdk9] [INFO] BUILD SUCCESS
> [windows-jdk9] [INFO] ---
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-520) Upgrade plexus-utils/qdox/plexus-archiver/

[Hudson (JIRA)]

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

Hudson commented on MJAVADOC-520:
-

Build unstable in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-520 #2

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-520/2/

> Upgrade plexus-utils/qdox/plexus-archiver/
> --
>
> Key: MJAVADOC-520
> URL: https://issues.apache.org/jira/browse/MJAVADOC-520
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> * plexus-utils to 3.1.0
> * qdox to 2.0-M8
> * plexus-archiver 3.5
> * plexus-utils-3.1.0
> * maven-archiver 3.2.0
> * plexus-interactivity-api 1.0-alpha-6



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MARCHETYPES-60) switch to Git

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MARCHETYPES-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412579#comment-16412579
 ] 

Hudson commented on MARCHETYPES-60:
---

SUCCESS: Integrated in Jenkins build maven-archetypes #135 (See 
[https://builds.apache.org/job/maven-archetypes/135/])
[MARCHETYPES-60] switched to Git (hboutemy: 
[http://svn.apache.org/viewvc/?view=rev=1827636])
* (add) MOVED_TO_GIT


> switch to Git
> -
>
> Key: MARCHETYPES-60
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-60
> Project: Maven Archetype Bundles
>  Issue Type: Task
>Affects Versions: maven-archetype-quickstart-1.2
>Reporter: Hervé Boutemy
>Priority: Major
> Fix For: 1.3
>
>
> see INFRA-16087



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJMOD-13) Upgrade plexus-java 0.9.7

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MJMOD-13.

Resolution: Fixed

Done in 
[394e20bc1973af783c96cb4ffa1326785413be6a|https://gitbox.apache.org/repos/asf?p=maven-jmod-plugin.git;a=commitdiff;h=394e20bc1973af783c96cb4ffa1326785413be6a]

> Upgrade plexus-java 0.9.7
> -
>
> Key: MJMOD-13
> URL: https://issues.apache.org/jira/browse/MJMOD-13
> Project: Maven JMod Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJLINK-15) Upgrade plexus-java 0.9.7

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MJLINK-15.
-
Resolution: Fixed

Done in 
[1bdeddacd525cc4537fc2b09f5bb3c27fd753ddd|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=1bdeddacd525cc4537fc2b09f5bb3c27fd753ddd]

> Upgrade plexus-java 0.9.7
> -
>
> Key: MJLINK-15
> URL: https://issues.apache.org/jira/browse/MJLINK-15
> Project: Maven JLink Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJLINK-15) Upgrade plexus-java 0.9.7

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJLINK-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412572#comment-16412572
 ] 

Hudson commented on MJLINK-15:
--

Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » master #7

See https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/master/7/

> Upgrade plexus-java 0.9.7
> -
>
> Key: MJLINK-15
> URL: https://issues.apache.org/jira/browse/MJLINK-15
> Project: Maven JLink Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJMOD-13) Upgrade plexus-java 0.9.7

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/MJMOD-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412573#comment-16412573
 ] 

Hudson commented on MJMOD-13:
-

Build succeeded in Jenkins: Maven TLP » maven-jmod-plugin » master #6

See https://builds.apache.org/job/maven-box/job/maven-jmod-plugin/job/master/6/

> Upgrade plexus-java 0.9.7
> -
>
> Key: MJMOD-13
> URL: https://issues.apache.org/jira/browse/MJMOD-13
> Project: Maven JMod Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MPOM-184) Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 issues

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MPOM-184:


 Summary: Upgrade maven-surefie/failsafe to 2.21.0 based on JDK 10 
issues
 Key: MPOM-184
 URL: https://issues.apache.org/jira/browse/MPOM-184
 Project: Maven POMs
  Issue Type: Dependency upgrade
  Components: doxia-tools, maven-plugins, maven-shared-components
Affects Versions: MAVEN-31
Reporter: Karl Heinz Marbaise
 Fix For: MAVEN-32






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJAVADOC-515) Upgrade parent to 31

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MJAVADOC-515.

Resolution: Fixed

Done in 
[e637834a1aecaaa835fe2cdcda67664156f3630d|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]

> Upgrade parent to 31
> 
>
> Key: MJAVADOC-515
> URL: https://issues.apache.org/jira/browse/MJAVADOC-515
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MRELEASE-1007) Rework usage workingDirectory and commonBasedir

[Robert Scholte (JIRA)]

Robert Scholte created MRELEASE-1007:


 Summary: Rework usage workingDirectory and commonBasedir
 Key: MRELEASE-1007
 URL: https://issues.apache.org/jira/browse/MRELEASE-1007
 Project: Maven Release Plugin
  Issue Type: Improvement
Reporter: Robert Scholte
Assignee: Robert Scholte


All over the code are recalculations based on commonbasedir and 
workingdirectory. Add several places the usage is unclear and is the intention 
hard to read. Quite often they're simply the same.

Better to use the commonbasedir as the workingdirectory and calculate the 
pomFile(s) relative to the working directory.

This step is required to better control the plugin when using an aggregator to 
do multiple releases at once. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJAVADOC-520) Upgrade plexus-utils/qdox/plexus-archiver/

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJAVADOC-520:
-
Description: 
* plexus-utils to 3.1.0
* qdox to 2.0-M8
* plexus-archiver 3.5
* plexus-utils-3.1.0
* maven-archiver 3.2.0
* plexus-interactivity-api 1.0-alpha-6

  was:
* plexus-utils to 3.1.0
* qdox to 2.0-M8
* plexus-archiver 3.5
* plexus-utils-3.1.0
* maven-archiver 3.2.0


> Upgrade plexus-utils/qdox/plexus-archiver/
> --
>
> Key: MJAVADOC-520
> URL: https://issues.apache.org/jira/browse/MJAVADOC-520
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> * plexus-utils to 3.1.0
> * qdox to 2.0-M8
> * plexus-archiver 3.5
> * plexus-utils-3.1.0
> * maven-archiver 3.2.0
> * plexus-interactivity-api 1.0-alpha-6



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MJAVADOC-520) Upgrade plexus-utils/qdox/plexus-archiver/

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJAVADOC-520:


 Summary: Upgrade plexus-utils/qdox/plexus-archiver/
 Key: MJAVADOC-520
 URL: https://issues.apache.org/jira/browse/MJAVADOC-520
 Project: Maven Javadoc Plugin
  Issue Type: Dependency upgrade
Affects Versions: 3.0.1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.1


* plexus-utils to 3.1.0
* qdox to 2.0-M8
* plexus-archiver 3.5
* plexus-utils-3.1.0
* maven-archiver 3.2.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (SCM-829) CommandParameter incorrectly removed from parameter list

[Michael Osipov (JIRA)]

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

Michael Osipov closed SCM-829.
--
Resolution: Fixed

Fixed with 
[8d7613c0b3c5b6337fee01baf9648b0ca3550509|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=8d7613c0b3c5b6337fee01baf9648b0ca3550509].

> CommandParameter incorrectly removed from parameter list
> 
>
> Key: SCM-829
> URL: https://issues.apache.org/jira/browse/SCM-829
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-api
>Affects Versions: 1.9.4
>Reporter: Dave Brosius
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 1.9.6
>
>
> https://github.com/apache/maven-scm/compare/master...mebigfatguy:master



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SCM-829) CommandParameter incorrectly removed from parameter list

[Michael Osipov (JIRA)]

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

Michael Osipov updated SCM-829:
---
Fix Version/s: 1.9.6

> CommandParameter incorrectly removed from parameter list
> 
>
> Key: SCM-829
> URL: https://issues.apache.org/jira/browse/SCM-829
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-api
>Affects Versions: 1.9.4
>Reporter: Dave Brosius
>Assignee: Michael Osipov
>Priority: Trivial
> Fix For: 1.9.6
>
>
> https://github.com/apache/maven-scm/compare/master...mebigfatguy:master



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJAVADOC-519) IT's detectLinks fails on Windows

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise updated MJAVADOC-519:
-
Description: 
[Currently|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]
 the following IT is failing:
{code}
[windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
[windows-jdk9] [INFO] -
[windows-jdk9] [WARNING] The following builds failed:
[windows-jdk9] [WARNING] *  detectLinks\pom.xml
[windows-jdk9] [INFO] -
[windows-jdk9] [WARNING] Ignoring that 1 build failed.
[windows-jdk9] [INFO] 

[windows-jdk9] [INFO] BUILD SUCCESS
[windows-jdk9] [INFO] ---
{code}

  was:
Currently the following IT is failing:
{code}
[windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
[windows-jdk9] [INFO] -
[windows-jdk9] [WARNING] The following builds failed:
[windows-jdk9] [WARNING] *  detectLinks\pom.xml
[windows-jdk9] [INFO] -
[windows-jdk9] [WARNING] Ignoring that 1 build failed.
[windows-jdk9] [INFO] 

[windows-jdk9] [INFO] BUILD SUCCESS
[windows-jdk9] [INFO] ---
{code}


> IT's detectLinks fails on Windows
> -
>
> Key: MJAVADOC-519
> URL: https://issues.apache.org/jira/browse/MJAVADOC-519
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 3.0.1
>
>
> [Currently|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=e637834a1aecaaa835fe2cdcda67664156f3630d]
>  the following IT is failing:
> {code}
> [windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] The following builds failed:
> [windows-jdk9] [WARNING] *  detectLinks\pom.xml
> [windows-jdk9] [INFO] -
> [windows-jdk9] [WARNING] Ignoring that 1 build failed.
> [windows-jdk9] [INFO] 
> 
> [windows-jdk9] [INFO] BUILD SUCCESS
> [windows-jdk9] [INFO] ---
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SUREFIRE-1372) Rerunning failing tests fails in combination with Description#createSuiteDescription

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SUREFIRE-1372:
--

adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375872140
 
 
   @mpkorstanje -- Thank you.. I did try by providing @CucumberOptions(junit = 
"--no-step-notifications") . but no luck.. I need each step to be show in my 
report.
   
   Please find below my runner file  - Parallel01it.java (parallel execution)
   
   @RunWith(Cucumber.class)
   @CucumberOptions(
   strict = true,
   features = 
{"/Automation/WOW-Automation-Web/src/test/resources/features/TestScenario.feature:5"},
   plugin = {"pretty", 
"junit:/Automation/Automation-Web/target/cucumber-parallel/1.xml", 
"html:/Automation/Automation-Web/target/cucumber-parallel/1", 
"json:/Automation/Automation-Web/target/cucumber-parallel/1.json", 
"rerun:/Automation/Automation-Web/target/cucumber-parallel/1.txt"},
   junit = "--no-step-notifications",
   monochrome = true,
   glue = {"steps"})
   
   
   **Below is the my XML file if I am using io.cucumber as group id for 
execution (cucumber-jvm v 2.4.0) --- Rerun works perfectly fine but testcase 
name is missing**
   
   Below is what I am getting at present:
   
   
![image](https://user-images.githubusercontent.com/33118961/37863208-9c2b116e-2fae-11e8-98aa-04854949928a.png)
   
   
 testcase name="Sign Up Verify That Error Message Is Shown If Any Of The 
Mandatory Field Is Left Blank" classname="Sign Up Verify That Error Message Is 
Shown If Any Of The Mandatory Field Is Left Blank" time="18.391"/>
   
   **Below is my XML file if i am using info.cukes as group ID for execution 
(cucumber-jvm v 1.2.5) -- Rerun doesnt work here but test case name is 
available.**
   
 testcase name="Given I am on the home page" classname="Scenario: Sign Up 
Verify That Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="0"/>
 testcase name="When I click on Login Profile on home page" 
classname="Scenario: Sign Up Verify That Error Message Is Shown If Any Of The 
Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I click on sign up in login page" classname="Scenario: 
Sign Up Verify That Error Message Is Shown If Any Of The Mandatory Field Is 
Left Blank" time="0"/>
 testcase name="Then I click on Sign Up" classname="Scenario: Sign Up 
Verify That Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="0"/>
 testcase name="And I should see the valid message The sign up was 
not successful. and There are 6 field(s) that require your 
attention." classname="Scenario: Sign Up Verify That Error Message Is 
Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for first name First 
name is required." classname="Scenario: Sign Up Verify That Error Message 
Is Shown If Any Of The Mandatory Field Is Left Blank" time="0.008"/>
 testcase name="And I should see error message for last name Last 
name is required." classname="Scenario: Sign Up Verify That Error Message 
Is Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for email address 
Email address is required." classname="Scenario: Sign Up Verify 
That Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="0"/>
 testcase name="And I should see error message for password Password 
is required." classname="Scenario: Sign Up Verify That Error Message Is 
Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for preferred contact number 
Phone number is required." classname="Scenario: Sign Up Verify That 
Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for delivery address 
Address is required." classname="Scenario: Sign Up Verify That 
Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="Scenario: Sign Up Verify That Error Message Is Shown If Any 
Of The Mandatory Field Is Left Blank" classname="Scenario: Sign Up Verify That 
Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="1.288"/>
   
   
   
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Rerunning failing tests fails in combination with 
> Description#createSuiteDescription
> 

[GitHub] adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by description

[GitBox]

adarshkv commented on issue #150: SUREFIRE-1372 Filter tests to be rerun by 
description
URL: https://github.com/apache/maven-surefire/pull/150#issuecomment-375872140
 
 
   @mpkorstanje -- Thank you.. I did try by providing @CucumberOptions(junit = 
"--no-step-notifications") . but no luck.. I need each step to be show in my 
report.
   
   Please find below my runner file  - Parallel01it.java (parallel execution)
   
   @RunWith(Cucumber.class)
   @CucumberOptions(
   strict = true,
   features = 
{"/Automation/WOW-Automation-Web/src/test/resources/features/TestScenario.feature:5"},
   plugin = {"pretty", 
"junit:/Automation/Automation-Web/target/cucumber-parallel/1.xml", 
"html:/Automation/Automation-Web/target/cucumber-parallel/1", 
"json:/Automation/Automation-Web/target/cucumber-parallel/1.json", 
"rerun:/Automation/Automation-Web/target/cucumber-parallel/1.txt"},
   junit = "--no-step-notifications",
   monochrome = true,
   glue = {"steps"})
   
   
   **Below is the my XML file if I am using io.cucumber as group id for 
execution (cucumber-jvm v 2.4.0) --- Rerun works perfectly fine but testcase 
name is missing**
   
   Below is what I am getting at present:
   
   
![image](https://user-images.githubusercontent.com/33118961/37863208-9c2b116e-2fae-11e8-98aa-04854949928a.png)
   
   
 testcase name="Sign Up Verify That Error Message Is Shown If Any Of The 
Mandatory Field Is Left Blank" classname="Sign Up Verify That Error Message Is 
Shown If Any Of The Mandatory Field Is Left Blank" time="18.391"/>
   
   **Below is my XML file if i am using info.cukes as group ID for execution 
(cucumber-jvm v 1.2.5) -- Rerun doesnt work here but test case name is 
available.**
   
 testcase name="Given I am on the home page" classname="Scenario: Sign Up 
Verify That Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="0"/>
 testcase name="When I click on Login Profile on home page" 
classname="Scenario: Sign Up Verify That Error Message Is Shown If Any Of The 
Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I click on sign up in login page" classname="Scenario: 
Sign Up Verify That Error Message Is Shown If Any Of The Mandatory Field Is 
Left Blank" time="0"/>
 testcase name="Then I click on Sign Up" classname="Scenario: Sign Up 
Verify That Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="0"/>
 testcase name="And I should see the valid message The sign up was 
not successful. and There are 6 field(s) that require your 
attention." classname="Scenario: Sign Up Verify That Error Message Is 
Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for first name First 
name is required." classname="Scenario: Sign Up Verify That Error Message 
Is Shown If Any Of The Mandatory Field Is Left Blank" time="0.008"/>
 testcase name="And I should see error message for last name Last 
name is required." classname="Scenario: Sign Up Verify That Error Message 
Is Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for email address 
Email address is required." classname="Scenario: Sign Up Verify 
That Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="0"/>
 testcase name="And I should see error message for password Password 
is required." classname="Scenario: Sign Up Verify That Error Message Is 
Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for preferred contact number 
Phone number is required." classname="Scenario: Sign Up Verify That 
Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="And I should see error message for delivery address 
Address is required." classname="Scenario: Sign Up Verify That 
Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" time="0"/>
 testcase name="Scenario: Sign Up Verify That Error Message Is Shown If Any 
Of The Mandatory Field Is Left Blank" classname="Scenario: Sign Up Verify That 
Error Message Is Shown If Any Of The Mandatory Field Is Left Blank" 
time="1.288"/>
   
   
   
   
   
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (MJAVADOC-519) IT's detectLinks fails on Windows

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJAVADOC-519:


 Summary: IT's detectLinks fails on Windows
 Key: MJAVADOC-519
 URL: https://issues.apache.org/jira/browse/MJAVADOC-519
 Project: Maven Javadoc Plugin
  Issue Type: Bug
Affects Versions: 3.0.1
Reporter: Karl Heinz Marbaise
 Fix For: 3.0.1


Currently the following IT is failing:
{code}
[windows-jdk9] [INFO]   Passed: 35, Failed: 1, Errors: 0, Skipped: 0
[windows-jdk9] [INFO] -
[windows-jdk9] [WARNING] The following builds failed:
[windows-jdk9] [WARNING] *  detectLinks\pom.xml
[windows-jdk9] [INFO] -
[windows-jdk9] [WARNING] Ignoring that 1 build failed.
[windows-jdk9] [INFO] 

[windows-jdk9] [INFO] BUILD SUCCESS
[windows-jdk9] [INFO] ---
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRELEASE-799) update-versions fails when the project artifact is used with a version other than the current snapshot

[Robert Scholte (JIRA)]

[ 
https://issues.apache.org/jira/browse/MRELEASE-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16412520#comment-16412520
 ] 

Robert Scholte commented on MRELEASE-799:
-

[~mirabilos], can you add a small project (just the poms) to reproduce this 
issue? This'll make it easier to fix.

> update-versions fails when the project artifact is used with a version other 
> than the current snapshot
> --
>
> Key: MRELEASE-799
> URL: https://issues.apache.org/jira/browse/MRELEASE-799
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: update-versions
>Affects Versions: 2.3.2
> Environment: maven 2.2.1, maven 3.0.3
>Reporter: Péter Miklós
>Priority: Major
>
> If a maven project uses its own artifact eg. as a dependency of a plugin with 
> a version other than the current snapshot then release:update-versions will 
> fail with an error like this:
> bq. The artifact (com.example:test) requires a different version (3.1.50) 
> than what is found (3.1.49) for the expression (lastReleasedProjectVersion) 
> in the project (com.example:test)
> Basically, the latest release of the same artifact is used for some sort of 
> regression testing and it seems that the update-versions, after moving to the 
> next release version from snapshot, notices that there is a discrepancy 
> between the new release version and the version used as a plugin dependency.
> This error popped up when I started to use release plugin 2.2.2 and as a 
> result of MRELEASE-412 the properties used in the version tag are also 
> updated.
> I think the update-versions should remember which artifacts have been updated 
> from snapshot to the new release version, and then check those only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (MRELEASE-799) update-versions fails when the project artifact is used with a version other than the current snapshot

[Michael Osipov (JIRA)]

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

Michael Osipov reopened MRELEASE-799:
-

reopening per request

> update-versions fails when the project artifact is used with a version other 
> than the current snapshot
> --
>
> Key: MRELEASE-799
> URL: https://issues.apache.org/jira/browse/MRELEASE-799
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: update-versions
>Affects Versions: 2.3.2
> Environment: maven 2.2.1, maven 3.0.3
>Reporter: Péter Miklós
>Priority: Major
>
> If a maven project uses its own artifact eg. as a dependency of a plugin with 
> a version other than the current snapshot then release:update-versions will 
> fail with an error like this:
> bq. The artifact (com.example:test) requires a different version (3.1.50) 
> than what is found (3.1.49) for the expression (lastReleasedProjectVersion) 
> in the project (com.example:test)
> Basically, the latest release of the same artifact is used for some sort of 
> regression testing and it seems that the update-versions, after moving to the 
> next release version from snapshot, notices that there is a discrepancy 
> between the new release version and the version used as a plugin dependency.
> This error popped up when I started to use release plugin 2.2.2 and as a 
> result of MRELEASE-412 the properties used in the version tag are also 
> updated.
> I think the update-versions should remember which artifacts have been updated 
> from snapshot to the new release version, and then check those only.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-5689) Checksum policy for mirrors

[Michael Osipov (JIRA)]

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

Michael Osipov commented on MNG-5689:
-

There is non that I am aware of.  You could always go via a repo manager. Have 
you tried to setup a minimal mirror with broken artifacts and see what Maven 
says?

> Checksum policy for mirrors
> ---
>
> Key: MNG-5689
> URL: https://issues.apache.org/jira/browse/MNG-5689
> Project: Maven
>  Issue Type: Improvement
>  Components: Settings
>Affects Versions: 3.2.3
>Reporter: Christopher Tubbs
>Priority: Major
>  Labels: security-issue
>
> It does not appear that there is any way to configure a checksum policy for 
> mirrors in the settings.xml file.
> In particular, I'd love to enforce a "strict" checksum policy on maven 
> central. I can configure a mirrorOf central, but I cannot set the checksum 
> policy. This seems like a big oversight.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-515) Upgrade parent to 31

[Hudson (JIRA)]

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

Hudson commented on MJAVADOC-515:
-

Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » master #28

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/28/

> Upgrade parent to 31
> 
>
> Key: MJAVADOC-515
> URL: https://issues.apache.org/jira/browse/MJAVADOC-515
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] khmarbaise commented on issue #1: Fix warning for 1.8.0.

[GitBox]

khmarbaise commented on issue #1: Fix warning for 
1.8.0.
URL: 
https://github.com/apache/maven-javadoc-plugin/pull/1#issuecomment-375859770
 
 
   Hi, can you please update your pr to rebase against current master and 
enhance the commit message like:
   ```
   [MJAVADOC-512] - Even when 1.8.0 matches 
there still is a warning.
   ```
   I would appreciate to merge your PR...
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (MJMOD-13) Upgrade plexus-java 0.9.7

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJMOD-13:


 Summary: Upgrade plexus-java 0.9.7
 Key: MJMOD-13
 URL: https://issues.apache.org/jira/browse/MJMOD-13
 Project: Maven JMod Plugin
  Issue Type: Improvement
Affects Versions: 3.0.0-alpha-2
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0-alpha-2






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-515) Upgrade parent to 31

[Hudson (JIRA)]

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

Hudson commented on MJAVADOC-515:
-

Build succeeded in Jenkins: Maven TLP » maven-javadoc-plugin » MJAVADOC-515 #5

See 
https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/MJAVADOC-515/5/

> Upgrade parent to 31
> 
>
> Key: MJAVADOC-515
> URL: https://issues.apache.org/jira/browse/MJAVADOC-515
> Project: Maven Javadoc Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MJLINK-15) Upgrade plexus-java 0.9.7

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MJLINK-15:
-

 Summary: Upgrade plexus-java 0.9.7
 Key: MJLINK-15
 URL: https://issues.apache.org/jira/browse/MJLINK-15
 Project: Maven JLink Plugin
  Issue Type: Improvement
Affects Versions: 3.0.0-alpha-2
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0-alpha-2






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSHARED-706) Upgrade parent to 31

[Karl Heinz Marbaise (JIRA)]

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

Karl Heinz Marbaise closed MSHARED-706.
---
Resolution: Fixed

Done in 
[4525661e738f8b45ef3922d0ebb265d879522d40|https://gitbox.apache.org/repos/asf?p=maven-file-management.git;a=commitdiff;h=4525661e738f8b45ef3922d0ebb265d879522d40]

> Upgrade parent to 31
> 
>
> Key: MSHARED-706
> URL: https://issues.apache.org/jira/browse/MSHARED-706
> Project: Maven Shared Components
>  Issue Type: Improvement
>  Components: file-management
>Affects Versions: file-management-3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: file-management-3.0.1
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)