[jira] [Updated] (MRELEASE-943) be more tolerant with project version

[Romain Manni-Bucau (JIRA)]

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

Romain Manni-Bucau updated MRELEASE-943:

Description: 
Edit/Note: this task has been split in 3 other tickets (linked), please keep 
this one as an umbrella task to ensure the goal is complete and not partially 
fixed only

In current version of maven-release-manager, the project version is quite 
strict and several cases are not handled preventing mvn release plugin to be 
used:

1- version aliases (${project.version}), it can 
makes sense to use that in some projects and is sometimes a way to avoid to 
spend nights rewriting multiple poms. This is ignored in hierarchic projects 
(at least 2 or 3 levels).
2- children not listing the parent. If the parent list children and children 
doesn't list the parent cause the goal is to let them be checkout directly then 
the child version is not handled by the mvn release plugin at all.
3- support autoVersionModules with multiple versions (just removing SNAPSHOT 
instead of applying parent version to all poms)

Would be great to at least have a flag to support 2 and detect properly or have 
a list of tolerated expressions as alias of the project version in the plugin 
(= tolerate 1). 3 is a nice to have.

Note: if it can help tomee project does it and the number of poms - ~251 poms 
(144 follow rule 2) - justified historically the rule 1.

  was:
In current version of maven-release-manager, the project version is quite 
strict and several cases are not handled preventing mvn release plugin to be 
used:

1- version aliases (${project.version}), it can 
makes sense to use that in some projects and is sometimes a way to avoid to 
spend nights rewriting multiple poms. This is ignored in hierarchic projects 
(at least 2 or 3 levels).
2- children not listing the parent. If the parent list children and children 
doesn't list the parent cause the goal is to let them be checkout directly then 
the child version is not handled by the mvn release plugin at all.
3- support autoVersionModules with multiple versions (just removing SNAPSHOT 
instead of applying parent version to all poms)

Would be great to at least have a flag to support 2 and detect properly or have 
a list of tolerated expressions as alias of the project version in the plugin 
(= tolerate 1). 3 is a nice to have.

Note: if it can help tomee project does it and the number of poms - ~251 poms 
(144 follow rule 2) - justified historically the rule 1.


> be more tolerant with project version
> -
>
> Key: MRELEASE-943
> URL: https://issues.apache.org/jira/browse/MRELEASE-943
> Project: Maven Release Plugin
>  Issue Type: Bug
>Reporter: Romain Manni-Bucau
>Priority: Major
>
> Edit/Note: this task has been split in 3 other tickets (linked), please keep 
> this one as an umbrella task to ensure the goal is complete and not partially 
> fixed only
> In current version of maven-release-manager, the project version is quite 
> strict and several cases are not handled preventing mvn release plugin to be 
> used:
> 1- version aliases (${project.version}), it can 
> makes sense to use that in some projects and is sometimes a way to avoid to 
> spend nights rewriting multiple poms. This is ignored in hierarchic projects 
> (at least 2 or 3 levels).
> 2- children not listing the parent. If the parent list children and children 
> doesn't list the parent cause the goal is to let them be checkout directly 
> then the child version is not handled by the mvn release plugin at all.
> 3- support autoVersionModules with multiple versions (just removing SNAPSHOT 
> instead of applying parent version to all poms)
> Would be great to at least have a flag to support 2 and detect properly or 
> have a list of tolerated expressions as alias of the project version in the 
> plugin (= tolerate 1). 3 is a nice to have.
> Note: if it can help tomee project does it and the number of poms - ~251 poms 
> (144 follow rule 2) - justified historically the rule 1.



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

[jira] [Commented] (MRELEASE-943) be more tolerant with project version

[Romain Manni-Bucau (JIRA)]

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

Romain Manni-Bucau commented on MRELEASE-943:
-

[~rfscholte] done

> be more tolerant with project version
> -
>
> Key: MRELEASE-943
> URL: https://issues.apache.org/jira/browse/MRELEASE-943
> Project: Maven Release Plugin
>  Issue Type: Bug
>Reporter: Romain Manni-Bucau
>Priority: Major
>
> Edit/Note: this task has been split in 3 other tickets (linked), please keep 
> this one as an umbrella task to ensure the goal is complete and not partially 
> fixed only
> In current version of maven-release-manager, the project version is quite 
> strict and several cases are not handled preventing mvn release plugin to be 
> used:
> 1- version aliases (${project.version}), it can 
> makes sense to use that in some projects and is sometimes a way to avoid to 
> spend nights rewriting multiple poms. This is ignored in hierarchic projects 
> (at least 2 or 3 levels).
> 2- children not listing the parent. If the parent list children and children 
> doesn't list the parent cause the goal is to let them be checkout directly 
> then the child version is not handled by the mvn release plugin at all.
> 3- support autoVersionModules with multiple versions (just removing SNAPSHOT 
> instead of applying parent version to all poms)
> Would be great to at least have a flag to support 2 and detect properly or 
> have a list of tolerated expressions as alias of the project version in the 
> plugin (= tolerate 1). 3 is a nice to have.
> Note: if it can help tomee project does it and the number of poms - ~251 poms 
> (144 follow rule 2) - justified historically the rule 1.



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

[jira] [Created] (MRELEASE-1003) support multiversions release with autoVersionModules=true

[Romain Manni-Bucau (JIRA)]

Romain Manni-Bucau created MRELEASE-1003:


 Summary: support multiversions release with autoVersionModules=true
 Key: MRELEASE-1003
 URL: https://issues.apache.org/jira/browse/MRELEASE-1003
 Project: Maven Release Plugin
  Issue Type: Task
Reporter: Romain Manni-Bucau


support autoVersionModules with multiple versions (just removing SNAPSHOT 
instead of applying parent version to all poms)



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

[jira] [Commented] (MNG-5600) Dependency management import should support exclusions.

[Deepak Abraham (JIRA)]

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

Deepak Abraham commented on MNG-5600:
-

Has this been fixed and added to the release build for maven 3.6?

