[GitHub] [maven-surefire] Tibor17 commented on issue #273: [SUREFIRE-1758] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
Tibor17 commented on issue #273: [SUREFIRE-1758] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups URL: https://github.com/apache/maven-surefire/pull/273#issuecomment-595647031 @sparsick Thank You for contributing! This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (SUREFIRE-1758) JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
[
https://issues.apache.org/jira/browse/SUREFIRE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1758.
--
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=cfdd9ea45f7d9090487019fcddd91276669b503e
> JUnit Platform provider isn't mentioned in the docu about groups and
> excludeGroups
> --
>
> Key: SUREFIRE-1758
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1758
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.22.0, 2.22.1, 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3,
> 3.0.0-M4
>Reporter: Sandra Parsick
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 3.0.0-M5
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> JUnit Platform provider works for the parameter {{groups}} and
> {{excludeGroups}}, but it isn't mention in the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-surefire] Tibor17 merged pull request #273: [SUREFIRE-1758] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
Tibor17 merged pull request #273: [SUREFIRE-1758] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups URL: https://github.com/apache/maven-surefire/pull/273 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (SUREFIRE-1758) JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
[
https://issues.apache.org/jira/browse/SUREFIRE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1758:
---
Affects Version/s: 2.22.0
2.22.1
2.22.2
3.0.0-M2
3.0.0-M1
3.0.0-M3
3.0.0-M4
> JUnit Platform provider isn't mentioned in the docu about groups and
> excludeGroups
> --
>
> Key: SUREFIRE-1758
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1758
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.22.0, 2.22.1, 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3,
> 3.0.0-M4
>Reporter: Sandra Parsick
>Priority: Minor
> Fix For: 3.0.0-M5
>
>
> JUnit Platform provider works for the parameter {{groups}} and
> {{excludeGroups}}, but it isn't mention in the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (SUREFIRE-1758) JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
[
https://issues.apache.org/jira/browse/SUREFIRE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1758:
--
Assignee: Tibor Digana
> JUnit Platform provider isn't mentioned in the docu about groups and
> excludeGroups
> --
>
> Key: SUREFIRE-1758
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1758
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Affects Versions: 2.22.0, 2.22.1, 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3,
> 3.0.0-M4
>Reporter: Sandra Parsick
>Assignee: Tibor Digana
>Priority: Minor
> Fix For: 3.0.0-M5
>
>
> JUnit Platform provider works for the parameter {{groups}} and
> {{excludeGroups}}, but it isn't mention in the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPIR-373) Upgrade from 2.9 to 3.0.0 introduces additional warning
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053118#comment-17053118
]
Robin Jansohn commented on MPIR-373:
Well sorry, did not mean to offend anybody. The release frequency (two releases
in 4 years) while 30 issues were resolved
([https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPIR%20AND%20fixVersion%20in%20(3.0.1%2C%203.0.0)])
does indicate that creating releases is the main issue with this project. The
voting on a mailing list certainly doesn't help but seems to be mandatory.
> Upgrade from 2.9 to 3.0.0 introduces additional warning
> ---
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: GWR
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Attachments: pom.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> 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 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
[GitHub] [maven-surefire] michael-o commented on issue #272: it would be better to use sha-512
michael-o commented on issue #272: it would be better to use sha-512 URL: https://github.com/apache/maven-surefire/pull/272#issuecomment-595645624 Agree with @Tibor17. SHA-256 is more than enough if bumped. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (SUREFIRE-1758) JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
[
https://issues.apache.org/jira/browse/SUREFIRE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1758:
---
Fix Version/s: 3.0.0-M5
> JUnit Platform provider isn't mentioned in the docu about groups and
> excludeGroups
> --
>
> Key: SUREFIRE-1758
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1758
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Reporter: Sandra Parsick
>Priority: Minor
> Fix For: 3.0.0-M5
>
>
> JUnit Platform provider works for the parameter {{groups}} and
> {{excludeGroups}}, but it isn't mention in the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1758) JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
[
https://issues.apache.org/jira/browse/SUREFIRE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053050#comment-17053050
]
Sandra Parsick commented on SUREFIRE-1758:
--
PR is created https://github.com/apache/maven-surefire/pull/273
> JUnit Platform provider isn't mentioned in the docu about groups and
> excludeGroups
> --
>
> Key: SUREFIRE-1758
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1758
> Project: Maven Surefire
> Issue Type: Improvement
> Components: documentation
>Reporter: Sandra Parsick
>Priority: Minor
>
> JUnit Platform provider works for the parameter {{groups}} and
> {{excludeGroups}}, but it isn't mention in the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-surefire] sparsick commented on issue #273: [SUREFIRE-1758] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
sparsick commented on issue #273: [SUREFIRE-1758] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups URL: https://github.com/apache/maven-surefire/pull/273#issuecomment-595610370 @Tibor17 Thank you for your hint. Ticket is created! This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (SUREFIRE-1758) JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
Sandra Parsick created SUREFIRE-1758:
Summary: JUnit Platform provider isn't mentioned in the docu about
groups and excludeGroups
Key: SUREFIRE-1758
URL: https://issues.apache.org/jira/browse/SUREFIRE-1758
Project: Maven Surefire
Issue Type: Improvement
Components: documentation
Reporter: Sandra Parsick
JUnit Platform provider works for the parameter {{groups}} and
{{excludeGroups}}, but it isn't mention in the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SUREFIRE-1628) Plugins fail to execute on Maven 3.0.5 and Java 8
[
https://issues.apache.org/jira/browse/SUREFIRE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1628:
---
Fix Version/s: 3.0.0-M5
> Plugins fail to execute on Maven 3.0.5 and Java 8
> -
>
> Key: SUREFIRE-1628
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1628
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 3.0.0-M3
> Environment: maven 3.0.5
> jdk 1.8u111
> sles 12
>Reporter: Jörg Sesterhenn
>Priority: Major
> Fix For: 3.0.0-M5
>
> Attachments: surefire-1628-mwe.zip
>
>
> The plugin seems to require plexus-java which cannot be found.
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test
> (default-integration-test) on project MyParentPOM: Execution
> default-integration-test of goal
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test
> failed: Unable to load the mojo 'integration-test' (or one of its required
> components) from the plugin
> 'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3':
> com.google.inject.ProvisionException: Guice provision errors:
> [ERROR] 1) No implementation for
> org.codehaus.plexus.languages.java.jpms.LocationManager was bound.
> [ERROR] while locating org.apache.maven.plugin.failsafe.IntegrationTestMojo
> [ERROR] at
> ClassRealm[plugin>org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3,
> parent: sun.misc.Launcher$AppClassLoader@55f96302]
> [ERROR] while locating org.apache.maven.plugin.Mojo annotated with
> @com.google.inject.name.Named(value=org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test)
> [ERROR] 1 error
> [ERROR] role: org.apache.maven.plugin.Mojo
> [ERROR] roleHint:
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test
> [ERROR] -> [Help 1]
> [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] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SUREFIRE-1628) Plugins fail to execute on Maven 3.0.5 and Java 8
[
https://issues.apache.org/jira/browse/SUREFIRE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052648#comment-17052648
]
Tibor Digana commented on SUREFIRE-1628:
[~joerg.sesterhenn]
[~nate_chadw...@percussion.com]
The bug can be fixed easily. You can contribute to the project and fix it by
instantiating LocationManager instead of injecting it in the class
AbstractSurefireMojo. Feel free to open a new pull request on Github.
> Plugins fail to execute on Maven 3.0.5 and Java 8
> -
>
> Key: SUREFIRE-1628
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1628
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Failsafe Plugin, Maven Surefire Plugin
>Affects Versions: 3.0.0-M3
> Environment: maven 3.0.5
> jdk 1.8u111
> sles 12
>Reporter: Jörg Sesterhenn
>Priority: Major
> Attachments: surefire-1628-mwe.zip
>
>
> The plugin seems to require plexus-java which cannot be found.
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test
> (default-integration-test) on project MyParentPOM: Execution
> default-integration-test of goal
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test
> failed: Unable to load the mojo 'integration-test' (or one of its required
> components) from the plugin
> 'org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3':
> com.google.inject.ProvisionException: Guice provision errors:
> [ERROR] 1) No implementation for
> org.codehaus.plexus.languages.java.jpms.LocationManager was bound.
> [ERROR] while locating org.apache.maven.plugin.failsafe.IntegrationTestMojo
> [ERROR] at
> ClassRealm[plugin>org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3,
> parent: sun.misc.Launcher$AppClassLoader@55f96302]
> [ERROR] while locating org.apache.maven.plugin.Mojo annotated with
> @com.google.inject.name.Named(value=org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test)
> [ERROR] 1 error
> [ERROR] role: org.apache.maven.plugin.Mojo
> [ERROR] roleHint:
> org.apache.maven.plugins:maven-failsafe-plugin:3.0.0-M3:integration-test
> [ERROR] -> [Help 1]
> [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] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-surefire] elharo commented on issue #271: docs: codehaus is defunct
elharo commented on issue #271: docs: codehaus is defunct URL: https://github.com/apache/maven-surefire/pull/271#issuecomment-595525076 Repositories can be configured by owners to require squash commits if that is preferred. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-surefire] Tibor17 edited a comment on issue #273: JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
Tibor17 edited a comment on issue #273: JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups URL: https://github.com/apache/maven-surefire/pull/273#issuecomment-595523434 @sparsick This is important issue for the user in the release notes. Pls create JIRA ticket and rename the title, and the message of commit in this issue in GH to `[] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups`. This is the JIRA link https://issues.apache.org/jira/projects/SUREFIRE/ This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-surefire] Tibor17 edited a comment on issue #273: JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
Tibor17 edited a comment on issue #273: JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups URL: https://github.com/apache/maven-surefire/pull/273#issuecomment-595523434 @sparsick This is important issue for the use in the release notes. Pls create JIRA ticket and rename the title, and the message of commit in this issue in GH to `[] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups`. This is the JIRA link https://issues.apache.org/jira/projects/SUREFIRE/ This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-surefire] Tibor17 commented on issue #273: JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups
Tibor17 commented on issue #273: JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups URL: https://github.com/apache/maven-surefire/pull/273#issuecomment-595523434 @sparsick This is important issue for the use in the release notes. Pls create JIRA ticket and rename the title in this issue in GH to `[] JUnit Platform provider isn't mentioned in the docu about groups and excludeGroups`. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-surefire] Tibor17 commented on issue #271: docs: codehaus is defunct
Tibor17 commented on issue #271: docs: codehaus is defunct URL: https://github.com/apache/maven-surefire/pull/271#issuecomment-595522043 @elharo Pls always use the squash/rebase here in GH button. This prevents from the merge commit in the commit history and the pull request will have just one commit on the top of the remote HEAD commit. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-shared-utils] slachiewicz commented on issue #12: deps: update JUnit
slachiewicz commented on issue #12: deps: update JUnit URL: https://github.com/apache/maven-shared-utils/pull/12#issuecomment-595512369 merged 2e3bcacb8744acfafa9e52a27adb2a1d61eaed91 (sorry typo in pr no) This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (MPIR-384) Use PatternExcludesArtifactFilter to exclude artifacts in PluginManagement
[ https://issues.apache.org/jira/browse/MPIR-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-384. - Resolution: Fixed > Use PatternExcludesArtifactFilter to exclude artifacts in PluginManagement > -- > > Key: MPIR-384 > URL: https://issues.apache.org/jira/browse/MPIR-384 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Gabriel Belingueres >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > > Cherry pick this commit containing the change: > [https://github.com/apache/maven-project-info-reports-plugin/pull/7/commits/56a2c7305cf2227d37980dd0e1fd911432a34e32] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-surefire] Tibor17 edited a comment on issue #272: it would be better to use sha-512
Tibor17 edited a comment on issue #272: it would be better to use sha-512 URL: https://github.com/apache/maven-surefire/pull/272#issuecomment-595503554 @YYTVicky Not sure if you know what purpose is of this class. It is not about security nothing but a placeholder string for the entire configuration. It is only an identity string identifying the identity of the config. Nothing else. If we use SHA 512, we may this way slow down the plugin execution a bit. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-surefire] Tibor17 commented on issue #272: it would be better to use sha-512
Tibor17 commented on issue #272: it would be better to use sha-512 URL: https://github.com/apache/maven-surefire/pull/272#issuecomment-595503554 @YYTVicky Not sure if you know what purpose is of this class. It is not about security nothing but a placeholder string for the entire configuration. It is not about security. It is only an identity string identifying the identity of the config. Nothing else. If we use SHA 512, we may this way slow down the plugin execution a bit. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (MPIR-384) Use PatternExcludesArtifactFilter to exclude artifacts in PluginManagement
[ https://issues.apache.org/jira/browse/MPIR-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052600#comment-17052600 ] Hudson commented on MPIR-384: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #93 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/93/ > Use PatternExcludesArtifactFilter to exclude artifacts in PluginManagement > -- > > Key: MPIR-384 > URL: https://issues.apache.org/jira/browse/MPIR-384 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Gabriel Belingueres >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > > Cherry pick this commit containing the change: > [https://github.com/apache/maven-project-info-reports-plugin/pull/7/commits/56a2c7305cf2227d37980dd0e1fd911432a34e32] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-386) Project building errors with plugins and central repository override
[
https://issues.apache.org/jira/browse/MPIR-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052599#comment-17052599
]
Hudson commented on MPIR-386:
-
Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin »
master #92
See
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/92/
> Project building errors with plugins and central repository override
>
>
> Key: MPIR-386
> URL: https://issues.apache.org/jira/browse/MPIR-386
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Eddie Wiegers
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Seeing errors like the following during site generation:
> {noformat}
> [ERROR] Unresolveable build extension: Plugin
> org.example:custom-extension:1.0.0 or one of its dependencies could not be
> resolved: Failure to find org.example:custom-extension:1.0.0 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 @
> [ERROR] Unknown packaging: custom-extension @ line 15, column 14
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:194)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:329)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147){noformat}
> My projects are overriding the {{central}} repository (and pluginRepository)
> that come from the Super POM, but that appears not to be honored here.
>
> From what I can tell, the problem here is that the
> {{pluginArtifactRepositories}} are not set on the building request:
> [https://github.com/apache/maven-project-info-reports-plugin/blob/ecdd72249300f64331b89bcd11ad3cdd253cf223/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java#L144]
>
> When I add:
> {code:java}
> buildingRequest.setPluginArtifactRepositories( remoteRepositories );
> {code}
> The site generates without errors. However, I'm not sure that using
> {{remoteRepositories}} is appropriate here as I'm not sure exactly how those
> can be populated. Using {{project.getPluginArtifactRepositories()}} should
> also work.
>
> I can create the PR, I just wanted to get feedback on the correct fix first.
> I also see this same code in the {{DependencyManagementReport}} and assume
> the same fix may need to be applied there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MPIR-387) make build Reproducible
[ https://issues.apache.org/jira/browse/MPIR-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-387: -- Fix Version/s: 3.1.0 > make build Reproducible > --- > > Key: MPIR-387 > URL: https://issues.apache.org/jira/browse/MPIR-387 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.0.1, 3.1.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-384) Use PatternExcludesArtifactFilter to exclude artifacts in PluginManagement
[ https://issues.apache.org/jira/browse/MPIR-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052597#comment-17052597 ] Sylwester Lachiewicz commented on MPIR-384: --- Done in [38dfe09323cc641e9746bb3d44a4550d64f23a94|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=38dfe09323cc641e9746bb3d44a4550d64f23a94] > Use PatternExcludesArtifactFilter to exclude artifacts in PluginManagement > -- > > Key: MPIR-384 > URL: https://issues.apache.org/jira/browse/MPIR-384 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Gabriel Belingueres >Assignee: Sylwester Lachiewicz >Priority: Minor > Fix For: 3.1.0 > > > Cherry pick this commit containing the change: > [https://github.com/apache/maven-project-info-reports-plugin/pull/7/commits/56a2c7305cf2227d37980dd0e1fd911432a34e32] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-386) Project building errors with plugins and central repository override
[
https://issues.apache.org/jira/browse/MPIR-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052595#comment-17052595
]
Hudson commented on MPIR-386:
-
Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin »
master #91
See
https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/91/
> Project building errors with plugins and central repository override
>
>
> Key: MPIR-386
> URL: https://issues.apache.org/jira/browse/MPIR-386
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Eddie Wiegers
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Seeing errors like the following during site generation:
> {noformat}
> [ERROR] Unresolveable build extension: Plugin
> org.example:custom-extension:1.0.0 or one of its dependencies could not be
> resolved: Failure to find org.example:custom-extension:1.0.0 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 @
> [ERROR] Unknown packaging: custom-extension @ line 15, column 14
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:194)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:329)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147){noformat}
> My projects are overriding the {{central}} repository (and pluginRepository)
> that come from the Super POM, but that appears not to be honored here.
>
> From what I can tell, the problem here is that the
> {{pluginArtifactRepositories}} are not set on the building request:
> [https://github.com/apache/maven-project-info-reports-plugin/blob/ecdd72249300f64331b89bcd11ad3cdd253cf223/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java#L144]
>
> When I add:
> {code:java}
> buildingRequest.setPluginArtifactRepositories( remoteRepositories );
> {code}
> The site generates without errors. However, I'm not sure that using
> {{remoteRepositories}} is appropriate here as I'm not sure exactly how those
> can be populated. Using {{project.getPluginArtifactRepositories()}} should
> also work.
>
> I can create the PR, I just wanted to get feedback on the correct fix first.
> I also see this same code in the {{DependencyManagementReport}} and assume
> the same fix may need to be applied there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MPIR-386) Project building errors with plugins and central repository override
[
https://issues.apache.org/jira/browse/MPIR-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MPIR-386.
-
Resolution: Fixed
> Project building errors with plugins and central repository override
>
>
> Key: MPIR-386
> URL: https://issues.apache.org/jira/browse/MPIR-386
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Eddie Wiegers
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Seeing errors like the following during site generation:
> {noformat}
> [ERROR] Unresolveable build extension: Plugin
> org.example:custom-extension:1.0.0 or one of its dependencies could not be
> resolved: Failure to find org.example:custom-extension:1.0.0 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 @
> [ERROR] Unknown packaging: custom-extension @ line 15, column 14
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:194)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:329)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147){noformat}
> My projects are overriding the {{central}} repository (and pluginRepository)
> that come from the Super POM, but that appears not to be honored here.
>
> From what I can tell, the problem here is that the
> {{pluginArtifactRepositories}} are not set on the building request:
> [https://github.com/apache/maven-project-info-reports-plugin/blob/ecdd72249300f64331b89bcd11ad3cdd253cf223/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java#L144]
>
> When I add:
> {code:java}
> buildingRequest.setPluginArtifactRepositories( remoteRepositories );
> {code}
> The site generates without errors. However, I'm not sure that using
> {{remoteRepositories}} is appropriate here as I'm not sure exactly how those
> can be populated. Using {{project.getPluginArtifactRepositories()}} should
> also work.
>
> I can create the PR, I just wanted to get feedback on the correct fix first.
> I also see this same code in the {{DependencyManagementReport}} and assume
> the same fix may need to be applied there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPIR-390) Verify build by Github action
[ https://issues.apache.org/jira/browse/MPIR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052594#comment-17052594 ] Sylwester Lachiewicz commented on MPIR-390: --- Done in [57463e6a899d61dcdab38c9b8a2d5dfae1192558|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=57463e6a899d61dcdab38c9b8a2d5dfae1192558] > Verify build by Github action > - > > Key: MPIR-390 > URL: https://issues.apache.org/jira/browse/MPIR-390 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > Using Github Action to verify your build - this will help collaborators with > earlier PR verification. > On the project side, we're still using builds and verifications with Jenkins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPIR-390) Verify build by Github action
[ https://issues.apache.org/jira/browse/MPIR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-390. - Resolution: Fixed > Verify build by Github action > - > > Key: MPIR-390 > URL: https://issues.apache.org/jira/browse/MPIR-390 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > Using Github Action to verify your build - this will help collaborators with > earlier PR verification. > On the project side, we're still using builds and verifications with Jenkins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-386) Project building errors with plugins and central repository override
[
https://issues.apache.org/jira/browse/MPIR-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052593#comment-17052593
]
Sylwester Lachiewicz commented on MPIR-386:
---
Done in
[03bce34f049dc6fceb39b1b32924316477cca062|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=03bce34f049dc6fceb39b1b32924316477cca062]
> Project building errors with plugins and central repository override
>
>
> Key: MPIR-386
> URL: https://issues.apache.org/jira/browse/MPIR-386
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependencies
>Affects Versions: 3.0.0
>Reporter: Eddie Wiegers
>Assignee: Sylwester Lachiewicz
>Priority: Major
> Fix For: 3.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Seeing errors like the following during site generation:
> {noformat}
> [ERROR] Unresolveable build extension: Plugin
> org.example:custom-extension:1.0.0 or one of its dependencies could not be
> resolved: Failure to find org.example:custom-extension:1.0.0 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 @
> [ERROR] Unknown packaging: custom-extension @ line 15, column 14
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:194)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:329)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
> at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
> at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147){noformat}
> My projects are overriding the {{central}} repository (and pluginRepository)
> that come from the Super POM, but that appears not to be honored here.
>
> From what I can tell, the problem here is that the
> {{pluginArtifactRepositories}} are not set on the building request:
> [https://github.com/apache/maven-project-info-reports-plugin/blob/ecdd72249300f64331b89bcd11ad3cdd253cf223/src/main/java/org/apache/maven/report/projectinfo/DependenciesReport.java#L144]
>
> When I add:
> {code:java}
> buildingRequest.setPluginArtifactRepositories( remoteRepositories );
> {code}
> The site generates without errors. However, I'm not sure that using
> {{remoteRepositories}} is appropriate here as I'm not sure exactly how those
> can be populated. Using {{project.getPluginArtifactRepositories()}} should
> also work.
>
> I can create the PR, I just wanted to get feedback on the correct fix first.
> I also see this same code in the {{DependencyManagementReport}} and assume
> the same fix may need to be applied there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPIR-390) Verify build by Github action
[ https://issues.apache.org/jira/browse/MPIR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052592#comment-17052592 ] Hudson commented on MPIR-390: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #90 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/90/ > Verify build by Github action > - > > Key: MPIR-390 > URL: https://issues.apache.org/jira/browse/MPIR-390 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > Using Github Action to verify your build - this will help collaborators with > earlier PR verification. > On the project side, we're still using builds and verifications with Jenkins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-project-info-reports-plugin] asfgit closed pull request #13: [MPIR-386] Add plugin repositories to project building requests
asfgit closed pull request #13: [MPIR-386] Add plugin repositories to project building requests URL: https://github.com/apache/maven-project-info-reports-plugin/pull/13 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-project-info-reports-plugin] slachiewicz commented on issue #14: verify build by github action
slachiewicz commented on issue #14: verify build by github action URL: https://github.com/apache/maven-project-info-reports-plugin/pull/14#issuecomment-595489628 Change merged, thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to 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-1757) maven-surefire-plugin versions starting from 2.22.0 do not run JUnit5 Test Suites junit-platform-runner
[
https://issues.apache.org/jira/browse/SUREFIRE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052588#comment-17052588
]
Tibor Digana commented on SUREFIRE-1757:
[~DenysGalyuk]
The plugins are significantly different and the old 2.22.1 cannot better
resolve the conflicts between your dependencies and the embedded provider
dependencies.
I think you use wrong dependencies.
Why you have {{junit-platform-runner}} and why you do not use the only APIs
{{junit-jupiter-api}} and {{junit:junit:4.13}}, see the last part of the
documentation:
https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-platform.html
> maven-surefire-plugin versions starting from 2.22.0 do not run JUnit5 Test
> Suites junit-platform-runner
> ---
>
> Key: SUREFIRE-1757
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1757
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.22.0, 2.22.1, 2.22.2, 3.0.0-M2, 3.0.0-M1, 3.0.0-M3,
> 3.0.0-M4
>Reporter: Denys Galyuk
>Assignee: Tibor Digana
>Priority: Major
> Attachments: Build_Failure.png, Build_Success.png, tag.7z
>
>
> h1. {color:#00875A}plugin works with version 2.19.1 (or 2.20, or
> 2.21.0){color}
> I've attached the project archive to the bug report.
> h2. *Preconditions:*
> h3. pom.xml
> # *{color:#00875A}maven-surefire-plugin 2.19.1{color}* (or 2.20, or 2.21.0)
> # maven-compiler-plugin 3.8.1
> # junit-platform-runner 1.6.0
> # junit-jupiter-engine 5.6.0
> {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
>tag
>tag
>1.0-SNAPSHOT
>
>
>
>org.junit.jupiter
>junit-jupiter-engine
>5.6.0
>test
>
>
>
>org.junit.platform
>junit-platform-runner
>1.6.0
>test
>
>
>
>
>
>
>org.apache.maven.plugins
>maven-compiler-plugin
>3.8.1
>
>1.8
>1.8
>UTF-8
>
>
>
>
>org.apache.maven.plugins
>maven-surefire-plugin
>
>
>
>
>
>
>
>
>
>
>2.21.0
>
>
>
>
>
>
> {code}
> h3. Test class base on JUnit5: @Test,@Tag,@Tags
> {code:java}package tests.testsuites.suite1;
> import org.junit.jupiter.api.Tag;
> import org.junit.jupiter.api.Tags;
> import org.junit.jupiter.api.Test;
> import static org.junit.jupiter.api.Assertions.assertTrue;
> public class Suite2TestNameTagsTests {
>@Test
>@Tag("UAT")
>void suite2_1Test() {
>System.out.println("Suite2TestNameTagsTests:suite2_1Test(UAT tag)");
>assertTrue(true);
>}
>@Test
>@Tag("SMOKE")
>void suite2_2Test() {
>System.out.println("Suite2TestNameTagsTests:suite2_2Test(SMOKE tag)");
>assertTrue(true);
>}
>@Test
>@Tags({@Tag("SMOKE"), @Tag("UAT")})
>void suite2_3Test() {
>System.out.println("Suite2TestNameTagsTests:suite2_3Test(SMOKE and UAT
> tags)");
>assertTrue(true);
>}
> }{code}
> h3. JUnit5 Test Suite based on: @RunWith, @SelectPackages, @IncludeTags
> {code:java}package tests.suites;
> import org.junit.platform.runner.JUnitPlatform;
> import org.junit.platform.suite.api.IncludeTags;
> import org.junit.platform.suite.api.SelectPackages;
> import org.junit.runner.RunWith;
> @RunWith(JUnitPlatform.class)
> @SelectPackages("tests")
> @IncludeTags({"SMOKE","UAT"})
> public class SmokeAndUatSuiteTest {
> }{code}
> h3. Steps to reproduce: (Run the created test suite with maven)
> # Open terminal or GitBASH in the project folder
> # Run the command mvn clean test -Dtest=TestSuite
> h4. Actual Result: (something like this)
> {color:#00875A}*BUILD SUCCESS*
> *Tests run: 6, Failures: 0, Errors: 0, Skipped: 0*{color}
> {code}$ mvn clean test -Dtest=SmokeAndUatSuiteTest
> [INFO] Scanning for projects...
> [INFO]
> [INFO] --< tag:tag
> >---
> [INFO] Building tag 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ tag ---
> [INFO] Deleting C:\Users\galyuk\IdeaProjects\tag\target
> [INFO]
> [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ tag ---
> [WARNING] Using platform encoding (Cp1252
[jira] [Updated] (MPIR-390) Verify build by Github action
[ https://issues.apache.org/jira/browse/MPIR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-390: -- Fix Version/s: 3.1.0 > Verify build by Github action > - > > Key: MPIR-390 > URL: https://issues.apache.org/jira/browse/MPIR-390 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > Using Github Action to verify your build - this will help collaborators with > earlier PR verification. > On the project side, we're still using builds and verifications with Jenkins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MPIR-390) Verify build by Github action
[ https://issues.apache.org/jira/browse/MPIR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPIR-390: - Assignee: Sylwester Lachiewicz > Verify build by Github action > - > > Key: MPIR-390 > URL: https://issues.apache.org/jira/browse/MPIR-390 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > > Using Github Action to verify your build - this will help collaborators with > earlier PR verification. > On the project side, we're still using builds and verifications with Jenkins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-388) upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts
[ https://issues.apache.org/jira/browse/MPIR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052579#comment-17052579 ] Sylwester Lachiewicz commented on MPIR-388: --- Done in [d3efb03979868e1400f94858c97ce59de0d350da|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=d3efb03979868e1400f94858c97ce59de0d350da] > upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts > --- > > Key: MPIR-388 > URL: https://issues.apache.org/jira/browse/MPIR-388 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Herve Boutemy >Assignee: Sylwester Lachiewicz >Priority: Major > Labels: up-for-grabs > Fix For: 3.1.0 > > > to benefit from dependencies removal in DOXIASITETOOLS-215 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPIR-388) upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts
[ https://issues.apache.org/jira/browse/MPIR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-388. - Resolution: Fixed > upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts > --- > > Key: MPIR-388 > URL: https://issues.apache.org/jira/browse/MPIR-388 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Herve Boutemy >Assignee: Sylwester Lachiewicz >Priority: Major > Labels: up-for-grabs > Fix For: 3.1.0 > > > to benefit from dependencies removal in DOXIASITETOOLS-215 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MPIR-388) upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts
[ https://issues.apache.org/jira/browse/MPIR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPIR-388: - Assignee: Sylwester Lachiewicz > upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts > --- > > Key: MPIR-388 > URL: https://issues.apache.org/jira/browse/MPIR-388 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Herve Boutemy >Assignee: Sylwester Lachiewicz >Priority: Major > Labels: up-for-grabs > Fix For: 3.1.0 > > > to benefit from dependencies removal in DOXIASITETOOLS-215 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MPIR-390) Verify build by Github action
Sylwester Lachiewicz created MPIR-390: - Summary: Verify build by Github action Key: MPIR-390 URL: https://issues.apache.org/jira/browse/MPIR-390 Project: Maven Project Info Reports Plugin Issue Type: Improvement Reporter: Sylwester Lachiewicz Using Github Action to verify your build - this will help collaborators with earlier PR verification. On the project side, we're still using builds and verifications with Jenkins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-373) Upgrade from 2.9 to 3.0.0 introduces additional warning
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052570#comment-17052570
]
Sylwester Lachiewicz commented on MPIR-373:
---
I'm reviewing remaining issues, please expect mail to vote on release on maven
dev mailing list.
> Upgrade from 2.9 to 3.0.0 introduces additional warning
> ---
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: GWR
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Attachments: pom.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> 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 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:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main
[jira] [Commented] (MPIR-388) upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts
[ https://issues.apache.org/jira/browse/MPIR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052562#comment-17052562 ] Hudson commented on MPIR-388: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #89 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/89/ > upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts > --- > > Key: MPIR-388 > URL: https://issues.apache.org/jira/browse/MPIR-388 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Herve Boutemy >Priority: Major > Labels: up-for-grabs > Fix For: 3.1.0 > > > to benefit from dependencies removal in DOXIASITETOOLS-215 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPIR-388) upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts
[ https://issues.apache.org/jira/browse/MPIR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-388: -- Fix Version/s: 3.1.0 > upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts > --- > > Key: MPIR-388 > URL: https://issues.apache.org/jira/browse/MPIR-388 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Herve Boutemy >Priority: Major > Labels: up-for-grabs > Fix For: 3.1.0 > > > to benefit from dependencies removal in DOXIASITETOOLS-215 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-389. - Resolution: Fixed > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL: https://issues.apache.org/jira/browse/MPIR-389 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > h2. Release Notes - Maven Doxia - Version 1.9 > h3. Bug > * [DOXIA-497] - APTSink: links and paragraphs inside tables > * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag > * [DOXIA-567] - update dependency schema: pegdown not used any more but > flexmark-java > * [DOXIA-570] - Unescaped links in xml based figureGraphics elements > * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink > * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax > * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the > list > * [DOXIA-581] - Provide a usable output implementation for definition lists > * [DOXIA-582] - Text within a monospace block need to escape characters with > special meaning in Confluence > * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly > h3. New Feature > * [DOXIA-584] - Support rewriting multiple page documentation crosslinks > from .md to .html > h3. Improvement > * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) > * [DOXIA-528] - Enable rendering of HTML5 data- attributes > * [DOXIA-575] - Add support for (X)HTML5 > * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml > parser > * [DOXIA-587] - Maven site generate invalid link with markdown > h3. Task > * [DOXIA-586] - Removed unused properties and cleaned up pom file > * [DOXIA-591] - Require minimum Java 7 at runtime > h3. Dependency upgrade > * [DOXIA-572] - Upgrade parent to 32 > * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 > (httpclient) > * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 > * [DOXIA-593] - Upgrade to Apache FOP 2.3 > h2. Release Notes - Maven Doxia - Version 1.9.1 > h3. Bug > * [DOXIA-571] - Markdown does not support syntax highlighting any more > * [DOXIA-595] - Cannot build site with reporting on Windows > * [DOXIA-597] - `code` not rendered as code > * [DOXIA-605] - Inline code elements in Markdown disappear in output > h3. Improvement > * [DOXIA-601] - Make Doxia build Reproducible > h3. Task > * [DOXIA-596] - add xhtml5 to modules image map > h3. Dependency upgrade > * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to > version 0.42.14 > * [DOXIA-602] - Upgrade test dependencies > * [DOXIA-604] - Upgrade to Apache FOP 2.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-373) Upgrade from 2.9 to 3.0.0 introduces additional warning
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052548#comment-17052548
]
Serge commented on MPIR-373:
Hey [~michael-o]. Thanks for joining in !
As a user, i don't know anything about the build process (and i can fully
understand it's time consuming and not so easy) - i'm just a bit surprised in
the end to see that it's possible to have some releases having been generated
without the corresponding artifacts having been published at the same in any
maven repository, as this is a bit why maven is in the first place : have some
easy way to retrieve dependencies (whatever they are, and including plugins),
without the hassle to have to locally build / publish.
So that being said, what can be done in the end to have this release generated
- as it seems you have some insider knowledge on this process, do you have any
clue about what to do about these artifacts not having been published ?
> Upgrade from 2.9 to 3.0.0 introduces additional warning
> ---
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: GWR
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Attachments: pom.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> 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 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
>
[jira] [Closed] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)
[
https://issues.apache.org/jira/browse/MPIR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MPIR-234.
-
Resolution: Auto Closed
> SCM-link in site of multimodule projects should not append module name by
> default (at least for git)
>
>
> Key: MPIR-234
> URL: https://issues.apache.org/jira/browse/MPIR-234
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: scm
>Affects Versions: 2.4
>Reporter: Mirko Friedenhagen
>Priority: Major
>
> I have setup a simple multi module project (see
> https://github.com/mfriedenhagen/multi-module-sample/tree/multi-site-complex)
> which uses git on github as {{scm}}. While rendering the site, MPIR will by
> default add the name of the module to the SCM-URLs in source-repository.html.
> So instead of https://github.com/mfriedenhagen/multi-module-sample/ I see
> https://github.com/mfriedenhagen/multi-module-sample/core/,
> g...@github.com:mfriedenhagen/multi-module-sample.git/core and
> git://github.com/mfriedenhagen/multi-module-sample.git/core in the report for
> the core module. All these URLs are invalid. For SVN this could be assumed to
> be the right behaviour, for git and probably other SCMs this is not true. As
> a workaround I have to reconfigure the scm section (see
> https://github.com/mfriedenhagen/multi-module-sample/blob/multi-site-complex/core/pom.xml)
> in the modules like this:
> {code:xml}
>
> ${project.parent.scm.connection}
>
> ${project.parent.scm.developerConnection}
> ${project.parent.scm.url}
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MPIR-382) Group different license spellings together
[ https://issues.apache.org/jira/browse/MPIR-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-382. - Fix Version/s: (was: wontfix-candidate) Resolution: Won't Fix > Group different license spellings together > -- > > Key: MPIR-382 > URL: https://issues.apache.org/jira/browse/MPIR-382 > Project: Maven Project Info Reports Plugin > Issue Type: Improvement > Components: licenses >Affects Versions: 3.0.0 >Reporter: Vincent Privat >Priority: Major > > The licenses report is not aware of the different possible spellings we can > find in all Maven dependencies published on Maven Central. This results in > any given license (for example, Apache 2.0) being listed several times. For > example, take a look to the seven variants listed in [maven-site-plugin > dependencies|http://maven.apache.org/plugins/maven-site-plugin/dependencies.html#Licenses]: > * Apache Public License 2.0 > * Apache License Version 2 > * Apache License, Version 2.0 > * Apache Software License - Version 2.0 > * Apache License 2.0 > * Apache License Version 2.0 > * The Apache Software License, Version 2.0 > On a large project, this makes the license report unreadable. The plugin > should detect all these variants denote the same license and group them > together. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052542#comment-17052542 ] Hudson commented on MPIR-389: - Build failed in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #87 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/87/ > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL: https://issues.apache.org/jira/browse/MPIR-389 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > h2. Release Notes - Maven Doxia - Version 1.9 > h3. Bug > * [DOXIA-497] - APTSink: links and paragraphs inside tables > * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag > * [DOXIA-567] - update dependency schema: pegdown not used any more but > flexmark-java > * [DOXIA-570] - Unescaped links in xml based figureGraphics elements > * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink > * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax > * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the > list > * [DOXIA-581] - Provide a usable output implementation for definition lists > * [DOXIA-582] - Text within a monospace block need to escape characters with > special meaning in Confluence > * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly > h3. New Feature > * [DOXIA-584] - Support rewriting multiple page documentation crosslinks > from .md to .html > h3. Improvement > * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) > * [DOXIA-528] - Enable rendering of HTML5 data- attributes > * [DOXIA-575] - Add support for (X)HTML5 > * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml > parser > * [DOXIA-587] - Maven site generate invalid link with markdown > h3. Task > * [DOXIA-586] - Removed unused properties and cleaned up pom file > * [DOXIA-591] - Require minimum Java 7 at runtime > h3. Dependency upgrade > * [DOXIA-572] - Upgrade parent to 32 > * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 > (httpclient) > * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 > * [DOXIA-593] - Upgrade to Apache FOP 2.3 > h2. Release Notes - Maven Doxia - Version 1.9.1 > h3. Bug > * [DOXIA-571] - Markdown does not support syntax highlighting any more > * [DOXIA-595] - Cannot build site with reporting on Windows > * [DOXIA-597] - `code` not rendered as code > * [DOXIA-605] - Inline code elements in Markdown disappear in output > h3. Improvement > * [DOXIA-601] - Make Doxia build Reproducible > h3. Task > * [DOXIA-596] - add xhtml5 to modules image map > h3. Dependency upgrade > * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to > version 0.42.14 > * [DOXIA-602] - Upgrade test dependencies > * [DOXIA-604] - Upgrade to Apache FOP 2.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MSHARED-856) Require Maven 3.1 or later
Elliotte Rusty Harold created MSHARED-856:
-
Summary: Require Maven 3.1 or later
Key: MSHARED-856
URL: https://issues.apache.org/jira/browse/MSHARED-856
Project: Maven Shared Components
Issue Type: Dependency upgrade
Components: maven-artifact-transfer
Reporter: Elliotte Rusty Harold
Can we remove support for pre-3.1 Mavens now? This is pulling in some really
old dependencies I don't trust and would like to get rid of:
{{}}{{ private MavenArtifactDeployer getMavenArtifactDeployer(
ProjectBuildingRequest buildingRequest )}}
{{ throws ComponentLookupException, ArtifactDeployerException}}
{{ {}}
{{ if ( isMaven31() )}}
{{ {}}
{{ org.eclipse.aether.RepositorySystem repositorySystem =}}
{{ container.lookup( org.eclipse.aether.RepositorySystem.class );}}
{{ org.eclipse.aether.RepositorySystemSession session =}}
{{ (org.eclipse.aether.RepositorySystemSession) Invoker.invoke(
buildingRequest, "getRepositorySession" );}}
{{ return new Maven31ArtifactDeployer( repositorySystem, session );}}
{{ }}}
{{ else}}
{{ {}}
{{ org.sonatype.aether.RepositorySystem repositorySystem =}}
{{ container.lookup( org.sonatype.aether.RepositorySystem.class );}}
{{ org.sonatype.aether.RepositorySystemSession session =}}
{{ (org.sonatype.aether.RepositorySystemSession) Invoker.invoke(
buildingRequest, "getRepositorySession" );}}
{{ return new Maven30ArtifactDeployer( repositorySystem, session );}}
{{ }}}
{{ }}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052540#comment-17052540 ] Sylwester Lachiewicz commented on MPIR-389: --- Done in [df96c2ef87f3962ffdeeba7b368deeb88cf2ac61|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=df96c2ef87f3962ffdeeba7b368deeb88cf2ac61] > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL: https://issues.apache.org/jira/browse/MPIR-389 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > h2. Release Notes - Maven Doxia - Version 1.9 > h3. Bug > * [DOXIA-497] - APTSink: links and paragraphs inside tables > * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag > * [DOXIA-567] - update dependency schema: pegdown not used any more but > flexmark-java > * [DOXIA-570] - Unescaped links in xml based figureGraphics elements > * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink > * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax > * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the > list > * [DOXIA-581] - Provide a usable output implementation for definition lists > * [DOXIA-582] - Text within a monospace block need to escape characters with > special meaning in Confluence > * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly > h3. New Feature > * [DOXIA-584] - Support rewriting multiple page documentation crosslinks > from .md to .html > h3. Improvement > * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) > * [DOXIA-528] - Enable rendering of HTML5 data- attributes > * [DOXIA-575] - Add support for (X)HTML5 > * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml > parser > * [DOXIA-587] - Maven site generate invalid link with markdown > h3. Task > * [DOXIA-586] - Removed unused properties and cleaned up pom file > * [DOXIA-591] - Require minimum Java 7 at runtime > h3. Dependency upgrade > * [DOXIA-572] - Upgrade parent to 32 > * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 > (httpclient) > * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 > * [DOXIA-593] - Upgrade to Apache FOP 2.3 > h2. Release Notes - Maven Doxia - Version 1.9.1 > h3. Bug > * [DOXIA-571] - Markdown does not support syntax highlighting any more > * [DOXIA-595] - Cannot build site with reporting on Windows > * [DOXIA-597] - `code` not rendered as code > * [DOXIA-605] - Inline code elements in Markdown disappear in output > h3. Improvement > * [DOXIA-601] - Make Doxia build Reproducible > h3. Task > * [DOXIA-596] - add xhtml5 to modules image map > h3. Dependency upgrade > * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to > version 0.42.14 > * [DOXIA-602] - Upgrade test dependencies > * [DOXIA-604] - Upgrade to Apache FOP 2.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-389: -- Fix Version/s: 3.1.0 > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL: https://issues.apache.org/jira/browse/MPIR-389 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > h2. Release Notes - Maven Doxia - Version 1.9 > h3. Bug > * [DOXIA-497] - APTSink: links and paragraphs inside tables > * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag > * [DOXIA-567] - update dependency schema: pegdown not used any more but > flexmark-java > * [DOXIA-570] - Unescaped links in xml based figureGraphics elements > * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink > * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax > * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the > list > * [DOXIA-581] - Provide a usable output implementation for definition lists > * [DOXIA-582] - Text within a monospace block need to escape characters with > special meaning in Confluence > * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly > h3. New Feature > * [DOXIA-584] - Support rewriting multiple page documentation crosslinks > from .md to .html > h3. Improvement > * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) > * [DOXIA-528] - Enable rendering of HTML5 data- attributes > * [DOXIA-575] - Add support for (X)HTML5 > * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml > parser > * [DOXIA-587] - Maven site generate invalid link with markdown > h3. Task > * [DOXIA-586] - Removed unused properties and cleaned up pom file > * [DOXIA-591] - Require minimum Java 7 at runtime > h3. Dependency upgrade > * [DOXIA-572] - Upgrade parent to 32 > * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 > (httpclient) > * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 > * [DOXIA-593] - Upgrade to Apache FOP 2.3 > h2. Release Notes - Maven Doxia - Version 1.9.1 > h3. Bug > * [DOXIA-571] - Markdown does not support syntax highlighting any more > * [DOXIA-595] - Cannot build site with reporting on Windows > * [DOXIA-597] - `code` not rendered as code > * [DOXIA-605] - Inline code elements in Markdown disappear in output > h3. Improvement > * [DOXIA-601] - Make Doxia build Reproducible > h3. Task > * [DOXIA-596] - add xhtml5 to modules image map > h3. Dependency upgrade > * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to > version 0.42.14 > * [DOXIA-602] - Upgrade test dependencies > * [DOXIA-604] - Upgrade to Apache FOP 2.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MPIR-389: - Assignee: Sylwester Lachiewicz > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL: https://issues.apache.org/jira/browse/MPIR-389 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Assignee: Sylwester Lachiewicz >Priority: Major > Fix For: 3.1.0 > > > h2. Release Notes - Maven Doxia - Version 1.9 > h3. Bug > * [DOXIA-497] - APTSink: links and paragraphs inside tables > * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag > * [DOXIA-567] - update dependency schema: pegdown not used any more but > flexmark-java > * [DOXIA-570] - Unescaped links in xml based figureGraphics elements > * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink > * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax > * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the > list > * [DOXIA-581] - Provide a usable output implementation for definition lists > * [DOXIA-582] - Text within a monospace block need to escape characters with > special meaning in Confluence > * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly > h3. New Feature > * [DOXIA-584] - Support rewriting multiple page documentation crosslinks > from .md to .html > h3. Improvement > * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) > * [DOXIA-528] - Enable rendering of HTML5 data- attributes > * [DOXIA-575] - Add support for (X)HTML5 > * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml > parser > * [DOXIA-587] - Maven site generate invalid link with markdown > h3. Task > * [DOXIA-586] - Removed unused properties and cleaned up pom file > * [DOXIA-591] - Require minimum Java 7 at runtime > h3. Dependency upgrade > * [DOXIA-572] - Upgrade parent to 32 > * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 > (httpclient) > * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 > * [DOXIA-593] - Upgrade to Apache FOP 2.3 > h2. Release Notes - Maven Doxia - Version 1.9.1 > h3. Bug > * [DOXIA-571] - Markdown does not support syntax highlighting any more > * [DOXIA-595] - Cannot build site with reporting on Windows > * [DOXIA-597] - `code` not rendered as code > * [DOXIA-605] - Inline code elements in Markdown disappear in output > h3. Improvement > * [DOXIA-601] - Make Doxia build Reproducible > h3. Task > * [DOXIA-596] - add xhtml5 to modules image map > h3. Dependency upgrade > * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to > version 0.42.14 > * [DOXIA-602] - Upgrade test dependencies > * [DOXIA-604] - Upgrade to Apache FOP 2.4 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-389: -- Description: h2. Release Notes - Maven Doxia - Version 1.9 h3. Bug * [DOXIA-497] - APTSink: links and paragraphs inside tables * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag * [DOXIA-567] - update dependency schema: pegdown not used any more but flexmark-java * [DOXIA-570] - Unescaped links in xml based figureGraphics elements * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the list * [DOXIA-581] - Provide a usable output implementation for definition lists * [DOXIA-582] - Text within a monospace block need to escape characters with special meaning in Confluence * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly h3. New Feature * [DOXIA-584] - Support rewriting multiple page documentation crosslinks from .md to .html h3. Improvement * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) * [DOXIA-528] - Enable rendering of HTML5 data- attributes * [DOXIA-575] - Add support for (X)HTML5 * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml parser * [DOXIA-587] - Maven site generate invalid link with markdown h3. Task * [DOXIA-586] - Removed unused properties and cleaned up pom file * [DOXIA-591] - Require minimum Java 7 at runtime h3. Dependency upgrade * [DOXIA-572] - Upgrade parent to 32 * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient) * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 * [DOXIA-593] - Upgrade to Apache FOP 2.3 h2. Release Notes - Maven Doxia - Version 1.9.1 h3. Bug * [DOXIA-571] - Markdown does not support syntax highlighting any more * [DOXIA-595] - Cannot build site with reporting on Windows * [DOXIA-597] - `code` not rendered as code * [DOXIA-605] - Inline code elements in Markdown disappear in output h3. Improvement * [DOXIA-601] - Make Doxia build Reproducible h3. Task * [DOXIA-596] - add xhtml5 to modules image map h3. Dependency upgrade * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to version 0.42.14 * [DOXIA-602] - Upgrade test dependencies * [DOXIA-604] - Upgrade to Apache FOP 2.4 was: Release Notes - Maven Doxia - Version 1.9 ** Bug * [DOXIA-497] - APTSink: links and paragraphs inside tables * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag * [DOXIA-567] - update dependency schema: pegdown not used any more but flexmark-java * [DOXIA-570] - Unescaped links in xml based figureGraphics elements * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the list * [DOXIA-581] - Provide a usable output implementation for definition lists * [DOXIA-582] - Text within a monospace block need to escape characters with special meaning in Confluence * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly ** New Feature * [DOXIA-584] - Support rewriting multiple page documentation crosslinks from .md to .html ** Improvement * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) * [DOXIA-528] - Enable rendering of HTML5 data- attributes * [DOXIA-575] - Add support for (X)HTML5 * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml parser * [DOXIA-587] - Maven site generate invalid link with markdown ** Task * [DOXIA-586] - Removed unused properties and cleaned up pom file * [DOXIA-591] - Require minimum Java 7 at runtime ** Dependency upgrade * [DOXIA-572] - Upgrade parent to 32 * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient) * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 * [DOXIA-593] - Upgrade to Apache FOP 2.3 Release Notes - Maven Doxia - Version 1.9.1 ** Bug * [DOXIA-571] - Markdown does not support syntax highlighting any more * [DOXIA-595] - Cannot build site with reporting on Windows * [DOXIA-597] - `code` not rendered as code * [DOXIA-605] - Inline code elements in Markdown disappear in output ** Improvement * [DOXIA-601] - Make Doxia build Reproducible ** Task * [DOXIA-596] - add xhtml5 to modules image map ** Dependency upgrade * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to version 0.42.14 * [DOXIA-602] - Upgrade test dependencies * [DOXIA-604] - Upgrade to Apache FOP 2.4 > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL:
[jira] [Updated] (MPIR-389) Upgrade Doxia to 1.9.1
[ https://issues.apache.org/jira/browse/MPIR-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MPIR-389: -- Description: Release Notes - Maven Doxia - Version 1.9 ** Bug * [DOXIA-497] - APTSink: links and paragraphs inside tables * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag * [DOXIA-567] - update dependency schema: pegdown not used any more but flexmark-java * [DOXIA-570] - Unescaped links in xml based figureGraphics elements * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after the list * [DOXIA-581] - Provide a usable output implementation for definition lists * [DOXIA-582] - Text within a monospace block need to escape characters with special meaning in Confluence * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly ** New Feature * [DOXIA-584] - Support rewriting multiple page documentation crosslinks from .md to .html ** Improvement * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) * [DOXIA-528] - Enable rendering of HTML5 data- attributes * [DOXIA-575] - Add support for (X)HTML5 * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml parser * [DOXIA-587] - Maven site generate invalid link with markdown ** Task * [DOXIA-586] - Removed unused properties and cleaned up pom file * [DOXIA-591] - Require minimum Java 7 at runtime ** Dependency upgrade * [DOXIA-572] - Upgrade parent to 32 * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 (httpclient) * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 * [DOXIA-593] - Upgrade to Apache FOP 2.3 Release Notes - Maven Doxia - Version 1.9.1 ** Bug * [DOXIA-571] - Markdown does not support syntax highlighting any more * [DOXIA-595] - Cannot build site with reporting on Windows * [DOXIA-597] - `code` not rendered as code * [DOXIA-605] - Inline code elements in Markdown disappear in output ** Improvement * [DOXIA-601] - Make Doxia build Reproducible ** Task * [DOXIA-596] - add xhtml5 to modules image map ** Dependency upgrade * [DOXIA-600] - com.vladsch.flexmark:flexmark need to be updated to version 0.42.14 * [DOXIA-602] - Upgrade test dependencies * [DOXIA-604] - Upgrade to Apache FOP 2.4 > Upgrade Doxia to 1.9.1 > -- > > Key: MPIR-389 > URL: https://issues.apache.org/jira/browse/MPIR-389 > Project: Maven Project Info Reports Plugin > Issue Type: Dependency upgrade >Reporter: Sylwester Lachiewicz >Priority: Major > > Release Notes - Maven Doxia - Version 1.9 > ** Bug > * [DOXIA-497] - APTSink: links and paragraphs inside tables > * [DOXIA-538] - Tag used for monospaced is not a valid html5 tag > * [DOXIA-567] - update dependency schema: pegdown not used any more but > flexmark-java > * [DOXIA-570] - Unescaped links in xml based figureGraphics elements > * [DOXIA-577] - Handle whitespace in tables properly in ConfluenceSink > * [DOXIA-578] - Boxed verbatim sections uses incorrect Confluence syntax > * [DOXIA-579] - Lists in Confluence syntax requires 2 line breaks after > the list > * [DOXIA-581] - Provide a usable output implementation for definition > lists > * [DOXIA-582] - Text within a monospace block need to escape characters > with special meaning in Confluence > * [DOXIA-583] - XhtmlBaseSink: Table caption is escaped incorrectly > ** New Feature > * [DOXIA-584] - Support rewriting multiple page documentation crosslinks > from .md to .html > ** Improvement > * [DOXIA-409] - Upgrade to Apache FOP 2.2 (was 1.0) > * [DOXIA-528] - Enable rendering of HTML5 data- attributes > * [DOXIA-575] - Add support for (X)HTML5 > * [DOXIA-585] - Propagate macro related exceptions to caller in xhtml > parser > * [DOXIA-587] - Maven site generate invalid link with markdown > ** Task > * [DOXIA-586] - Removed unused properties and cleaned up pom file > * [DOXIA-591] - Require minimum Java 7 at runtime > ** Dependency upgrade > * [DOXIA-572] - Upgrade parent to 32 > * [DOXIA-576] - Upgrade Http Components to 4.4.11 (core) and 4.5.8 > (httpclient) > * [DOXIA-592] - Upgrade Markdown parser - flexmark-java to 0.42.8 > * [DOXIA-593] - Upgrade to Apache FOP 2.3 > Release Notes - Maven Doxia - Version 1.9.1 > ** Bug > * [DOXIA-571] - Markdown does not support syntax highlighting any more > * [DOXIA-595] - Cannot build site with reporting on Windows > * [DOXIA-597] - `code` not rendered as code > * [DOXIA-605] - Inline code elements in Markdown disappear in output > ** Improvement > *
[jira] [Created] (MPIR-389) Upgrade Doxia to 1.9.1
Sylwester Lachiewicz created MPIR-389: - Summary: Upgrade Doxia to 1.9.1 Key: MPIR-389 URL: https://issues.apache.org/jira/browse/MPIR-389 Project: Maven Project Info Reports Plugin Issue Type: Dependency upgrade Reporter: Sylwester Lachiewicz -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052418#comment-17052418
]
Michael Osipov commented on MASSEMBLY-929:
--
Also works on:
{noformat}
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T20:33:14+02:00)
Maven home: /usr/local/apache-maven-3.5.4
Java version: 1.8.0_242, vendor: Oracle Corporation, runtime:
/usr/local/openjdk8/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "12.1-stable", arch: "amd64", family: "unix"
{noformat}
{noformat}
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T20:33:14+02:00)
Maven home: /usr/local/apache-maven-3.5.4
Java version: 11.0.6, vendor: Oracle Corporation, runtime: /usr/local/openjdk11
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "12.1-stable", arch: "amd64", family: "unix"
{noformat}
{noformat}
$ unzip -t target/camel-activemq-1.0.0-SNAPSHOT-jar-with-dependencies.jar |
grep JAXB
testing: org/apache/camel/impl/DefaultModelJAXBContextFactory.class OK
testing: org/apache/camel/spi/ModelJAXBContextFactory.class OK
testing: org/apache/camel/spring/SpringModelJAXBContextFactory.class
OK
testing: META-INF/JAXB/episode_generate%20schema.xjb OK
{noformat}
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Michael Ritzert
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052415#comment-17052415
]
Michael Osipov commented on MASSEMBLY-929:
--
I cannot reproduce the issue with Maven 3.7.0-SNAPSHOT, MASSEMBY 3.2.0, Zulu 8,
Zulu 11 or Zulu 13. Works for me at least on Windows. Will try AdoptOpenJDK on
FreeBSD.
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Michael Ritzert
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052405#comment-17052405
]
Michael Osipov commented on MASSEMBLY-929:
--
One side note: the episode file is pointless, it contains an empty root element.
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Michael Ritzert
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MASSEMBLY-929:
-
Affects Version/s: 3.2.0
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Michael Ritzert
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052395#comment-17052395
]
Michael Osipov commented on MASSEMBLY-929:
--
Can you please provide debug log?
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Michael Ritzert
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MASSEMBLY-929:
-
Priority: Major (was: Minor)
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Michael Ritzert
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPIR-373) Upgrade from 2.9 to 3.0.0 introduces additional warning
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052392#comment-17052392
]
Michael Osipov commented on MPIR-373:
-
[~jansohn], that is not true. I have invested a LOT of FREE time in the last
couple of years into it. We work on stuff when we have spare time or the
motivation. You may grab the failed vote, workout on the issue, discuss and
provide a solution. Also consider releasing a component is just a lot of work.
It is way more than just {{mvn release:prepare release:perform}},
> Upgrade from 2.9 to 3.0.0 introduces additional warning
> ---
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: GWR
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Attachments: pom.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> 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 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)
[jira] [Commented] (MSHADE-353) Any transformer should be "relocatable"
[ https://issues.apache.org/jira/browse/MSHADE-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052194#comment-17052194 ] Thomas Andraschko commented on MSHADE-353: -- Tested with PrimeFaces and works fine; See my comment in the PR > Any transformer should be "relocatable" > --- > > Key: MSHADE-353 > URL: https://issues.apache.org/jira/browse/MSHADE-353 > Project: Maven Shade Plugin > Issue Type: Task >Reporter: Romain Manni-Bucau >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Need is to ensure any transformer can relocate its resource contents, even if > originally not designed as such. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-shade-plugin] tandraschko commented on issue #39: [MSHADE-353] adding a generic relocation friendly transformer
tandraschko commented on issue #39: [MSHADE-353] adding a generic relocation friendly transformer URL: https://github.com/apache/maven-shade-plugin/pull/39#issuecomment-595257807 tested and works fine: https://github.com/primefaces/primefaces/commit/9e8e2c3b81005f5f8ef8cd77c5a8a42449c8a327 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [maven-shade-plugin] rmannibucau opened a new pull request #39: [MSHADE-353] adding a generic relocation friendly transformer
rmannibucau opened a new pull request #39: [MSHADE-353] adding a generic relocation friendly transformer URL: https://github.com/apache/maven-shade-plugin/pull/39 The generic transformer will actually delegate to other transformers for the actual processing to avoid to reimplement again and again the same logic. //cc @rfscholte can you review it since you worked on the manifest flavor? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] [Comment Edited] (MPIR-373) Upgrade from 2.9 to 3.0.0 introduces additional warning
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052172#comment-17052172
]
Robin Jansohn edited comment on MPIR-373 at 3/5/20, 2:14 PM:
-
We're in the same boat. Seems like this plugin is pretty much dead since no one
feels responsible for creating releases for fixed bugs.
You could try building the repository locally and maybe deploy it to your
internal Maven repository to work around the problem...
was (Author: jansohn):
We're in the same boat. Seems like this plugin is pretty much dead since no one
feels responsible of creating releases for fixed bugs.
You could try building the repository locally and maybe deploy it to your
internal Maven repository to work around the problem...
> Upgrade from 2.9 to 3.0.0 introduces additional warning
> ---
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: GWR
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Attachments: pom.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> 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 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)
>
[jira] [Commented] (MPIR-373) Upgrade from 2.9 to 3.0.0 introduces additional warning
[
https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052172#comment-17052172
]
Robin Jansohn commented on MPIR-373:
We're in the same boat. Seems like this plugin is pretty much dead since no one
feels responsible of creating releases for fixed bugs.
You could try building the repository locally and maybe deploy it to your
internal Maven repository to work around the problem...
> Upgrade from 2.9 to 3.0.0 introduces additional warning
> ---
>
> Key: MPIR-373
> URL: https://issues.apache.org/jira/browse/MPIR-373
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: GWR
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.0.1, 3.1.0
>
> Attachments: pom.xml
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> a new warning-message introduced, causing some confusion in the devteam.
> When stepping up to maven-project-info-reports-plugin:3.0.0 (from2.9) the
> stacktrace below is seen.
> mvn3.0.5, 3.3.9 and 3.5.2 all give same stacktrace.
> Seems to caused by the xml-resolver:1.2, having a pom.xml containing the
> section.
>
> {code:java}
>
> deployed
>
> {code}
> Is there some more restrictive pom validation introduced with
> maven-project-info-reports-plugin:3.0.0
> {code:java}
> $ mvn project-info-reports:dependencies
> [WARNING] Unable to create Maven project from repository for artifact
> xml-resolver:xml-resolver:jar:1.2
> org.apache.maven.project.ProjectBuildingException: Some problems were
> encountered while processing the POMs:
> [ERROR] 'distributionManagement.status' must not be specified. @ line 36,
> column 13
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:191)
> at org.apache.maven.project.DefaultProjectBuilder.build
> (DefaultProjectBuilder.java:326)
> at
> org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository
> (RepositoryUtils.java:125)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDescriptionsAndURLs
> (DependenciesRenderer.java:890)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:847)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.printDependencyListing
> (DependenciesRenderer.java:867)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionDependencyTree
> (DependenciesRenderer.java:486)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderSectionProjectDependencyGraph
> (DependenciesRenderer.java:449)
> at
> org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRenderer.renderBody
> (DependenciesRenderer.java:222)
> at org.apache.maven.reporting.AbstractMavenReportRenderer.render
> (AbstractMavenReportRenderer.java:80)
> at org.apache.maven.report.projectinfo.DependenciesReport.executeReport
> (DependenciesReport.java:162)
> at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:251)
> at org.apache.maven.report.projectinfo.AbstractProjectInfoReport.execute
> (AbstractProjectInfoReport.java:220)
> 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 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
[jira] [Comment Edited] (SUREFIRE-1757) maven-surefire-plugin versions starting from 2.22.0 do not run JUnit5 Test Suites junit-platform-runner
[
https://issues.apache.org/jira/browse/SUREFIRE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052121#comment-17052121
]
Denys Galyuk edited comment on SUREFIRE-1757 at 3/5/20, 1:27 PM:
-
Hello again, [~tibordigana].
Thank you for your answer and ability to use 3.0.0-SNAPSHOT from the Apache
Development Snapshot Repository.
But, in the end, this version of the surefire plugin also {color:#DE350B}does
not see the JUnit5 test suites{color}. :( It can run only methods that has
annotation @Test.
My JDK and mvn versions:
{code} mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Program Files\Maven\apache-maven-3.6.3
Java version: 12.0.2, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk-12.0.2
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
{code}
1. I've created fresh new project with the 3.0.0-SNAPSHOT to avoid any cached
problems, conflicts, etc.
And included to use 3.0.0-SNAPSHOT
{code}
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
org.example
surefire
1.0-SNAPSHOT
org.junit.jupiter
junit-jupiter-engine
5.6.0
test
org.junit.platform
junit-platform-runner
1.6.0
test
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
1.8
1.8
UTF-8
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-SNAPSHOT
apache.snapshots
Apache Development Snapshot Repository
https://repository.apache.org/content/repositories/snapshots/
false
true
{code}
2. *Then I did smoke test to check if surefire plugin works:*
maven-surefire-plugin 3.0.0-SNAPSHOT
Run Type: *mvn test* (maven searches for tests for himself)
{color:#00875A}*BUILD SUCCESS Tests run: 3, Failures: 0, Errors: 0, Skipped:
0*{color}
And it worked fine
{code}$ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO] < org.example:surefire >
[INFO] Building surefire 1.0-SNAPSHOT
[INFO] [ jar ]-
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-metadata.xml
(1.0 kB at 650 B/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.pom
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.pom
(8.1 kB at 8.0 kB/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/maven-metadata.xml
(827 B at 813 B/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/surefire-3.0.0-20200305.030602-252.pom
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/surefire-3.0.0-20200305.030602-252.pom
(27 kB at 24 kB/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.jar
Downloaded from apache.snapshots:
[jira] [Created] (MSHADE-353) Any transformer should be "relocatable"
Romain Manni-Bucau created MSHADE-353: - Summary: Any transformer should be "relocatable" Key: MSHADE-353 URL: https://issues.apache.org/jira/browse/MSHADE-353 Project: Maven Shade Plugin Issue Type: Task Reporter: Romain Manni-Bucau Need is to ensure any transformer can relocate its resource contents, even if originally not designed as such. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (SUREFIRE-1757) maven-surefire-plugin versions starting from 2.22.0 do not run JUnit5 Test Suites junit-platform-runner
[
https://issues.apache.org/jira/browse/SUREFIRE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052121#comment-17052121
]
Denys Galyuk edited comment on SUREFIRE-1757 at 3/5/20, 1:17 PM:
-
Hello again, [~tibordigana].
Thank you for your answer and ability to use 3.0.0-SNAPSHOT from the Apache
Development Snapshot Repository.
But, in the end, this version of the surefire plugin also {color:#DE350B}does
not see the JUnit5 test suites{color}. :( It can run only methods that has
annotation @Test.
My JDK and mvn versions:
{code} mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Program Files\Maven\apache-maven-3.6.3
Java version: 12.0.2, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk-12.0.2
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
{code}
1. I've created fresh new project with the 3.0.0-SNAPSHOT to avoid any cached
problems, conflicts, etc.
And included to use 3.0.0-SNAPSHOT
{code}
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
org.example
surefire
1.0-SNAPSHOT
org.junit.jupiter
junit-jupiter-engine
5.6.0
test
org.junit.platform
junit-platform-runner
1.6.0
test
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
1.8
1.8
UTF-8
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-SNAPSHOT
apache.snapshots
Apache Development Snapshot Repository
https://repository.apache.org/content/repositories/snapshots/
false
true
{code}
2. *Then I did smoke test to check if surefire plugin works:*
maven-surefire-plugin 3.0.0-SNAPSHOT
Run Type: *mvn test* (maven searches for tests for himself)
{color:#00875A}*BUILD SUCCESS Tests run: 3, Failures: 0, Errors: 0, Skipped:
0*{color}
And it worked fine
{code}$ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO] < org.example:surefire >
[INFO] Building surefire 1.0-SNAPSHOT
[INFO] [ jar ]-
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-metadata.xml
(1.0 kB at 650 B/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.pom
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.pom
(8.1 kB at 8.0 kB/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/maven-metadata.xml
(827 B at 813 B/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/surefire-3.0.0-20200305.030602-252.pom
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/surefire-3.0.0-20200305.030602-252.pom
(27 kB at 24 kB/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.jar
Downloaded from apache.snapshots:
[jira] [Commented] (SUREFIRE-1757) maven-surefire-plugin versions starting from 2.22.0 do not run JUnit5 Test Suites junit-platform-runner
[
https://issues.apache.org/jira/browse/SUREFIRE-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052121#comment-17052121
]
Denys Galyuk commented on SUREFIRE-1757:
Hello again, [~tibordigana].
Thank you for your answer and ability to use 3.0.0-SNAPSHOT from the Apache
Development Snapshot Repository.
But, in the end, this version of the surefire plugin also {color:#DE350B}does
not see the JUnit5 test suites{color}. :( It can run only methods that has
annotation @Test.
My JDK and mvn versions:
{code} mvn -v
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Program Files\Maven\apache-maven-3.6.3
Java version: 12.0.2, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk-12.0.2
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
java -version
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
{code}
1. I've created fresh new project with the 3.0.0-SNAPSHOT to avoid any cached
problems, conflicts, etc.
And included to use 3.0.0-SNAPSHOT
{code}
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
org.example
surefire
1.0-SNAPSHOT
org.junit.jupiter
junit-jupiter-engine
5.6.0
test
org.junit.platform
junit-platform-runner
1.6.0
test
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
1.8
1.8
UTF-8
org.apache.maven.plugins
maven-surefire-plugin
3.0.0-SNAPSHOT
apache.snapshots
Apache Development Snapshot Repository
https://repository.apache.org/content/repositories/snapshots/
false
true
{code}
2. *Then I did smoke test to check if surefire plugin works:*
maven-surefire-plugin 3.0.0-SNAPSHOT
Run Type: *mvn test* (maven searches for tests for himself)
{color:#00875A}BUILD SUCCESS Tests run: 3, Failures: 0, Errors: 0, Skipped:
0{color}
And it worked fine
{code}$ mvn clean test
[INFO] Scanning for projects...
[INFO]
[INFO] < org.example:surefire >
[INFO] Building surefire 1.0-SNAPSHOT
[INFO] [ jar ]-
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-metadata.xml
(1.0 kB at 650 B/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.pom
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.pom
(8.1 kB at 8.0 kB/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/maven-metadata.xml
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/maven-metadata.xml
(827 B at 813 B/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/surefire-3.0.0-20200305.030602-252.pom
Downloaded from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/surefire/3.0.0-SNAPSHOT/surefire-3.0.0-20200305.030602-252.pom
(27 kB at 24 kB/s)
Downloading from apache.snapshots:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-surefire-plugin/3.0.0-SNAPSHOT/maven-surefire-plugin-3.0.0-20200305.030801-252.jar
Downloaded from apache.snapshots:
[GitHub] [maven-resolver] michael-o commented on issue #30: Fixes MRESOLVER-7, third try
michael-o commented on issue #30: Fixes MRESOLVER-7, third try URL: https://github.com/apache/maven-resolver/pull/30#issuecomment-595218808 Basically, we have frequent race conditions in the Maven ITs. @Tibor17 Do you remember the discussion the mailing list? I guess it was on Slack only :-( @Eskibear. I think you can reproduce it yourself. Fetch the first broken Resolver release and run Maven ITs multiple times. I think you should see failures not related to Maven itself. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (DOXIA-597) `code` not rendered as code
[ https://issues.apache.org/jira/browse/DOXIA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052087#comment-17052087 ] James Harrison commented on DOXIA-597: -- Thank you... I guess I'll wait for maven-site-plugin 3.9.0 to be released then. > `code` not rendered as code > --- > > Key: DOXIA-597 > URL: https://issues.apache.org/jira/browse/DOXIA-597 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Markdown >Affects Versions: 1.9 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 1.9.1 > > > ``` > pre > ``` > works but not `code` -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MASSEMBLY-774) too many open files
[ https://issues.apache.org/jira/browse/MASSEMBLY-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold resolved MASSEMBLY-774. - Resolution: Fixed > too many open files > --- > > Key: MASSEMBLY-774 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-774 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Dan Armbrust >Priority: Major > > I ran across this - > http://mail-archives.apache.org/mod_mbox/maven-dev/201501.mbox/%3ca2ee0d04-04e3-4c99-8842-673463862...@takari.io%3E > - and since I'm making huge zip files, I thought I would give it a try. > I configured as: > > org.apache.maven.plugins > maven-assembly-plugin > 2.5.5 > > > org.codehaus.plexus > plexus-archiver > 3.0.1 > > > org.codehaus.plexus > plexus-io > 2.6 > > > > But this lead to a failure: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (zip) on project > ... sememe/seg.3182.sememe.map (Too many open files) -> [Help 1] > I certainly could raise my ulimit: > darmbrust@overkill:/mnt/STORAGE/Work/Apelon/Workspaces/ISAAC-Core-2/va-solor-goods$ > ulimit -a > ... > open files (-n) 1024 > But it seems it would be better if the zip process limited itself to a > reasonable number of open files. I don't know the algorithm... but it seems > that double or triple the processor count would be more than enough. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MASSEMBLY-774) too many open files
[ https://issues.apache.org/jira/browse/MASSEMBLY-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold closed MASSEMBLY-774. --- > too many open files > --- > > Key: MASSEMBLY-774 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-774 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Dan Armbrust >Priority: Major > > I ran across this - > http://mail-archives.apache.org/mod_mbox/maven-dev/201501.mbox/%3ca2ee0d04-04e3-4c99-8842-673463862...@takari.io%3E > - and since I'm making huge zip files, I thought I would give it a try. > I configured as: > > org.apache.maven.plugins > maven-assembly-plugin > 2.5.5 > > > org.codehaus.plexus > plexus-archiver > 3.0.1 > > > org.codehaus.plexus > plexus-io > 2.6 > > > > But this lead to a failure: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (zip) on project > ... sememe/seg.3182.sememe.map (Too many open files) -> [Help 1] > I certainly could raise my ulimit: > darmbrust@overkill:/mnt/STORAGE/Work/Apelon/Workspaces/ISAAC-Core-2/va-solor-goods$ > ulimit -a > ... > open files (-n) 1024 > But it seems it would be better if the zip process limited itself to a > reasonable number of open files. I don't know the algorithm... but it seems > that double or triple the processor count would be more than enough. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-resolver] Eskibear commented on issue #30: Fixes MRESOLVER-7, third try
Eskibear commented on issue #30: Fixes MRESOLVER-7, third try URL: https://github.com/apache/maven-resolver/pull/30#issuecomment-595192167 @michael-o thanks for the information. BTW, could you share some details (or point out the link) about the failed cases, race conditions mentioned above. My point is, if someone from community is willing to fix that, your previous discussion would help a lot. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051989#comment-17051989
]
Michael Ritzert commented on MASSEMBLY-929:
---
And I finally figured out how to convince maven to use the 3.2.0 version of the
assembly plugin.
I compiled our full application, and there are still some issues I did not see
before, but they are probably unrelated to this issue.
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Michael Ritzert
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051950#comment-17051950
]
Michael Ritzert commented on MASSEMBLY-929:
---
mvn clean package assembly:single leads to the same error.
{noformat}
Caused by: java.io.FileNotFoundException: JAR entry
META-INF/JAXB/episode_generate schema.xjb not found in
/root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
at sun.net.www.protocol.jar.JarURLConnection.connect
(JarURLConnection.java:147)
at sun.net.www.protocol.jar.JarURLConnection.getInputStream
(JarURLConnection.java:155)
at java.net.URL.openStream (URL.java:1163)
at
org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
(PlexusIoURLResource.java:30){noformat}
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Michael Ritzert
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MASSEMBLY-930) Assembly FileSet and Files do no consistently handle -f directory location
[
https://issues.apache.org/jira/browse/MASSEMBLY-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MASSEMBLY-930:
-
Issue Type: Bug (was: Task)
> Assembly FileSet and Files do no consistently handle -f directory location
> --
>
> Key: MASSEMBLY-930
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-930
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Environment: * macOS (development machine) using maven 3.6.0
> * Unbuntu (build server)
>Reporter: Jody Garnett
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> We have observed fileSet and file handling of relative paths in an
> inconsistent fashion when using mvn -f command line option to run a pom.xml
> file in a subdirectory.
> {panel:title=current directory}
> cd src
> mvn assembly:attached
> {panel}
> {panel:title=subdirectory location}
> mvn -f src/pom.xml assembly:attached
> {panel}
> Inconsistent behaviour:
> * fileSet directory - path based on location of pom.xml
> Works with both current directory, or subdirectory location, approach
> above.
> * file source - path based on where mvn executable is run, ignoring -f
> subdirectory location
>
>Impossible to define assembly independently of how maven is run (choose
> one of current directory or subdirectory approach).
> For the following example of file release/extensions/LICENSE.txt:
> {code:xml}
>
> release/extensions/LICENSE.txt
>
> LICENSE-LGPL.txt
>
> {code}
> Running with "cd src" "mvn assembly:attached" succeeds:
> * src/release/extensions/LICENSE.txt
> Running from the root folder with "mvn -f src/pom.xml assembly:attached"
> fails with:
> * release/extensions/LICENSE.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MASSEMBLY-930) Assembly FileSet and Files do no consistently handle -f directory location
[
https://issues.apache.org/jira/browse/MASSEMBLY-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MASSEMBLY-930:
-
Fix Version/s: waiting-for-feedback
> Assembly FileSet and Files do no consistently handle -f directory location
> --
>
> Key: MASSEMBLY-930
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-930
> Project: Maven Assembly Plugin
> Issue Type: Task
> Environment: * macOS (development machine) using maven 3.6.0
> * Unbuntu (build server)
>Reporter: Jody Garnett
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> We have observed fileSet and file handling of relative paths in an
> inconsistent fashion when using mvn -f command line option to run a pom.xml
> file in a subdirectory.
> {panel:title=current directory}
> cd src
> mvn assembly:attached
> {panel}
> {panel:title=subdirectory location}
> mvn -f src/pom.xml assembly:attached
> {panel}
> Inconsistent behaviour:
> * fileSet directory - path based on location of pom.xml
> Works with both current directory, or subdirectory location, approach
> above.
> * file source - path based on where mvn executable is run, ignoring -f
> subdirectory location
>
>Impossible to define assembly independently of how maven is run (choose
> one of current directory or subdirectory approach).
> For the following example of file release/extensions/LICENSE.txt:
> {code:xml}
>
> release/extensions/LICENSE.txt
>
> LICENSE-LGPL.txt
>
> {code}
> Running with "cd src" "mvn assembly:attached" succeeds:
> * src/release/extensions/LICENSE.txt
> Running from the root folder with "mvn -f src/pom.xml assembly:attached"
> fails with:
> * release/extensions/LICENSE.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-930) Assembly FileSet and Files do no consistently handle -f directory location
[
https://issues.apache.org/jira/browse/MASSEMBLY-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051900#comment-17051900
]
Michael Osipov commented on MASSEMBLY-930:
--
The attached goal does not exist anymore. Retry with 3.2.0 and the single goal.
> Assembly FileSet and Files do no consistently handle -f directory location
> --
>
> Key: MASSEMBLY-930
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-930
> Project: Maven Assembly Plugin
> Issue Type: Task
> Environment: * macOS (development machine) using maven 3.6.0
> * Unbuntu (build server)
>Reporter: Jody Garnett
>Priority: Major
>
> We have observed fileSet and file handling of relative paths in an
> inconsistent fashion when using mvn -f command line option to run a pom.xml
> file in a subdirectory.
> {panel:title=current directory}
> cd src
> mvn assembly:attached
> {panel}
> {panel:title=subdirectory location}
> mvn -f src/pom.xml assembly:attached
> {panel}
> Inconsistent behaviour:
> * fileSet directory - path based on location of pom.xml
> Works with both current directory, or subdirectory location, approach
> above.
> * file source - path based on where mvn executable is run, ignoring -f
> subdirectory location
>
>Impossible to define assembly independently of how maven is run (choose
> one of current directory or subdirectory approach).
> For the following example of file release/extensions/LICENSE.txt:
> {code:xml}
>
> release/extensions/LICENSE.txt
>
> LICENSE-LGPL.txt
>
> {code}
> Running with "cd src" "mvn assembly:attached" succeeds:
> * src/release/extensions/LICENSE.txt
> Running from the root folder with "mvn -f src/pom.xml assembly:attached"
> fails with:
> * release/extensions/LICENSE.txt
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MASSEMBLY-929:
-
Fix Version/s: waiting-for-feedback
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Michael Ritzert
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-929) assembly fails trying to include file with space in name from JAR
[
https://issues.apache.org/jira/browse/MASSEMBLY-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051896#comment-17051896
]
Michael Osipov commented on MASSEMBLY-929:
--
The assembly goal is gone. Retry with 3.2.0 and single goal.
> assembly fails trying to include file with space in name from JAR
> -
>
> Key: MASSEMBLY-929
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-929
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Reporter: Michael Ritzert
>Priority: Minor
> Fix For: waiting-for-feedback
>
> Attachments: pom.xml
>
>
> When I try to assemble a complete jar from the attached pom.xml (no other
> files needed), it ends with this error:
>
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-5:assembly
> (default-cli) on project camel-activemq: Failed to create assembly: Error
> creating assembly archive jar-with-dependencies: Problem creating jar: JAR
> entry META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> -> [Help 1]
>
> ...
> Caused by: java.io.FileNotFoundException: JAR entry
> META-INF/JAXB/episode_generate schema.xjb not found in
> /root/.m2/repository/org/apache/camel/camel-spring/3.0.1/camel-spring-3.0.1.jar
> at sun.net.www.protocol.jar.JarURLConnection.connect
> (JarURLConnection.java:147)
> at sun.net.www.protocol.jar.JarURLConnection.getInputStream
> (JarURLConnection.java:155)
> at java.net.URL.openStream (URL.java:1163)
> at
> org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents
> (PlexusIoURLResource.java:30)
> {noformat}
>
> To reproduce, put the pom.xml in a directory and run
> {code:java}
> docker run --network=host -it --rm --name my-maven-project -v
> "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:3.6.3-jdk-13 mvn -X -e
> clean package assembly:assembly
> {code}
> The file name in the jar file is URL-encoded, i.e.
> {code:java}
> 131 2020-01-11 06:18
> META-INF/JAXB/episode_generate%20schema.xjb{code}
> So the problem may as well be in the JAR file. Please tell me so, and I will
> report it against camel (or can this report be moved around within Jira?).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MASSEMBLY-774) too many open files
[ https://issues.apache.org/jira/browse/MASSEMBLY-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17051876#comment-17051876 ] Geoff Soutter commented on MASSEMBLY-774: - OK, love being wrong, so with sample size of 1, an upgrade to 3.1 and my CI build worked. So it _maybe_ fixed. YMMV. > too many open files > --- > > Key: MASSEMBLY-774 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-774 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.5.5 >Reporter: Dan Armbrust >Priority: Major > > I ran across this - > http://mail-archives.apache.org/mod_mbox/maven-dev/201501.mbox/%3ca2ee0d04-04e3-4c99-8842-673463862...@takari.io%3E > - and since I'm making huge zip files, I thought I would give it a try. > I configured as: > > org.apache.maven.plugins > maven-assembly-plugin > 2.5.5 > > > org.codehaus.plexus > plexus-archiver > 3.0.1 > > > org.codehaus.plexus > plexus-io > 2.6 > > > > But this lead to a failure: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (zip) on project > ... sememe/seg.3182.sememe.map (Too many open files) -> [Help 1] > I certainly could raise my ulimit: > darmbrust@overkill:/mnt/STORAGE/Work/Apelon/Workspaces/ISAAC-Core-2/va-solor-goods$ > ulimit -a > ... > open files (-n) 1024 > But it seems it would be better if the zip process limited itself to a > reasonable number of open files. I don't know the algorithm... but it seems > that double or triple the processor count would be more than enough. -- This message was sent by Atlassian Jira (v8.3.4#803005)
