[jira] Created: (MNG-4888) Enforcer 1.1-SNAPSHOT uses wrong maven-parent
Enforcer 1.1-SNAPSHOT uses wrong maven-parent - Key: MNG-4888 URL: http://jira.codehaus.org/browse/MNG-4888 Project: Maven 2 3 Issue Type: Bug Components: General Reporter: Matthias Weßendorf The enforcer's trunk pom.xml: https://svn.apache.org/repos/asf/maven/enforcer/trunk/pom.xml is linked against maven-parent 17. I don't see the 17 'release'. Examples: https://repository.apache.org/content/repositories/releases/org/apache/maven/maven-parent/ https://repository.apache.org/content/repositories/public/org/apache/maven/maven-parent/ http://repo2.maven.org/maven2/org/apache/maven/maven-parent/ However, there is only 17-SNAPSHOT: https://repository.apache.org/content/groups/snapshots/org/apache/maven/maven-parent/ FWIW, it's trunk, however, is labeled as 18-SNAPSHOT: https://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml Looks like the 17 is missing... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4888) Enforcer 1.1-SNAPSHOT uses wrong maven-parent
[ http://jira.codehaus.org/browse/MNG-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242199#action_242199 ] Anders Hammar commented on MNG-4888: maven-parent 17 is being voted for and should be released very soon. Here's the vote on the dev list: http://maven.40175.n5.nabble.com/vote-release-maven-parent-17-td3245817.html#a3245817 Enforcer 1.1-SNAPSHOT uses wrong maven-parent - Key: MNG-4888 URL: http://jira.codehaus.org/browse/MNG-4888 Project: Maven 2 3 Issue Type: Bug Components: General Reporter: Matthias Weßendorf The enforcer's trunk pom.xml: https://svn.apache.org/repos/asf/maven/enforcer/trunk/pom.xml is linked against maven-parent 17. I don't see the 17 'release'. Examples: https://repository.apache.org/content/repositories/releases/org/apache/maven/maven-parent/ https://repository.apache.org/content/repositories/public/org/apache/maven/maven-parent/ http://repo2.maven.org/maven2/org/apache/maven/maven-parent/ However, there is only 17-SNAPSHOT: https://repository.apache.org/content/groups/snapshots/org/apache/maven/maven-parent/ FWIW, it's trunk, however, is labeled as 18-SNAPSHOT: https://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml Looks like the 17 is missing... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MENFORCER-110) Enforcer 1.1-SNAPSHOT uses wrong maven-parent
[ http://jira.codehaus.org/browse/MENFORCER-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann moved MNG-4888 to MENFORCER-110: -- Complexity: (was: Intermediate) Component/s: (was: General) Key: MENFORCER-110 (was: MNG-4888) Project: Maven 2.x Enforcer Plugin (was: Maven 2 3) Enforcer 1.1-SNAPSHOT uses wrong maven-parent - Key: MENFORCER-110 URL: http://jira.codehaus.org/browse/MENFORCER-110 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Reporter: Matthias Weßendorf The enforcer's trunk pom.xml: https://svn.apache.org/repos/asf/maven/enforcer/trunk/pom.xml is linked against maven-parent 17. I don't see the 17 'release'. Examples: https://repository.apache.org/content/repositories/releases/org/apache/maven/maven-parent/ https://repository.apache.org/content/repositories/public/org/apache/maven/maven-parent/ http://repo2.maven.org/maven2/org/apache/maven/maven-parent/ However, there is only 17-SNAPSHOT: https://repository.apache.org/content/groups/snapshots/org/apache/maven/maven-parent/ FWIW, it's trunk, however, is labeled as 18-SNAPSHOT: https://svn.apache.org/repos/asf/maven/pom/trunk/maven/pom.xml Looks like the 17 is missing... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-132) Upgrade to Checkstyle 5.1
[ http://jira.codehaus.org/browse/MCHECKSTYLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242205#action_242205 ] Paul Nyheim commented on MCHECKSTYLE-132: - Indeed 5.1 seems to be missing, but current version is 5.3, and please note that in version 5.2 they changed groupId from checkstyle to com.puppycrawl.tools, as noted in the [Release Notes|http://checkstyle.sourceforge.net/releasenotes.html] Both 5.2 and 5.3 are present in central repo: [https://repository.sonatype.org/index.html#nexus-search;quick~checkstyle] Upgrade to Checkstyle 5.1 - Key: MCHECKSTYLE-132 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-132 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Reporter: Simon Brandhof [Release notes|http://checkstyle.sourceforge.net/releasenotes.html] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCHECKSTYLE-132) Upgrade to Checkstyle 5.1
[ http://jira.codehaus.org/browse/MCHECKSTYLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Nyheim updated MCHECKSTYLE-132: Attachment: checkstyle-5.3.patch patch against v2.6 in svn All tests run green. Upgrade to Checkstyle 5.1 - Key: MCHECKSTYLE-132 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-132 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Reporter: Simon Brandhof Attachments: checkstyle-5.3.patch [Release notes|http://checkstyle.sourceforge.net/releasenotes.html] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MCHECKSTYLE-132) Upgrade to Checkstyle 5.1
[ http://jira.codehaus.org/browse/MCHECKSTYLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242206#action_242206 ] Paul Nyheim edited comment on MCHECKSTYLE-132 at 11/5/10 6:41 AM: -- patch against v2.6 in svn -All tests run green.- _oops_ Forgot to run mvn clean test, so there are currently 7 failures. I'll have a quick look and see if I can fix them quickly... was (Author: pnyheim): patch against v2.6 in svn All tests run green. Upgrade to Checkstyle 5.1 - Key: MCHECKSTYLE-132 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-132 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Reporter: Simon Brandhof Attachments: checkstyle-5.3.patch [Release notes|http://checkstyle.sourceforge.net/releasenotes.html] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-657) Surefire silently fails when argLine contains tabs or newlines
Surefire silently fails when argLine contains tabs or newlines -- Key: SUREFIRE-657 URL: http://jira.codehaus.org/browse/SUREFIRE-657 Project: Maven Surefire Issue Type: Bug Components: process forking Affects Versions: 2.6 Reporter: Axel Fontaine Surefire will silently fail without executing any tests if the argLine for the forked process contains tabs \t or newlines \n. This commonly occurs when the argLine is long, and an IDE feels the need to break up the line while reformating the xml. A solution could be to replace \t and \n with a space. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHECKSTYLE-132) Upgrade to Checkstyle 5.1
[
http://jira.codehaus.org/browse/MCHECKSTYLE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242223#action_242223
]
Paul Nyheim commented on MCHECKSTYLE-132:
-
Did not have time to actually fix them now, but managed to track down the error.
The tests that fail are related to this change in Checkstyle 5.3 (all tests run
fine with 5.2)
[changeset:DefaultConfiguration.java|http://checkstyle.hg.sourceforge.net/hgweb/checkstyle/checkstyle/diff/917266ff93a4/src/checkstyle/com/puppycrawl/tools/checkstyle/DefaultConfiguration.java]
As far as I can find out, cacheFile is specified in both min-plugin-config.xml
and in sun_checks.xml (with substitution property), and this creates problems
due to the previous mentioned change, where the absolute path would be added to
the property with a comma to separate them. This obviously fails when trying to
create the file...
So the bottom line is that so long that you do not specify e.g. {{cacheFile}}
several times in your config, you should be all clear.
I am not sure whether this is in fact a bug with 5.3, or if it is a result of
maven-checkstyle-plugin using the Checkstyle API in the wrong way.
Upgrade to Checkstyle 5.1
-
Key: MCHECKSTYLE-132
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-132
Project: Maven 2.x Checkstyle Plugin
Issue Type: Improvement
Reporter: Simon Brandhof
Attachments: checkstyle-5.3.patch
[Release notes|http://checkstyle.sourceforge.net/releasenotes.html]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MDEP-262) Add support for custom ProjectDependencyAnalyzer implementations
[ http://jira.codehaus.org/browse/MDEP-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-262. -- Resolution: Fixed Fix Version/s: 2.2 Add support for custom ProjectDependencyAnalyzer implementations Key: MDEP-262 URL: http://jira.codehaus.org/browse/MDEP-262 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: analyze Reporter: Tobias Gierke Assignee: Brian Fox Fix For: 2.2 Attachments: maven-dependency-analyzer_1.2.patch, maven-dependency-analyzer_1.2.patch, maven-dependency-plugin_2.2.patch, maven-dependency-plugin_2.2.patch I've written a customized ProjectDependencyAnalyzer (includes dependencies from Spring XMLs) that I'd like to be able to use with the maven-dependency-plugin. The current plugin implementation only supports a single ProjectDependencyAnalyzer component on the classpath (otherwise plexus will fail) and has no way of specifying which analyzer to use at runtime. The appended patches add support for custom ProjectDependencyAnalyzer components to the plugin. The basic idea is to assign ProjectDependencyAnalyzer components a unique role-hint and let the plugin dynamically look-up the implementation to use by specifying the role-hint as configuration parameter. 1. maven-dependency-analyzer_1.2.patch Patch against maven-dependency-analyzer 1.2-SNAPSHOT (trunk / r942613) To apply patch: patch -p1 maven-dependency-analyzer_1.2.patch CHANGES: - DefaultProjectDependencyAnalyzer component now has an additonal role-hint 'default' so plexus won't complain when multiple ProjectDependencyAnalyzer components are one the classpath - changes the visibility of buildDependencyClasses() and findArtifactForClassName() from private to protected to allow subclassing - buildDependencyClasses() now takes the artifact map as additional parameter so subclasses can call findArtifactForClassName() with it 2. maven-dependency-plugin_2.2.patch Patch against maven-dependency-plugin 2.2-SNAPSHOT (trunk / r942613) To apply patch: patch -p1 maven-dependency-plugin_2.2.patch CHANGES: - AbstractDependencyMojo now has a new 'analyzer' parameter that is the role hint to use when looking up the ProjectDependencyAnalyzer from the container ( the default value is set to 'default' and thus references DefaultProjectDependencyAnalyzer) - AbstractDependencyMojo now implements Contextualizable and dynamically looks up the ProjectDependencyAnalyzer component to use from the plexus container - Integration test added that first buids and installs a custom dummy ProjectDependencyAnalyzer component and then runs dependency:analyze with this analyzer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-658) Excessive synchronization in ReporterManager blocks performance
Excessive synchronization in ReporterManager blocks performance --- Key: SUREFIRE-658 URL: http://jira.codehaus.org/browse/SUREFIRE-658 Project: Maven Surefire Issue Type: Improvement Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin, TestNG support, xml generation Affects Versions: 2.6 Reporter: Kristian Rosenvold Priority: Minor All the methods in ReporterManager are synchronized, effectively making this whole subsystem a blocker in terms of performance. Single threaded providers wast time acquiring the lock, parallel providers have a choke point blocking parallelism. Since this block guards all the file writing of reports, it effectively reduces performance quite a lot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (SUREFIRE-658) Excessive synchronization in ReporterManager blocks performance
[ http://jira.codehaus.org/browse/SUREFIRE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SUREFIRE-658 started by Kristian Rosenvold. Excessive synchronization in ReporterManager blocks performance --- Key: SUREFIRE-658 URL: http://jira.codehaus.org/browse/SUREFIRE-658 Project: Maven Surefire Issue Type: Improvement Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin, TestNG support, xml generation Affects Versions: 2.6 Reporter: Kristian Rosenvold Assignee: Kristian Rosenvold Priority: Minor All the methods in ReporterManager are synchronized, effectively making this whole subsystem a blocker in terms of performance. Single threaded providers wast time acquiring the lock, parallel providers have a choke point blocking parallelism. Since this block guards all the file writing of reports, it effectively reduces performance quite a lot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (SUREFIRE-658) Excessive synchronization in ReporterManager blocks performance
[ http://jira.codehaus.org/browse/SUREFIRE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-658. --- Resolution: Fixed Fix Version/s: 2.7 Fixed in r1031678 Excessive synchronization in ReporterManager blocks performance --- Key: SUREFIRE-658 URL: http://jira.codehaus.org/browse/SUREFIRE-658 Project: Maven Surefire Issue Type: Improvement Components: JUnit 3.x support, Junit 4.7+ (parallel) support, Junit 4.x support, Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin, TestNG support, xml generation Affects Versions: 2.6 Reporter: Kristian Rosenvold Assignee: Kristian Rosenvold Priority: Minor Fix For: 2.7 All the methods in ReporterManager are synchronized, effectively making this whole subsystem a blocker in terms of performance. Single threaded providers wast time acquiring the lock, parallel providers have a choke point blocking parallelism. Since this block guards all the file writing of reports, it effectively reduces performance quite a lot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SUREFIRE-659) Maven PDF plugin:showSuccess=false creates empty table causing error
Maven PDF plugin:showSuccess=false creates empty table causing error Key: SUREFIRE-659 URL: http://jira.codehaus.org/browse/SUREFIRE-659 Project: Maven Surefire Issue Type: Bug Affects Versions: 2.6 Environment: maven 2.2.1, surefire 2.6, maven-pdf-plugin Reporter: Darren Hartford The problem is that for showSuccess=false an empty table is written but fo expects some tableRows even if they are empty. Cheers, -Lukas Darren Hartford wrote: Hey all, Not sure where to put this issue, but using the surefire-report(2.6) with showSuccess=false, with the maven-pdf-plugin (1.1) breaks. This is using a multi-module/aggregate report approach, maven 2.2.1. With showSuccess=true, everything works fine. Basic intent is to, on a release, create an aggregate/summary PDF of the release, but some of the items. such as the surefire-report, are too verbose. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-report-plugin/artifactId version2.6/version configuration !-- although would prefer this, causing fo:table-body generation issues -- showSuccessfalse/showSuccess aggregatetrue/aggregate /configuration /plugin Error === [ERROR] BUILD ERROR [INFO] [INFO] Error during document generation: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error during document generation: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during document generation: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) at org.apache.maven.plugins.pdf.PdfMojo.generatedPdf(PdfMojo.java:574) at org.apache.maven.plugins.pdf.PdfMojo.execute(PdfMojo.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.apache.maven.doxia.docrenderer.DocumentRendererException: Error creating PDF from /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: org.apache.fop.fo.ValidationException: file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): fo:table-body is missing child elements. Required Content Model: marker* (table-row+|table-cell+) at
[jira] Closed: (MDEP-211) Possibility to prepend groupId to dependencies
[ http://jira.codehaus.org/browse/MDEP-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-211. -- Resolution: Fixed Fix Version/s: 2.2 Possibility to prepend groupId to dependencies -- Key: MDEP-211 URL: http://jira.codehaus.org/browse/MDEP-211 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Components: build-classpath, copy-dependencies Affects Versions: 2.2 Reporter: Oumar Aziz OUATTARA Assignee: Brian Fox Fix For: 2.2 Attachments: add_parameter_prepend_groupId.patch Hi, I would like to use the dependency plugin to copy dependencies including the groupId in the destination filename. This is to be able afterward to classify the plugins based on their groupId. It can also avoid a scenario like two dependencies with different groupIds and the same ArtifactId to collide when doing the copy. For this I propose a new configuration parameter prependGroupId. See attached patch for more details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-231) Create a single dependency resolution plugin
[ http://jira.codehaus.org/browse/MDEP-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242249#action_242249 ] Brian Fox commented on MDEP-231: no tests, no docs/site updates for the new goal Create a single dependency resolution plugin Key: MDEP-231 URL: http://jira.codehaus.org/browse/MDEP-231 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Components: resolve Affects Versions: 2.1, 2.2 Reporter: Marvin Froeder Assignee: John Casey Fix For: 2.2 Attachments: maven-dependency-plugin.patch, maven-dependency-plugin.patch, maven-dependency-plugin.patch The attached patch has a new goal that allows a single dependency to be resolved, like this: mvn org.apache.maven.plugins:maven-dependency-plugin:2.2-SNAPSHOT:resolve-single -DgroupId=com.acme -DartifactId=dummy -Dversion=1.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MDEP-273) Analyze Dependency Versions Mojo
[ http://jira.codehaus.org/browse/MDEP-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242250#action_242250 ] Brian Fox commented on MDEP-273: can you provide a patch to add proper site updates for your new goal? Analyze Dependency Versions Mojo Key: MDEP-273 URL: http://jira.codehaus.org/browse/MDEP-273 Project: Maven 2.x Dependency Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Cole Mickens Assignee: Brian Fox Attachments: analyze-dep-versions.patch, core.PNG, script-ant.PNG This is a patch that adds a new mojo and a report class to maven-dependency-plugin trunk (2.2). The goal `dependency:analyze-dep-versions` lists dependencies that are either resolved at a lower version than needed by a dependency farther from the project root or are being overridden by the dependencyManagement section. In some sense it is complimentary to `dependency:analyze-dep-mgt`. I checked out trunk today, added my new files, `svn add`ed them, then performed an `svn diff`. The patches applied correctly with a rechecked out copy of trunk with `cd apache-maven-dependency-plugin; patch -p0 ../analyze-dep-versions.patch`. After patching, it built, installed and passed IT tests (including the 6 new ones that I've added) properly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-522) release plugin tagging don't work for submodules
[ http://jira.codehaus.org/browse/MRELEASE-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242253#action_242253 ] werner mueller commented on MRELEASE-522: - this structure is a bit unusual. have you tried to reproduce the plugin config and the scm in the modules? of if you have a common parent use some properties and overwrite them in the submodules? this would mean you have to add the release-plugin config or the properties into every module-pom but that should work? release plugin tagging don't work for submodules Key: MRELEASE-522 URL: http://jira.codehaus.org/browse/MRELEASE-522 Project: Maven 2.x Release Plugin Issue Type: Bug Components: perform Affects Versions: 2.0 Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200) Java version: 1.6.0_14 Java home: C:\Programme\Java\jdk1.6.0_14\jre Default locale: de_DE, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows Reporter: Ruediger Gubler release:prepare doesn't tag submodules which are in different svn path. We have the following structure in our svn repositories: parentmodule/[trunk|tags|branches] module1/[trunk|tags|branches] module2/[trunk|tags|branches] ... moduleN/[trunk|tags|branches] I tried to include the modules using module../module1/module Which caused to the svn error: the parent directory is not in version control After changing the modules to modulemodule1/module and adding the submodules via svn:externals into the parent svn directory the release:prepare finishes successfully but the submodules are not tagged. Yours Rüdiger -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-347) Allow fields like scm, developers, licenses, etc to be set when generating an archetype
Allow fields like scm, developers, licenses, etc to be set when generating an archetype --- Key: ARCHETYPE-347 URL: http://jira.codehaus.org/browse/ARCHETYPE-347 Project: Maven Archetype Issue Type: New Feature Reporter: Paul Gier Currently a generated archetype only sets basic fields like the groupId, artifactId, etc. There should be options to set generated values for all POM fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARCHETYPE-347) Allow fields like scm, developers, licenses, etc to be set when generating an archetype
[ http://jira.codehaus.org/browse/ARCHETYPE-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated ARCHETYPE-347: Component/s: Creator Allow fields like scm, developers, licenses, etc to be set when generating an archetype --- Key: ARCHETYPE-347 URL: http://jira.codehaus.org/browse/ARCHETYPE-347 Project: Maven Archetype Issue Type: New Feature Components: Creator Reporter: Paul Gier Currently a generated archetype only sets basic fields like the groupId, artifactId, etc. There should be options to set generated values for all POM fields. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