> Dependency management import should support exclusions.
> ---
>
> Key: MNG-5600
> URL: https://issues.apache.org/jira/browse/MNG-5600
> Project: Maven
>  Issue Type: Improvement
>  Components: Dependencies
>Reporter: Radai Rosenblatt
>Priority: Major
> Fix For: 3.5.x-candidate
>
>
> suppose i have a multi-module project that uses spring, and so have this in 
> dependency-managements in a parent pom:
> {code:xml}
> 
>   org.springframework
>   spring-framework-bom
>   ${org.springframework.version}
>   pom
>   import   
> 
> {code}
> spring artifacts (or at least a lot of them) have a dependency on 
> commons-logging. right now, if i want to exclude commons-logging i have to 
> add an exclusion to every spring dependency in every module of my project, 
> which is actually more XML overall than giving up on using the bom dependency 
> altogether and listing all spring dependencies with excludes once in the 
> parent dependency management.
> I'd like to be able to do this:
> {code:xml}
> 
>   org.springframework
>   spring-framework-bom
>   ${org.springframework.version}
>   pom
>   import
>   
>   
>   commons-logging
>   commons-logging
>   
>   
> 
> {code}



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

[jira] [Created] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

Roberto Benedetti created MPIR-362:
--

 Summary: CLONE - Dependency Management report doesn't exclude 
system scoped dependencies
 Key: MPIR-362
 URL: https://issues.apache.org/jira/browse/MPIR-362
 Project: Maven Project Info Reports Plugin
  Issue Type: Bug
  Components: dependency-management
Affects Versions: 2.5.1
 Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
Reporter: Roberto Benedetti


{noformat}
[WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion 
from repository.
org.apache.maven.project.ProjectBuildingException: Error resolving project 
artifact: Failure to find com.sun:tools:pom:localVersion in 
http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the 
local repository, resolution will not be reattempted until the update interval 
of jclarity-central has elapsed or updates are forced for project 
com.sun:tools:pom:localVersion
at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
at 
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
at 
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
at 
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
at 
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at 
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at 
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at 
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at 
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at 

[jira] [Updated] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

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

Roberto Benedetti updated MPIR-362:
---
Affects Version/s: (was: 2.5.1)
   2.9

> CLONE - Dependency Management report doesn't exclude system scoped 
> dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>  Components: dependency-management
>Affects Versions: 2.9
> Environment: Mac OS X 10.7.2, Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34
>Reporter: Roberto Benedetti
>Priority: Major
>
> {noformat}
> [WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion 
> from repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project 
> artifact: Failure to find com.sun:tools:pom:localVersion in 
> http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the 
> local repository, resolution will not be reattempted until the update 
> interval of jclarity-central has elapsed or updates are forced for project 
> com.sun:tools:pom:localVersion
>   at 
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
>   at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
>   at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
>   at 
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
>   at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
>   at 
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
>   at 
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
>   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 

[jira] [Updated] (SUREFIRE-1492) Failsafe doesn't fail when a TestEngine throws an Error

[Mateusz Stefek (JIRA)]

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

Mateusz Stefek updated SUREFIRE-1492:
-
Description: 
My Jupiter engine fails due to some classloader hell. The logs are below. But 
that's not the point.

In such case, {{maven-failsafe-plugin}} should fail, but it exits as if nothing 
happened. Even with  {{failIfNoTests>true}} the plugin finishes 
and generates {{failsafe-summary.xml}} with {{0}}

{noformat}
Forking command line: cmd.exe /X /C ""C:\Program 
Files\Java\jdk1.8.0_91\jre\bin\java" -jar 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefirebooter5276177102867119205.jar
 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefire268158133198646317tmp
 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefire_05629521514361875618tmp"
Mar 01, 2018 12:29:15 PM org.junit.platform.launcher.core.DefaultLauncher 
handleThrowable
WARNING: TestEngine with ID 'junit-jupiter' failed to discover tests
java.lang.BootstrapMethodError: java.lang.NoSuchMethodError: 
org.junit.platform.commons.util.ReflectionUtils.isNotPrivate(Ljava/lang/reflect/Member;)Z
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveContainedMethods(JavaElementsResolver.java:189)
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveChildren(JavaElementsResolver.java:177)
at java.lang.Iterable.forEach(Iterable.java:75)
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveClass(JavaElementsResolver.java:61)
at 
org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.lambda$resolve$3(DiscoverySelectorResolver.java:69)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at 
org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.resolve(DiscoverySelectorResolver.java:68)
at 
org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.resolveSelectors(DiscoverySelectorResolver.java:50)
at 
org.junit.jupiter.engine.JupiterTestEngine.discover(JupiterTestEngine.java:61)
at 
org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:130)
at 
org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:117)
at 
org.junit.platform.launcher.core.DefaultLauncher.discover(DefaultLauncher.java:82)
at 
org.junit.platform.surefire.provider.TestPlanScannerFilter.accept(TestPlanScannerFilter.java:50)
at 
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:98)
at 
org.junit.platform.surefire.provider.JUnitPlatformProvider.scanClasspath(JUnitPlatformProvider.java:121)
at 
org.junit.platform.surefire.provider.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:111)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.lang.NoSuchMethodError: 
org.junit.platform.commons.util.ReflectionUtils.isNotPrivate(Ljava/lang/reflect/Member;)Z
at java.lang.invoke.MethodHandleNatives.resolve(Native Method)
at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:977)
at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1002)
at java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1390)
at 
java.lang.invoke.MethodHandles$Lookup.linkMethodHandleConstant(MethodHandles.java:1746)
at 
java.lang.invoke.MethodHandleNatives.linkMethodHandleConstant(MethodHandleNatives.java:477)
... 19 more

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{noformat}
 

  was:
My Jupiter engine fails due to some classloader hell. The logs are below. But 
that's not the point. In such case, the build should fail, but the plugin 
exists as if nothing happened. Even with  
{{failIfNoTests>true}} the plugin finishes and generates 
{{failsafe-summary.xml}} with {{0}}

{noformat}
Forking command line: cmd.exe /X /C ""C:\Program 
Files\Java\jdk1.8.0_91\jre\bin\java" -jar 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefirebooter5276177102867119205.jar
 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefire268158133198646317tmp
 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefire_05629521514361875618tmp"
