[jira] Commented: (MNG-4211) [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+

[ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185079#action_185079 ] Sylvain Marié commented on MNG-4211: Hi John, Any news concerning that topic ? We are behind a com

[jira] Commented: (MECLIPSE-178) symbolic links need to able to be specified in the pom

[ http://jira.codehaus.org/browse/MECLIPSE-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185082#action_185082 ] Arnaud Heritier commented on MECLIPSE-178: -- I deployed a snapshot version of the plugin :

[jira] Closed: (MSITE-169) links to modules where not working if a modules dir is used

[ http://jira.codehaus.org/browse/MSITE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-169. --- Assignee: Lukas Theussl Resolution: Fixed I also cannot reproduce this with the attached test project

[jira] Updated: (MSITE-227) site:deploy -> wrong links in ${modules} when artifactId=module's directory

[ http://jira.codehaus.org/browse/MSITE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-227: Attachment: MSITE-227.zip I can reproduce this with the attached test case (both with site-plugin-2.0 and

[jira] Updated: (MSITE-227) site:deploy -> wrong links in ${modules} when artifactId=module's directory

[ http://jira.codehaus.org/browse/MSITE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-227: Affects Version/s: 2.0 > site:deploy -> wrong links in ${modules} when artifactId=module's directory > ---

[jira] Commented: (MSITE-141) Possible security hole when deploying site

[ http://jira.codehaus.org/browse/MSITE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185086#action_185086 ] Lukas Theussl commented on MSITE-141: - The maven 1 site plugin had the two options maven.site.chmo

[jira] Created: (MNG-4262) Make-like reactor mode fails to find projects selected by relative paths with leading dots

Make-like reactor mode fails to find projects selected by relative paths with leading dots -- Key: MNG-4262 URL: http://jira.codehaus.org/browse/MNG-4262 Project:

[jira] Closed: (MNG-4262) Make-like reactor mode fails to find projects selected by relative paths with leading dots

[ http://jira.codehaus.org/browse/MNG-4262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4262. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 3.0-alpha-3 Fixed in [r798

[jira] Created: (ARCHETYPE-255) custom variable filtered in created resources

custom variable filtered in created resources - Key: ARCHETYPE-255 URL: http://jira.codehaus.org/browse/ARCHETYPE-255 Project: Maven Archetype Issue Type: Wish Components: Creator, Genera

[jira] Closed: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor

[ http://jira.codehaus.org/browse/MNG-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3043. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: (was: 2.2.x)

[jira] Created: (MRELEASE-464) snapshot dependencies are not resolved for items inside tag using release:prepare

snapshot dependencies are not resolved for items inside tag using release:prepare - Key: MRELEASE-464 URL: http://jira.codehaus.org/browse/MRELEASE-464 Proje

[jira] Maven Version-plug-in Issue

Hi, We are trying to extend maven-version-plugin as a standalone java application to get latest available versions. If we run the plugin from command-line, it works fine but our custom application fails. The following is what we are trying to do: /* ==

[jira] Commented: (MRELEASE-452) allowTimestampedSnapshots=true still fails with snapshot dependencies

[ http://jira.codehaus.org/browse/MRELEASE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185110#action_185110 ] silver commented on MRELEASE-452: - This patch works well it will be fine to add it for the 2.0-beta

[jira] Created: (MPECLIPSE-136) Eclipse Maven project doesn't have a Java Nature after Importing

Eclipse Maven project doesn't have a Java Nature after Importing Key: MPECLIPSE-136 URL: http://jira.codehaus.org/browse/MPECLIPSE-136 Project: Maven 1.x Eclipse Plugin Issue T

[jira] Commented: (MPECLIPSE-136) Eclipse Maven project doesn't have a Java Nature after Importing

[ http://jira.codehaus.org/browse/MPECLIPSE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185111#action_185111 ] Benjamin Bentmann commented on MPECLIPSE-136: - Are you sured you filled this issue at

[jira] Closed: (MNG-4245) can't access protected mirrors with latest 3.0-SNAPSHOT (rev 795227)

[ http://jira.codehaus.org/browse/MNG-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4245. -- Assignee: Jason van Zyl Resolution: Fixed Fix Version/s: 3.0-alpha-3 Applied in [r79591

[jira] Commented: (MPECLIPSE-136) Eclipse Maven project doesn't have a Java Nature after Importing

[ http://jira.codehaus.org/browse/MPECLIPSE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185116#action_185116 ] vychtrle commented on MPECLIPSE-136: It is the plugin http://m2eclipse.sonatype.org/update-de

[jira] Maven Version-plug-in Issue

Hi, We are trying to extend maven-version-plugin as a standalone java application to get latest available versions. If we run the plugin from command-line, it works fine but our custom application fails. The following is what we are trying to do: /* ==

[jira] Maven Version-plug-in Issue

Hi, We are trying to extend maven-version-plugin as a standalone java application to get latest available versions. If we run the plugin from command-line, it works fine but our custom application fails. The following is what we are trying to do: /* ==

[jira] Closed: (MPECLIPSE-136) Eclipse Maven project doesn't have a Java Nature after Importing

[ http://jira.codehaus.org/browse/MPECLIPSE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPECLIPSE-136. --- Assignee: Benjamin Bentmann Resolution: Not A Bug bq. It is the plugin http://m2ec

[jira] Maven Version-plug-in Issue

Hi, We are trying to extend maven-version-plugin as a standalone java application to get latest available versions. If we run the plugin from command-line, it works fine but our custom application fails. The following is what we are trying to do: /* ==

[jira] Commented: (MAVENUPLOAD-2497) gwt-mvc 0.2.0-gwt1.5

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185118#action_185118 ] François Wauquier commented on MAVENUPLOAD-2497: By using this tutorial: http:

[jira] Commented: (MDEP-156) dependency:analyze mistakenly reports an implemented interface as an unused, declared dependency

[ http://jira.codehaus.org/browse/MDEP-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185120#action_185120 ] Kernix Ski commented on MDEP-156: - I have the same problem. I have a dependency containing interfaces

[jira] Commented: (MAVENUPLOAD-2489) iText 2.1.6 released

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185121#action_185121 ] Brian Fox commented on MAVENUPLOAD-2489: fwiw, the maven-metadata.xml is broken, it has

[jira] Created: (MPIR-171) support "TimeZones" as a timezone

support "TimeZones" as a timezone - Key: MPIR-171 URL: http://jira.codehaus.org/browse/MPIR-171 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.1.2 Re

[jira] Created: (MNG-4263) Dependencies resolution & the order in the declaration

Dependencies resolution & the order in the declaration -- Key: MNG-4263 URL: http://jira.codehaus.org/browse/MNG-4263 Project: Maven 2 Issue Type: Bug Components: Dependencies

[jira] Commented: (MNG-4263) Dependencies resolution & the order in the declaration

[ http://jira.codehaus.org/browse/MNG-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185124#action_185124 ] Arnaud commented on MNG-4263: - Maybe , the problem is between keyboard adn chair > Dependencies resol

[jira] Issue Comment Edited: (MNG-4263) Dependencies resolution & the order in the declaration

[ http://jira.codehaus.org/browse/MNG-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185124#action_185124 ] Arnaud edited comment on MNG-4263 at 7/28/09 8:39 AM: -- Maybe , the problem is bet

[jira] Commented: (MAVENUPLOAD-2489) iText 2.1.6 released

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185126#action_185126 ] Juven Xu commented on MAVENUPLOAD-2489: --- it's now fixed http://repo1.maven.org/maven2/co

[jira] Commented: (MNG-4263) Dependencies resolution & the order in the declaration

[ http://jira.codehaus.org/browse/MNG-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185127#action_185127 ] Joerg Schaible commented on MNG-4263: - Since M2.0.10 this is deterministic, in older versions there

[jira] Closed: (MNG-4263) Dependencies resolution & the order in the declaration

[ http://jira.codehaus.org/browse/MNG-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4263. -- Assignee: Benjamin Bentmann Resolution: Duplicate > Dependencies resolution & the order in the de

[jira] Created: (SUREFIRE-561) after running test, when tests fail, it's hard to the find the failure reason

after running test, when tests fail, it's hard to the find the failure reason - Key: SUREFIRE-561 URL: http://jira.codehaus.org/browse/SUREFIRE-561 Project: Maven Surefire

[jira] Commented: (SUREFIRE-561) after running test, when tests fail, it's hard to the find the failure reason

[ http://jira.codehaus.org/browse/SUREFIRE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185136#action_185136 ] Benjamin Bentmann commented on SUREFIRE-561: bq. 1. Surefire summary does not show the

[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version

[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185138#action_185138 ] Brett Porter commented on MNG-4257: --- @Joerg that's not uncommon (antlr did the same). I don't think t

[jira] Updated: (MPDF-23) Definition Lists are not formatted correctly

[ http://jira.codehaus.org/browse/MPDF-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Swor updated MPDF-23: Attachment: pdfPluginDefinitionTest.zip Here's a sample Maven project with the resulting PDF in the target folder.

[jira] Commented: (MPDF-23) Definition Lists are not formatted correctly

[ http://jira.codehaus.org/browse/MPDF-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185151#action_185151 ] Lukas Theussl commented on MPDF-23: --- Ok, you are using the itext implementation, I missed that. It wor

[jira] Commented: (SUREFIRE-561) after running test, when tests fail, it's hard to the find the failure reason

[ http://jira.codehaus.org/browse/SUREFIRE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185155#action_185155 ] Szczepan Faber commented on SUREFIRE-561: - No I haven't - it didn't occur me at all that th

[jira] Created: (DOXIA-353) IText sink: Definition Lists are not formatted correctly

IText sink: Definition Lists are not formatted correctly Key: DOXIA-353 URL: http://jira.codehaus.org/browse/DOXIA-353 Project: Maven Doxia Issue Type: Bug Components: Module

[jira] Closed: (MRELEASE-387) command line versions don't seem to work on release:branch

[ http://jira.codehaus.org/browse/MRELEASE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-387. - Assignee: Olivier Lamy Resolution: Fixed fix in rev 798709. Thanks ! > command line versions d

[jira] Created: (MNG-4264) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled

Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled Key: MNG-4264 URL: http://jira.codehaus.org/browse/MNG-4264 Proj

[jira] Commented: (MNG-4264) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled

[ http://jira.codehaus.org/browse/MNG-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185181#action_185181 ] Benjamin Bentmann commented on MNG-4264: Can you provide some more details, like a build log th

[jira] Closed: (MRELEASE-452) allowTimestampedSnapshots=true still fails with snapshot dependencies

[ http://jira.codehaus.org/browse/MRELEASE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-452. - Assignee: Olivier Lamy Resolution: Fixed Fix Version/s: 2.0-beta-10 fix in [rev 7987

[jira] Commented: (MRELEASE-452) allowTimestampedSnapshots=true still fails with snapshot dependencies

[ http://jira.codehaus.org/browse/MRELEASE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185188#action_185188 ] Antony Stubbs commented on MRELEASE-452: Is it possible to make a test for this? for future

[jira] Commented: (MRELEASE-445) Validate tagBase before starting

[ http://jira.codehaus.org/browse/MRELEASE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185189#action_185189 ] Olivier Lamy commented on MRELEASE-445: --- IMHO we should simply use svn options --parents with

[jira] Commented: (MRELEASE-444) Prepare in multi-module project update the snaphsot version to release version only in one of the submodule

[ http://jira.codehaus.org/browse/MRELEASE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185190#action_185190 ] Olivier Lamy commented on MRELEASE-444: --- I understand some are not rewritten because they are

[jira] Closed: (MRELEASE-443) Add a mojo parameter for using the new remote tagging for svn scm provider (to prevent issue with svn > 1.5.0 in release:branch)

[ http://jira.codehaus.org/browse/MRELEASE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-443. - Assignee: Olivier Lamy Resolution: Duplicate > Add a mojo parameter for using the new remote ta

[jira] Closed: (MRELEASE-444) Prepare in multi-module project update the snaphsot version to release version only in one of the submodule

[ http://jira.codehaus.org/browse/MRELEASE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-444. - Resolution: Won't Fix > Prepare in multi-module project update the snaphsot version to release > ver

[jira] Reopened: (MCHANGES-165) Using type="update" but the result says "Fixes [bug...]"

[ http://jira.codehaus.org/browse/MCHANGES-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy reopened MCHANGES-165: --- > Using type="update" but the result says "Fixes [bug...]" >

[jira] Commented: (MRELEASE-452) allowTimestampedSnapshots=true still fails with snapshot dependencies

[ http://jira.codehaus.org/browse/MRELEASE-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185191#action_185191 ] Olivier Lamy commented on MRELEASE-452: --- no problem you can provide a patch with a test case

[jira] Closed: (MRELEASE-437) -Darguments don't seemt o work with new release plugin

[ http://jira.codehaus.org/browse/MRELEASE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-437. - Assignee: Olivier Lamy Resolution: Duplicate > -Darguments don't seemt o work with new release

[jira] Commented: (MRELEASE-436) Spaces in scmCommitPrefix cause errors in attempting to release

[ http://jira.codehaus.org/browse/MRELEASE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185192#action_185192 ] Olivier Lamy commented on MRELEASE-436: --- Can we have the full stack trace ? The attached one

[jira] Closed: (MRELEASE-434) Assumes scm.url is Current Directory for Remote Tagging

[ http://jira.codehaus.org/browse/MRELEASE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-434. - Assignee: Olivier Lamy Resolution: Not A Bug Yes sure we trust what the user put on the pom scm

[jira] Created: (MAVENUPLOAD-2532) Wrong sha1 sum of xalan-2.7.1.jar

Wrong sha1 sum of xalan-2.7.1.jar - Key: MAVENUPLOAD-2532 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2532 Project: Maven Upload Requests Issue Type: Bug Reporter: Stepan Koltsov http://mirr

[jira] Updated: (MRELEASE-425) When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run

[ http://jira.codehaus.org/browse/MRELEASE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated MRELEASE-425: -- Priority: Minor (was: Major) Issue Type: Wish (was: Bug) just run : mvn release:clean (afte

[jira] Closed: (MRELEASE-425) When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run

[ http://jira.codehaus.org/browse/MRELEASE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-425. - Assignee: Olivier Lamy Resolution: Won't Fix > When running release:branch in -DdryRun mode, th

[jira] Closed: (MRELEASE-424) Release plugin invoker loses interactive mode

[ http://jira.codehaus.org/browse/MRELEASE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-424. - Assignee: Olivier Lamy Resolution: Not A Bug > Release plugin invoker loses interactive mode >

[jira] Created: (MNG-4265) Properties in "system"-scope dependencies breaks transitive dependency resolution

Properties in "system"-scope dependencies breaks transitive dependency resolution - Key: MNG-4265 URL: http://jira.codehaus.org/browse/MNG-4265 Project: Maven 2

[jira] Updated: (MNG-4264) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled

[ http://jira.codehaus.org/browse/MNG-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Wilkes updated MNG-4264: -- Attachment: javadoc-problem.zip "mvn javadoc:javadoc" will return [INFO] -

[jira] Reopened: (MRELEASE-444) Prepare in multi-module project update the snaphsot version to release version only in one of the submodule

[ http://jira.codehaus.org/browse/MRELEASE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Paul GUIGUI reopened MRELEASE-444: --- Hi Olivier, Agree, the pom.xml of dependency1/2 should not be modified, they are external d