[jira] [Created] (MCHANGES-389) ${release.description} is not set for JIRA
Thomas Scheffler created MCHANGES-389:
-
Summary: ${release.description} is not set for JIRA
Key: MCHANGES-389
URL: https://issues.apache.org/jira/browse/MCHANGES-389
Project: Maven Changes Plugin
Issue Type: Bug
Affects Versions: 2.12.1
Reporter: Thomas Scheffler
[Using a Custom Announcement
Template|https://maven.apache.org/plugins/maven-changes-plugin/examples/using-a-custom-announcement-template.html]
states that {{$\{release.description}}} can be used in templates. This does
not work with Jira where the release has a description set.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-720) Toolchain is ignored
[ https://issues.apache.org/jira/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235233#comment-16235233 ] Thomas Scheffler commented on SUREFIRE-720: --- Can confirm this bug is still present in 2.20 > Toolchain is ignored > > > Key: SUREFIRE-720 > URL: https://issues.apache.org/jira/browse/SUREFIRE-720 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_19, vendor: Sun Microsystems Inc. > Java home: C:\Users\alex\Software\jdk1.6.0_19\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" >Reporter: Jun >Assignee: Kristian Rosenvold >Priority: Major > Fix For: 2.9 > > Attachments: SurefireToolchains.zip > > > The following debug output demonstrates the problem: > ... > [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > ... > [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > [WARNING] Toolchains are ignored, 'executable' parameter is set to > C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java > Forking command line: cmd.exe /X /C > "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar > ... > Compiler plugin uses proper JDK, while Surefire falls back to default. The > problem is not reproducible with Surefire 2.6 and 2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-720) Toolchain is ignored
[ https://issues.apache.org/jira/browse/SUREFIRE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16235232#comment-16235232 ] Thomas Scheffler commented on SUREFIRE-720: --- Can confirm this bug is still present in 2.20 > Toolchain is ignored > > > Key: SUREFIRE-720 > URL: https://issues.apache.org/jira/browse/SUREFIRE-720 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.7, 2.7.1, 2.7.2, 2.8 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: C:\Users\alex\Software\apache-maven-3.0.3\bin\.. > Java version: 1.6.0_19, vendor: Sun Microsystems Inc. > Java home: C:\Users\alex\Software\jdk1.6.0_19\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "x86", family: "windows" >Reporter: Jun >Assignee: Kristian Rosenvold >Priority: Major > Fix For: 2.9 > > Attachments: SurefireToolchains.zip > > > The following debug output demonstrates the problem: > ... > [INFO] Toolchain in compiler-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > ... > [INFO] Toolchain in surefire-plugin: JDK[C:/Users/alex/Software/jdk1.5.0_22] > [WARNING] Toolchains are ignored, 'executable' parameter is set to > C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java > Forking command line: cmd.exe /X /C > "C:\Users\alex\Software\jdk1.6.0_19\jre\bin\java -jar > ... > Compiler plugin uses proper JDK, while Surefire falls back to default. The > problem is not reproducible with Surefire 2.6 and 2.5. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] (MCHECKSTYLE-287) checkstyle report throws NPE
Thomas Scheffler created MCHECKSTYLE-287:
Summary: checkstyle report throws NPE
Key: MCHECKSTYLE-287
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-287
Project: Maven Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.14, 2.13
Reporter: Thomas Scheffler
I don't know what triggers this bug. Somehow
org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.collectArtifacts(String)
produces a List which contains the null object. And therefor an exception is
thrown here (2.14):
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project
oaipmh: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
NullPointerException - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on project
oaipmh: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
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
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-site of goal org.apache.maven.plugins:maven-site-plugin:3.3:site failed.
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:143)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.configureResourceLocator(DefaultCheckstyleExecutor.java:852)
at
org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:102)
at
org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:474)
at
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:156)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:255)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
... 20 more
{noformat}
Looking at the code, you see a null check is done for the list, bit not for
elements of that list:
{noformat}
// MCHECKSTYLE-225: load licenses from additional artifacts, not from
classpath
if ( additionalArtifacts != null )
{
for ( Artifact licenseArtifact : additionalArtifacts )
{
try
{
resourceManager.addSearchPath( jar, jar: +
[jira] (MCHANGES-333) announcement-generate for JIRA doesn't query for relevant issues
[
https://jira.codehaus.org/browse/MCHANGES-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=361137#comment-361137
]
Thomas Scheffler commented on MCHANGES-333:
---
I noticed the same behaviour. We switched from SourceForge to JIRA and therefor
from changes.xml to JIRA, too. But I cannot get the announcement to work. Here
are some numbers:
- Issues count: *667*
- Issues fixed in the current release: *2*
- Issues fetched from JIRA to accidentally get the current release name: *25*
- Fields fetched to get the fixVersion field: *all*
You see I have to configure: {{maxEntries666/maxEntries}} (which is a bad
number) for {{changes:announcement-generate}} to work.
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.11:announcement-generate
(default-cli) on project mycore: No releases found in any of the configured
issue management systems. - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-changes-plugin:2.11:announcement-generate
(default-cli) on project mycore: No releases found in any of the configured
issue management systems.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
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
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: No releases found in
any of the configured issue management systems.
at
org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:580)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{noformat}
Instead of querying *all* issues with *all* fields to get a list of all
versions, it would be better to use
*_[/rest/api/2/project/\{projectIdOrKey\}/versions|https://docs.atlassian.com/jira/REST/latest/#d2e231]_*.
announcement-generate for JIRA doesn't query for relevant issues
Key: MCHANGES-333
URL: https://jira.codehaus.org/browse/MCHANGES-333
Project: Maven Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.9
Reporter: Richard Barnett
Attachments: MCHANGES-333.patch
{{announcement-generate}} for JIRA submits a JQL query eg
{code}
Address: https://palomamobile.atlassian.net/rest/api/2/search
...
Payload: {jql:project = PCSV AND status in (5, 6) AND resolution in (1,
8),maxResults:25,fields:[*all]}
{code}
and then selects issues from the response which were fixed in the current
version. If no issues are selected the goal fails, eg:
{code}
Couldn't find the release '1.0.76' among the supplied releases:
[Release[version='1.0.73.1', date='null', description='null', actionsSize=2],
Release[version='1.0.73', date='null', description='null', actionsSize=3],
Release[version='1.0.72', date='null', description='null', actionsSize=2],
Release[version='1.0.75', date='null', description='null', actionsSize=5],
Release[version='1.0.74', date='null', description='null', actionsSize=4],
[jira] (MCHANGES-326) announcement-mail does not respect templateEncoding
Thomas Scheffler created MCHANGES-326:
-
Summary: announcement-mail does not respect templateEncoding
Key: MCHANGES-326
URL: https://jira.codehaus.org/browse/MCHANGES-326
Project: Maven Changes Plugin
Issue Type: Bug
Components: announcement
Affects Versions: 2.9
Reporter: Thomas Scheffler
While announcement-generate goal uses templateEncoding with defaults to
${project.build.sourceEncoding}, announcement-mail uses the system default
encoding. This results in scrambled mails.
Currently FileReader is used to read the announcement which does not allow to
specify a encoding. InputStreamReader should be used instead in
org.apache.maven.plugin.announcement.AnnouncementMailMojo.readAnnouncement()
kind regards
Thomas
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-486) Site navigation not generated for submodules of multimodule project when site.xml defined in the parent
[
http://jira.codehaus.org/browse/MSITE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=235039#action_235039
]
Thomas Scheffler commented on MSITE-486:
The workaround described by André
{quote}
Adding an _inherit_ attribute will do it (for 2.1.1).
{{menu ref=modules inherit=top/}}
{quote}
does *not* work for me with 2.1.1.
It is definitely not an option to provide a site.xml to every child pom just to
define a skin for every subproject, as it works find with 2.0.1
Site navigation not generated for submodules of multimodule project when
site.xml defined in the parent
---
Key: MSITE-486
URL: http://jira.codehaus.org/browse/MSITE-486
Project: Maven 2.x Site Plugin
Issue Type: Bug
Affects Versions: 2.1, 2.1.1
Environment: Windows XP SP2, Sun/Oracle JDK 1.6, Maven 2.2.1
Reporter: Grzegorz Slowikowski
Attachments: MSITE-486.zip
Bug that manifests itself like http://jira.codehaus.org/browse/MSITE-456 but
in different configuration.
If you define src/site/site.xml file for the root module the navigation
left menu in submodule is completely empty. After deleting this site.xml
file everything works (maybe something has recently changed in this file
content/structure requirements).
Everything works without problems for 2.0.1 version of Maven site plugin.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTTASKS-203) java.lang.ClassCastException: org.codehaus.plexus.DefaultPlexusContainer cannot be cast to org.codehaus.plexus.PlexusContainer
java.lang.ClassCastException: org.codehaus.plexus.DefaultPlexusContainer cannot be cast to org.codehaus.plexus.PlexusContainer -- Key: MANTTASKS-203 URL: http://jira.codehaus.org/browse/MANTTASKS-203 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: dependencies task Affects Versions: 2.1.1, 2.1.0 Environment: Apache Ant version 1.8.1 Linux java version 1.6.0_21 Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode) Reporter: Thomas Scheffler Priority: Critical Attachments: build.xml Running ant test test2 for the submitted test results in a ClassCastException: java.lang.ClassCastException: org.codehaus.plexus.DefaultPlexusContainer cannot be cast to org.codehaus.plexus.PlexusContainer at org.apache.maven.artifact.ant.AbstractArtifactTask.getContainer(AbstractArtifactTask.java:481) at org.apache.maven.artifact.ant.AbstractArtifactTask.lookup(AbstractArtifactTask.java:456) at org.apache.maven.artifact.ant.AbstractArtifactTask.initSettings(AbstractArtifactTask.java:289) at org.apache.maven.artifact.ant.AbstractArtifactTask.execute(AbstractArtifactTask.java:717) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:390) at org.apache.tools.ant.Target.performTasks(Target.java:411) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397) at org.apache.tools.ant.Project.executeTarget(Project.java:1366) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1249) at org.apache.tools.ant.Main.runBuild(Main.java:801) at org.apache.tools.ant.Main.startAnt(Main.java:218) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
