[jira] (SUREFIRE-870) Error occurred in starting fork shouldn't be reported for all forks with non-zero exit codes
[ https://jira.codehaus.org/browse/SUREFIRE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-870: Fix Version/s: 2.12.1 Error occurred in starting fork shouldn't be reported for all forks with non-zero exit codes -- Key: SUREFIRE-870 URL: https://jira.codehaus.org/browse/SUREFIRE-870 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.12 Reporter: Andrew Bayer Assignee: Kristian Rosenvold Fix For: 2.12.1 If a forked test has a non-zero exit code for any reason, it's reported by Surefire as Error occurred in starting fork. It's distinctly possible for a forked test to have a non-zero exit code for reasons other than problems starting the fork - i.e., a bad test that as a System.exit(1) in it, etc. The error should either be more general, or more specific tracing of the problem should be done. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-651) Unnecessary parent and modules menus show up as empty sections in sitemap
[
https://jira.codehaus.org/browse/MSITE-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307422#comment-307422
]
Andreas Sewe commented on MSITE-651:
As shown in the screenshot, the fix has at least one shortcoming: What was
previously the Project Documentation menu now becomes the reports menu.
Likewise, parent and module should be replaced by proper, localized titles.
That being said, while the fix improves upon the current situation, it is far
from perfect (IMHO: It doesn't warrant a _Fixed_ for this issue, as per the
issue's title): Ideally, the empty sections would not show up at all. After
all, they don't show up in the menu sidebar either, so it seems illogical to
have them in the sitemap. (I am curious why the menu generation code cannot be
adapted for sitemap generation.)
Unnecessary parent and modules menus show up as empty sections in sitemap
-
Key: MSITE-651
URL: https://jira.codehaus.org/browse/MSITE-651
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Affects Versions: 3.1
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Reporter: Andreas Sewe
Attachments: example.tar.gz, screenshot-1.jpg
When using {{generateSitemap}}, the resulting {{sitemap.html}} contains ugly
empty sections (empty {{h4}}, superfluous {{hr}}) if one of the _special_
menus ({{parent}}, {{module}}) is empty as the project in question does not
have a parent or modules, respectively.
The {{sitemap.html}} generated by the attached example project ({{mvn site}})
illustrates this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-179) Warnings
Sascha Vogt created MCOMPILER-179: - Summary: Warnings Key: MCOMPILER-179 URL: https://jira.codehaus.org/browse/MCOMPILER-179 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.5.1, 2.5, 2.4 Environment: Windows7, 64-bit VMs, 1.6.0_32 and 1.7.0_04 both 64-bit Reporter: Sascha Vogt If one error occurs, all warnings are shown as error as well. Up to 2.3.2 this was not the case. Sample output 2.4 and higher: [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] bad path element : no such file or directory C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [ERROR] C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [ERROR] C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15] [unchecked] unchecked conversion found : java.util.List required: java.util.Listjava.lang.String [ERROR] C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29] getList() in de.maybebuggy.sample.Main cannot be applied to (int) [INFO] 4 errors Sample output 2.3.2: [INFO] - [WARNING] COMPILATION WARNING : [INFO] - [WARNING] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [WARNING] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [WARNING] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15] [unchecked] unchecked conversion found : java.util.List required: java.util.Listjava.lang.String [INFO] 3 warnings [INFO] - [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29] getList() in de.maybebuggy.sample.Main cannot be applied to (int) [INFO] 1 error [INFO] - With the current behavior it is extremely hard to spot the error if there are multiple warnings in a project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-179) Warnings
[ https://jira.codehaus.org/browse/MCOMPILER-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307425#comment-307425 ] Sascha Vogt commented on MCOMPILER-179: --- I'm sorry, I missed the settings for the compiler (copied from the effective pom): compilerArgument-Xlint:all/compilerArgument showWarningstrue/showWarnings showDeprecationtrue/showDeprecation compilerVersion1.6/compilerVersion source1.6/source target1.6/target Warnings - Key: MCOMPILER-179 URL: https://jira.codehaus.org/browse/MCOMPILER-179 Project: Maven 2.x Compiler Plugin Issue Type: Bug Affects Versions: 2.4, 2.5, 2.5.1 Environment: Windows7, 64-bit VMs, 1.6.0_32 and 1.7.0_04 both 64-bit Reporter: Sascha Vogt If one error occurs, all warnings are shown as error as well. Up to 2.3.2 this was not the case. Sample output 2.4 and higher: [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] bad path element : no such file or directory C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [ERROR] C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [ERROR] C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15] [unchecked] unchecked conversion found : java.util.List required: java.util.Listjava.lang.String [ERROR] C:\dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29] getList() in de.maybebuggy.sample.Main cannot be applied to (int) [INFO] 4 errors Sample output 2.3.2: [INFO] - [WARNING] COMPILATION WARNING : [INFO] - [WARNING] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[19,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [WARNING] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[20,18] [unchecked] unchecked call to add(E) as a member of the raw type java.util.List [WARNING] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[24,15] [unchecked] unchecked conversion found : java.util.List required: java.util.Listjava.lang.String [INFO] 3 warnings [INFO] - [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] \dev-tmp\sample\src\main\java\de\maybebuggy\sample\Main.java:[29,29] getList() in de.maybebuggy.sample.Main cannot be applied to (int) [INFO] 1 error [INFO] - With the current behavior it is extremely hard to spot the error if there are multiple warnings in a project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2521) Using JDK 1.5+ annotations for mojos metadata
[ https://jira.codehaus.org/browse/MNG-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-2521. -- Resolution: Fixed Fix Version/s: (was: 3.1) Assignee: Herve Boutemy (was: Jason van Zyl) done in maven-plugin-tools 3.0 (not in Maven Core), see MPLUGIN-189 Using JDK 1.5+ annotations for mojos metadata - Key: MNG-2521 URL: https://jira.codehaus.org/browse/MNG-2521 Project: Maven 2 3 Issue Type: New Feature Components: Multiple Language Support Affects Versions: 2.0-alpha-1, 2.0.4, 2.0.5 Reporter: Yoav Landman Assignee: Herve Boutemy Attachments: format-maven-plugin-plugin.diff, format-maven-plugin-tools-java5.diff, maven-plugin-plugin-postcompile.diff, maven-plugin-tools-anno.patch, maven-plugin-tools-annotations.tar.gz, maven-plugin-tools-java5.diff, maven-plugin-tools-java5.tar.gz The attached patch contains a plugin-tool that allows writing annotatd mojos using JDK 1.5 annotations instead of doclet comments. It is was created from (my) sf.net project https://sourceforge.net/projects/mvn-anno-mojo/. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-626) NullPointerException in PlexusIoURLResource.getContents
Nathaniel Mishkin created MASSEMBLY-626: --- Summary: NullPointerException in PlexusIoURLResource.getContents Key: MASSEMBLY-626 URL: https://jira.codehaus.org/browse/MASSEMBLY-626 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.3 Reporter: Nathaniel Mishkin I have a situation where I can reliably reproduce an NPE during assembly in one dev environment but not in another. Probably the most notable difference between the environments is that the working one is running Windows and the non-working one is running Linux, but it's not clear why that should matter. The project is unfortunately part of a large multi-module project so I can't readily attach it here and I haven't yet attempted to boil it down. So hopefully this stack trace will help: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.3:single (default) on project system-tests: Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:2.3:single failed. NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.3:single (default) on project system-tests: Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:2.3:single failed. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:2.3:single failed. at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.components.io.resources.PlexusIoURLResource.getContents(PlexusIoURLResource.java:38) at org.codehaus.plexus.archiver.ArchiveEntry.getInputStream(ArchiveEntry.java:106) at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.zipFile(AbstractZipArchiver.java:552) at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.addResources(AbstractZipArchiver.java:387) at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:312) at org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:211) at org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:897) at org.apache.maven.plugin.assembly.archive.archiver.AssemblyProxyArchiver.createArchive(AssemblyProxyArchiver.java:512) at org.apache.maven.plugin.assembly.archive.DefaultAssemblyArchiver.createArchive(DefaultAssemblyArchiver.java:185) at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:452) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) ... 20 more The relevant bit of the effective POM is pretty simple, but here it is anyway: plugin artifactIdmaven-assembly-plugin/artifactId
[jira] (MASSEMBLY-557) Corrupted zip created by assembly: extracting the zip forgets certain folders (or throws permission denied errors) possibly because zip index is corrupted
[
https://jira.codehaus.org/browse/MASSEMBLY-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307479#comment-307479
]
Christian Bayer commented on MASSEMBLY-557:
---
@Christoph Gritschenberger
We have a similar setup, that can be reduced to a fileSet with a directory but
no explicit directoryMode set. Try adding
{code}
directoryMode0755/directoryMode
{code}
to your fileSet. Worked for us.
Corrupted zip created by assembly: extracting the zip forgets certain folders
(or throws permission denied errors) possibly because zip index is corrupted
--
Key: MASSEMBLY-557
URL: https://jira.codehaus.org/browse/MASSEMBLY-557
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2.1
Reporter: Geoffrey De Smet
Priority: Critical
Attachments:
droolsjbpm-integration-distribution-5.2.0.M2_BROKEN_IN_reference_manual_gutted.zip
Take a look at the attached zip created by the assembly plugin.
- If you open it, you can see navigate to the submap
/droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/pdf/. In that
map you find the file droolsjbpm-integration-docs.pdf which you can open with
a PDF reader.
- If instead you extract the entire archive to a directory, and navigate to
the submap
/droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/pdf/, you 'll
find that that map is unreadable (chmod 000) and the pdf file is gone.
The directories html_single and html suffer the same fate, but none of the
other directories do.
I used the default linux Ubuntu 10.10 archive manager (which according to
about screen is called File-roller 2.32.0).
I used Maven 3.0.3, maven-assembly-plugin 2.2.1.
Note that that attached zip is gutted to stay inside the maximum file upload
size.
Possible reproduce recipe:
{code}
git clone g...@github.com:droolsjbpm/droolsjbpm-integration.git
cd droolsjbpm-integration
git checkout 5.2.0.M2
mvn clean install -DskipTests -Dfull
cd droolsjbpm-integration/target
ls
{code}
{code}
checkdir error: cannot create
/home/gdesmet/tmp/releases/problem_with_the_release_zip/droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/html_single/images
Permission denied
unable to process
droolsjbpm-integration-distribution-5.2.0.M2/reference_manual/html_single/images/.
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5339) update the format
[ https://jira.codehaus.org/browse/MNG-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianbin Wei updated MNG-5339: - Attachment: MNG-5339.patch update the format -- Key: MNG-5339 URL: https://jira.codehaus.org/browse/MNG-5339 Project: Maven 2 3 Issue Type: Improvement Components: Documentation: Guides Affects Versions: Documentation Deficit Reporter: Jianbin Wei Priority: Trivial Attachments: MNG-5339.patch Update the project structure under Maven in 5 Minutes guide -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5339) update the format
Jianbin Wei created MNG-5339: Summary: update the format Key: MNG-5339 URL: https://jira.codehaus.org/browse/MNG-5339 Project: Maven 2 3 Issue Type: Improvement Components: Documentation: Guides Affects Versions: Documentation Deficit Reporter: Jianbin Wei Priority: Trivial Attachments: MNG-5339.patch Update the project structure under Maven in 5 Minutes guide -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-790) multi-module projects in profiles are ignored by release-prepare
[ https://jira.codehaus.org/browse/MRELEASE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307500#comment-307500 ] Johannes bannhofer commented on MRELEASE-790: - well I definetly acticated it, because i also start a code generator by another profile and both have and the code was generated but the multimodule part was ignored. Thanks for the hint to the other bug I will check it out, it sounds promising. multi-module projects in profiles are ignored by release-prepare Key: MRELEASE-790 URL: https://jira.codehaus.org/browse/MRELEASE-790 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Environment: win 7, maven 3.0.4, mvn-release 2.3 Reporter: Johannes bannhofer Assignee: Robert Scholte Priority: Minor modules defined in profiles are ignored by release:prepare. I tried to move my modules build to a profile, but after that releae:prepare just builds and tags the parent itself, althought the profile was ativated. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg reassigned MCHANGES-285: Assignee: Dennis Lundberg SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Assignee: Dennis Lundberg Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLScanner.scanAttributeValue(Unknown Source) at
[jira] (MCHANGES-285) SAXException parsing JIRA XML from JIRA 5.1
[ https://jira.codehaus.org/browse/MCHANGES-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307501#comment-307501 ] Dennis Lundberg commented on MCHANGES-285: -- Thanks for the patch. I'll have a closer look at it. Unfortunately it contains both refactorings and new functionality. It can be quite difficult to read such a patch, but I'll give it a try. SAXException parsing JIRA XML from JIRA 5.1 Key: MCHANGES-285 URL: https://jira.codehaus.org/browse/MCHANGES-285 Project: Maven 2.x Changes Plugin Issue Type: Bug Components: jira Affects Versions: 2.7.1 Environment: osx rhel sun java 1.6.0_30 Reporter: Micah Whitacre Attachments: patch-2.7.x.txt, patch.txt When trying to generate a changes report from a JIRA instance running 5.1[1] I get the following exception [INFO] Generating JIRA Report report--- maven-changes-plugin:2.7.1 Jul 16, 2012 5:32:53 PM org.apache.commons.httpclient.HttpMethodBase getResponseBody WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://bugs.cloud.cerner.corp/secure/IssueNavigator.jspa?view=rsspid=10670component=kepler-clientcomponent=kepler-parentstatus=Verifiedstatus=Closedresolution=1resolution=12tempMax=100reset=truedecorator=none [WARNING] org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML. at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132) at org.apache.maven.plugin.jira.JiraXML.parseXML(JiraXML.java:108) at org.apache.maven.plugin.jira.AbstractJiraDownloader.getIssueList(AbstractJiraDownloader.java:755) at org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:347) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.xml.sax.SAXParseException: The entity name must immediately follow the '' in the entity reference. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at
[jira] (MNG-5339) update the format
[ https://jira.codehaus.org/browse/MNG-5339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jianbin Wei updated MNG-5339: - Attachment: MNG-5339.patch replace more formats of directory structure update the format -- Key: MNG-5339 URL: https://jira.codehaus.org/browse/MNG-5339 Project: Maven 2 3 Issue Type: Improvement Components: Documentation: Guides Affects Versions: Documentation Deficit Reporter: Jianbin Wei Priority: Trivial Attachments: MNG-5339.patch, MNG-5339.patch Update the project structure under Maven in 5 Minutes guide -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-841) Incorrect Test Run Count
[
https://jira.codehaus.org/browse/SUREFIRE-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=307511#comment-307511
]
Mikhail Mazursky commented on SUREFIRE-841:
---
Also encountered this with surefire 2.12.3 and TestNG 6.7. Failure in
@BeforeClass increments Tests run.
{code}
public class RealTest {
@BeforeClass
public void beforeClass() {
assertThat(false).isTrue();
}
@Test
public void test(){}
}
{code}
With failure it's output is
{noformat}
Tests run: 2, Failures: 1, Errors: 0, Skipped: 1
{noformat}
Without:
{noformat}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
{noformat}
Incorrect Test Run Count
Key: SUREFIRE-841
URL: https://jira.codehaus.org/browse/SUREFIRE-841
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Reporter: karthik kandasamy
When a simple Junit test with errors in the @Before() and @After() method are
run directly with java or ant's junit task, it reports correctly that the
Tests Run = 1 and Errors = 2.
But when the same is run through maven surefire plugin, it reports it as
Tests Run = 2 and Errors = 2.
Its the same test in which 2 errors are encountered, so the Tests Run should
be 1.
I traced the issue to the org.apache.maven.surefire.report.TestSetRunListener
Class - testError() method, where the completed count is also incremented
along with the error count irrespective of whether its in the same test the
error is encountered.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
