[jira] [Created] (MSHARED-720) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MSHARED-720: --- Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MSHARED-720 URL: https://issues.apache.org/jira/browse/MSHARED-720 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-archiver Affects Versions: maven-archiver-3.2.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-archiver-3.2.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIASITETOOLS-179:
-
Affects Version/s: (was: 1.6)
1.7
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 1.7, 1.8
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Fix For: 1.8.1
>
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(Sin
[jira] [Updated] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIASITETOOLS-179:
-
Affects Version/s: 1.6
1.8
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 1.6, 1.8
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Fix For: 1.8.1
>
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreaded
[jira] [Updated] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated DOXIASITETOOLS-179:
-
Fix Version/s: 1.8.1
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Affects Versions: 1.6, 1.8
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Fix For: 1.8.1
>
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
[jira] [Commented] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439017#comment-16439017
]
Hervé Boutemy commented on DOXIASITETOOLS-179:
--
ok, found the cause: with Velocity 1.5, Velocity displays error message in logs
before sending its VelocityException
{noformat}[ERROR] Method charAt threw exception for reference $text in template
C:\Users\mosipov\Downloads\velocity-exception-site\src\site\apt\index.apt.vm at
[20,17]{noformat}
Then the general exception handling algorithm did not try to get the info: it
was displayed.
With Velocity 1.7, this Velocity error log behaviour disappeared, which is IMHO
more consistent.
Then the exception handling is not sufficient any more...
I'll update the code tonight, since there is some cleanup to do around this old
code
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.exe
[jira] [Commented] (MNG-6394) ${revision} and parent.releativePath
[
https://issues.apache.org/jira/browse/MNG-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439016#comment-16439016
]
Dorian Vallant commented on MNG-6394:
-
I think so. I have configured flatten-maven-plugin in my parent-project's pom.
Do I have to configure it in child's pom too?
> ${revision} and parent.releativePath
>
>
> Key: MNG-6394
> URL: https://issues.apache.org/jira/browse/MNG-6394
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.3
> Environment: Ubuntu 17.10; Maven 3.5.3; Java 1.8.0_161
>Reporter: Dorian Vallant
>Priority: Major
>
> If the CI friendly ${revision} property is used it seems maven does not
> simple replace the property with the given value.
> Consider the following example:
> parent-project/
> pom.xml
> child-project/
> pom.xml
> parent-project/pom.xml:
> ...
> my.group
> parentArtifact
> ${revision}
> pom
> ...
> child-project/pom.xml:
>
> my.group
> parentArtifact
> ${revision}
> ../parent-project
>
> If you build the child-project with 'mvn -Drevision=1.0.0-SNAPSHOT -f
> child-project/pom.xml clean install' all works fine as long as the parent
> project is present in the file system. But if you move the parent project to
> another place, build & install it to your local repository and then try to
> build the child project, maven tries to download the pom.xml of the parent
> project but does not replace ${revision}. So maven complains about a missing
> dependency.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MRESOURCES-246) set filtering = true will make some excel file to be broken
[ https://issues.apache.org/jira/browse/MRESOURCES-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439001#comment-16439001 ] Karl Heinz Marbaise commented on MRESOURCES-246: Than turn off filtering for any kind of files you don't like to be changed in any case..or make separate directories as I suggested. > set filtering = true will make some excel file to be broken > --- > > Key: MRESOURCES-246 > URL: https://issues.apache.org/jira/browse/MRESOURCES-246 > Project: Maven Resources Plugin > Issue Type: Bug > Components: filtering >Affects Versions: 3.0.2 >Reporter: george >Assignee: Robert Scholte >Priority: Major > Attachments: QQ截图20180414171050.png, QQ截图20180414171103.png, > export.xlsx > > > while I set filtering = true, maven-resources-plugin will copy my excel file > to the directory, but the file is broken, can be opened, > after I set filtering = false, or comment this line of settings, the file is > ok, > I use maven-kotlin-plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRESOURCES-246) set filtering = true will make some excel file to be broken
[
https://issues.apache.org/jira/browse/MRESOURCES-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438937#comment-16438937
]
george commented on MRESOURCES-246:
---
I just want to copy the excel file to output directory, do not modify the
content of the file,
here is the pom config:
{code:java}
maven-resources-plugin
copy-resources
validate
copy-resources
${project.build.directory}/resources
src/main/resources
{code}
here if I commented the "filtering" config, the file which copied to output
directory is OK; but if I set filtering = true, the file is broken
> set filtering = true will make some excel file to be broken
> ---
>
> Key: MRESOURCES-246
> URL: https://issues.apache.org/jira/browse/MRESOURCES-246
> Project: Maven Resources Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 3.0.2
>Reporter: george
>Assignee: Robert Scholte
>Priority: Major
> Attachments: QQ截图20180414171050.png, QQ截图20180414171103.png,
> export.xlsx
>
>
> while I set filtering = true, maven-resources-plugin will copy my excel file
> to the directory, but the file is broken, can be opened,
> after I set filtering = false, or comment this line of settings, the file is
> ok,
> I use maven-kotlin-plugin
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] sormuras commented on issue #183: junit5
sormuras commented on issue #183: junit5 URL: https://github.com/apache/maven-surefire/pull/183#issuecomment-381454091 - https://junit.org/junit5/docs/current/user-guide/#overview-what-is-junit-5 - https://junit.org/junit5/docs/current/user-guide/#advanced-topics - https://blog.codefx.org/design/architecture/junit-5-architecture/#JUnit-5 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Comment Edited] (MSHADE-154) Add ability for shade to find primary artifact from attached artifacts (similar to assembly-plugin)
[
https://issues.apache.org/jira/browse/MSHADE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438867#comment-16438867
]
Igor Dvorzhak edited comment on MSHADE-154 at 4/16/18 12:05 AM:
I found workaround, you need to package both main jar and jar with classifier
and then detach main jar from project after shading:
{code:xml}
maven-jar-plugin
classifier-jar
jar
${classifier}
maven-shade-plugin
. . .
org.codehaus.gmaven
gmaven-plugin
remove-primary-artifact
package
execute
project.getArtifact().setFile(null)
{code}
was (Author: medb):
I found workaround, you need to package both main jar and jar with classifier
and then detach main jar from project after shading:
{code:xml}
maven-jar-plugin
jar
classifier-jar
jar
${classifier}
maven-shade-plugin
. . .
org.codehaus.gmaven
gmaven-plugin
remove-primary-artifact
package
execute
project.getArtifact().setFile(null)
{code}
> Add ability for shade to find primary artifact from attached artifacts
> (similar to assembly-plugin)
> ---
>
> Key: MSHADE-154
> URL: https://issues.apache.org/jira/browse/MSHADE-154
> Project: Maven Shade Plugin
> Issue Type: New Feature
>Affects Versions: 2.0
> Environment: all
>Reporter: Richard Sand
>Priority: Major
> Attachments: patch.txt, patch139and154.txt
>
>
> When switching from assembly-plugin to shade-plugin for a given project, I
> discovered that the shade plugin did not have the capability of using an
> attached artifact as the primary artifact - only the project's main artifact
> was supported.
> I've attached changes to add a configuration parameter
> "alternativeInputClassifier", which, when specified, tells the plugin to look
> for an artifact with the specified classifier in the project attachments, and
> to use that as the primary artifact. This makes shade behave similar to
> assembly-plugin, and allows shade to recognize attached artifacts generated
> by previous plugins in a maven execution.
> This was a trivial change, but required modifying several other classes and
> methods to accept the "primary" artifact as a parameter instead of a global
> variable. IMHO these changes are good for the plugin as a whole, as it will
> allow for future flexibility and logic for determining the entrypoint for the
> plugin (e.g. being able to run as a standalone goal with a specific artifact
> as input).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-154) Add ability for shade to find primary artifact from attached artifacts (similar to assembly-plugin)
[
https://issues.apache.org/jira/browse/MSHADE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438867#comment-16438867
]
Igor Dvorzhak commented on MSHADE-154:
--
I found workaround, you need to package both main jar and jar with classifier
and then detach main jar from project after shading:
{code:xml}
maven-jar-plugin
jar
classifier-jar
jar
${classifier}
maven-shade-plugin
. . .
org.codehaus.gmaven
gmaven-plugin
remove-primary-artifact
package
execute
project.getArtifact().setFile(null)
{code}
> Add ability for shade to find primary artifact from attached artifacts
> (similar to assembly-plugin)
> ---
>
> Key: MSHADE-154
> URL: https://issues.apache.org/jira/browse/MSHADE-154
> Project: Maven Shade Plugin
> Issue Type: New Feature
>Affects Versions: 2.0
> Environment: all
>Reporter: Richard Sand
>Priority: Major
> Attachments: patch.txt, patch139and154.txt
>
>
> When switching from assembly-plugin to shade-plugin for a given project, I
> discovered that the shade plugin did not have the capability of using an
> attached artifact as the primary artifact - only the project's main artifact
> was supported.
> I've attached changes to add a configuration parameter
> "alternativeInputClassifier", which, when specified, tells the plugin to look
> for an artifact with the specified classifier in the project attachments, and
> to use that as the primary artifact. This makes shade behave similar to
> assembly-plugin, and allows shade to recognize attached artifacts generated
> by previous plugins in a maven execution.
> This was a trivial change, but required modifying several other classes and
> methods to accept the "primary" artifact as a parameter instead of a global
> variable. IMHO these changes are good for the plugin as a whole, as it will
> allow for future flexibility and logic for determining the entrypoint for the
> plugin (e.g. being able to run as a standalone goal with a specific artifact
> as input).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] Tibor17 commented on issue #183: junit5
Tibor17 commented on issue #183: junit5 URL: https://github.com/apache/maven-surefire/pull/183#issuecomment-381436819 @marcphilipp What real difference is between jupiter and platform engine? Can they be both on the same classpath? I want the Surefire provider to have zero conflicts with user's code. Currently my POM has only one dependency `junit-platform-launcher:1.1.1`. It does not look like an API. Having maybe only API (interfaces) with scope=provided would be something more natural I would be looking for. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (DOXIASITETOOLS-179) Report error line and column from Velocity runtime exception
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438772#comment-16438772
]
Hervé Boutemy commented on DOXIASITETOOLS-179:
--
ok, issue introduced in maven-site-plugin 3.5, which uses doxia-site-tools 1.7
(was 1.6 in m-site-p 3.4)
notice that this release contains an upgrade from Velocity 1.5 to Velocity 1.7
DOXIASITETOOLS-92, which may contribute to the change...
I'm continuing to investigate
> Report error line and column from Velocity runtime exception
>
>
> Key: DOXIASITETOOLS-179
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-179
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Site renderer
>Reporter: Jan Krupička
>Priority: Major
> Labels: usability
> Attachments: velocity-exception-site.zip
>
>
> I have a site page {{index.apt.vm}} which is a Velocity template:
> {noformat}
> My best index page
> #set ($text = 'text')
> #set ($text = $text.charAt(-1))
> {noformat}
> When building maven site, this template fails (of course) with a runtime
> exception. Also the maven build fails (good) with the following output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on project
> test-project: Error getting a parser for 'My/site/path/index.apt.vm'
> {noformat}
> This output is not much helpful and is a little misleading. Velocity throws
> an exception with parsing error line and column. It would be nice to see this
> in maven error message so it is easy to see where the problem is.
> I can see full stack trace with maven debug build (-X) but I would expect
> this type of error to be reported in normal build.
> Related class and method:
> {{org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)}}
> Velocity method that throws useful exception with error description
> (line/column)
> {{org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)}}
> Velocity exception to catch and use:
> {{org.apache.velocity.exception.ParseErrorException}}
> Full stacktrace from debug output:
> {noformat}
> [ERROR] Error parsing My/site/path/index.apt.vm as a velocity template, using
> as text.
> org.apache.velocity.exception.MethodInvocationException: Invocation of method
> 'charAt' in class java.lang.String threw exception
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1 at d:\projects\test\tmp\test\src\site\apt\index.apt.vm[line 3, column 23]
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243)
> at
> org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
> at
> org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
> at
> org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
> at
> org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
> at
> org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
> at org.apache.velocity.Template.merge(Template.java:356)
> at org.apache.velocity.Template.merge(Template.java:260)
> at
> org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:354)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderDocument(DefaultSiteRenderer.java:381)
> at
> org.apache.maven.doxia.siterenderer.DoxiaDocumentRenderer.renderDocument(DoxiaDocumentRenderer.java:53)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:337)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderDoxiaDocuments(SiteMojo.java:262)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:168)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:132)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apa
[jira] [Created] (MSITE-817) inherit edit value in site.xml
Hervé Boutemy created MSITE-817: --- Summary: inherit edit value in site.xml Key: MSITE-817 URL: https://issues.apache.org/jira/browse/MSITE-817 Project: Maven Site Plugin Issue Type: Bug Components: doxia integration Affects Versions: 3.7 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: 3.7.1 see DOXIASITETOOLS-187 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-154) Add ability for shade to find primary artifact from attached artifacts (similar to assembly-plugin)
[ https://issues.apache.org/jira/browse/MSHADE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438746#comment-16438746 ] Igor Dvorzhak commented on MSHADE-154: -- Hit this issue. Any plans to add this feature? > Add ability for shade to find primary artifact from attached artifacts > (similar to assembly-plugin) > --- > > Key: MSHADE-154 > URL: https://issues.apache.org/jira/browse/MSHADE-154 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 2.0 > Environment: all >Reporter: Richard Sand >Priority: Major > Attachments: patch.txt, patch139and154.txt > > > When switching from assembly-plugin to shade-plugin for a given project, I > discovered that the shade plugin did not have the capability of using an > attached artifact as the primary artifact - only the project's main artifact > was supported. > I've attached changes to add a configuration parameter > "alternativeInputClassifier", which, when specified, tells the plugin to look > for an artifact with the specified classifier in the project attachments, and > to use that as the primary artifact. This makes shade behave similar to > assembly-plugin, and allows shade to recognize attached artifacts generated > by previous plugins in a maven execution. > This was a trivial change, but required modifying several other classes and > methods to accept the "primary" artifact as a parameter instead of a global > variable. IMHO these changes are good for the plugin as a whole, as it will > allow for future flexibility and logic for determining the entrypoint for the > plugin (e.g. being able to run as a standalone goal with a specific artifact > as input). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MJAVADOC-524) Running javadoc plugin under JDK 10 fails with NPE
[
https://issues.apache.org/jira/browse/MJAVADOC-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJAVADOC-524:
-
Summary: Running javadoc plugin under JDK 10 fails with NPE (was: Running
javadoc plugin JDK 10 fails with NPE)
> Running javadoc plugin under JDK 10 fails with NPE
> --
>
> Key: MJAVADOC-524
> URL: https://issues.apache.org/jira/browse/MJAVADOC-524
> Project: Maven Javadoc Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.1
>
>
> Running under JDK 10 produces the following:
> {code}
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs) on
> project maven-dependency-analyzer: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MJAVADOC-524) Running javadoc plugin JDK 10 fails with NPE
Karl Heinz Marbaise created MJAVADOC-524: Summary: Running javadoc plugin JDK 10 fails with NPE Key: MJAVADOC-524 URL: https://issues.apache.org/jira/browse/MJAVADOC-524 Project: Maven Javadoc Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Fix For: 3.0.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MJAVADOC-524) Running javadoc plugin JDK 10 fails with NPE
[
https://issues.apache.org/jira/browse/MJAVADOC-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJAVADOC-524:
-
Description:
Running under JDK 10 produces the following:
{code}
[INFO] [INFO]
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs) on
project maven-dependency-analyzer: Execution attach-javadocs of goal
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
NullPointerException -> [Help 1]
[INFO] [ERROR]
[INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
[INFO] [ERROR]
{code}
> Running javadoc plugin JDK 10 fails with NPE
>
>
> Key: MJAVADOC-524
> URL: https://issues.apache.org/jira/browse/MJAVADOC-524
> Project: Maven Javadoc Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.1
>
>
> Running under JDK 10 produces the following:
> {code}
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (attach-javadocs) on
> project maven-dependency-analyzer: Execution attach-javadocs of goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.:
> NullPointerException -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINSTALL-144) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MINSTALL-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438732#comment-16438732 ] Hudson commented on MINSTALL-144: - Build succeeded in Jenkins: Maven TLP » maven-install-plugin » MNGSITE-332 #2 See https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/MNGSITE-332/2/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MINSTALL-144 > URL: https://issues.apache.org/jira/browse/MINSTALL-144 > Project: Maven Install Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNGSITE-332) Changed download templates of plugins not to reference .md5 anymore
[
https://issues.apache.org/jira/browse/MNGSITE-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438733#comment-16438733
]
Hudson commented on MNGSITE-332:
Build succeeded in Jenkins: Maven TLP » maven-install-plugin » MNGSITE-332 #2
See
https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/MNGSITE-332/2/
> Changed download templates of plugins not to reference .md5 anymore
> ---
>
> Key: MNGSITE-332
> URL: https://issues.apache.org/jira/browse/MNGSITE-332
> Project: Maven Project Web Site
> Issue Type: Task
>Reporter: Karl Heinz Marbaise
>Priority: Critical
>
> Currently we have links to md5 checksums for the plugin download pages this
> has to be changed into links to {{sha1}} and {{sha256}} instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MINSTALL-144) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MINSTALL-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINSTALL-144. Resolution: Done Done in [886c76c6edd5651c2623ddf5d50f2c0ff6449dbb|https://gitbox.apache.org/repos/asf?p=maven-install-plugin.git;a=commitdiff;h=886c76c6edd5651c2623ddf5d50f2c0ff6449dbb] > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MINSTALL-144 > URL: https://issues.apache.org/jira/browse/MINSTALL-144 > Project: Maven Install Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINSTALL-144) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MINSTALL-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438725#comment-16438725 ] Hudson commented on MINSTALL-144: - Build succeeded in Jenkins: Maven TLP » maven-install-plugin » master #8 See https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/master/8/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MINSTALL-144 > URL: https://issues.apache.org/jira/browse/MINSTALL-144 > Project: Maven Install Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] marcphilipp commented on issue #183: junit5
marcphilipp commented on issue #183: junit5 URL: https://github.com/apache/maven-surefire/pull/183#issuecomment-381411134 > I want to understand the old commit of IT junit4/pom.xml . Why we have two profiles junit5-jupiter and junit5-vintage? They are the same. The profiles are similar but not the same. While the former adds junit-jupiter-engine as a dependency, the latter adds junit-vintage-engine. > Why we have direct dependencies of junit-platform-launcher, junit-platform-engine with scope=compile. Why there is not provided scope like it is in TestNG provider in Surefire? Users of Surefire/Jupiter only need junit-jupiter-api in their POM's dependencies (scope=test) in order to write tests. At runtime, they need junit-jupiter-engine to execute tests using the new provider (as added by the `junit5-jupiter` profile). The provider needs junit-platform-launcher and its dependency junit-platform-engine because it references classes from both artifacts in its code. You can think of the Launcher API as a replacement of `JUnitCore` from JUnit 4. These are usually not added/provided by the users manually. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MINSTALL-144) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MINSTALL-144: Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MINSTALL-144 URL: https://issues.apache.org/jira/browse/MINSTALL-144 Project: Maven Install Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Tibor17 commented on issue #183: junit5
Tibor17 commented on issue #183: junit5 URL: https://github.com/apache/maven-surefire/pull/183#issuecomment-381404680 @sormuras @britter I want to understand the old commit of IT `junit4/pom.xml` . Why we have two profiles `junit5-jupiter` and `junit5-vintage`? They are the same. How our ITs should look like? Why we have direct dependencies of `junit-platform-launcher`, `junit-platform-engine` with scope=compile. Why there is not provided scope like it is in TestNG provider in Surefire? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MDEP-607) maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException
[ https://issues.apache.org/jira/browse/MDEP-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438677#comment-16438677 ] Karl Heinz Marbaise commented on MDEP-607: -- Upgraded maven-dependency-analyzer after it's released I can do a new release of maven-dependency-plugin... > maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException > --- > > Key: MDEP-607 > URL: https://issues.apache.org/jira/browse/MDEP-607 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Affects Versions: 3.1.0 > Environment: mvn --version > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; > 2018-02-24T19:49:05Z) > Maven home: /usr/local/Cellar/maven/3.5.3/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_PT, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.4", arch: "x86_64", family: "mac" >Reporter: Filipe Sousa >Priority: Major > Fix For: next-release > > Attachments: analyze-3.0.2.txt.gz, analyze-3.1.0.txt.gz, > image-2018-04-14-23-09-21-784.png, image-2018-04-14-23-10-37-681.png > > > I'm having this NPE with 3.1.0. I have no problem with 3.0.2 > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:analyze > I'm attaching the output of both versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-718) Upgrade asm to most recent version 6.1.1
[ https://issues.apache.org/jira/browse/MSHARED-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438673#comment-16438673 ] Hudson commented on MSHARED-718: Build failed in Jenkins: Maven TLP » maven-dependency-analyzer » master #20 See https://builds.apache.org/job/maven-box/job/maven-dependency-analyzer/job/master/20/ > Upgrade asm to most recent version 6.1.1 > > > Key: MSHARED-718 > URL: https://issues.apache.org/jira/browse/MSHARED-718 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-dependency-analyzer-1.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-dependency-analyzer-1.10 > > > Based on the upgrade of asm to 6.1.1 it is also required to upgrade > commons-lang3 to version 3.7 which requires a JDK minimum upgrade to 7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-718) Upgrade asm to most recent version 6.1.1
[ https://issues.apache.org/jira/browse/MSHARED-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-718: Fix Version/s: (was: maven-dependency-analyzer-3.0.0) maven-dependency-analyzer-1.10 > Upgrade asm to most recent version 6.1.1 > > > Key: MSHARED-718 > URL: https://issues.apache.org/jira/browse/MSHARED-718 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-dependency-analyzer-1.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-dependency-analyzer-1.10 > > > Based on the upgrade of asm to 6.1.1 it is also required to upgrade > commons-lang3 to version 3.7 which requires a JDK minimum upgrade to 7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-718) Upgrade asm to most recent version 6.1.1
[ https://issues.apache.org/jira/browse/MSHARED-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-718: Description: Based on the upgrade of asm to 6.1.1 it is also required to upgrade commons-lang3 to version 3.7 which requires a JDK minimum upgrade to 7. > Upgrade asm to most recent version 6.1.1 > > > Key: MSHARED-718 > URL: https://issues.apache.org/jira/browse/MSHARED-718 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-dependency-analyzer-1.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-dependency-analyzer-3.0.0 > > > Based on the upgrade of asm to 6.1.1 it is also required to upgrade > commons-lang3 to version 3.7 which requires a JDK minimum upgrade to 7. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-718) Upgrade asm to most recent version 6.1.1
[ https://issues.apache.org/jira/browse/MSHARED-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438671#comment-16438671 ] Hudson commented on MSHARED-718: Build succeeded in Jenkins: Maven TLP » maven-dependency-analyzer » MSHARED-718 #2 See https://builds.apache.org/job/maven-box/job/maven-dependency-analyzer/job/MSHARED-718/2/ > Upgrade asm to most recent version 6.1.1 > > > Key: MSHARED-718 > URL: https://issues.apache.org/jira/browse/MSHARED-718 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-dependency-analyzer-1.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-dependency-analyzer-3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MDEP-607) maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException
[ https://issues.apache.org/jira/browse/MDEP-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-607: - Fix Version/s: next-release > maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException > --- > > Key: MDEP-607 > URL: https://issues.apache.org/jira/browse/MDEP-607 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Affects Versions: 3.1.0 > Environment: mvn --version > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; > 2018-02-24T19:49:05Z) > Maven home: /usr/local/Cellar/maven/3.5.3/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_PT, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.4", arch: "x86_64", family: "mac" >Reporter: Filipe Sousa >Priority: Major > Fix For: next-release > > Attachments: analyze-3.0.2.txt.gz, analyze-3.1.0.txt.gz, > image-2018-04-14-23-09-21-784.png, image-2018-04-14-23-10-37-681.png > > > I'm having this NPE with 3.1.0. I have no problem with 3.0.2 > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:analyze > I'm attaching the output of both versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-607) maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException
[ https://issues.apache.org/jira/browse/MDEP-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438659#comment-16438659 ] Filipe Sousa commented on MDEP-607: --- [~rfscholte] you are right. With the last asm (6.1.1) works without the NPE. Thanks. > maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException > --- > > Key: MDEP-607 > URL: https://issues.apache.org/jira/browse/MDEP-607 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Affects Versions: 3.1.0 > Environment: mvn --version > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; > 2018-02-24T19:49:05Z) > Maven home: /usr/local/Cellar/maven/3.5.3/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_PT, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.4", arch: "x86_64", family: "mac" >Reporter: Filipe Sousa >Priority: Major > Attachments: analyze-3.0.2.txt.gz, analyze-3.1.0.txt.gz, > image-2018-04-14-23-09-21-784.png, image-2018-04-14-23-10-37-681.png > > > I'm having this NPE with 3.1.0. I have no problem with 3.0.2 > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:analyze > I'm attaching the output of both versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-719) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MSHARED-719: --- Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MSHARED-719 URL: https://issues.apache.org/jira/browse/MSHARED-719 Project: Maven Shared Components Issue Type: Dependency upgrade Components: file-management Affects Versions: file-management-3.0.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: file-management-3.0.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (MSHARED-718) Upgrade asm to most recent version 6.1.1
[ https://issues.apache.org/jira/browse/MSHARED-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MSHARED-718: --- Assignee: Karl Heinz Marbaise > Upgrade asm to most recent version 6.1.1 > > > Key: MSHARED-718 > URL: https://issues.apache.org/jira/browse/MSHARED-718 > Project: Maven Shared Components > Issue Type: Task >Affects Versions: maven-dependency-analyzer-1.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-dependency-analyzer-3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-718) Upgrade asm to most recent version 6.1.1
Karl Heinz Marbaise created MSHARED-718: --- Summary: Upgrade asm to most recent version 6.1.1 Key: MSHARED-718 URL: https://issues.apache.org/jira/browse/MSHARED-718 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-dependency-analyzer-1.9 Reporter: Karl Heinz Marbaise Fix For: maven-dependency-analyzer-3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6396) Internal Exception running clean install
[ https://issues.apache.org/jira/browse/MNG-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438647#comment-16438647 ] Mario La Menza commented on MNG-6396: - Thanks!!! > Internal Exception running clean install > > > Key: MNG-6396 > URL: https://issues.apache.org/jira/browse/MNG-6396 > Project: Maven > Issue Type: Bug > Components: Errors >Affects Versions: 3.3.9 > Environment: Mac OSX Yosemite, java 1.7.0 >Reporter: Mario La Menza >Priority: Major > Attachments: debug.log > > > I leave the log. Thanks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-607) maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException
[ https://issues.apache.org/jira/browse/MDEP-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16438646#comment-16438646 ] Robert Scholte commented on MDEP-607: - Looks like an ASM issue. Can you try to add the latest asm version as dependency to the plugin in your pom? > maven-dependency-plugin:3.1.0:analyze failed.: NullPointerException > --- > > Key: MDEP-607 > URL: https://issues.apache.org/jira/browse/MDEP-607 > Project: Maven Dependency Plugin > Issue Type: Bug > Components: analyze >Affects Versions: 3.1.0 > Environment: mvn --version > Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; > 2018-02-24T19:49:05Z) > Maven home: /usr/local/Cellar/maven/3.5.3/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_PT, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.4", arch: "x86_64", family: "mac" >Reporter: Filipe Sousa >Priority: Major > Attachments: analyze-3.0.2.txt.gz, analyze-3.1.0.txt.gz, > image-2018-04-14-23-09-21-784.png, image-2018-04-14-23-10-37-681.png > > > I'm having this NPE with 3.1.0. I have no problem with 3.0.2 > mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.0:analyze > I'm attaching the output of both versions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MNG-6396) Internal Exception running clean install
[ https://issues.apache.org/jira/browse/MNG-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-6396. Resolution: Not A Problem The simple reason that the used gitflowincrementalbuild needs JDK 8 to run...which you obviously not using. Furthermore you are using Sping Boot which needs JDK 8 which is not the case. So you have to use JDK 8 instead of JDK 7 > Internal Exception running clean install > > > Key: MNG-6396 > URL: https://issues.apache.org/jira/browse/MNG-6396 > Project: Maven > Issue Type: Bug > Components: Errors >Affects Versions: 3.3.9 > Environment: Mac OSX Yosemite, java 1.7.0 >Reporter: Mario La Menza >Priority: Major > Attachments: debug.log > > > I leave the log. Thanks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MNG-6396) Internal Exception running clean install
Mario La Menza created MNG-6396: --- Summary: Internal Exception running clean install Key: MNG-6396 URL: https://issues.apache.org/jira/browse/MNG-6396 Project: Maven Issue Type: Bug Components: Errors Affects Versions: 3.3.9 Environment: Mac OSX Yosemite, java 1.7.0 Reporter: Mario La Menza Attachments: debug.log I leave the log. Thanks -- This message was sent by Atlassian JIRA (v7.6.3#76005)
