[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018835#comment-17018835
]
Maxim Solodovnik commented on MSITE-854:
[~michael-o] of cause you need to manually change maven-site-plugin version to
3.8.2
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
> Stacktraces:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 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:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:157)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at
[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018794#comment-17018794
]
Maxim Solodovnik commented on MSITE-854:
Both {{mvn clean site -e}} and {{mvn clean install -e}} produces this error for
me
{code}
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /opt/maven
Java version: 11.0.5, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-9-generic", arch: "amd64", family: "unix"
{code}
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
> Stacktraces:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 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:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3
[jira] [Created] (MNG-6851) Need to change "property" to "system property" in POM Reference
Jiahongchao created MNG-6851: Summary: Need to change "property" to "system property" in POM Reference Key: MNG-6851 URL: https://issues.apache.org/jira/browse/MNG-6851 Project: Maven Issue Type: Bug Components: Documentation: General Reporter: Jiahongchao In "Profiles" section, it says "The profile will activate if Maven detects a property". I think it's better to change "property" to "system property" since project property can not activate profile -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-parent] eolivelli merged pull request #7: add elharo to committers list
eolivelli merged pull request #7: add elharo to committers list URL: https://github.com/apache/maven-parent/pull/7 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-jlink-plugin] iovuio commented on issue #7: Allow for module exclusions
iovuio commented on issue #7: Allow for module exclusions URL: https://github.com/apache/maven-jlink-plugin/pull/7#issuecomment-575941514 @michab66 thank you for your notification. I have pushed the necessary change. Please let me know what else is needed. 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-parent] elharo opened a new pull request #7: add elharo to committers list
elharo opened a new pull request #7: add elharo to committers list URL: https://github.com/apache/maven-parent/pull/7 @hboutemy 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-jlink-plugin] michab66 commented on issue #7: Allow for module exclusions
michab66 commented on issue #7: Allow for module exclusions URL: https://github.com/apache/maven-jlink-plugin/pull/7#issuecomment-575940059 Note that a null-check on excludeModules is missing. 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] (MRRESOURCES-72) Process mojo ignores offline mode
[
https://issues.apache.org/jira/browse/MRRESOURCES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018716#comment-17018716
]
Michael Osipov commented on MRRESOURCES-72:
---
I will have a look at it tomorrow. It was dormant for years, it can wait a few
days ;-)
> Process mojo ignores offline mode
> -
>
> Key: MRRESOURCES-72
> URL: https://issues.apache.org/jira/browse/MRRESOURCES-72
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Maven 3.0.3 (r1172588; 2011-09-19 14:36:33+0200)
> Maven home: /usr/local/apache-maven-3.0.3
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: /usr/local/openjdk7/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "freebsd", version: "9.2-prerelease", arch: "i386", family: "unix"
>Reporter: Michael Osipov
>Assignee: Herve Boutemy
>Priority: Major
> Attachments: build.log, offline.log
>
>
> Building Maven 3.1.1 with {{-o}} still tries to retrieve a remote resource
> and fails with:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. SUCCESS [00:04.666]
> [INFO] Maven Model ... SUCCESS [00:09.662]
> [INFO] Maven Artifact SUCCESS [00:08.064]
> [INFO] Maven Plugin API .. SUCCESS [00:04.378]
> [INFO] Maven Model Builder ... SUCCESS [00:09.794]
> [INFO] Maven Settings SUCCESS [00:07.018]
> [INFO] Maven Settings Builder SUCCESS [00:03.158]
> [INFO] Maven Repository Metadata Model ... SUCCESS [00:06.664]
> [INFO] Maven Aether Provider . SUCCESS [00:07.652]
> [INFO] Maven Core SUCCESS [00:41.676]
> [INFO] Maven Compat .. SUCCESS [00:25.343]
> [INFO] Maven Embedder SUCCESS [00:04.635]
> [INFO] Apache Maven Distribution . FAILURE [02:31.770]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:15.916 (Wall Clock)
> [INFO] Finished at: 2013-11-14 09:15:00
> [INFO] Final Memory: 46M/346M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project apache-maven: Error rendering velocity resource. Invocation of
> method 'getResourceAsFile' in class
> org.codehaus.plexus.resource.DefaultResourceManager threw exception
> org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find
> resource 'https://glassfish.java.net/public/CDDLv1.0.html'. at
> remote-resources[line 40, column 26] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :apache-maven
> {noformat}
> Offline mode shall be passed to every plugin execution.
> In my case, I am behind a corporate firewall and did not configure it in my
> {{settings.xml}} because we have a local Nexus instance for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018715#comment-17018715
]
Michael Osipov commented on MSITE-854:
--
Can't reproduce
{noformat}
[INFO] --- maven-site-plugin:3.8.2:site (default-site) @ openmeetings-server ---
[INFO] configuring report plugin
org.apache.maven.plugins:maven-project-info-reports-plugin:3.0.0
[INFO] 14 reports configured for maven-project-info-reports-plugin:3.0.0:
index, ci-management, dependencies, dependency-convergence,
dependency-management, distribution-management, issue-management, licenses,
mailing-lists, plugin-management, plugins, team, scm, summary
[INFO] configuring report plugin
org.apache.maven.plugins:maven-surefire-report-plugin:3.0.0-M4
[INFO] 1 report configured for maven-surefire-report-plugin:3.0.0-M4:
report-only
[INFO] configuring report plugin org.apache.rat:apache-rat-plugin:0.13
[INFO] 1 report configured for apache-rat-plugin:0.13: rat
[INFO] Rendering site with default locale English (en)
[INFO] Relativizing decoration links with respect to localized project URL:
https://openmeetings.apache.org
[INFO] Rendering content with
io.github.devacfr.maven.skins:reflow-maven-skin:jar:2.1.0 skin.
[INFO] Skipped "About" report (maven-project-info-reports-plugin:3.0.0:index),
file "index.html" already exists.
[INFO] Rendering 65 Doxia documents: 5 markdown, 60 xdoc
[WARNING] The directive.evaluate.context.class property has been deprecated. It
will be removed in Velocity 2.0. Instead, please use the automatically
provided $evaluate namespace to get and set local references (e.g.
#set($evaluate.foo = 'bar') and $evaluate.foo).
[WARNING] The directive.evaluate.context.class property has been deprecated. It
will be removed in Velocity 2.0. Instead, please use the automatically
provided $evaluate namespace to get and set local references (e.g.
#set($evaluate.foo = 'bar') and $evaluate.foo).
[WARNING] The directive.evaluate.context.class property has been deprecated. It
will be removed in Velocity 2.0. Instead, please use the automatically
provided $evaluate namespace to get and set local references (e.g.
#set($evaluate.foo = 'bar') and $evaluate.foo).
[WARNING] The directive.evaluate.context.class property has been deprecated. It
will be removed in Velocity 2.0. Instead, please use the automatically
provided $evaluate namespace to get and set local references (e.g.
#set($evaluate.foo = 'bar') and $evaluate.foo).
[WARNING] The directive.evaluate.context.class property has been deprecated. It
will be removed in Velocity 2.0. Instead, please use the automatically
provided $evaluate namespace to get and set local references (e.g.
#set($evaluate.foo = 'bar') and $evaluate.foo).
[INFO] Generating "CI Management" report ---
maven-project-info-reports-plugin:3.0.0:ci-management
{noformat}
with
{noformat}
PS D:\Entwicklung\Projekte\openmeetings> mvn -v
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T20:33:14+02:00)
Maven home: D:\Entwicklung\Programme\apache-maven-3.5.4\bin\..
Java version: 11.0.6, vendor: AdoptOpenJDK, runtime: C:\Program
Files\AdoptOpenJDK\jdk-11.0.6.10-hotspot
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{noformat}
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
> Stacktraces:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out
[jira] [Closed] (MPIR-385) Emails in mailing list section of pom are improperly handled
[ https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MPIR-385. - Resolution: Fixed > Emails in mailing list section of pom are improperly handled > > > Key: MPIR-385 > URL: https://issues.apache.org/jira/browse/MPIR-385 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: mailing-lists >Affects Versions: 3.0.0, 3.0.1 >Reporter: Sebb >Assignee: Sylwester Lachiewicz >Priority: Major > Labels: regression > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The generated file mailing-lists.html contains email names of the form: > Subscribe > instead of > mailto:test-subscr...@maven.apache.org;>Subscribe > Since the protocol is omitted, browsers assume it is the same as the page, > i.e. http[s]. > Easy to demonstrate: > clone the repo > mvn clean integration-test > examine target/test-harness/mailing-lists/mailing-lists.html > To show that it worked previously, checkout the tag > maven-project-info-reports-plugin-2.9 > and try the test again. > examine the file target/test-harness/mailing-lists/mail-lists.html > There don't appear to be any tests to check whether the table entries are > correctly generated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-385) Emails in mailing list section of pom are improperly handled
[ https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018712#comment-17018712 ] Sylwester Lachiewicz commented on MPIR-385: --- Done in [6ec9e397b9131f786e3096d57268df12d07c5056|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=6ec9e397b9131f786e3096d57268df12d07c5056] and [c7acb571ac57de67ba966183ff5816a063ebb96a|https://gitbox.apache.org/repos/asf?p=maven-project-info-reports-plugin.git;a=commit;h=c7acb571ac57de67ba966183ff5816a063ebb96a] > Emails in mailing list section of pom are improperly handled > > > Key: MPIR-385 > URL: https://issues.apache.org/jira/browse/MPIR-385 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: mailing-lists >Affects Versions: 3.0.0, 3.0.1 >Reporter: Sebb >Assignee: Sylwester Lachiewicz >Priority: Major > Labels: regression > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The generated file mailing-lists.html contains email names of the form: > Subscribe > instead of > mailto:test-subscr...@maven.apache.org;>Subscribe > Since the protocol is omitted, browsers assume it is the same as the page, > i.e. http[s]. > Easy to demonstrate: > clone the repo > mvn clean integration-test > examine target/test-harness/mailing-lists/mailing-lists.html > To show that it worked previously, checkout the tag > maven-project-info-reports-plugin-2.9 > and try the test again. > examine the file target/test-harness/mailing-lists/mail-lists.html > There don't appear to be any tests to check whether the table entries are > correctly generated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRRESOURCES-72) Process mojo ignores offline mode
[
https://issues.apache.org/jira/browse/MRRESOURCES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018710#comment-17018710
]
Herve Boutemy commented on MRRESOURCES-72:
--
what is your proposal for this plugin issue?
> Process mojo ignores offline mode
> -
>
> Key: MRRESOURCES-72
> URL: https://issues.apache.org/jira/browse/MRRESOURCES-72
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Maven 3.0.3 (r1172588; 2011-09-19 14:36:33+0200)
> Maven home: /usr/local/apache-maven-3.0.3
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: /usr/local/openjdk7/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "freebsd", version: "9.2-prerelease", arch: "i386", family: "unix"
>Reporter: Michael Osipov
>Assignee: Herve Boutemy
>Priority: Major
> Attachments: build.log, offline.log
>
>
> Building Maven 3.1.1 with {{-o}} still tries to retrieve a remote resource
> and fails with:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. SUCCESS [00:04.666]
> [INFO] Maven Model ... SUCCESS [00:09.662]
> [INFO] Maven Artifact SUCCESS [00:08.064]
> [INFO] Maven Plugin API .. SUCCESS [00:04.378]
> [INFO] Maven Model Builder ... SUCCESS [00:09.794]
> [INFO] Maven Settings SUCCESS [00:07.018]
> [INFO] Maven Settings Builder SUCCESS [00:03.158]
> [INFO] Maven Repository Metadata Model ... SUCCESS [00:06.664]
> [INFO] Maven Aether Provider . SUCCESS [00:07.652]
> [INFO] Maven Core SUCCESS [00:41.676]
> [INFO] Maven Compat .. SUCCESS [00:25.343]
> [INFO] Maven Embedder SUCCESS [00:04.635]
> [INFO] Apache Maven Distribution . FAILURE [02:31.770]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:15.916 (Wall Clock)
> [INFO] Finished at: 2013-11-14 09:15:00
> [INFO] Final Memory: 46M/346M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project apache-maven: Error rendering velocity resource. Invocation of
> method 'getResourceAsFile' in class
> org.codehaus.plexus.resource.DefaultResourceManager threw exception
> org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find
> resource 'https://glassfish.java.net/public/CDDLv1.0.html'. at
> remote-resources[line 40, column 26] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :apache-maven
> {noformat}
> Offline mode shall be passed to every plugin execution.
> In my case, I am behind a corporate firewall and did not configure it in my
> {{settings.xml}} because we have a local Nexus instance for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MSOURCES-126) reproducible IT failing since January 1st 2020
[
https://issues.apache.org/jira/browse/MSOURCES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018661#comment-17018661
]
Herve Boutemy edited comment on MSOURCES-126 at 1/18/20 9:10 PM:
-
tested on a VM forcing date to get reproducible-1.0-sources.jar as built in
2019-12-18 and 2020-01-18, then see what is the difference between the 2
archives using diffoscope:
{noformat}$ diffoscope
reproducible-20191218/target/reproducible-1.0-sources.jar
reproducible-20200118/target/reproducible-1.0-sources.jar
--- reproducible-20191218/target/reproducible-1.0-sources.jar
+++ reproducible-20200118/target/reproducible-1.0-sources.jar
[...]
├── META-INF/NOTICE
│ @@ -1,8 +1,8 @@
│
│ Test for reproducibility of jar
│ -Copyright 2019 The Apache Software Foundation
│ +Copyright 2020 The Apache Software Foundation
│
│ This product includes software developed at
│ The Apache Software Foundation (http://www.apache.org/).{noformat}
generated META-INF/NOTICE contains current year...
was (Author: hboutemy):
tested on a VM forcing date to get reproducible-1.0-sources.jar as built in
2019-12-18 and 2020-01-18, then see what is the difference between the 2
archives using diffoscope:
{noformat}$ diffoscope
reproducible-20191218/target/reproducible-1.0-sources.jar
reproducible-20200118/target/reproducible-1.0-sources.jar
--- reproducible-20191218/target/reproducible-1.0-sources.jar
+++ reproducible-20200118/target/reproducible-1.0-sources.jar
├── zipinfo -v {}
│ @@ -366,15 +366,15 @@
│minimum file system compatibility required: MS-DOS, OS/2 or NT FAT
│minimum software version required to extract: 2.0
│compression method: deflated
│compression sub-type (deflation): normal
│file security status: not encrypted
│extended local header: no
│file last modified on (DOS date/time): 2019 Aug 21 18:28:52
│ - 32-bit CRC value (hex): aeabb55c
│ + 32-bit CRC value (hex): 62b3bac9
│compressed size:129 bytes
│uncompressed size: 183 bytes
│length of filename: 15 characters
│length of extra field: 0 bytes
│length of file comment: 0 characters
│disk number on which file begins: disk 1
│apparent file type: binary
├── META-INF/NOTICE
│ @@ -1,8 +1,8 @@
│
│ Test for reproducibility of jar
│ -Copyright 2019 The Apache Software Foundation
│ +Copyright 2020 The Apache Software Foundation
│
│ This product includes software developed at
│ The Apache Software Foundation (http://www.apache.org/).{noformat}
generated META-INF/NOTICE contains current year...
> reproducible IT failing since January 1st 2020
> --
>
> Key: MSOURCES-126
> URL: https://issues.apache.org/jira/browse/MSOURCES-126
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.2.2
>
>
> {noformat}[INFO] Building: reproducible/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] reproducible/pom.xml . FAILED
> (2.2 s)
> [INFO] The post-build script did not succeed. assert buf.startsWith(
> "reproducible-1.0-sources.jar sha1 =
> 3a3687b063cfc164fbbccd1b9573b4232f540e8a" )
>| |
>| false
>reproducible-1.0-sources.jar sha1 =
> 499c6f39564643f1e55da33967121fc56fe24537{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MPOM-237) Reproducible Builds: upgrade maven-remote-resources-plugin to 1.7.0
Herve Boutemy created MPOM-237: -- Summary: Reproducible Builds: upgrade maven-remote-resources-plugin to 1.7.0 Key: MPOM-237 URL: https://issues.apache.org/jira/browse/MPOM-237 Project: Maven POMs Issue Type: Improvement Components: asf Affects Versions: ASF-22 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: ASF-23 without this upgrade, META-INF/NOTICE files generated during releases contain current year, which is not reproducible -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (MSOURCES-126) reproducible IT failing since January 1st 2020
[
https://issues.apache.org/jira/browse/MSOURCES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy reopened MSOURCES-126:
temporary fix done, using maven-antrun-plugin
once maven-remote-resources-plugin 1.7.0 is out with MRRESOURCES-114 built in,
we can remove the Ant run hack
> reproducible IT failing since January 1st 2020
> --
>
> Key: MSOURCES-126
> URL: https://issues.apache.org/jira/browse/MSOURCES-126
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.2.2
>
>
> {noformat}[INFO] Building: reproducible/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] reproducible/pom.xml . FAILED
> (2.2 s)
> [INFO] The post-build script did not succeed. assert buf.startsWith(
> "reproducible-1.0-sources.jar sha1 =
> 3a3687b063cfc164fbbccd1b9573b4232f540e8a" )
>| |
>| false
>reproducible-1.0-sources.jar sha1 =
> 499c6f39564643f1e55da33967121fc56fe24537{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MRRESOURCES-114) make projectTimespan reproducible: use outputTimestamp instead of current date
[ https://issues.apache.org/jira/browse/MRRESOURCES-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MRRESOURCES-114. - Resolution: Fixed done in https://gitbox.apache.org/repos/asf?p=maven-remote-resources-plugin.git;a=commitdiff;h=33022e15c1f6212443bd9d10367f07b666fb69b6 > make projectTimespan reproducible: use outputTimestamp instead of current date > -- > > Key: MRRESOURCES-114 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-114 > Project: Maven Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.6.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 1.7.0 > > > as found in MSOURCES-126 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRRESOURCES-114) make projectTimespan reproducible: use outputTimestamp instead of current date
[ https://issues.apache.org/jira/browse/MRRESOURCES-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018705#comment-17018705 ] Hudson commented on MRRESOURCES-114: Build succeeded in Jenkins: Maven TLP » maven-remote-resources-plugin » master #23 See https://builds.apache.org/job/maven-box/job/maven-remote-resources-plugin/job/master/23/ > make projectTimespan reproducible: use outputTimestamp instead of current date > -- > > Key: MRRESOURCES-114 > URL: https://issues.apache.org/jira/browse/MRRESOURCES-114 > Project: Maven Remote Resources Plugin > Issue Type: Improvement >Affects Versions: 1.6.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Major > Fix For: 3.0 > > > as found in MSOURCES-126 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPIR-385) Emails in mailing list section of pom are improperly handled
[ https://issues.apache.org/jira/browse/MPIR-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018702#comment-17018702 ] Hudson commented on MPIR-385: - Build succeeded in Jenkins: Maven TLP » maven-project-info-reports-plugin » master #77 See https://builds.apache.org/job/maven-box/job/maven-project-info-reports-plugin/job/master/77/ > Emails in mailing list section of pom are improperly handled > > > Key: MPIR-385 > URL: https://issues.apache.org/jira/browse/MPIR-385 > Project: Maven Project Info Reports Plugin > Issue Type: Bug > Components: mailing-lists >Affects Versions: 3.0.0, 3.0.1 >Reporter: Sebb >Assignee: Sylwester Lachiewicz >Priority: Major > Labels: regression > Fix For: 3.1.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The generated file mailing-lists.html contains email names of the form: > Subscribe > instead of > mailto:test-subscr...@maven.apache.org;>Subscribe > Since the protocol is omitted, browsers assume it is the same as the page, > i.e. http[s]. > Easy to demonstrate: > clone the repo > mvn clean integration-test > examine target/test-harness/mailing-lists/mailing-lists.html > To show that it worked previously, checkout the tag > maven-project-info-reports-plugin-2.9 > and try the test again. > examine the file target/test-harness/mailing-lists/mail-lists.html > There don't appear to be any tests to check whether the table entries are > correctly generated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MRRESOURCES-114) make projectTimespan reproducible: use outputTimestamp instead of current date
Herve Boutemy created MRRESOURCES-114: - Summary: make projectTimespan reproducible: use outputTimestamp instead of current date Key: MRRESOURCES-114 URL: https://issues.apache.org/jira/browse/MRRESOURCES-114 Project: Maven Remote Resources Plugin Issue Type: Improvement Affects Versions: 1.6.0 Reporter: Herve Boutemy Assignee: Herve Boutemy Fix For: 3.0 as found in MSOURCES-126 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRRESOURCES-72) Process mojo ignores offline mode
[
https://issues.apache.org/jira/browse/MRRESOURCES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018701#comment-17018701
]
Michael Osipov commented on MRRESOURCES-72:
---
[~hboutemy], we should avoid cruft like Plexus's {{ResourceManager}}. This is
competely not transparent.
> Process mojo ignores offline mode
> -
>
> Key: MRRESOURCES-72
> URL: https://issues.apache.org/jira/browse/MRRESOURCES-72
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Maven 3.0.3 (r1172588; 2011-09-19 14:36:33+0200)
> Maven home: /usr/local/apache-maven-3.0.3
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: /usr/local/openjdk7/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "freebsd", version: "9.2-prerelease", arch: "i386", family: "unix"
>Reporter: Michael Osipov
>Assignee: Herve Boutemy
>Priority: Major
> Attachments: build.log, offline.log
>
>
> Building Maven 3.1.1 with {{-o}} still tries to retrieve a remote resource
> and fails with:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. SUCCESS [00:04.666]
> [INFO] Maven Model ... SUCCESS [00:09.662]
> [INFO] Maven Artifact SUCCESS [00:08.064]
> [INFO] Maven Plugin API .. SUCCESS [00:04.378]
> [INFO] Maven Model Builder ... SUCCESS [00:09.794]
> [INFO] Maven Settings SUCCESS [00:07.018]
> [INFO] Maven Settings Builder SUCCESS [00:03.158]
> [INFO] Maven Repository Metadata Model ... SUCCESS [00:06.664]
> [INFO] Maven Aether Provider . SUCCESS [00:07.652]
> [INFO] Maven Core SUCCESS [00:41.676]
> [INFO] Maven Compat .. SUCCESS [00:25.343]
> [INFO] Maven Embedder SUCCESS [00:04.635]
> [INFO] Apache Maven Distribution . FAILURE [02:31.770]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:15.916 (Wall Clock)
> [INFO] Finished at: 2013-11-14 09:15:00
> [INFO] Final Memory: 46M/346M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project apache-maven: Error rendering velocity resource. Invocation of
> method 'getResourceAsFile' in class
> org.codehaus.plexus.resource.DefaultResourceManager threw exception
> org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find
> resource 'https://glassfish.java.net/public/CDDLv1.0.html'. at
> remote-resources[line 40, column 26] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :apache-maven
> {noformat}
> Offline mode shall be passed to every plugin execution.
> In my case, I am behind a corporate firewall and did not configure it in my
> {{settings.xml}} because we have a local Nexus instance for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018700#comment-17018700
]
Michael Osipov commented on MSITE-854:
--
Running the build now, let me see how far I get with {{mvn install site}}.
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
> Stacktraces:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 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:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:157)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at
[jira] [Updated] (MRRESOURCES-72) Process mojo ignores offline mode
[
https://issues.apache.org/jira/browse/MRRESOURCES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MRRESOURCES-72:
-
Fix Version/s: (was: more-investigation)
> Process mojo ignores offline mode
> -
>
> Key: MRRESOURCES-72
> URL: https://issues.apache.org/jira/browse/MRRESOURCES-72
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Maven 3.0.3 (r1172588; 2011-09-19 14:36:33+0200)
> Maven home: /usr/local/apache-maven-3.0.3
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: /usr/local/openjdk7/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "freebsd", version: "9.2-prerelease", arch: "i386", family: "unix"
>Reporter: Michael Osipov
>Assignee: Herve Boutemy
>Priority: Major
> Attachments: build.log, offline.log
>
>
> Building Maven 3.1.1 with {{-o}} still tries to retrieve a remote resource
> and fails with:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. SUCCESS [00:04.666]
> [INFO] Maven Model ... SUCCESS [00:09.662]
> [INFO] Maven Artifact SUCCESS [00:08.064]
> [INFO] Maven Plugin API .. SUCCESS [00:04.378]
> [INFO] Maven Model Builder ... SUCCESS [00:09.794]
> [INFO] Maven Settings SUCCESS [00:07.018]
> [INFO] Maven Settings Builder SUCCESS [00:03.158]
> [INFO] Maven Repository Metadata Model ... SUCCESS [00:06.664]
> [INFO] Maven Aether Provider . SUCCESS [00:07.652]
> [INFO] Maven Core SUCCESS [00:41.676]
> [INFO] Maven Compat .. SUCCESS [00:25.343]
> [INFO] Maven Embedder SUCCESS [00:04.635]
> [INFO] Apache Maven Distribution . FAILURE [02:31.770]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:15.916 (Wall Clock)
> [INFO] Finished at: 2013-11-14 09:15:00
> [INFO] Final Memory: 46M/346M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project apache-maven: Error rendering velocity resource. Invocation of
> method 'getResourceAsFile' in class
> org.codehaus.plexus.resource.DefaultResourceManager threw exception
> org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find
> resource 'https://glassfish.java.net/public/CDDLv1.0.html'. at
> remote-resources[line 40, column 26] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :apache-maven
> {noformat}
> Offline mode shall be passed to every plugin execution.
> In my case, I am behind a corporate firewall and did not configure it in my
> {{settings.xml}} because we have a local Nexus instance for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MRRESOURCES-72) Process mojo ignores offline mode
[
https://issues.apache.org/jira/browse/MRRESOURCES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MRRESOURCES-72.
Assignee: Herve Boutemy
Resolution: Not A Problem
the download was not in plugins code but in the Velocity template from the
project: cannot fix at plugin level
> Process mojo ignores offline mode
> -
>
> Key: MRRESOURCES-72
> URL: https://issues.apache.org/jira/browse/MRRESOURCES-72
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: Apache Maven 3.0.3 (r1172588; 2011-09-19 14:36:33+0200)
> Maven home: /usr/local/apache-maven-3.0.3
> Java version: 1.7.0_25, vendor: Oracle Corporation
> Java home: /usr/local/openjdk7/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "freebsd", version: "9.2-prerelease", arch: "i386", family: "unix"
>Reporter: Michael Osipov
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: more-investigation
>
> Attachments: build.log, offline.log
>
>
> Building Maven 3.1.1 with {{-o}} still tries to retrieve a remote resource
> and fails with:
> {noformat}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Maven .. SUCCESS [00:04.666]
> [INFO] Maven Model ... SUCCESS [00:09.662]
> [INFO] Maven Artifact SUCCESS [00:08.064]
> [INFO] Maven Plugin API .. SUCCESS [00:04.378]
> [INFO] Maven Model Builder ... SUCCESS [00:09.794]
> [INFO] Maven Settings SUCCESS [00:07.018]
> [INFO] Maven Settings Builder SUCCESS [00:03.158]
> [INFO] Maven Repository Metadata Model ... SUCCESS [00:06.664]
> [INFO] Maven Aether Provider . SUCCESS [00:07.652]
> [INFO] Maven Core SUCCESS [00:41.676]
> [INFO] Maven Compat .. SUCCESS [00:25.343]
> [INFO] Maven Embedder SUCCESS [00:04.635]
> [INFO] Apache Maven Distribution . FAILURE [02:31.770]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 04:15.916 (Wall Clock)
> [INFO] Finished at: 2013-11-14 09:15:00
> [INFO] Final Memory: 46M/346M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project apache-maven: Error rendering velocity resource. Invocation of
> method 'getResourceAsFile' in class
> org.codehaus.plexus.resource.DefaultResourceManager threw exception
> org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find
> resource 'https://glassfish.java.net/public/CDDLv1.0.html'. at
> remote-resources[line 40, column 26] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn -rf :apache-maven
> {noformat}
> Offline mode shall be passed to every plugin execution.
> In my case, I am behind a corporate firewall and did not configure it in my
> {{settings.xml}} because we have a local Nexus instance for that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018697#comment-17018697
]
Michael Osipov commented on MSITE-854:
--
Thanks, acknowledged that the error message is really confusing. I assume that
then convertion from Markdown to XHTML provide shitty code which makes the
XhtmlParser choke on it.
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
> Stacktraces:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 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:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:157)
> at
[jira] [Commented] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018693#comment-17018693 ] Robert Scholte commented on MJAR-269: - Maven offers several options you can write by yourself: plugins, extensions and custom lifecycles. Since you want to call several plugins bound to the same phase, a custom lifecycle might be an option. These aren't well described, though. > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018691#comment-17018691 ] Brian Wyka edited comment on MJAR-269 at 1/18/20 7:33 PM: -- Any ideas other than the one mentioned in the issue description on how to acccomplish this? Honestly, to me, the "solution" in the issue description is more of a hack than anything else. Trying to brainstorm how we can do this better, but not seeing a way since I still want other plugins to be able to tie into the deploy phase and to not be skipped as they would be by calling *deploy:deploy* in isolation. was (Author: brianwyka): Any ideas other than the one mentioned in the issue description on how to acccomplish this? Honestly, to me, the "solution" in the issue description is more of a hack than anything else. Trying to brainstorm how we can do this better, but not seeing a way since I still want other plugins to be able to tie into the deploy phase and to not by skipped when calling *deploy:deploy* in isolation. > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018691#comment-17018691 ] Brian Wyka commented on MJAR-269: - Any ideas other than the one mentioned in the issue description on how to acccomplish this? Honestly, to me, the "solution" in the issue description is more of a hack than anything else. Trying to brainstorm how we can do this better, but not seeing a way since I still want other plugins to be able to tie into the deploy phase and to not by skipped when calling *deploy:deploy* in isolation. > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jar-plugin] brianwyka removed a comment on issue #7: [MJAR-269] Add Skip Property to Skip Plugin Execution
brianwyka removed a comment on issue #7: [MJAR-269] Add Skip Property to Skip Plugin Execution URL: https://github.com/apache/maven-jar-plugin/pull/7#issuecomment-575928060 @rfscholte, almost every maven plugin has some skip property to allow its execution to be skipped based on the user's discretion. Why is this plugin any different? 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] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018677#comment-17018677 ] Brian Wyka edited comment on MJAR-269 at 1/18/20 7:26 PM: -- [~rfscholte], both of those plugins already have skip properties enabled: * maven-compiler-plugin: [https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#skipMain] * maven-resources-plgin: [https://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#skip] Calling *deploy:deploy* is a partial solution in this case for sure. However, it prevents custom implementations of a pom which tie into the *deploy* phase from executing in this case, so not optimal or ideal, unfortunately. was (Author: brianwyka): [~rfscholte], both of those plugins already have skip properties enabled: * maven-compiler-plugin: [https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#skipMain] * maven-resources-plgin: [https://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#skip] Calling *deploy:deploy* is a partial solution in this case for sure. However, it prevents custom implementations of a pom which tie into the *deploy* phase from executing in this case, so not optimal or idea, unfortunately. > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018682#comment-17018682 ] Robert Scholte commented on MJAR-269: - I didn't expect these parameters to exist, but it doesn't change my opinion. The description is quite clear, it is no recommended and that's for me a code smell. I won't introduce workarounds if I know we can do better (because once workarounds exist it is very hard to remove them). > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018678#comment-17018678 ] Brian Wyka commented on MJAR-269: - I guess I don't understand why we wouldn't want to give power to the user to decide? > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJAR-269) Add Skip Property to Skip Plugin Execution
[ https://issues.apache.org/jira/browse/MJAR-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018677#comment-17018677 ] Brian Wyka commented on MJAR-269: - [~rfscholte], both of those plugins already have skip properties enabled: * maven-compiler-plugin: [https://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#skipMain] * maven-resources-plgin: [https://maven.apache.org/plugins/maven-resources-plugin/resources-mojo.html#skip] Calling *deploy:deploy* is a partial solution in this case for sure. However, it prevents custom implementations of a pom which tie into the *deploy* phase from executing in this case, so not optimal or idea, unfortunately. > Add Skip Property to Skip Plugin Execution > -- > > Key: MJAR-269 > URL: https://issues.apache.org/jira/browse/MJAR-269 > Project: Maven JAR Plugin > Issue Type: New Feature >Reporter: Brian Wyka >Assignee: Robert Scholte >Priority: Minor > Labels: skip > Original Estimate: 96h > Time Spent: 20m > Remaining Estimate: 95h 40m > > Expose plugin configuration as well as a user property to allow the plugin > execution to be skipped. > > There are occasions when we do not always want to run jar plugin. > > Example: > In a build pipeline, we run different phases in different stages > > # Run install in isolation (we need jar here) > # Run deploy in isolation (we don't need jar again - so need a way to skip) > > Currently there is only a hack to do this, by overriding the *default-jar* > execution of the plugin and setting the phase to a user property, and then > overriding that to a non-existent phase, to keep it from being attached to > the maven lifecycle. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-jar-plugin] brianwyka commented on issue #7: [MJAR-269] Add Skip Property to Skip Plugin Execution
brianwyka commented on issue #7: [MJAR-269] Add Skip Property to Skip Plugin Execution URL: https://github.com/apache/maven-jar-plugin/pull/7#issuecomment-575928060 @rfscholte, almost every maven plugin has some skip property to allow its execution to be skipped based on the user's discretion. Why is this plugin any different? 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] (MSOURCES-126) reproducible IT failing since January 1st 2020
[
https://issues.apache.org/jira/browse/MSOURCES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MSOURCES-126.
--
Assignee: Herve Boutemy
Resolution: Fixed
fixed in
https://gitbox.apache.org/repos/asf?p=maven-source-plugin.git;a=commitdiff;h=85dd30a1cfc297a827dc7a778252c3c9f90f8ea6
> reproducible IT failing since January 1st 2020
> --
>
> Key: MSOURCES-126
> URL: https://issues.apache.org/jira/browse/MSOURCES-126
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Herve Boutemy
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: 3.2.2
>
>
> {noformat}[INFO] Building: reproducible/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] reproducible/pom.xml . FAILED
> (2.2 s)
> [INFO] The post-build script did not succeed. assert buf.startsWith(
> "reproducible-1.0-sources.jar sha1 =
> 3a3687b063cfc164fbbccd1b9573b4232f540e8a" )
>| |
>| false
>reproducible-1.0-sources.jar sha1 =
> 499c6f39564643f1e55da33967121fc56fe24537{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSOURCES-126) reproducible IT failing since January 1st 2020
[
https://issues.apache.org/jira/browse/MSOURCES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018671#comment-17018671
]
Hudson commented on MSOURCES-126:
-
Build succeeded in Jenkins: Maven TLP » maven-source-plugin » master #44
See
https://builds.apache.org/job/maven-box/job/maven-source-plugin/job/master/44/
> reproducible IT failing since January 1st 2020
> --
>
> Key: MSOURCES-126
> URL: https://issues.apache.org/jira/browse/MSOURCES-126
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: 3.2.2
>
>
> {noformat}[INFO] Building: reproducible/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] reproducible/pom.xml . FAILED
> (2.2 s)
> [INFO] The post-build script did not succeed. assert buf.startsWith(
> "reproducible-1.0-sources.jar sha1 =
> 3a3687b063cfc164fbbccd1b9573b4232f540e8a" )
>| |
>| false
>reproducible-1.0-sources.jar sha1 =
> 499c6f39564643f1e55da33967121fc56fe24537{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSOURCES-126) reproducible IT failing since January 1st 2020
[
https://issues.apache.org/jira/browse/MSOURCES-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018661#comment-17018661
]
Herve Boutemy commented on MSOURCES-126:
tested on a VM forcing date to get reproducible-1.0-sources.jar as built in
2019-12-18 and 2020-01-18, then see what is the difference between the 2
archives using diffoscope:
{noformat}$ diffoscope
reproducible-20191218/target/reproducible-1.0-sources.jar
reproducible-20200118/target/reproducible-1.0-sources.jar
--- reproducible-20191218/target/reproducible-1.0-sources.jar
+++ reproducible-20200118/target/reproducible-1.0-sources.jar
├── zipinfo -v {}
│ @@ -366,15 +366,15 @@
│minimum file system compatibility required: MS-DOS, OS/2 or NT FAT
│minimum software version required to extract: 2.0
│compression method: deflated
│compression sub-type (deflation): normal
│file security status: not encrypted
│extended local header: no
│file last modified on (DOS date/time): 2019 Aug 21 18:28:52
│ - 32-bit CRC value (hex): aeabb55c
│ + 32-bit CRC value (hex): 62b3bac9
│compressed size:129 bytes
│uncompressed size: 183 bytes
│length of filename: 15 characters
│length of extra field: 0 bytes
│length of file comment: 0 characters
│disk number on which file begins: disk 1
│apparent file type: binary
├── META-INF/NOTICE
│ @@ -1,8 +1,8 @@
│
│ Test for reproducibility of jar
│ -Copyright 2019 The Apache Software Foundation
│ +Copyright 2020 The Apache Software Foundation
│
│ This product includes software developed at
│ The Apache Software Foundation (http://www.apache.org/).{noformat}
generated META-INF/NOTICE contains current year...
> reproducible IT failing since January 1st 2020
> --
>
> Key: MSOURCES-126
> URL: https://issues.apache.org/jira/browse/MSOURCES-126
> Project: Maven Source Plugin
> Issue Type: Bug
>Affects Versions: 3.2.1
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: 3.2.2
>
>
> {noformat}[INFO] Building: reproducible/pom.xml
> [INFO] run post-build script verify.groovy
> [INFO] reproducible/pom.xml . FAILED
> (2.2 s)
> [INFO] The post-build script did not succeed. assert buf.startsWith(
> "reproducible-1.0-sources.jar sha1 =
> 3a3687b063cfc164fbbccd1b9573b4232f540e8a" )
>| |
>| false
>reproducible-1.0-sources.jar sha1 =
> 499c6f39564643f1e55da33967121fc56fe24537{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MSOURCES-126) reproducible IT failing since January 1st 2020
Herve Boutemy created MSOURCES-126:
--
Summary: reproducible IT failing since January 1st 2020
Key: MSOURCES-126
URL: https://issues.apache.org/jira/browse/MSOURCES-126
Project: Maven Source Plugin
Issue Type: Bug
Affects Versions: 3.2.1
Reporter: Herve Boutemy
Fix For: 3.2.2
{noformat}[INFO] Building: reproducible/pom.xml
[INFO] run post-build script verify.groovy
[INFO] reproducible/pom.xml . FAILED (2.2
s)
[INFO] The post-build script did not succeed. assert buf.startsWith(
"reproducible-1.0-sources.jar sha1 = 3a3687b063cfc164fbbccd1b9573b4232f540e8a" )
| |
| false
reproducible-1.0-sources.jar sha1 =
499c6f39564643f1e55da33967121fc56fe24537{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MPOM-221) All Links for Diff produce Forbidden
[
https://issues.apache.org/jira/browse/MPOM-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPOM-221.
--
Assignee: Herve Boutemy
Resolution: Fixed
fixed in mavent-parent in
https://gitbox.apache.org/repos/asf?p=maven-parent.git;a=commitdiff;h=2c5ece17385cf1a875b68826bfd6bd2ef4861c28
> All Links for Diff produce Forbidden
>
>
> Key: MPOM-221
> URL: https://issues.apache.org/jira/browse/MPOM-221
> Project: Maven POMs
> Issue Type: Bug
> Components: asf, doxia-tools, maven, maven-archeypes, maven-plugins,
> maven-shared-components, maven-skins
>Affects Versions: MAVEN-SHARED-22, MAVEN-PLUGINS-28, MAVEN-33, ASF-21
>Reporter: Karl Heinz Marbaise
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: MAVEN-34, ASF-22, MAVEN-PLUGINS-28, MAVEN-PLUGINS-27,
> MAVEN-SKINS-10
>
>
> Currently all links to diffs on the pages like
> http://maven.apache.org/pom/asf/, http://maven.apache.org/pom/maven/ will
> produce:
> {code}
> Forbidden
> You don't have permission to access /repos/asf on this server.
> {code}
> So we need to change all of the diff links to diff links on GitHub
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MPOM-234. -- Assignee: Herve Boutemy Resolution: Fixed fixed in Apache parent in https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=commitdiff;h=0ebfdbc6d11474e8424b2f76f3c8fc6dcadd1969 and in maven-parent in https://gitbox.apache.org/repos/asf?p=maven-parent.git;a=commitdiff;h=e5d2767d01eb247d778134e28700a59a0e5da01c > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: MAVEN-33, ASF-22 >Reporter: Sylwester Lachiewicz >Assignee: Herve Boutemy >Priority: Minor > Fix For: MAVEN-34, ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in > maven-parent that causes warning in MPIR (see MPIR-375 for the future > workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018635#comment-17018635
]
Maxim Solodovnik commented on MSITE-854:
[~michael-o] sorry, thoght there is enough info
Stacktraces are added
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
> Stacktraces:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:215)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> 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:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271)
> at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:157)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at
[jira] [Updated] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Solodovnik updated MSITE-854:
---
Description:
site is generated as expected with 3.7.1
after upgrading to 3.8.2
following error is being reported
{code}
ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
project openmeetings-server: Error parsing
'/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
line [3] Error parsing the model: end tag name must match start tag name
from line 3 (position: TEXT seen ...out bd-callout-danger"> It should be
run under same user as OM... @3:271) -> [Help 1]
{code}
the error message is totally misleading, there is no {{}} tag in
https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
Would appreciate any help on this
Stacktraces:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
project openmeetings-server: Error parsing
'/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
line [3] Error parsing the model: end tag name must match start tag name
from line 3 (position: TEXT seen ...out bd-callout-danger"> It should be
run under same user as OM... @3:271) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
project openmeetings-server: Error parsing
'/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
line [3] Error parsing the model: end tag name must match start tag name
from line 3 (position: TEXT seen ...out bd-callout-danger"> It should be
run under same user as OM... @3:271)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:215)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
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:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error parsing
'/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
line [3] Error parsing the model: end tag name must match start tag name
from line 3 (position: TEXT seen ...out bd-callout-danger"> It should be
run under same user as OM... @3:271)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:157)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
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:56)
at
[jira] [Commented] (MSITE-854) Markup validation error after upgrading to 3.8.2
[
https://issues.apache.org/jira/browse/MSITE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018608#comment-17018608
]
Michael Osipov commented on MSITE-854:
--
This is a bit little input. What about stacktraces?
> Markup validation error after upgrading to 3.8.2
>
>
> Key: MSITE-854
> URL: https://issues.apache.org/jira/browse/MSITE-854
> Project: Maven Site Plugin
> Issue Type: Bug
>Affects Versions: 3.8.2
>Reporter: Maxim Solodovnik
>Priority: Major
>
> site is generated as expected with 3.7.1
> after upgrading to 3.8.2
> following error is being reported
> {code}
> ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.8.2:site (generate-site) on
> project openmeetings-server: Error parsing
> '/home/solomax/work/openmeetings/openmeetings/openmeetings-server/src/site/markdown/InstallMediaServer.md':
> line [3] Error parsing the model: end tag name must match start tag
> name from line 3 (position: TEXT seen ...out bd-callout-danger"> It
> should be run under same user as OM... @3:271) -> [Help 1]
> {code}
> the error message is totally misleading, there is no {{}} tag in
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/site/markdown/InstallMediaServer.md
> Would appreciate any help on this
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-surefire] marcphilipp opened a new pull request #263: Use Surefire's StringUtils instead of JUnit's
marcphilipp opened a new pull request #263: Use Surefire's StringUtils instead of JUnit's URL: https://github.com/apache/maven-surefire/pull/263 org.junit.platform.commons.util.StringUtils is an internal API of JUnit in an internal package (i.e. not exported in the module descriptor). Thus, Surefire's own `StringUtils` are now used instead. 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] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018578#comment-17018578 ] Hudson commented on MPOM-234: - Build succeeded in Jenkins: Maven TLP » maven-parent » master #36 See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/36/ > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: MAVEN-33, ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: MAVEN-34, ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in > maven-parent that causes warning in MPIR (see MPIR-375 for the future > workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018577#comment-17018577 ] Hudson commented on MPOM-234: - Build succeeded in Jenkins: Maven TLP » maven-apache-parent » master #41 See https://builds.apache.org/job/maven-box/job/maven-apache-parent/job/master/41/ > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: MAVEN-33, ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: MAVEN-34, ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in > maven-parent that causes warning in MPIR (see MPIR-375 for the future > workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-234: --- Affects Version/s: MAVEN-33 > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: MAVEN-33, ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in > maven-parent that causes warning in MPIR (see MPIR-375 for the future > workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-234: --- Description: given the work done in RAT-199, this will permit to remove the org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in maven-parent that causes warning in MPIR (see MPIR-375 for the future workaround) (was: given the work done in RAT-199, this will permit to remove the org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement that causes warning in MPIR (see MPIR-375 for the future workaround)) > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in > maven-parent that causes warning in MPIR (see MPIR-375 for the future > workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-234: --- Fix Version/s: MAVEN-34 > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: MAVEN-33, ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: MAVEN-34, ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement in > maven-parent that causes warning in MPIR (see MPIR-375 for the future > workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-234: --- Description: given the work done in RAT-199, this will permit to remove the org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement that causes warning in MPIR (see MPIR-375 for the future workaround) (was: given the work done in MRAT-199, this will permit to remove the org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement that causes warning in MPIR (see MPIR-375 for the future workaround)) > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: ASF-23 > > > given the work done in RAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement > that causes warning in MPIR (see MPIR-375 for the future workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-234) Upgrade apache-rat-plugin to 0.13
[ https://issues.apache.org/jira/browse/MPOM-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-234: --- Description: given the work done in MRAT-199, this will permit to remove the org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement that causes warning in MPIR (see MPIR-375 for the future workaround) > Upgrade apache-rat-plugin to 0.13 > - > > Key: MPOM-234 > URL: https://issues.apache.org/jira/browse/MPOM-234 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: ASF-22 >Reporter: Sylwester Lachiewicz >Priority: Minor > Fix For: ASF-23 > > > given the work done in MRAT-199, this will permit to remove the > org.eclipse.m2e:lifecycle-mapping:1.0.0 pseudo plugin in pluginManagement > that causes warning in MPIR (see MPIR-375 for the future workaround) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MPOM-221) All Links for Diff produce Forbidden
[
https://issues.apache.org/jira/browse/MPOM-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018576#comment-17018576
]
Hudson commented on MPOM-221:
-
Build succeeded in Jenkins: Maven TLP » maven-parent » master #35
See https://builds.apache.org/job/maven-box/job/maven-parent/job/master/35/
> All Links for Diff produce Forbidden
>
>
> Key: MPOM-221
> URL: https://issues.apache.org/jira/browse/MPOM-221
> Project: Maven POMs
> Issue Type: Bug
> Components: asf, doxia-tools, maven, maven-archeypes, maven-plugins,
> maven-shared-components, maven-skins
>Affects Versions: MAVEN-SHARED-22, MAVEN-PLUGINS-28, MAVEN-33, ASF-21
>Reporter: Karl Heinz Marbaise
>Priority: Major
> Fix For: MAVEN-SKINS-10, MAVEN-PLUGINS-27, MAVEN-PLUGINS-28,
> MAVEN-34, ASF-22
>
>
> Currently all links to diffs on the pages like
> http://maven.apache.org/pom/asf/, http://maven.apache.org/pom/maven/ will
> produce:
> {code}
> Forbidden
> You don't have permission to access /repos/asf on this server.
> {code}
> So we need to change all of the diff links to diff links on GitHub
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MPOM-134) Add profile to use a different resource bundle for incubator projects
[
https://issues.apache.org/jira/browse/MPOM-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPOM-134:
---
Fix Version/s: (was: ASF-23)
ASF-24
> Add profile to use a different resource bundle for incubator projects
> -
>
> Key: MPOM-134
> URL: https://issues.apache.org/jira/browse/MPOM-134
> Project: Maven POMs
> Issue Type: Improvement
>Affects Versions: ASF-18
>Reporter: Christopher Tubbs
>Priority: Major
> Fix For: ASF-24
>
>
> The {{org.apache:apache-jar-resource-bundle:1.4}} resourceBundle currently
> specified in the parent POM does not handle the DISCLAIMER file for incubator
> projects.
> It would be nice if there were an incubation profile, which could be
> activated for incubating projects, to use an incubating resource bundle which
> did handle this DISCLAIMER file.
> This could be done in several ways:
> # An optional second execution of the {{maven-remote-resources-plugin}} could
> run when the profile is activated, which handles a second resource bundle for
> the DISCLAIMER file.
> # The current resourceBundle could be turned into a property, which is
> overridden when the profile is activated, using a resourceBundle which
> handles everything the current one does, plus the DISCLAIMER file.
> # The current {{maven-remote-resources-plugin}} execution could have the
> {{}} element changed to {{ combine.children="append">}}, and the profile could specify an additional
> {{}} to handle the DISCLAIMER file, for the same execution id
> of {{maven-remote-resources-plugin}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MPOM-168) JDK 9 requires updates to plugins
[ https://issues.apache.org/jira/browse/MPOM-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-168: --- Fix Version/s: (was: ASF-23) ASF-24 > JDK 9 requires updates to plugins > - > > Key: MPOM-168 > URL: https://issues.apache.org/jira/browse/MPOM-168 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-19 >Reporter: Karl Heinz Marbaise >Priority: Minor > Fix For: ASF-24 > > > The following plugins needed to be updated to work with JDK 9: > * The maven-enforcer-plugin should be updated to final 3.0.0 release to make > the pom working with JDK 9... > * maven-shade-plugin should be upgraded to 3.0.0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-208) upgrade m-scm-publish-p
[ https://issues.apache.org/jira/browse/MPOM-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MPOM-208: --- Fix Version/s: (was: ASF-23) ASF-24 > upgrade m-scm-publish-p > --- > > Key: MPOM-208 > URL: https://issues.apache.org/jira/browse/MPOM-208 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: ASF-21 >Reporter: Herve Boutemy >Priority: Major > Fix For: ASF-24 > > > to benefit from MSCMPUB-37 (important when you publish site documentation > from Linux) that benefits in fact from SCM-763 > if m-scm-publish-p is not yet release and we want to release ASF parent POM, > just adding an upgraded dependency on maven-scm-provider-svnexe can do the > job (I tested) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MPOM-236) scm-publish:publish-scm java.lang.AbstractMethodError failure on Git checkout
[
https://issues.apache.org/jira/browse/MPOM-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy closed MPOM-236.
--
Resolution: Fixed
fixed
https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git;a=commitdiff;h=38dd8af10b49a1a7a5f38a6855fd8e1c270c4a38
> scm-publish:publish-scm java.lang.AbstractMethodError failure on Git checkout
> -
>
> Key: MPOM-236
> URL: https://issues.apache.org/jira/browse/MPOM-236
> Project: Maven POMs
> Issue Type: Bug
> Components: asf
>Affects Versions: ASF-22
>Reporter: Christofer Dutz
>Assignee: Herve Boutemy
>Priority: Major
> Fix For: ASF-23
>
>
> after updating to the lates apache-parent 22, we're having problems pushing
> our generated site to git on jenkins ... we're getting strange API
> compatibility errors ...
> {noformat}[DEBUG] -- end configuration --
> [INFO] Checking out the pub tree from
> scm:git:https://gitbox.apache.org/repos/asf/plc4x-website.git into
> /home/jenkins/jenkins-slave/workspace/PLC4X_PLC4X_develop/target/scmpublish-checkout
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4.487 s
> [INFO] Finished at: 2020-01-16T10:26:43Z
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:3.0.0:publish-scm
> (default-cli) on project plc4x-jenkins-tools: Execution default-cli of goal
> org.apache.maven.plugins:maven-scm-publish-plugin:3.0.0:publish-scm failed:
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-scm-publish-plugin:3.0.0:publish-scm:
> java.lang.AbstractMethodError:
> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCheckOutCommand(Lorg/apache/maven/scm/provider/ScmProviderRepository;Lorg/apache/maven/scm/ScmFileSet;Lorg/apache/maven/scm/ScmVersion;ZZ)Lorg/apache/maven/scm/command/checkout/CheckOutScmResult;{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MPOM-208) upgrade m-scm-publish-p
[ https://issues.apache.org/jira/browse/MPOM-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018565#comment-17018565 ] Herve Boutemy commented on MPOM-208: [~cdutz] this comment should go to MPOM-236, not really here... > upgrade m-scm-publish-p > --- > > Key: MPOM-208 > URL: https://issues.apache.org/jira/browse/MPOM-208 > Project: Maven POMs > Issue Type: Dependency upgrade > Components: asf >Affects Versions: ASF-21 >Reporter: Herve Boutemy >Priority: Major > Fix For: ASF-23 > > > to benefit from MSCMPUB-37 (important when you publish site documentation > from Linux) that benefits in fact from SCM-763 > if m-scm-publish-p is not yet release and we want to release ASF parent POM, > just adding an upgraded dependency on maven-scm-provider-svnexe can do the > job (I tested) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MPOM-208) upgrade m-scm-publish-p
[
https://issues.apache.org/jira/browse/MPOM-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018050#comment-17018050
]
Herve Boutemy edited comment on MPOM-208 at 1/18/20 11:48 AM:
--
Adding the following to the projects parent pom solved the problem:
{code:xml}
org.apache.maven.plugins
maven-scm-publish-plugin
org.apache.maven.scm
maven-scm-provider-gitexe
1.10.0
{code}
was (Author: cdutz):
Adding the following to the projects parent pom solved the problem:
{code:java}
org.apache.maven.plugins
maven-scm-publish-plugin
org.apache.maven.scm
maven-scm-provider-gitexe
1.10.0
{code}
> upgrade m-scm-publish-p
> ---
>
> Key: MPOM-208
> URL: https://issues.apache.org/jira/browse/MPOM-208
> Project: Maven POMs
> Issue Type: Dependency upgrade
> Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: ASF-23
>
>
> to benefit from MSCMPUB-37 (important when you publish site documentation
> from Linux) that benefits in fact from SCM-763
> if m-scm-publish-p is not yet release and we want to release ASF parent POM,
> just adding an upgraded dependency on maven-scm-provider-svnexe can do the
> job (I tested)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MPOM-208) upgrade m-scm-publish-p
[
https://issues.apache.org/jira/browse/MPOM-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018050#comment-17018050
]
Herve Boutemy edited comment on MPOM-208 at 1/18/20 11:48 AM:
--
Adding the following to the projects parent pom solved the problem:
{code:java}
org.apache.maven.plugins
maven-scm-publish-plugin
org.apache.maven.scm
maven-scm-provider-gitexe
1.10.0
{code}
was (Author: cdutz):
Adding the following to the projects parent pom solved the problem:
{code:java}
org.apache.maven.plugins
maven-scm-publish-plugin
3.0.0
org.apache.maven.scm
maven-scm-provider-gitexe
1.10.0
{code}
> upgrade m-scm-publish-p
> ---
>
> Key: MPOM-208
> URL: https://issues.apache.org/jira/browse/MPOM-208
> Project: Maven POMs
> Issue Type: Dependency upgrade
> Components: asf
>Affects Versions: ASF-21
>Reporter: Herve Boutemy
>Priority: Major
> Fix For: ASF-23
>
>
> to benefit from MSCMPUB-37 (important when you publish site documentation
> from Linux) that benefits in fact from SCM-763
> if m-scm-publish-p is not yet release and we want to release ASF parent POM,
> just adding an upgraded dependency on maven-scm-provider-svnexe can do the
> job (I tested)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-verifier-plugin] KroArtem commented on issue #2: [MVERIFIER-38] Define encoding for FileReader
KroArtem commented on issue #2: [MVERIFIER-38] Define encoding for FileReader URL: https://github.com/apache/maven-verifier-plugin/pull/2#issuecomment-575885839 @slachiewicz, ping 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
