http://blog.gmane.org/gmane.comp.apache.maven.issues hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.apache.maven.issues/37708 <pre>Hi ALL: I write some unicode configuration to .properties files.But when i use command "maven package -P product" to generae corresponding configuration file,maven will decode these unicode configurations.for example:profile: test.configuration=${test.configuration}product properties file: test.configuration=\u516c\u6c11\u8eab\u4efd\u53f7\u7801 after run "maven package -P product",test.congiguration=aaabut i want to keep the origin propertie: test.configuration=\u516c\u6c11\u8eab\u4efd\u53f7\u7801 how can i do?thank u! </pre> 芸 郭 2013-04-25T10:57:04 http://comments.gmane.org/gmane.comp.apache.maven.issues/37668 <pre>Hello Maven Team, may be i am missing something or i just have covered a bug. I am facing problems with the maven-javadoc-plugin. This is probably related to the ticket found here http://jira.codehaus.org/browse/MJAVADOC-259 I have created a SSCCE according the information given of the plugin examples. The url to the example i am refering to: http://maven.apache.org/plugins/maven-javadoc-plugin/examples/javadoc-resources.html But as stated here, the example may be wrong. http://www.mail-archive.com/issues-3+t1Dttqs2kyzMRdD/IqWQ&lt; at &gt;public.gmane.org/msg55395.html The problem is that the files located in src\main\javadoc\org\apache\myapp\doc-files are not copied to the target\site\apidocs\org\apache\myapp\doc-files location, although the pom specifies to do so! The archive attached should provide the complete project with pom and sources to reproduce the behavior. Thanks in advance, sincerly Isaias Bartelborth </pre> Isaias Bartelborth 2013-04-19T14:25:15 http://comments.gmane.org/gmane.comp.apache.maven.issues/36723 <pre>Henning Schmiedehausen created MSHARED-276: ---------------------------------------------- Summary: analyzer ignores project directories in a multi-module build Key: MSHARED-276 URL: https://jira.codehaus.org/browse/MSHARED-276 Project: Maven Shared Components Issue Type: Bug Components: maven-dependency-analyzer Affects Versions: maven-dependency-analyzer-1.3, maven-dependency-analyzer-1.2 Reporter: Henning Schmiedehausen Attachments: DEP-399.patch The dependency analyzer had a patch for DEP-72 applied a long time ago which in turn makes it ignore the local folders for a multimodule build. This change restores this behavior. -- 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 </pre> Henning Schmiedehausen (JIRA 2013-02-23T02:28:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36712 <pre>David Matejcek created MNG-5439: ----------------------------------- Summary: Resolved 1.02 when declared [1.2.0] Key: MNG-5439 URL: https://jira.codehaus.org/browse/MNG-5439 Project: Maven 2 &amp; 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4, 3.0.3 Environment: Linux Reporter: David Matejcek Priority: Trivial I have following versions in Archiva, artifact type is ear: ... &lt;version&gt;1.2.0&lt;/version&gt; &lt;version&gt;1.02&lt;/version&gt; &lt;version&gt;1.2.1-SNAPSHOT&lt;/version&gt; ... The Installer's pom have dependency on this artifact: &lt;version&gt;[1.2.0]&lt;/version&gt; But Maven 3.0.4 (same with 3.0.3) downloads a very old version 1.02 instead of 1.2.0. When I change the dependency to &lt;version&gt;1.2.0&lt;/version&gt;, Maven downloads the correct version of artifact 1.2.0. I think maven resolves [1.2.0] as a range, parses it as numbers and numerically 1.2.0 might be considered the sam</pre> David Matejcek (JIRA 2013-02-22T19:38:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36710 <pre>Tom Snee created MRELEASE-825: --------------------------------- Summary: updateWorkingCopyVersions=false does not change tagged POMs to release version Key: MRELEASE-825 URL: https://jira.codehaus.org/browse/MRELEASE-825 Project: Maven 2.x Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.3 Reporter: Tom Snee Assignee: Robert Scholte Fix For: 2.3.2 The flag updateWorkingCopyVersions (more specifically with value "false") is not handled correctly. Attached project is a simple Maven project with version 1.0-SNAPSHOT, depending on version 2.3 of the release plugin. It is configured with dryRun=true and updateWorkingCopyVersions=false. When running mvn:prepare (and accepting the versions that are proposed), you'll see that pom.xml.next file contains 1.1-SNAPSHOT (the next development version) instead of 1.0 (the tagged version). -- This message is automatically gen</pre> Tom Snee (JIRA 2013-02-22T19:15:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36709 <pre>Henning Schmiedehausen created MDEP-403: ------------------------------------------- Summary: add a "skip" configuration option to the dependency plugin Key: MDEP-403 URL: https://jira.codehaus.org/browse/MDEP-403 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: analyze Affects Versions: 2.6 Reporter: Henning Schmiedehausen Attachments: maven-dependency-plugin-skip.patch Most of the maven plugins have a skip configuration option that allows skipping the execution. The dependency plugin has not. This patch adds this configuration property. -- 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 </pre> Henning Schmiedehausen (JIRA 2013-02-22T18:53:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36707 <pre>Manuel Blechschmidt created DOXIA-483: ----------------------------------------- Summary: (SwfMacro) org.apache.maven.plugins:maven-site-plugin:3.2:site: org.apache.maven.doxia.module.apt.AptParser cannot be cast to java.lang.String Key: DOXIA-483 URL: https://jira.codehaus.org/browse/DOXIA-483 Project: Maven Doxia Issue Type: Bug Components: Core Affects Versions: 1.3 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /usr/share/maven Java version: 1.6.0_41, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" Reporter: Manuel Blechschmidt Attachments: DOXIA-SWF-BUG.patch, DOXIA-SWF-BUG.tgz, Screen Shot 2013-02-22 at 17.56.12.png # Download the attached tgz file # Open a console # Enter "tar xzf DOXIA</pre> Manuel Blechschmidt (JIRA 2013-02-22T17:07:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36703 <pre>Lukasz Strzelecki created MCHECKSTYLE-187: --------------------------------------------- Summary: Enable checkstyle for all files in project Key: MCHECKSTYLE-187 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-187 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.9.1 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Java version: 1.6.0_33, vendor: Sun Microsystems Inc. OS name: "linux", version: "3.2.0-36-generic", arch: "amd64", family: "unix" Reporter: Lukasz Strzelecki When I have module configured as war (packaging war). Checkstyle plugin should check for all file in project i.e. * /src/main/java * /src/main/resources * /src/main/webapp when includeTestSourceDirectory is enabled, chekckstyle plugin should add more paths like: * /src/test/java * /src/test/resources * /src/test/webapp -- This message is automatically generated by JIRA. If you think it was </pre> Lukasz Strzelecki (JIRA 2013-02-22T13:56:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36701 <pre>Steve Loughran created SUREFIRE-966: --------------------------------------- Summary: Add ability to set a default timeout on all JUnit4 tests that don't set one explicitly Key: SUREFIRE-966 URL: https://jira.codehaus.org/browse/SUREFIRE-966 Project: Maven Surefire Issue Type: Improvement Components: Junit 4.x support Affects Versions: 2.13 Reporter: Steve Loughran Priority: Minor add ability to set a default timeout on for JUnit4 tests that don't set one in their attributes -- 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 </pre> Steve Loughran (JIRA 2013-02-22T11:22:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36699 <pre>Odin Hole Standal created SUREFIRE-965: ------------------------------------------ Summary: Changed behaviour for Maven properties from surefire 2.12.4 to 2.13 Key: SUREFIRE-965 URL: https://jira.codehaus.org/browse/SUREFIRE-965 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.13 Environment: Maven 3.0.4 JDK 1.7.0_10 Windows Reporter: Odin Hole Standal Priority: Minor We just upgraded Surefire from 2.12.4 to 2.13 and witnessed a change in behaviour with respect to system properties defined in Maven profiles. Our build is a multi-module one with a nested structure. In our parent project, we define profiles that set a system property to either 'A' or 'B'. Our tests rely on this system property being set to either 'A' or 'B' across all tests in all modules. However, when we upgraded to 2.13 and ran tests with profile 'A', suddenly one of the modul</pre> Odin Hole Standal (JIRA 2013-02-22T09:39:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36696 <pre>Olivier Lamy created MSKINS-78: ---------------------------------- Summary: Do not generate line with doxia timestamp Key: MSKINS-78 URL: https://jira.codehaus.org/browse/MSKINS-78 Project: Maven Skins Issue Type: Bug Components: Fluido Skin Affects Versions: fluido-1.3.0 Reporter: Olivier Lamy generated html contains: Generated by Apache Maven Doxia at Feb 8, 2013 Make this off per default and add an option to generate 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 </pre> Olivier Lamy (JIRA 2013-02-22T08:27:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36686 <pre>Michael Koch created MSKINS-77: ---------------------------------- Summary: Add Github ribbon for maven-skins to fluido site Key: MSKINS-77 URL: https://jira.codehaus.org/browse/MSKINS-77 Project: Maven Skins Issue Type: Improvement Components: Fluido Skin Reporter: Michael Koch Priority: Minor The maven-skins scm report shows the svn repository location. However, there is also a mirror on Github at http://github.com/apache/maven-skins/. Since maven-fluido-skin supports adding a Github ribbon, one pointing to maven-skins could be added to the maven-fluido-skin site itself. (I didn't find out about the Github mirror until after messing with git svn for preparing my last patches.) -- 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 JIR</pre> Michael Koch (JIRA 2013-02-21T21:00:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36682 <pre>Josh Unger created SUREFIRE-964: ----------------------------------- Summary: TEST-*.xml files generated by Surefire throw validation warnings in Eclipse for no grammer constraints (DTD or XML schema) referenced in the document Key: SUREFIRE-964 URL: https://jira.codehaus.org/browse/SUREFIRE-964 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin Affects Versions: 2.13 Environment: Any OS, Eclipse Juno with m2e and m2e-wtp. Reporter: Josh Unger 1. Create a Maven project in Eclipse. 2. Add a single class and a single test method decorated with &lt; at &gt;Test. {code} import org.junit.Test; public class ATest { &lt; at &gt;Test public void test() { } } {code} 3. Add the necessary information to the POM - {code} &lt;build&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-surefire-plugin&lt;/artifactId&gt; &lt;versio</pre> Josh Unger (JIRA 2013-02-21T18:37:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36681 <pre>Sarah Haselbauer created MNG-5438: ------------------------------------- Summary: cli parameter to use a custom path settings-security.xml Key: MNG-5438 URL: https://jira.codehaus.org/browse/MNG-5438 Project: Maven 2 &amp; 3 Issue Type: New Feature Components: Command Line Affects Versions: 3.0.4, 3.0.5 Reporter: Sarah Haselbauer Attachments: apache-maven-3.0.4-ssec-bin.zip, maven-3.0.4-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch, maven-latest-0001-added-ssec-as-cli-param-so-that-you-have-the-same-fl.patch added -ssec as cli param, so that you have the same flexibility to place your settings-security.xml as you have to point to a custom settings.xml file mvn -s /path/to/my/custom/settings.xml -ssec /path/to/my/custom/settings-security.xml I attached to patches: one that can be run on the maven-3.0.4 tag and one that can be run on trunk (latest code state of today). I also attached a ma</pre> Sarah Haselbauer (JIRA 2013-02-21T18:32:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36676 <pre>Christofer Dutz created MRELEASE-824: ---------------------------------------- Summary: Allow update of artifact-versions of dependencies that are currently not in the maven reactor Key: MRELEASE-824 URL: https://jira.codehaus.org/browse/MRELEASE-824 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: prepare Affects Versions: 2.4 Reporter: Christofer Dutz Priority: Minor Attachments: release-prepare.patch Currently when using the default way to restrict the reactor projects processed by maven (using the --projects parameter), only the versions of artifacts currently in the reactor are updated, even if more version-data is passed in. Attachted patch allows a user to provide versions for all modules of a maven project, and to update only some of these. The patch shouldn't break anything, but it would allow to use the release plugin in special release-strategies that might </pre> Christofer Dutz (JIRA 2013-02-21T10:26:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36664 <pre>John Casey created MDEP-402: ------------------------------- Summary: Allow resolve-plugins to exclude plugins in the current reactor Key: MDEP-402 URL: https://jira.codehaus.org/browse/MDEP-402 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: resolve-plugins Affects Versions: 2.6 Reporter: John Casey plugins that are built and then used all in the same build should not be in the list of plugins to be resolved during the resolve-plugins mojo run. We need a new parameter excludeReactor to allow exclusion of these plugins. -- 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 </pre> John Casey (JIRA 2013-02-20T18:04:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36662 <pre>John Casey created MDEP-401: ------------------------------- Summary: Support include/exclude of artifactId/groupId in resolve-plugins Key: MDEP-401 URL: https://jira.codehaus.org/browse/MDEP-401 Project: Maven 2.x Dependency Plugin Issue Type: Bug Components: resolve-plugins Affects Versions: 2.6 Reporter: John Casey exclude* and include* (for dealing with artifact coordinates) are mentioned in the docs for resolve-plugins, but only because they're present as parameters in an abstract superclass. It would be very useful to actually support these in the resolve-plugins mojo's functionality. -- 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 </pre> John Casey (JIRA 2013-02-20T18:02:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36660 <pre>Jesse Glick created MNG-5437: -------------------------------- Summary: Do not load plugins from snapshot JARs Key: MNG-5437 URL: https://jira.codehaus.org/browse/MNG-5437 Project: Maven 2 &amp; 3 Issue Type: Bug Components: Class Loading Affects Versions: 3.0.4 Environment: Solaris 10, JDK 1.7.0 Reporter: Jesse Glick Priority: Minor See [mailing list discussion|http://mail-archives.apache.org/mod_mbox/www-builds/201302.mbox/browser] for background. When a reactor build creates a plugin JAR and then loads classes from it, a JVM crash is a possibility: {code:none} [INFO] Installing /export/home/hudson/hudson-slave/workspace/sis-jdk7/sis-build-helper/target/sis-build-helper-0.3-jdk7-SNAPSHOT.jar to /export/home/hudson/hudson-slave/maven-repositories/0/org/apache/sis/sis-build-helper/0.3-jdk7-SNAPSHOT/sis-build-helper-0.3-jdk7-SNAPSHOT.jar ...moving on to another project in the reactor... [INFO] </pre> Jesse Glick (JIRA 2013-02-20T15:20:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36658 <pre>Nicolas Delsaux created MNG-5436: ------------------------------------ Summary: Up to Maven 3.0.4, there can be only one ExecutionListener Key: MNG-5436 URL: https://jira.codehaus.org/browse/MNG-5436 Project: Maven 2 &amp; 3 Issue Type: Improvement Affects Versions: 3.0.4 Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files (x86)\Maven-3.0.4\bin\.. Java version: 1.6.0_30, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_30\jre Default locale: fr_FR, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" Reporter: Nicolas Delsaux I'm working on a maven growl extension (https://github.com/Riduidel/maven-growl-plugin) that should send growl notification based upon project lifecycle. Typical use case is to receive a growl notification when build is over. According to discussion with olamy, there currently can b</pre> Nicolas Delsaux (JIRA 2013-02-20T13:50:13 http://comments.gmane.org/gmane.comp.apache.maven.issues/36653 <pre>Alex Halovanic created MCHANGES-304: --------------------------------------- Summary: Include an HTML announcement template Key: MCHANGES-304 URL: https://jira.codehaus.org/browse/MCHANGES-304 Project: Maven 2.x Changes Plugin Issue Type: Improvement Components: announcement Reporter: Alex Halovanic Priority: Trivial Attachments: announcement_html.vm I'm pretty sure this has been brought up before, but is there interest in including an HTML version of the announcement email velocity template as an alternative to the default plaintext one? I've attached the one I've been using for a year or two here. It's my best attempt to emulate the appearance of the project report page with velocity. For others like me, it would eliminate having to unpack another dependency to make the email look more like the report page. -- This message is automatically generated by JIRA. If you think it was sent incorr</pre> Alex Halovanic (JIRA 2013-02-20T03:07:14 http://comments.gmane.org/gmane.comp.apache.maven.issues/36650 <pre>Kirk Rasmussen created MNG-5435: ----------------------------------- Summary: Project which has shared dependency with a plugin fails to recognize artifact was downloaded and fails. Key: MNG-5435 URL: https://jira.codehaus.org/browse/MNG-5435 Project: Maven 2 &amp; 3 Issue Type: Bug Components: Artifacts and Repositories, Dependencies Affects Versions: 3.0.4 Reporter: Kirk Rasmussen Priority: Blocker Attachments: maven2.log, maven.log, pom.xml, settings.xml, simple.zip This is a twofer bug report :) Issue #1: I have included a stripped down version of an example using the maven antrun plugin to spawn the Antlr tool. For technical reasons we cannot use the native maven Antlr plugin. If you look at the attached project you will see that Antlr is a dependency of both the antrun plugin: {code} ... &lt;build&gt; &lt;plugins&gt; &lt;plugin&gt; &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt; &lt;artifa</pre> Kirk Rasmussen (JIRA 2013-02-19T22:15:13 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.apache.maven.issues