[jira] (MPIR-236) Create a new report to show how to include the module in different build systems
[
https://jira.codehaus.org/browse/MPIR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305607#comment-305607
]
Simone Tripodi commented on MPIR-236:
-
Thanks for reporting Christian, looks like the {{project.packaging}} property
was a corrupted, see modifications on
[r1369732|https://svn.apache.org/viewvc/maven/plugins/trunk/maven-project-info-reports-plugin/src/main/java/org/apache/maven/report/projectinfo/DependencyInformationReport.java?r1=1369732r2=1369731pathrev=1369732]
Do you have any chance to test it against latest snapshot? You may have to
rebuilt it locally first.
TIA!
Create a new report to show how to include the module in different build
systems
Key: MPIR-236
URL: https://jira.codehaus.org/browse/MPIR-236
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Components: dependency-info
Affects Versions: 2.5
Reporter: Simone Tripodi
Assignee: Simone Tripodi
Fix For: 2.5
Attachments: Clipboard01.png
Different Maven Repositories usually show an info section to show how to
include the found artifact in different build systems (Maven, Ivy, ...), it
would be nice having it directly in the documentation site as well
--
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] (MSKINS-55) Website layout broken when browser width is small.
[ https://jira.codehaus.org/browse/MSKINS-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305610#comment-305610 ] Edward J. Yoon commented on MSKINS-55: -- Thanks eric! Website layout broken when browser width is small. -- Key: MSKINS-55 URL: https://jira.codehaus.org/browse/MSKINS-55 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Reporter: Edward J. Yoon I use new fluido skin for http://hama.apache.org/ But, there's small layout problem when browser width is small. Please fix this, and let me know how can I fix this problem urgently. -- 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] (MPIR-236) Create a new report to show how to include the module in different build systems
[ https://jira.codehaus.org/browse/MPIR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305614#comment-305614 ] Christian Schlichtherle commented on MPIR-236: -- Thank you very much for the quick fix. I'm afraid building Maven components is beyond me - sorry! Create a new report to show how to include the module in different build systems Key: MPIR-236 URL: https://jira.codehaus.org/browse/MPIR-236 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Components: dependency-info Affects Versions: 2.5 Reporter: Simone Tripodi Assignee: Simone Tripodi Fix For: 2.5 Attachments: Clipboard01.png Different Maven Repositories usually show an info section to show how to include the found artifact in different build systems (Maven, Ivy, ...), it would be nice having it directly in the documentation site as well -- 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] (MPIR-236) Create a new report to show how to include the module in different build systems
[
https://jira.codehaus.org/browse/MPIR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305616#comment-305616
]
Simone Tripodi commented on MPIR-236:
-
You are welcome!
I may can help you on leading how to test it:
* open the shell and run {{svn co
https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-project-info-reports-plugin}};
* get into the directory and run {{mvn install}};
* in your project's {{pom.xml}} file, upgrade the
{{maven-project-info-reports-plugin}} declared version to {{2.6-SNAPSHOT}};
* open the shell in your project's location and run {{mvn site}}.
HTH!
Create a new report to show how to include the module in different build
systems
Key: MPIR-236
URL: https://jira.codehaus.org/browse/MPIR-236
Project: Maven 2.x Project Info Reports Plugin
Issue Type: Improvement
Components: dependency-info
Affects Versions: 2.5
Reporter: Simone Tripodi
Assignee: Simone Tripodi
Fix For: 2.5
Attachments: Clipboard01.png
Different Maven Repositories usually show an info section to show how to
include the found artifact in different build systems (Maven, Ivy, ...), it
would be nice having it directly in the documentation site as well
--
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:comment-tabpanelfocusedCommentId=305617#comment-305617
]
Jamie Duncombe commented on MCHANGES-285:
-
I am also able to confirm that I'm seeing this problem using a Jira 5.1 hosted
by Atlassian OnDemand, project was previously working on Jira 4.1.3 download
edition.
Viewing the generated URL from my stack trace in a web browser I can confirm
that the page returned is not in XML format but is the html page without
decoration, in my case at least it does return the correct results for the JQL
query.
URL generated:
https://{jira instance address removed for
security}/secure/IssueNavigator.jspa?view=rsspid=10680statusIds=1statusIds=3statusIds=4statusIds=5statusIds=6resolutionIds=-1resolutionIds=1resolutionIds=2resolutionIds=3resolutionIds=4resolutionIds=5component=11750sorter/field=createdsorter/order=DESCsorter/field=prioritysorter/order=DESCtempMax=100reset=truedecorator=none
A working URL obtained by requesting the xml (rss 0.9.2) format from the above
page:
https://{jira instance address removed for
security}/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+TOOLS+AND+component+%3D+toolname+ORDER+BY+created+DESC%2C+priority+DESCtempMax=100
Hope this helps,
Jamie
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
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
[jira] (JXR-97) jxr:jxr - Add regular expressions for the exclude and include pattern
Johannes Schur created JXR-97: - Summary: jxr:jxr - Add regular expressions for the exclude and include pattern Key: JXR-97 URL: https://jira.codehaus.org/browse/JXR-97 Project: Maven JXR Issue Type: New Feature Components: jxr Affects Versions: 2.3 Reporter: Johannes Schur Priority: Minor With the current filters only explicit 'includes' and 'excludes' are possible. With the pattern include**/test/*.java/include only files in the package test are included, but not the files in subpackages. To include all subpackages, you need includes up to maximum package depth. e.g.: include**/test/*.java/include include**/test/**/*.java/include include**/test/**/**/*.java/include include**/test/**/**/**/*.java/include and so on... -- 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] (JXR-97) jxr:jxr - Add regular expressions for the exclude and include pattern
[ https://jira.codehaus.org/browse/JXR-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305619#comment-305619 ] Johannes Schur commented on JXR-97: --- I thought: include***/test/**.java/include include***/test//**.java/include include***/test///**.java/include include***/test////**.java/include jxr:jxr - Add regular expressions for the exclude and include pattern - Key: JXR-97 URL: https://jira.codehaus.org/browse/JXR-97 Project: Maven JXR Issue Type: New Feature Components: jxr Affects Versions: 2.3 Reporter: Johannes Schur Priority: Minor With the current filters only explicit 'includes' and 'excludes' are possible. With the pattern include**/test/*.java/include only files in the package test are included, but not the files in subpackages. To include all subpackages, you need includes up to maximum package depth. e.g.: include**/test/*.java/include include**/test/**/*.java/include include**/test/**/**/*.java/include include**/test/**/**/**/*.java/include and so on... -- 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
]
Ton Swieb updated MCHANGES-285:
---
Attachment: patch.txt
I have the same issue with Jira 5.1 and created a patch for it.
The patch is based on the trunk.
I notice that at least since Jira 4.4.1 the URL's generated by this plugin are
rewritten by JIRA to a new type of URL based on JQL (Jira Query Language) en
probably since Jira 5.1 they have removed supported for the old type of URL.
The patch adds a new configuration flag useJql which can be enabled to query
for issues using JQL, but defaults to false for backwards compatibility.
The issue management URL must be of the form:
http(s)://host:port/browse/{projectname} because JQL uses the project name
instead of the project ID for constructing the query.
All other configuration parameters should work in the same way.
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.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
[jira] (SUREFIRE-899) Add support for TestNG order-by-instances property
Nicolas Labrot created SUREFIRE-899: --- Summary: Add support for TestNG order-by-instances property Key: SUREFIRE-899 URL: https://jira.codehaus.org/browse/SUREFIRE-899 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Affects Versions: 2.12 Reporter: Nicolas Labrot -- 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-5322) Support for 'Project Logo'
Ben Page created MNG-5322: - Summary: Support for 'Project Logo' Key: MNG-5322 URL: https://jira.codehaus.org/browse/MNG-5322 Project: Maven 2 3 Issue Type: Improvement Components: General, IDEs, POM Reporter: Ben Page Priority: Minor Has it ever been considered to have a way of specifing a URL / filepath for a project logo, so that IDEs / Site Generators / Etc could identify the project in a more visual fashion? Or is there a plugin that would allow this? -- 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-4792) Preemptive authentication doesn't work
[ https://jira.codehaus.org/browse/MNG-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305632#comment-305632 ] Brett Porter commented on MNG-4792: --- Lukasz - we frequently use Maven 2.2.1 to connect to private Archiva repos - feel free to ask for help on us...@archiva.apache.org. With regard to specifically enabling pre-emptive authentication on Maven 2.2.1, I believe it is possible to use the newer httpclient wagon with Maven 2.2.1 through an extension element, but I haven't confirmed that. Preemptive authentication doesn't work -- Key: MNG-4792 URL: https://jira.codehaus.org/browse/MNG-4792 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.2.1 Environment: Sun Java 1.6.0_21, Windows 7 Reporter: Marcin Zajaczkowski Assignee: Olivier Lamy Fix For: 3.0.4 It seems preemptive authentication in Maven using httpclient wagon provider doesn't work. With configuration taken form [1] Maven knock to repository (tested with Artifactory 2.2.5) as anonymous user. server idrepo-id/id usernameuser/username passwordpass/password configuration wagonProviderhttpclient/wagonProvider httpConfiguration put params param namehttp.authentication.preemptive/name value%b,true/value /param /params /put /httpConfiguration /configuration /server Confirmed by independent party also with Maven 2.2.1. I can sniff http traffic if needed. [1] - http://maven.apache.org/guides/mini/guide-http-settings.html -- 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] (MSHADE-127) NPE if shade plugin runs in artifact with packaging pom
Radim Kolar created MSHADE-127: -- Summary: NPE if shade plugin runs in artifact with packaging pom Key: MSHADE-127 URL: https://jira.codehaus.org/browse/MSHADE-127 Project: Maven 2.x Shade Plugin Issue Type: Bug Affects Versions: 1.7.1 Reporter: Radim Kolar Priority: Blocker Attachments: pom.xml If you run shade plugin in artifact with packagingpom/packaging it fails during replace step: [INFO] Replacing original artifact with shaded artifact. [INFO] Replacing null with C:\apache-nutch\nutch\runtime\deploy\runtime-1.5-SNAPSHOT-shaded.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 12.422s [INFO] Finished at: Mon Aug 06 15:44:11 CEST 2012 [INFO] Final Memory: 4M/62M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.7.1:shade (make-shaded-jar) on project runtime: Error creating shaded jar: null: NullPointerException - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.7.1:shade (make-shaded-jar) on project runtime: Error creating shaded jar: null at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) 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.MojoExecutionException: Error creating shaded jar: null at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:556) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: java.lang.NullPointerException at org.apache.maven.plugins.shade.mojo.ShadeMojo.replaceFile(ShadeMojo.java:570) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:536) ... 21 more -- 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] (MSHADE-128) Too many warnings We have duplicates
Raffaele created MSHADE-128: --- Summary: Too many warnings We have duplicates Key: MSHADE-128 URL: https://jira.codehaus.org/browse/MSHADE-128 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 1.7.1 Reporter: Raffaele Attachments: pom.xml, warning-we-have-duplicates.patch When creating an uberjar, sometimes the same class is present in two or more dependencies' JARs. For each class, maven-shade-plugin issues a WARNING We have a duplicate in. This is annoying and can muddle newcomers up (like myself), because it's not clear how to fix. I don't know if a programmatic solution to these warnings could exist: maybe it will always require human interaction. However, it's better to point users in the right direction and not spit out thousands of useless warnings. Attached is a pom which triggers thousands of warnings and a patch with a prettier (and hopefully more useful) output like [WARNING] bcprov-jdk14-138.jar, bcprov-jdk14-1.38.jar define 1292 overlappping classes: [WARNING] - org.bouncycastle.asn1.ocsp.ResponderID [WARNING] - org.bouncycastle.crypto.params.DSAPublicKeyParameters [WARNING] - org.bouncycastle.crypto.engines.DESEngine [WARNING] - org.bouncycastle.jce.provider.JCEElGamalPrivateKey [WARNING] - org.bouncycastle.jce.provider.JCEStreamCipher$Skipjack_CFB8 [WARNING] - org.bouncycastle.jce.provider.JCESecretKeyFactory [WARNING] - org.bouncycastle.i18n.filter.UntrustedInput [WARNING] - org.bouncycastle.asn1.x9.X962NamedCurves$5 [WARNING] - org.bouncycastle.jce.X509KeyUsage [WARNING] maven-shade-plugin has detected that some .class files [WARNING] are present in two or more JARs. When this happens, only [WARNING] one single version of the class is copied in the uberjar. [WARNING] Usually this is not harmful and you can skeep these [WARNING] warnings, otherwise try to manually exclude artifacts [WARNING] based on mvn dependency:tree -Ddetail=true and the above [WARNING] output [WARNING] See http://docs.codehaus.org/display/MAVENUSER/Shade+Plugin -- 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-856) Running single test in Failsafe using CLI does not override includes configuration
[
https://jira.codehaus.org/browse/SUREFIRE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305636#comment-305636
]
Ondrej Zizka commented on SUREFIRE-856:
---
Actually, this behavior is the correct default one, and Surefire should be
fixed to behave like this.
Whether to ignore includes / excludes or not should be optional.
Running single test in Failsafe using CLI does not override includes
configuration
Key: SUREFIRE-856
URL: https://jira.codehaus.org/browse/SUREFIRE-856
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin
Affects Versions: 2.12
Environment: Mac OS X 10.7, Maven 3.0.3, JDK 1.7.0_04-ea
Reporter: David Drake
Priority: Minor
h4. Description
If a single test is specified from using CLI parameters, but the test does
not match the includes pattern for failsafe, then the test will not run.
This is different from the behavior for the surefire plugin, which will run
any test specified using CLI parameters. If the test does match the
includes pattern for failsafe, then it will run.
h4. Reproduction steps
# Create a project with a single test named Sample.java.
# Add the following block to the failsafe configuration:
{code:xml}
includes
include**/Sample.java/include
/includes
{code}
# Run mvn clean verify -Dit.test=Sample from the command line (and verify
that test runs).
# Remove the includes block shown above from the pom.
# Run mvn clean verify -Dit.test=Sample from the command line.
h4. Expected results
Sample test is run, as before, and no other tests are run.
h4. Actual results
No tests are run.
--
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-856) Running single test in Failsafe using CLI does not override includes configuration
[
https://jira.codehaus.org/browse/SUREFIRE-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305637#comment-305637
]
Ondrej Zizka commented on SUREFIRE-856:
---
And why it's correct?
Imagine multiple executions of Surefire with different setups (for complex
testsuites).
Without includes, you'd end up with the single tests running once for each
execution.
With includes, the test will only run in the proper execution.
The use case when you want to run test which is not included should be covered
by aforementioned option to ignore/follow includes.
Running single test in Failsafe using CLI does not override includes
configuration
Key: SUREFIRE-856
URL: https://jira.codehaus.org/browse/SUREFIRE-856
Project: Maven Surefire
Issue Type: Bug
Components: Maven Failsafe Plugin
Affects Versions: 2.12
Environment: Mac OS X 10.7, Maven 3.0.3, JDK 1.7.0_04-ea
Reporter: David Drake
Priority: Minor
h4. Description
If a single test is specified from using CLI parameters, but the test does
not match the includes pattern for failsafe, then the test will not run.
This is different from the behavior for the surefire plugin, which will run
any test specified using CLI parameters. If the test does match the
includes pattern for failsafe, then it will run.
h4. Reproduction steps
# Create a project with a single test named Sample.java.
# Add the following block to the failsafe configuration:
{code:xml}
includes
include**/Sample.java/include
/includes
{code}
# Run mvn clean verify -Dit.test=Sample from the command line (and verify
that test runs).
# Remove the includes block shown above from the pom.
# Run mvn clean verify -Dit.test=Sample from the command line.
h4. Expected results
Sample test is run, as before, and no other tests are run.
h4. Actual results
No tests are run.
--
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-900) System.err seems to be ignored
Marco Brandizi created SUREFIRE-900: --- Summary: System.err seems to be ignored Key: SUREFIRE-900 URL: https://jira.codehaus.org/browse/SUREFIRE-900 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.7.2 Environment: OS/X 10.7.4 Reporter: Marco Brandizi Priority: Minor Attachments: testSureFireStdErr.zip See the attached project. If I send something to System.err from a JUnit test and then I try 'mvn test 2/dev/null', I can still see the output on the console, surefire (or Maven?!) seems to ignore this. I've tried with -Dsurefire.forkMode=false too. Is it possible to redirect the standard error? I'd like to do that because I have a few tests that tests a line command (ie, main()). Since the command is supposed to return XML to the invoker (which, for example, might pipe it to another command), I've implemented this command line by sending all the logging output to System.err (that's possible in Logback via the 'Target' option in the Console appender). When I invoke this line command outside Maven/Surefire it works as I want. In Maven, instead, I cannot what I described. -- 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-758) Documentation incorrect for running single integration test
[ https://jira.codehaus.org/browse/SUREFIRE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305643#comment-305643 ] Lyle Hanson commented on SUREFIRE-758: -- I'm not sure what has changed since I reported the issue, but with Failsafe 2.12 I can no longer reproduce the problem. Single integration tests work as expected with -Dit.test. Documentation incorrect for running single integration test --- Key: SUREFIRE-758 URL: https://jira.codehaus.org/browse/SUREFIRE-758 Project: Maven Surefire Issue Type: Improvement Components: documentation Reporter: Lyle Hanson Priority: Minor The online documentation for Failsafe which describes [Running a Single Test|http://maven.apache.org/plugins/maven-failsafe-plugin/examples/single-test.html] shows: bq.mvn -Dit.test=ITCircle verify The it.test parameter does not seem to work. Rather, the same parameter as Surefire (-Dtest=foo) appears to also work for Failsafe. -- 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-900) System.err seems to be ignored
[ https://jira.codehaus.org/browse/SUREFIRE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-900. --- Resolution: Won't Fix Assignee: Kristian Rosenvold System.out and System.err are captured by surefire, and that is not going to change. You can either use the plugin parameter redirectTestOutputToFile or you can use System.setErr to a stream of your own inside the test; preferably forwarding the output to the original System.err stream System.err seems to be ignored -- Key: SUREFIRE-900 URL: https://jira.codehaus.org/browse/SUREFIRE-900 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.7.2 Environment: OS/X 10.7.4 Reporter: Marco Brandizi Assignee: Kristian Rosenvold Priority: Minor Attachments: testSureFireStdErr.zip See the attached project. If I send something to System.err from a JUnit test and then I try 'mvn test 2/dev/null', I can still see the output on the console, surefire (or Maven?!) seems to ignore this. I've tried with -Dsurefire.forkMode=false too. Is it possible to redirect the standard error? I'd like to do that because I have a few tests that tests a line command (ie, main()). Since the command is supposed to return XML to the invoker (which, for example, might pipe it to another command), I've implemented this command line by sending all the logging output to System.err (that's possible in Logback via the 'Target' option in the Console appender). When I invoke this line command outside Maven/Surefire it works as I want. In Maven, instead, I cannot what I described. -- 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-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305654#comment-305654
]
Ravi Luthra commented on MNG-2971:
--
I'm recommending an alternative syntax for to-be-replaced variables at
install/deploy time. There are now projects that heavily depend on variables
now because of the glitch.
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
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-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-846.
---
Resolution: Fixed
Fix Version/s: 2.12.2
Assignee: Kristian Rosenvold
Fixed in r1369919. The surefire directory is now only left around when maven
is run with the -X option for increased logging. Thanks for the patch!
Maven surefire plugin creates two surefire* directories in the
${project.build.directory}
-
Key: SUREFIRE-846
URL: https://jira.codehaus.org/browse/SUREFIRE-846
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.12
Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
Reporter: Martin Todorov
Assignee: Kristian Rosenvold
Fix For: 2.12.2
Attachments: SUREFIRE-846.patch
Hi,
This is somewhere between a bug and a feature. I am filing it as per
krosenv's suggestion.
The Maven surefire plugin is creating two surefire* directories in the
${project.build.directory}:
- surefire (empty after test executions)
- surefire-reports (containing the output of the tests)
I find this rather annoying. As far as I understand, the surefire directory
is used during the testing and it contains some temporary stuff which is
removed after the execution of the tests.
I have tried looking up the option to remove the surefire directory, but I
can seem to find it. The thing is -- I have other projects that don't have
this empty directory, just the surefire-reports.
This empty directory breaks tab autocomplete in the console which sort of
bugs me, mainly since the directory is empty.
In addition, this is just the test plugin, not the reporting one. There is no
section in the project (not any parent).
This is my surefire plugin setup:
{code}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
version2.12/version
configuration
excludes
exclude**/*Abstr*Test*/exclude
/excludes
/configuration
/plugin
{code}
If this directory is really necessary, I would like to propose the following
options:
1) Make surefire use one directory:
{code}
- surefire
| |- reports
| |- tmp
{code}
This way things will be tidy.
2) Have an option for the plugin which allows you to turn on the preserving
of this directory (I think it should be removed by default).
Regards,
Martin
--
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-898) error with 2.12.1 (works with 2.12)
[
https://jira.codehaus.org/browse/SUREFIRE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-898.
---
Resolution: Not A Bug
Fix Version/s: 2.12.2
Assignee: Kristian Rosenvold
The build problem is being caused by 2 poms containing workaround for a bug
that was fixed.
archiva/archiva-modules/archiva-web/archiva-webapp-test-js/pom.xml
archiva/archiva-modules/archiva-web/archiva-webapp-test/pom.xml
Both should remove the excludedGroups parameters since they are basically
workarounds for a bug that has been fixed. The stacktrace you are seeing is the
correct behaviour
error with 2.12.1 (works with 2.12)
---
Key: SUREFIRE-898
URL: https://jira.codehaus.org/browse/SUREFIRE-898
Project: Maven Surefire
Issue Type: Bug
Reporter: Olivier Lamy
Assignee: Kristian Rosenvold
Fix For: 2.12.2
log
{code}
java.lang.reflect.InvocationTargetException: null
java.lang.reflect.InvocationTargetException
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.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:104)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.lang.RuntimeException: Unable to load category:
foonotatestsurefireissue
at
org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:116)
at
org.apache.maven.surefire.common.junit48.FilterFactory.createGroupFilter(FilterFactory.java:97)
at
org.apache.maven.surefire.junitcore.JUnitCoreProvider.createJUnit48Filter(JUnitCoreProvider.java:183)
at
org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:115)
... 9 more
Caused by: java.lang.ClassNotFoundException: foonotatestsurefireissue
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.apache.maven.surefire.group.match.SingleGroupMatcher.loadGroupClasses(SingleGroupMatcher.java:112)
... 12 more
{code}
Build archiva trunk with -Pit-js
(http://svn.apache.org/repos/asf/archiva/trunk/)
change surefire version in pom.
--
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-758) Documentation incorrect for running single integration test
[ https://jira.codehaus.org/browse/SUREFIRE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-758. --- Resolution: Cannot Reproduce Documentation incorrect for running single integration test --- Key: SUREFIRE-758 URL: https://jira.codehaus.org/browse/SUREFIRE-758 Project: Maven Surefire Issue Type: Improvement Components: documentation Reporter: Lyle Hanson Priority: Minor The online documentation for Failsafe which describes [Running a Single Test|http://maven.apache.org/plugins/maven-failsafe-plugin/examples/single-test.html] shows: bq.mvn -Dit.test=ITCircle verify The it.test parameter does not seem to work. Rather, the same parameter as Surefire (-Dtest=foo) appears to also work for Failsafe. -- 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] (MSHADE-129) outputDirectory do not works together with outputFile
Radim Kolar created MSHADE-129: -- Summary: outputDirectory do not works together with outputFile Key: MSHADE-129 URL: https://jira.codehaus.org/browse/MSHADE-129 Project: Maven 2.x Shade Plugin Issue Type: Improvement Affects Versions: 1.7.1 Reporter: Radim Kolar I would really like to have outputDirectory work with outputFile. Currently it works only with finalName. If this is intended behaviour, then please DOCUMENT IT. -- 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-897) System.exit() in ForkedBooter might hang due to swing/windows bug
[ https://jira.codehaus.org/browse/SUREFIRE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-897. --- Resolution: Fixed Fix Version/s: 2.12.2 Assignee: Kristian Rosenvold Ficed in r1369951, thanks for the patch ! System.exit() in ForkedBooter might hang due to swing/windows bug - Key: SUREFIRE-897 URL: https://jira.codehaus.org/browse/SUREFIRE-897 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.12 Environment: Windows, Java 6,7 Reporter: Ralf Stuckert Assignee: Kristian Rosenvold Fix For: 2.12.2 Attachments: ForkedBooter.patch Due to a bug in Swing on Windows (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7071160) the forked process may not respond to System.exit() in class ForkedBooter after excuting swing tests on windows. This leads to a hanging build, and the only way to resolve it, is to kill the hanging process. After all, sending Runtime.halt() will always stop the process. But since this is not a clean shutdown (e.g. shutdown-hooks not running), this should not be the default behaviour. As a workaround, you could start a daemon thread as a watchdog before calling System.exit(). The deamon sleeps for a certain time, let's say a minute. If it ever resumes from sleeping, it means that the JVM is still running, so the System.exit() was not completed in that time. Now it's time to call Runtime.halt() as a last exit. We used this strategy to overcome the Swing bug (see attached patch). I guess it would be nice, if the timeout would be configurable. -- 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] (MDEP-365) includes/excludes doesn't work anymore with unpack-dependencies 2.5
Olivier Lamy created MDEP-365: - Summary: includes/excludes doesn't work anymore with unpack-dependencies 2.5 Key: MDEP-365 URL: https://jira.codehaus.org/browse/MDEP-365 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: unpack-dependencies Affects Versions: 2.5 Reporter: Olivier Lamy -- 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] (MDEP-365) includes/excludes doesn't work anymore with unpack-dependencies 2.5
[ https://jira.codehaus.org/browse/MDEP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MDEP-365: -- Fix Version/s: 2.5.1 Assignee: Olivier Lamy includes/excludes doesn't work anymore with unpack-dependencies 2.5 --- Key: MDEP-365 URL: https://jira.codehaus.org/browse/MDEP-365 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: unpack-dependencies Affects Versions: 2.5 Reporter: Olivier Lamy Assignee: Olivier Lamy Fix For: 2.5.1 -- 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] (MDEP-365) includes/excludes doesn't work anymore with unpack-dependencies 2.5
[ https://jira.codehaus.org/browse/MDEP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MDEP-365: -- Priority: Blocker (was: Major) includes/excludes doesn't work anymore with unpack-dependencies 2.5 --- Key: MDEP-365 URL: https://jira.codehaus.org/browse/MDEP-365 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: unpack-dependencies Affects Versions: 2.5 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Blocker Fix For: 2.5.1 -- 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-2971) Variables are not replaced into installed pom file
[
https://jira.codehaus.org/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305666#comment-305666
]
abhijith nagarajan commented on MNG-2971:
-
Is there any rationale beyond placing the same pom in the repository instead of
effective pom?
Variables are not replaced into installed pom file
--
Key: MNG-2971
URL: https://jira.codehaus.org/browse/MNG-2971
Project: Maven 2 3
Issue Type: Bug
Components: Deployment, Inheritance and Interpolation
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Assignee: Ralph Goers
Fix For: Issues to be reviewed for 3.x
Attachments: pom.xml
Variables are not replaced into installed pom file.
Here is a sample pom file
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.xxx.root/groupId
artifactIdroot/artifactId
packagingpom/packaging
version${prop.version}/version
nameMy Project/name
...
properties
prop.version3.0.20/prop.version
/properties
/project
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
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] (MDEP-365) includes/excludes doesn't work anymore with unpack-dependencies 2.5
[ https://jira.codehaus.org/browse/MDEP-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MDEP-365. - Resolution: Fixed fixed r1370041 includes/excludes doesn't work anymore with unpack-dependencies 2.5 --- Key: MDEP-365 URL: https://jira.codehaus.org/browse/MDEP-365 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: unpack-dependencies Affects Versions: 2.5 Reporter: Olivier Lamy Assignee: Olivier Lamy Priority: Blocker Fix For: 2.5.1 -- 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:comment-tabpanelfocusedCommentId=305669#comment-305669
]
Gary Clayburg commented on MCHANGES-285:
Ton,
Thank your for attaching this patch. I was able to install the patch and build
the plugin. However, I am getting this new error:
{code}
$ mvn -f pom-changestest.xml changes:jira-report
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.7.1:jira-report (default-cli) @ changes-tests
---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
Aug 6, 2012 6:29:48 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[ERROR] Unable to extract a JIRA pid from the page at the url
https://urlremoved.jira.com/browse/OIAM
[ERROR] Error accessing https://urlremoved.jira.com/browse/OIAM
java.lang.RuntimeException: The issue management URL in the POM does not
include a pid, and it was not possible to extract it from the page at that URL.
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:230)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:144)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:354)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:187)
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:319)
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)
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
{code}
This is the slimmed down pom file I am using:
{code}
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.urlremoved/groupId
artifactIdchanges-tests/artifactId
packagingjar/packaging
namechanges-tests/name
version1.22/version
issueManagement
systemJIRA/system
urlhttps://urlremoved.jira.com/browse/OIAM/url
/issueManagement
build
finalNamechanges-tests/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changes-plugin/artifactId
version2.7.1/version
[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=305669#comment-305669
]
Gary Clayburg edited comment on MCHANGES-285 at 8/6/12 7:40 PM:
Ton,
Thank your for attaching this patch. I was able to install the patch and build
the plugin. However, I am getting this new error:
{code}
$ mvn -f pom-changestest.xml changes:jira-report
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building changes-tests 1.22
[INFO]
[INFO]
[INFO] --- maven-changes-plugin:2.7.1:jira-report (default-cli) @ changes-tests
---
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance
and no SinkFactory available. Please update this plugin.
Aug 6, 2012 6:29:48 PM org.apache.commons.httpclient.HttpMethodBase
getResponseBody
WARNING: Going to buffer response body of large or unknown size. Using
getResponseBodyAsStream instead is recommended.
[ERROR] Unable to extract a JIRA pid from the page at the url
https://urlremoved.jira.com/browse/OIAM
[ERROR] Error accessing https://urlremoved.jira.com/browse/OIAM
java.lang.RuntimeException: The issue management URL in the POM does not
include a pid, and it was not possible to extract it from the page at that URL.
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.getParameterBasedQueryURL(AbstractJiraDownloader.java:230)
at
org.apache.maven.plugin.jira.AbstractJiraDownloader.doExecute(AbstractJiraDownloader.java:144)
at
org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:354)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
at
org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:187)
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:319)
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)
[WARNING]
org.apache.maven.plugin.MojoExecutionException: Failed to parse JIRA XML.
at org.apache.maven.plugin.jira.JiraXML.parse(JiraXML.java:132)
{code}
This is the slimmed down pom file I am using:
{code}
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.urlremoved/groupId
artifactIdchanges-tests/artifactId
packagingjar/packaging
namechanges-tests/name
version1.22/version
issueManagement
systemJIRA/system
urlhttps://urlremoved.jira.com/browse/OIAM/url
/issueManagement
build
finalNamechanges-tests/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
[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 ] Jamie Duncombe updated MCHANGES-285: Attachment: patch-2.7.x.txt Hi Gary, The error you are seeing is because you have applied the patch to the 2.7.1 tag source code (there have been changes in the trunk to how the annotations are specified which are not backward compatible with the 2.7.1 codebase). I'm attaching a slight variation of the patch to fix this issue. It will also update the pom to build a 2.7.2 version of the pom so you should update your client project to match this. Let me know if you run into any problems, Jamie 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
[jira] (SUREFIRE-897) System.exit() in ForkedBooter might hang due to swing/windows bug
[ https://jira.codehaus.org/browse/SUREFIRE-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305661#comment-305661 ] Kristian Rosenvold edited comment on SUREFIRE-897 at 8/7/12 12:35 AM: -- Fixed in r1369951, thanks for the patch ! was (Author: krosenvold): Ficed in r1369951, thanks for the patch ! System.exit() in ForkedBooter might hang due to swing/windows bug - Key: SUREFIRE-897 URL: https://jira.codehaus.org/browse/SUREFIRE-897 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.12 Environment: Windows, Java 6,7 Reporter: Ralf Stuckert Assignee: Kristian Rosenvold Fix For: 2.12.2 Attachments: ForkedBooter.patch Due to a bug in Swing on Windows (see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7071160) the forked process may not respond to System.exit() in class ForkedBooter after excuting swing tests on windows. This leads to a hanging build, and the only way to resolve it, is to kill the hanging process. After all, sending Runtime.halt() will always stop the process. But since this is not a clean shutdown (e.g. shutdown-hooks not running), this should not be the default behaviour. As a workaround, you could start a daemon thread as a watchdog before calling System.exit(). The deamon sleeps for a certain time, let's say a minute. If it ever resumes from sleeping, it means that the JVM is still running, so the System.exit() was not completed in that time. Now it's time to call Runtime.halt() as a last exit. We used this strategy to overcome the Swing bug (see attached patch). I guess it would be nice, if the timeout would be configurable. -- 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-895) TestNG reporter options cannot be setup using the Maven Surefire Plugin
[ https://jira.codehaus.org/browse/SUREFIRE-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-895: Component/s: (was: Maven Surefire Plugin) TestNG reporter options cannot be setup using the Maven Surefire Plugin --- Key: SUREFIRE-895 URL: https://jira.codehaus.org/browse/SUREFIRE-895 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Reporter: Bimal TestNG reporter options cannot be setup using the Maven Surefire Plugin As per the TestNG (http://testng.org/doc/documentation-main.html#logging-reporters) Following options can be setup using Ant only outputDirectory timestampFormat fileFragmentationLevel splitClassAndPackageNames generateGroupsAttribute generateTestResultAttributes stackTraceOutputMethod generateDependsOnMethods generateDependsOnGroups In my project I'm using Maven. This cannot be achieved with Maven Surefire Plugin. Please Add this feature to Maven Surefire Plugin. -- 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-895) TestNG reporter options cannot be setup using the Maven Surefire Plugin
[ https://jira.codehaus.org/browse/SUREFIRE-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-895: Component/s: TestNG support TestNG reporter options cannot be setup using the Maven Surefire Plugin --- Key: SUREFIRE-895 URL: https://jira.codehaus.org/browse/SUREFIRE-895 Project: Maven Surefire Issue Type: Improvement Components: TestNG support Reporter: Bimal TestNG reporter options cannot be setup using the Maven Surefire Plugin As per the TestNG (http://testng.org/doc/documentation-main.html#logging-reporters) Following options can be setup using Ant only outputDirectory timestampFormat fileFragmentationLevel splitClassAndPackageNames generateGroupsAttribute generateTestResultAttributes stackTraceOutputMethod generateDependsOnMethods generateDependsOnGroups In my project I'm using Maven. This cannot be achieved with Maven Surefire Plugin. Please Add this feature to Maven Surefire Plugin. -- 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