Mar 01, 2018 12:29:15 PM org.junit.platform.launcher.core.DefaultLauncher 
handleThrowable
WARNING: TestEngine with ID 'junit-jupiter' failed to discover tests
java.lang.BootstrapMethodError: java.lang.NoSuchMethodError: 
org.junit.platform.commons.util.ReflectionUtils.isNotPrivate(Ljava/lang/reflect/Member;)Z
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveContainedMethods(JavaElementsResolver.java:189)
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveChildren(JavaElementsResolver.java:177)
at java.lang.Iterable.forEach(Iterable.java:75)
at 

[jira] [Updated] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

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

Roberto Benedetti updated MPIR-362:
---
Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161  (was: Mac OS X 10.7.2, 
Maven 3.0.4, JDK 1.7.0_06 / JDK 1.6.0_34)

> CLONE - Dependency Management report doesn't exclude system scoped 
> dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>  Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Priority: Major
>
> {noformat}
> [WARNING] Unable to create Maven project for com.sun:tools:pom:localVersion 
> from repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project 
> artifact: Failure to find com.sun:tools:pom:localVersion in 
> http://ci.jclarity.com:8081/nexus/content/groups/public/ was cached in the 
> local repository, resolution will not be reattempted until the update 
> interval of jclarity-central has elapsed or updates are forced for project 
> com.sun:tools:pom:localVersion
>   at 
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:296)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:236)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:251)
>   at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository(RepositoryUtils.java:298)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow(DependencyManagementRenderer.java:237)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope(DependencyManagementRenderer.java:204)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes(DependencyManagementRenderer.java:157)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies(DependencyManagementRenderer.java:146)
>   at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody(DependencyManagementRenderer.java:132)
>   at 
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
>   at 
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport(DependencyManagementReport.java:112)
>   at 
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
>   at 
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
>   at 
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
>   at 
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
>   at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
>   at 
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>   at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>   at 
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   

[jira] [Updated] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

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

Roberto Benedetti updated MPIR-362:
---
Description: 
I have the same issue that was closed as "non reproducible". With this pom.xml
{code:xml}
http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0

free.test
system-scope-test
0.0.1-SNAPSHOT
jar
http://test.free/


1.8

UTF-8





netscape
plugin
${java.version}
system

${java.home}/lib/plugin.jar









maven-compiler-plugin
3.3

${java.version}
${java.version}










maven-project-info-reports-plugin
2.9




dependency-management







