[jira] Commented: (MASSEMBLY-264) Filtering in Assembly Generates Blank Files in the Archive

[ http://jira.codehaus.org/browse/MASSEMBLY-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147313#action_147313 ] Neill Alexander commented on MASSEMBLY-264: --- Hi Petar, I can't reproduce it either. I'v

[jira] Commented: (MWAR-169) NPE during packaging.

[ http://jira.codehaus.org/browse/MWAR-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147323#action_147323 ] Jonathan Ramsey commented on MWAR-169: -- This problem occurs when you run any of the goals on versi

[jira] Issue Comment Edited: (MWAR-169) NPE during packaging.

[ http://jira.codehaus.org/browse/MWAR-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147323#action_147323 ] jonathan.ramsey edited comment on MWAR-169 at 9/8/08 8:26 AM: -- This proble

[jira] Commented: (MSITE-30) site:deploy incompatibilities with m1.02

[ http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147326#action_147326 ] Paul Spencer commented on MSITE-30: --- Dennis, I object to this issue be downgraded from a BUG since th

[jira] Created: (MNG-3745) help:effective-pom should be available through an API

help:effective-pom should be available through an API - Key: MNG-3745 URL: http://jira.codehaus.org/browse/MNG-3745 Project: Maven 2 Issue Type: Improvement Components: General

[jira] Closed: (MNG-3743) pluginManagement not consulted when building from lifecycle forked via javdoc reports

[ http://jira.codehaus.org/browse/MNG-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3743. --- Resolution: Fixed executionProject was not being used to verify plugins in a forked lifecycle. This meant that when

[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1

[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147352#action_147352 ] Grégory Joseph commented on SCM-406: Has anyone had a chance to test with a 1.5.2 client ? (source r

[jira] Created: (MNG-3746) POM properties do not override default system properties during POM interpolation

POM properties do not override default system properties during POM interpolation - Key: MNG-3746 URL: http://jira.codehaus.org/browse/MNG-3746 Project: Maven 2

[jira] Updated: (MNG-3746) POM properties do not override default system properties during POM interpolation

[ http://jira.codehaus.org/browse/MNG-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3746: Assignee: John Casey Fix Version/s: 2.1.0-M1 > POM properties do not override default system properties du

[jira] Work started: (MNG-3746) POM properties do not override default system properties during POM interpolation

[ http://jira.codehaus.org/browse/MNG-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3746 started by John Casey. > POM properties do not override default system properties during POM > interpolation > -

[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1

[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147355#action_147355 ] Grégory Joseph commented on SCM-406: Good news, I guess: using the macports.org port of the subversi

[jira] Commented: (MSITE-30) site:deploy incompatibilities with m1.02

[ http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147356#action_147356 ] Dennis Lundberg commented on MSITE-30: -- Paul, When you say "a prior version", do you mean it used

[jira] Issue Comment Edited: (SCM-406) scm tag does not work with Subversion 1.5.1

[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147355#action_147355 ] gjoseph edited comment on SCM-406 at 9/8/08 1:38 PM: Good news, I guess: usi

[jira] Commented: (MENFORCER-51) build failure in case of available updates

[ http://jira.codehaus.org/browse/MENFORCER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147357#action_147357 ] Tomasz Pik commented on MENFORCER-51: - I agree that having it in enforcer is a better idea, the

[jira] Commented: (MNG-3746) POM properties do not override default system properties during POM interpolation

[ http://jira.codehaus.org/browse/MNG-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147368#action_147368 ] Paul Benedict commented on MNG-3746: I am not quite sure what the correct solution is. Obviously, p

[jira] Closed: (MNG-3746) POM properties do not override default system properties during POM interpolation

[ http://jira.codehaus.org/browse/MNG-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3746. --- Resolution: Fixed > POM properties do not override default system properties during POM > interpolation > --

[jira] Reopened: (MNG-3746) POM properties do not override default system properties during POM interpolation

[ http://jira.codehaus.org/browse/MNG-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey reopened MNG-3746: - Need to verify that -Djava.version=1.4 will override in POM. > POM properties do not override default system proper

[jira] Closed: (MNG-3746) POM properties do not override default system properties during POM interpolation

[ http://jira.codehaus.org/browse/MNG-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3746. --- Resolution: Fixed fixed CLI overrides of POM properties, and added another integration test for this case. > POM pr

[jira] Commented: (MSITE-30) site:deploy incompatibilities with m1.02

[ http://jira.codehaus.org/browse/MSITE-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147374#action_147374 ] Paul Spencer commented on MSITE-30: --- Yes. Paul Spencer > site:deploy incompatibilities with m1.02 >

[jira] Created: (MNG-3747) relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations

relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations --- Key: MNG-3747

[jira] Updated: (MNG-3747) relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations

[ http://jira.codehaus.org/browse/MNG-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-3747: Assignee: John Casey Fix Version/s: 2.1.0-M1 to be clear, the key points to this issue are the prefixed ex

[jira] Commented: (MNG-3747) relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations

[ http://jira.codehaus.org/browse/MNG-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147384#action_147384 ] John Casey commented on MNG-3747: - One additional point critical to reproducing this problem is to use

[jira] Commented: (SCM-406) scm tag does not work with Subversion 1.5.1

[ http://jira.codehaus.org/browse/SCM-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147386#action_147386 ] James William Dumay commented on SCM-406: - I can still confirm this issue with the SVN 1.5.2 rel

[jira] Closed: (MNG-3747) relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations

[ http://jira.codehaus.org/browse/MNG-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-3747. --- Resolution: Fixed > relative build paths are not path-translated when using prefixed expressions > (eg. project.buil

[jira] Created: (MECLIPSE-486) ITs dont compare expected files if the IT is a multi-module project

ITs dont compare expected files if the IT is a multi-module project --- Key: MECLIPSE-486 URL: http://jira.codehaus.org/browse/MECLIPSE-486 Project: Maven 2.x Eclipse Plugin Iss

[jira] Commented: (MECLIPSE-185) mvn eclipse:eclipse report 'Build Successful' even when generation fails

[ http://jira.codehaus.org/browse/MECLIPSE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147391#action_147391 ] Barrie Treloar commented on MECLIPSE-185: - This affects the IT tests too. I've noticed tha