{code}
Running {{mvn site}} will give the following warning:
{noformat}
[INFO] Generating "Dependency Management" report--- 
maven-project-info-reports-plugin:2.9
[WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from 
repository.
org.apache.maven.project.ProjectBuildingException: Error resolving project 
artifact: Failure to find netscape:plugin:pom:1.8 in 
https://repo.maven.apache.org/maven2 was cached in the local repository, 
resolution will not be reattempted until the update interval of central has 
elapsed or updates are forced for project netscape:plugin:pom:1.8
at org.apache.maven.project.DefaultProjectBuilder.build 
(DefaultProjectBuilder.java:314)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
(DefaultMavenProjectBuilder.java:236)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
(DefaultMavenProjectBuilder.java:251)
at 
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
 (RepositoryUtils.java:298)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
 (DependencyManagementRenderer.java:260)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
 (DependencyManagementRenderer.java:208)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
 (DependencyManagementRenderer.java:161)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
 (DependencyManagementRenderer.java:150)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
 (DependencyManagementRenderer.java:136)
at org.apache.maven.reporting.AbstractMavenReportRenderer.render 
(AbstractMavenReportRenderer.java:83)
at 
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport 
(DependencyManagementReport.java:124)
at org.apache.maven.reporting.AbstractMavenReport.generate 
(AbstractMavenReport.java:255)
at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument 
(ReportDocumentRenderer.java:219)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule 
(DefaultSiteRenderer.java:319)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render 
(DefaultSiteRenderer.java:135)
at org.apache.maven.plugins.site.SiteMojo.renderLocale (SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute (SiteMojo.java:138)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at 

[jira] [Updated] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

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

Roberto Benedetti updated MPIR-362:
---
Description: 
I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
{code:xml}
http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0

free.test
system-scope-test
0.0.1-SNAPSHOT
jar
http://test.free/


1.8

UTF-8





netscape
plugin
${java.version}
system

${java.home}/lib/plugin.jar









maven-compiler-plugin
3.3

${java.version}
${java.version}










maven-project-info-reports-plugin
2.9




dependency-management







{code}
running {{mvn site}} will give the following warning:
{noformat}
[INFO] Generating "Dependency Management" report--- 
maven-project-info-reports-plugin:2.9
[WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from 
repository.
org.apache.maven.project.ProjectBuildingException: Error resolving project 
artifact: Failure to find netscape:plugin:pom:1.8 in 
https://repo.maven.apache.org/maven2 was cached in the local repository, 
resolution will not be reattempted until the update interval of central has 
elapsed or updates are forced for project netscape:plugin:pom:1.8
at org.apache.maven.project.DefaultProjectBuilder.build 
(DefaultProjectBuilder.java:314)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
(DefaultMavenProjectBuilder.java:236)
at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
(DefaultMavenProjectBuilder.java:251)
at 
org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
 (RepositoryUtils.java:298)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
 (DependencyManagementRenderer.java:260)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
 (DependencyManagementRenderer.java:208)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
 (DependencyManagementRenderer.java:161)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
 (DependencyManagementRenderer.java:150)
at 
org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
 (DependencyManagementRenderer.java:136)
at org.apache.maven.reporting.AbstractMavenReportRenderer.render 
(AbstractMavenReportRenderer.java:83)
at 
org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport 
(DependencyManagementReport.java:124)
at org.apache.maven.reporting.AbstractMavenReport.generate 
(AbstractMavenReport.java:255)
at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument 
(ReportDocumentRenderer.java:219)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule 
(DefaultSiteRenderer.java:319)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render 
(DefaultSiteRenderer.java:135)
at org.apache.maven.plugins.site.SiteMojo.renderLocale (SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute (SiteMojo.java:138)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at 

[jira] [Updated] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

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

Roberto Benedetti updated MPIR-362:
---
Priority: Major  (was: Critical)

> CLONE - Dependency Management report doesn't exclude system scoped 
> dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>  Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Priority: Major
>
> I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
> {code:xml}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
>   4.0.0
>   free.test
>   system-scope-test
>   0.0.1-SNAPSHOT
>   jar
>   http://test.free/
>   
>   1.8
>   
> UTF-8
>   
>   
>   
>   
>   netscape
>   plugin
>   ${java.version}
>   system
>   
> ${java.home}/lib/plugin.jar
>   
>   
>   
>   
>   
>   
>   
>   
> maven-compiler-plugin
>   3.3
>   
>   ${java.version}
>   ${java.version}
>   
>   
>   
>   
>   
>   
>   
>   
>   
> maven-project-info-reports-plugin
>   2.9
>   
>   
>   
>   
> dependency-management
>   
>   
>   
>   
>   
>   
> 
> {code}
> running {{mvn site}} will give the following warning:
> {noformat}
> [INFO] Generating "Dependency Management" report--- 
> maven-project-info-reports-plugin:2.9
> [WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from 
> repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project 
> artifact: Failure to find netscape:plugin:pom:1.8 in 
> https://repo.maven.apache.org/maven2 was cached in the local repository, 
> resolution will not be reattempted until the update interval of central has 
> elapsed or updates are forced for project netscape:plugin:pom:1.8
> at org.apache.maven.project.DefaultProjectBuilder.build 
> (DefaultProjectBuilder.java:314)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
> (DefaultMavenProjectBuilder.java:236)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
> (DefaultMavenProjectBuilder.java:251)
> at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
>  (RepositoryUtils.java:298)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
>  (DependencyManagementRenderer.java:260)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
>  (DependencyManagementRenderer.java:208)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
>  (DependencyManagementRenderer.java:161)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
>  (DependencyManagementRenderer.java:150)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
>  (DependencyManagementRenderer.java:136)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render 
> (AbstractMavenReportRenderer.java:83)
> at 
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport 
> (DependencyManagementReport.java:124)
> at org.apache.maven.reporting.AbstractMavenReport.generate 
> (AbstractMavenReport.java:255)
> at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument 
> 

[jira] [Updated] (MPIR-362) CLONE - Dependency Management report doesn't exclude system scoped dependencies

[Roberto Benedetti (JIRA)]

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

Roberto Benedetti updated MPIR-362:
---
Priority: Critical  (was: Major)

> CLONE - Dependency Management report doesn't exclude system scoped 
> dependencies
> ---
>
> Key: MPIR-362
> URL: https://issues.apache.org/jira/browse/MPIR-362
> Project: Maven Project Info Reports Plugin
>  Issue Type: Bug
>  Components: dependency-management
>Affects Versions: 2.9
> Environment: Windows 7, Maven, 3.5.2, JDK 1.7.0_161
>Reporter: Roberto Benedetti
>Priority: Critical
>
> I have the same issue that was closed as "Cannot Reproduce". With this pom.xml
> {code:xml}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
>   4.0.0
>   free.test
>   system-scope-test
>   0.0.1-SNAPSHOT
>   jar
>   http://test.free/
>   
>   1.8
>   
> UTF-8
>   
>   
>   
>   
>   netscape
>   plugin
>   ${java.version}
>   system
>   
> ${java.home}/lib/plugin.jar
>   
>   
>   
>   
>   
>   
>   
>   
> maven-compiler-plugin
>   3.3
>   
>   ${java.version}
>   ${java.version}
>   
>   
>   
>   
>   
>   
>   
>   
>   
> maven-project-info-reports-plugin
>   2.9
>   
>   
>   
>   
> dependency-management
>   
>   
>   
>   
>   
>   
> 
> {code}
> running {{mvn site}} will give the following warning:
> {noformat}
> [INFO] Generating "Dependency Management" report--- 
> maven-project-info-reports-plugin:2.9
> [WARNING] Unable to create Maven project for netscape:plugin:pom:1.8 from 
> repository.
> org.apache.maven.project.ProjectBuildingException: Error resolving project 
> artifact: Failure to find netscape:plugin:pom:1.8 in 
> https://repo.maven.apache.org/maven2 was cached in the local repository, 
> resolution will not be reattempted until the update interval of central has 
> elapsed or updates are forced for project netscape:plugin:pom:1.8
> at org.apache.maven.project.DefaultProjectBuilder.build 
> (DefaultProjectBuilder.java:314)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
> (DefaultMavenProjectBuilder.java:236)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository 
> (DefaultMavenProjectBuilder.java:251)
> at 
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
>  (RepositoryUtils.java:298)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.getDependencyRow
>  (DependencyManagementRenderer.java:260)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForScope
>  (DependencyManagementRenderer.java:208)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderDependenciesForAllScopes
>  (DependencyManagementRenderer.java:161)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderSectionProjectDependencies
>  (DependencyManagementRenderer.java:150)
> at 
> org.apache.maven.report.projectinfo.dependencies.renderer.DependencyManagementRenderer.renderBody
>  (DependencyManagementRenderer.java:136)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render 
> (AbstractMavenReportRenderer.java:83)
> at 
> org.apache.maven.report.projectinfo.DependencyManagementReport.executeReport 
> (DependencyManagementReport.java:124)
> at org.apache.maven.reporting.AbstractMavenReport.generate 
> (AbstractMavenReport.java:255)
> at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument 
> 

[jira] [Created] (WAGON-503) Directory is out of date error in putDirectory() to a non-empty svn repo

[Ilya Basin (JIRA)]

Ilya Basin created WAGON-503:


 Summary: Directory is out of date error in putDirectory() to a 
non-empty svn repo
 Key: WAGON-503
 URL: https://issues.apache.org/jira/browse/WAGON-503
 Project: Maven Wagon
  Issue Type: Bug
  Components: wagon-scm
Affects Versions: 3.0.0, 3.0.1
Reporter: Ilya Basin


ScmWagon checks out target directory non-recursively, calls 
FileUtils.copyDirectoryStructure() and then tries to add and checkin these 
files.

However, from the perspective of svn ScmWagon is trying to re-add existing 
folders which is an error.



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

[jira] [Commented] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[Nicolas Zin (JIRA)]

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

Nicolas Zin commented on SUREFIRE-1346:
---

Hi guys,

I just faced the problem you are mentioning (my maven-failsafe-plugin is 
configured to use several fork (2)), and testng-results.xml is overwritten by 
each thread/fork.
I tried to configure the reportsDirectory in my pom.xml, but so far I didn't 
manage to set it properly. I tried something like:

{{}}
{{  maven-failsafe-plugin}}
{{  2.18.1}}
{{  
${project.build.directory}/surefire-reports/${surefire.forkNumber}}}
{{  ...}}
{{ }}

But I finish with a directory named 
"target/surefire-reports/${surefire.forkNumber}/testng-results.xml"

i.e. the variable is not interpolated
Do you known which value I can use instead of surefire.forkNumber? or even 
better is there a ${surefire.classname} ?

> surefire-reports overwrite each other when using reuseForks=false
> -
>
> Key: SUREFIRE-1346
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1346
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking, TestNG support
>Affects Versions: 2.19.1
>Reporter: Antoine Tran
>Priority: Major
>
> In a Maven project with the setting "false" and 
> TestNg, the file testng-result.xml gets overwritten by the last test.
> I somehow understand why it is difficult to avoid this by design of fork, but 
> a workaround solution, as suggested by SUREFIRE-1018 or SUREFIRE-446, is to 
> use the individual TEST-[className].xml files.
> However, if I use a Jenkins plugin like testng, I cannot make him ingest 
> these files, as they do not have the same structure as testng-result.xml. 
> This is a bug of testng, rather than the Jenkins plugin testng. Couldn't we 
> make testng-result-[className].xml, for each test, with the testng-result.xml 
> structure? Otherwise, the Jenkins plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/testng-plugin is completely not 
> usable.
> Thank you.



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

[jira] [Updated] (WAGON-503) Directory is out of date error in putDirectory() to a non-empty svn repo

[Ilya Basin (JIRA)]

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

Ilya Basin updated WAGON-503:
-
Description: 
ScmWagon checks out target directory non-recursively, calls 
FileUtils.copyDirectoryStructure() and then tries to add and checkin these 
files.

However, from the perspective of svn ScmWagon is trying to re-add existing 
folders which is an error.

Normally, you would explicitly "svn up subdir", but the scm API does not 
support that. Instead I will erase existing checkout dir and perform a new 
checkout, recursive this time.

  was:
ScmWagon checks out target directory non-recursively, calls 
FileUtils.copyDirectoryStructure() and then tries to add and checkin these 
files.

However, from the perspective of svn ScmWagon is trying to re-add existing 
folders which is an error.


> Directory is out of date error in putDirectory() to a non-empty svn repo
> 
>
> Key: WAGON-503
> URL: https://issues.apache.org/jira/browse/WAGON-503
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-scm
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ilya Basin
>Priority: Major
>
> ScmWagon checks out target directory non-recursively, calls 
> FileUtils.copyDirectoryStructure() and then tries to add and checkin these 
> files.
> However, from the perspective of svn ScmWagon is trying to re-add existing 
> folders which is an error.
> Normally, you would explicitly "svn up subdir", but the scm API does not 
> support that. Instead I will erase existing checkout dir and perform a new 
> checkout, recursive this time.



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

[jira] [Created] (SUREFIRE-1492) Failsafe doesn't fail when a TestEngine throws an Error

[Mateusz Stefek (JIRA)]

Mateusz Stefek created SUREFIRE-1492:


 Summary: Failsafe doesn't fail when a TestEngine throws an Error
 Key: SUREFIRE-1492
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1492
 Project: Maven Surefire
  Issue Type: Bug
  Components: classloading, JUnit 5.x support
Affects Versions: 2.19.1
Reporter: Mateusz Stefek


My Jupiter engine fails due to some classloader hell. The logs are below. But 
that's not the point. In such case, the build should fail, but the plugin 
exists as if nothing happened. Even with  
{{failIfNoTests>true}} the plugin finishes and generates 
{{failsafe-summary.xml}} with {{0}}

{noformat}
Forking command line: cmd.exe /X /C ""C:\Program 
Files\Java\jdk1.8.0_91\jre\bin\java" -jar 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefirebooter5276177102867119205.jar
 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefire268158133198646317tmp
 
C:\Users\matste\uptime\uptime\ui\ui-demo\target\surefire\surefire_05629521514361875618tmp"
Mar 01, 2018 12:29:15 PM org.junit.platform.launcher.core.DefaultLauncher 
handleThrowable
WARNING: TestEngine with ID 'junit-jupiter' failed to discover tests
java.lang.BootstrapMethodError: java.lang.NoSuchMethodError: 
org.junit.platform.commons.util.ReflectionUtils.isNotPrivate(Ljava/lang/reflect/Member;)Z
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveContainedMethods(JavaElementsResolver.java:189)
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveChildren(JavaElementsResolver.java:177)
at java.lang.Iterable.forEach(Iterable.java:75)
at 
org.junit.jupiter.engine.discovery.JavaElementsResolver.resolveClass(JavaElementsResolver.java:61)
at 
org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.lambda$resolve$3(DiscoverySelectorResolver.java:69)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at 
org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.resolve(DiscoverySelectorResolver.java:68)
at 
org.junit.jupiter.engine.discovery.DiscoverySelectorResolver.resolveSelectors(DiscoverySelectorResolver.java:50)
at 
org.junit.jupiter.engine.JupiterTestEngine.discover(JupiterTestEngine.java:61)
at 
org.junit.platform.launcher.core.DefaultLauncher.discoverEngineRoot(DefaultLauncher.java:130)
at 
org.junit.platform.launcher.core.DefaultLauncher.discoverRoot(DefaultLauncher.java:117)
at 
org.junit.platform.launcher.core.DefaultLauncher.discover(DefaultLauncher.java:82)
at 
org.junit.platform.surefire.provider.TestPlanScannerFilter.accept(TestPlanScannerFilter.java:50)
at 
org.apache.maven.surefire.util.DefaultScanResult.applyFilter(DefaultScanResult.java:98)
at 
org.junit.platform.surefire.provider.JUnitPlatformProvider.scanClasspath(JUnitPlatformProvider.java:121)
at 
org.junit.platform.surefire.provider.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:111)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
Caused by: java.lang.NoSuchMethodError: 
org.junit.platform.commons.util.ReflectionUtils.isNotPrivate(Ljava/lang/reflect/Member;)Z
at java.lang.invoke.MethodHandleNatives.resolve(Native Method)
at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:977)
at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1002)
at java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1390)
at 
java.lang.invoke.MethodHandles$Lookup.linkMethodHandleConstant(MethodHandles.java:1746)
at 
java.lang.invoke.MethodHandleNatives.linkMethodHandleConstant(MethodHandleNatives.java:477)
... 19 more

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
{noformat}
 



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

[jira] [Comment Edited] (SUREFIRE-1346) surefire-reports overwrite each other when using reuseForks=false

[Nicolas Zin (JIRA)]

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

Nicolas Zin edited comment on SUREFIRE-1346 at 3/1/18 12:41 PM:


Hi guys,

I just faced the problem you are mentioning (my maven-failsafe-plugin is 
configured to use several fork (2)), and testng-results.xml is overwritten by 
each thread/fork.
 I tried to configure the reportsDirectory in my pom.xml, but so far I didn't 
manage to set it properly. I tried something like:

{{}}
 {{  maven-failsafe-plugin}}
 {{  2.18.1}}
 {{  
${project.build.directory}/surefire-reports/${surefire.forkNumber}}}
 {{  ...}}


But I finish with a directory named 
"target/surefire-reports/${surefire.forkNumber}/testng-results.xml"

i.e. the variable is not interpolated
 Do you known which value I can use instead of surefire.forkNumber? or even 
better is there a ${surefire.classname} ?


was (Author: nzin):
Hi guys,

I just faced the problem you are mentioning (my maven-failsafe-plugin is 
configured to use several fork (2)), and testng-results.xml is overwritten by 
each thread/fork.
I tried to configure the reportsDirectory in my pom.xml, but so far I didn't 
manage to set it properly. I tried something like:

{{}}
{{  maven-failsafe-plugin}}
{{  2.18.1}}
{{  
${project.build.directory}/surefire-reports/${surefire.forkNumber}}}
{{  ...}}
{{ }}

But I finish with a directory named 
"target/surefire-reports/${surefire.forkNumber}/testng-results.xml"

i.e. the variable is not interpolated
Do you known which value I can use instead of surefire.forkNumber? or even 
better is there a ${surefire.classname} ?

> surefire-reports overwrite each other when using reuseForks=false
> -
>
> Key: SUREFIRE-1346
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1346
> Project: Maven Surefire
>  Issue Type: Bug
>  Components: process forking, TestNG support
>Affects Versions: 2.19.1
>Reporter: Antoine Tran
>Priority: Major
>
> In a Maven project with the setting "false" and 
> TestNg, the file testng-result.xml gets overwritten by the last test.
> I somehow understand why it is difficult to avoid this by design of fork, but 
> a workaround solution, as suggested by SUREFIRE-1018 or SUREFIRE-446, is to 
> use the individual TEST-[className].xml files.
> However, if I use a Jenkins plugin like testng, I cannot make him ingest 
> these files, as they do not have the same structure as testng-result.xml. 
> This is a bug of testng, rather than the Jenkins plugin testng. Couldn't we 
> make testng-result-[className].xml, for each test, with the testng-result.xml 
> structure? Otherwise, the Jenkins plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/testng-plugin is completely not 
> usable.
> Thank you.



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

[GitHub] maven-wagon pull request #47: [WAGON-503] fix Directory is out of date error...

[basinilya]

GitHub user basinilya opened a pull request:

https://github.com/apache/maven-wagon/pull/47

[WAGON-503] fix Directory is out of date error in putDirectory() to a 
non-empty svn repo



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

$ git pull https://github.com/basinilya/maven-wagon WAGON-503

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

https://github.com/apache/maven-wagon/pull/47.patch

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

This closes #47


commit b6e79d554db83f3f0fba33574b26bbef3fe9617d
Author: Ilya Basin 
Date:   2018-02-18T08:55:32Z

[WAGON-497] fix ScmWagon.put() strips existing parent directories

commit 36c4a21fe044305f49160d7c85c7a7cf945715ea
Author: Ilya Basin 
Date:   2018-02-18T19:34:20Z

[WAGON-498] use maven-scm 1.9.6-SNAPSHOT

commit 98ff45fb934ce856d3fde3fb84ac177604dd0293
Author: Ilya Basin 
Date:   2018-02-18T19:49:30Z

[WAGON-498] ScmWagon should work in binary mode when possible

commit 1fe65b1a05f3945931f1fc09a95ad68d43a0dad3
Author: Ilya Basin 
Date:   2018-02-20T14:37:28Z

fix ScmWagon cannot checkout when list() unsupported

commit 8cb0abe9026119d1d352cefb0902a0db5eba7e34
Author: Ilya Basin 
Date:   2018-02-22T08:13:52Z

[WAGON-495] fix testWagonPutDirectoryWhenDirectoryAlreadyExists false
positive

commit a7688623c5f8b31f7acec3b4283b77ee4a159dbc
Author: Ilya Basin 
Date:   2018-03-01T13:12:42Z

[WAGON-503] fix Directory is out of date error in putDirectory() to a 
non-empty svn repo




---

[jira] [Commented] (WAGON-503) Directory is out of date error in putDirectory() to a non-empty svn repo

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/WAGON-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381975#comment-16381975
 ] 

ASF GitHub Bot commented on WAGON-503:
--

GitHub user basinilya opened a pull request:

https://github.com/apache/maven-wagon/pull/47

[WAGON-503] fix Directory is out of date error in putDirectory() to a 
non-empty svn repo



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

$ git pull https://github.com/basinilya/maven-wagon WAGON-503

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

https://github.com/apache/maven-wagon/pull/47.patch

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

This closes #47


commit b6e79d554db83f3f0fba33574b26bbef3fe9617d
Author: Ilya Basin 
Date:   2018-02-18T08:55:32Z

[WAGON-497] fix ScmWagon.put() strips existing parent directories

commit 36c4a21fe044305f49160d7c85c7a7cf945715ea
Author: Ilya Basin 
Date:   2018-02-18T19:34:20Z

[WAGON-498] use maven-scm 1.9.6-SNAPSHOT

commit 98ff45fb934ce856d3fde3fb84ac177604dd0293
Author: Ilya Basin 
Date:   2018-02-18T19:49:30Z

[WAGON-498] ScmWagon should work in binary mode when possible

commit 1fe65b1a05f3945931f1fc09a95ad68d43a0dad3
Author: Ilya Basin 
Date:   2018-02-20T14:37:28Z

fix ScmWagon cannot checkout when list() unsupported

commit 8cb0abe9026119d1d352cefb0902a0db5eba7e34
Author: Ilya Basin 
Date:   2018-02-22T08:13:52Z

[WAGON-495] fix testWagonPutDirectoryWhenDirectoryAlreadyExists false
positive

commit a7688623c5f8b31f7acec3b4283b77ee4a159dbc
Author: Ilya Basin 
Date:   2018-03-01T13:12:42Z

[WAGON-503] fix Directory is out of date error in putDirectory() to a 
non-empty svn repo




> Directory is out of date error in putDirectory() to a non-empty svn repo
> 
>
> Key: WAGON-503
> URL: https://issues.apache.org/jira/browse/WAGON-503
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-scm
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ilya Basin
>Priority: Major
>
> ScmWagon checks out target directory non-recursively, calls 
> FileUtils.copyDirectoryStructure() and then tries to add and checkin these 
> files.
> However, from the perspective of svn ScmWagon is trying to re-add existing 
> folders which is an error.
> Normally, you would explicitly "svn up subdir", but the scm API does not 
> support that. Instead I will erase existing checkout dir and perform a new 
> checkout, recursive this time.



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

[jira] [Commented] (MJAVADOC-444) Add an 'aggregated-no-fork' goal

[Sean Busbey (JIRA)]

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

Sean Busbey commented on MJAVADOC-444:
--

linking a PR I put together that implements this.

> Add an 'aggregated-no-fork' goal
> 
>
> Key: MJAVADOC-444
> URL: https://issues.apache.org/jira/browse/MJAVADOC-444
> Project: Maven Javadoc Plugin
>  Issue Type: Improvement
>Affects Versions: 2.10.3
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> Currently you can call maven-javadoc-plugin via {{mvn clean package 
> javadoc:aggregate}} which results in deleting all previously created 
> artifacts in {{target}} folder. So it would be helpful having a separate goal 
> without forking the life cycle.



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

[jira] [Commented] (MRELEASE-913) Nested properties in versions cause prepare to fail

[Phil Clay (JIRA)]

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

Phil Clay commented on MRELEASE-913:


Note that I contributed an example project and slightly different patch to fix 
the problem in MRELEASE-920.  Please evaluate the patches to ensure the best 
fix.  (I haven't compared the patches much more than to notice that they are 
different)

> Nested properties in versions cause prepare to fail
> ---
>
> Key: MRELEASE-913
> URL: https://issues.apache.org/jira/browse/MRELEASE-913
> Project: Maven Release Plugin
>  Issue Type: Bug
>  Components: prepare
>Affects Versions: 2.5.2
>Reporter: Tim Mullender
>Priority: Minor
> Attachments: MRELEASE-913-1.patch, example.zip
>
>
> We have a multi module project in which module-b depends on module-a, the 
> version of module-a in the pom for module-b is defined as a property which 
> defaults to project.version
> When running release:prepare we get an error similar to the following:
> {noformat}
> The artifact (groupId:module-a) requires a different version (1.0) than what 
> is found (${project.version}) for the expression (property.name) in the 
> project (groupId:module-b).
> {noformat}



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

[jira] [Created] (MCHANGELOG-144) svn and maven-changelog-plugin results in “The filename, directory name, or volume label syntax is incorrect”

[Adrian Wyssmann (JIRA)]

Adrian Wyssmann created MCHANGELOG-144:
--

 Summary: svn and maven-changelog-plugin results in “The filename, 
directory name, or volume label syntax is incorrect”
 Key: MCHANGELOG-144
 URL: https://issues.apache.org/jira/browse/MCHANGELOG-144
 Project: Maven Changelog Plugin
  Issue Type: Bug
Affects Versions: 2.3
 Environment: Windows Server 2016
maven 3.5.2
Reporter: Adrian Wyssmann


We are using maven-changelog-plugin:2.3 to generate the changelog. The job is 
triggered by Jenkins but recently the job starts failing. Here is what I see in 
the log
{code:java}
... 
...
22:05:41 [DEBUG] Multipage report: 0 subreports
22:05:41 [DEBUG] Generating 
D:\jenkins\workspace\MAVEN-Company-Project\target\site\changelog.html
22:05:41 [INFO] Generating "Change Log" report--- 
maven-changelog-plugin:2.3:changelog
22:05:41 [INFO] Generating changed sets xml to: 
D:\jenkins\workspace\MAVEN-Company-Project\target\changelog.xml
22:05:41 [INFO] Executing: cmd.exe /X /C "svn --username CIUSER --password 
* --no-auth-cache --non-interactive log -v -r "{2018-01-29 21:05:41 
+}:{2018-03-01 21:05:41 +}" 
http://svn.mycompany.intra:80/svn/parentpom/trunk/;
22:05:41 [INFO] Working directory: D:\jenkins\workspace\MAVEN-Company-Project
22:05:41 [ERROR] Provider message:
22:05:41 [ERROR] The svn command failed.
22:05:41 [ERROR] Command output:
22:05:41 [ERROR] The filename, directory name, or volume label syntax is 
incorrect.
22:05:41 
22:05:41 [INFO] 

22:05:41 [INFO] BUILD FAILURE
22:05:41 [INFO] 

22:05:41 [INFO] Total time: 13.994 s
22:05:41 [INFO] Finished at: 2018-02-28T22:05:41+01:00
22:05:41 [INFO] Final Memory: 43M/451M
22:05:41 [INFO] 

22:05:41 [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) on project 
mycompany: Error generating maven-changelog-plugin:2.3:changelog: An error has 
occurred during changelog command : : Command failed. -> [Help 1]
22:05:41 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to 
execute goal org.apache.maven.plugins:maven-site-plugin:3.6:site (default-cli) 
on project mycompany: Error generating maven-changelog-plugin:2.3:changelog: An 
error has occurred during changelog command : 
22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
22:05:41 at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
22:05:41 at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
22:05:41 at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
22:05:41 at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:51)
22:05:41 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
...{code}
Running the command manually in the workspace directory 
D:\jenkins\workspace\MAVEN-Company-Project\ works without problems.

The problems occurs in conjunction with maven 3.5.2. When switching back to 
maven 3.1.1 the error does not appear.



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

[GitHub] stevegutz commented on issue #2: Enable blazar

[GitBox]

stevegutz commented on issue #2: Enable blazar
URL: 
https://github.com/apache/maven-checkstyle-plugin/pull/2#issuecomment-369657435
 
 
   Sorry, wrong repo :(


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] stevegutz opened a new pull request #2: Enable blazar

[GitBox]

stevegutz opened a new pull request #2: Enable blazar
URL: https://github.com/apache/maven-checkstyle-plugin/pull/2
 
 
   This will allow us to publish and use SNAPSHOTs internally
   
   @jhaber


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] stevegutz closed pull request #2: Enable blazar

[GitBox]

stevegutz closed pull request #2: Enable blazar
URL: https://github.com/apache/maven-checkstyle-plugin/pull/2
 
 
   

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/.blazar-enabled b/.blazar-enabled
new file mode 100644
index 000..e69de29
diff --git a/.blazar.yaml b/.blazar.yaml
new file mode 100644
index 000..a8099ad
--- /dev/null
+++ b/.blazar.yaml
@@ -0,0 +1,15 @@
+env:
+  SKIP_VERSION_OVERRIDE: true
+  MAVEN_OPTS: -Xmx768m
+  MAVEN_ARGS: -Drat.skip=true
+
+
+buildpack:
+  host: git.hubteam.com
+  organization: HubSpot
+  repository: Blazar-Buildpack-Java
+  branch: v2
+
+  stepActivation:
+  notify:
+branches: [trunk]
diff --git a/.hubspot-blazar-discovery.yaml b/.hubspot-blazar-discovery.yaml
new file mode 100644
index 000..1f4be0f
--- /dev/null
+++ b/.hubspot-blazar-discovery.yaml
@@ -0,0 +1 @@
+disabledDiscoveries: ["maven"]


 


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-444) Add an 'aggregated-no-fork' goal

[Sean Busbey (JIRA)]

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

Sean Busbey commented on MJAVADOC-444:
--

this would help immensely for our builds over in Apache HBase. we build 4 
aggregate docs (user and internal facing for main and test) and right now that 
means 4 additional times forking a build that we don't need.

> Add an 'aggregated-no-fork' goal
> 
>
> Key: MJAVADOC-444
> URL: https://issues.apache.org/jira/browse/MJAVADOC-444
> Project: Maven Javadoc Plugin
>  Issue Type: Improvement
>Affects Versions: 2.10.3
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> Currently you can call maven-javadoc-plugin via {{mvn clean package 
> javadoc:aggregate}} which results in deleting all previously created 
> artifacts in {{target}} folder. So it would be helpful having a separate goal 
> without forking the life cycle.



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

[jira] [Commented] (MJAVADOC-490) Aggregate goal fails if artifacts not installed

[Sean Busbey (JIRA)]

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

Sean Busbey commented on MJAVADOC-490:
--

using maven-site-plugin version 3.4, I still have this problem but only for 
test-jar intra-project dependencies. specifically, those dependencies are test 
scope but the forked compile build for the main aggregate for some reason still 
tries to find them.

> Aggregate goal fails if artifacts not installed
> ---
>
> Key: MJAVADOC-490
> URL: https://issues.apache.org/jira/browse/MJAVADOC-490
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>  Components: javadoc
>Affects Versions: 2.10.4
>Reporter: Shannon Carey
>Priority: Major
>
> Using the javadoc aggregate report causes release:perform to fail if the 
> modules were not already installed into the local repository.
> During release:perform's execution of "deploy site-deploy", when 
> report:aggregate runs it appears to fork executions on all of the reactor 
> modules ("Forking mymodule 0.0.1"). When it gets to a module which has a 
> dependency on another module, it cannot find it locally (since that module 
> has not yet been installed), tries to download it from Nexus, and ultimately 
> fails with "... Could not resolve dependencies for project ... The following 
> artifacts could not be resolved ..."
> The only way I can think of to fix this is to add "install" to the 
> "preparationGoals" of release:prepare so that the modules are already 
> installed before release:perform is run. However, this violates the 
> self-containment of release:perform's deploy build, and is generally 
> confusing and difficult to diagnose.



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

[GitHub] busbey opened a new pull request #2: [MJAVADOC-444] add aggregate-no-fork and aggregate-test-no-fork for non-forking versions of aggregate goals.

[GitBox]

busbey opened a new pull request #2: [MJAVADOC-444] add aggregate-no-fork and 
aggregate-test-no-fork for non-forking versions of aggregate goals.
URL: https://github.com/apache/maven-javadoc-plugin/pull/2
 
 
   
   Follows the same pattern as JavadocNoForkReport with the aggregate goals.
   
   Tested out locally by installing a SNAPSHOT version and then moving my 
project over to it.


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-444) Add an 'aggregated-no-fork' goal

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on MJAVADOC-444:
-

busbey opened a new pull request #2: [MJAVADOC-444] add aggregate-no-fork and 
aggregate-test-no-fork for non-forking versions of aggregate goals.
URL: https://github.com/apache/maven-javadoc-plugin/pull/2
 
 
   
   Follows the same pattern as JavadocNoForkReport with the aggregate goals.
   
   Tested out locally by installing a SNAPSHOT version and then moving my 
project over to it.


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


> Add an 'aggregated-no-fork' goal
> 
>
> Key: MJAVADOC-444
> URL: https://issues.apache.org/jira/browse/MJAVADOC-444
> Project: Maven Javadoc Plugin
>  Issue Type: Improvement
>Affects Versions: 2.10.3
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> Currently you can call maven-javadoc-plugin via {{mvn clean package 
> javadoc:aggregate}} which results in deleting all previously created 
> artifacts in {{target}} folder. So it would be helpful having a separate goal 
> without forking the life cycle.



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