[jira] Commented: (MNG-4126) [regression] Properties defined in profiles.xml of parent are not inherited during multimodule build

[ http://jira.codehaus.org/browse/MNG-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177225#action_177225 ] Will Horn commented on MNG-4126: False alarm, the profile in my profiles.xml was not active. In 2.0.

[jira] Commented: (MNG-4126) [regression] Properties defined in profiles.xml of parent are not inherited during multimodule build

[ http://jira.codehaus.org/browse/MNG-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177224#action_177224 ] Will Horn commented on MNG-4126: Is this fix supposed to be in 2.2.0 RC2? I find my profiles.xml prope

[jira] Issue Comment Edited: (MNG-4159) NPE in DefaultDependencyTreeBuilder when using version ranges.

[ http://jira.codehaus.org/browse/MNG-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=176192#action_176192 ] Will Horn edited comment on MNG-4159 at 5/12/09 3:40 PM: - Potential fix/hack.

[jira] Updated: (MNG-4159) NPE in DefaultDependencyTreeBuilder when using version ranges.

[ http://jira.codehaus.org/browse/MNG-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Horn updated MNG-4159: --- Attachment: maven-dependency-tree-fix Potential fix/hack. Uses getVersionRange instead of getBaseVersion in the map

[jira] Created: (MNG-4159) NPE in DefaultDependencyTreeBuilder when using version ranges.

NPE in DefaultDependencyTreeBuilder when using version ranges. -- Key: MNG-4159 URL: http://jira.codehaus.org/browse/MNG-4159 Project: Maven 2 Issue Type: Bug Components:

[jira] Commented: (MNG-4060) Remove support for profiles.xml

[ http://jira.codehaus.org/browse/MNG-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175461#action_175461 ] Will Horn commented on MNG-4060: Is there any documentation about this change? I don't see any here or

[jira] Updated: (MECLIPSE-495) excludes should support *

[ http://jira.codehaus.org/browse/MECLIPSE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will Horn updated MECLIPSE-495: --- Attachment: MECLIPSE-495.patch patch that makes resolveDependencies a parameter > excludes should suppor

[jira] Commented: (MECLIPSE-495) excludes should support *

[ http://jira.codehaus.org/browse/MECLIPSE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151546#action_151546 ] Will Horn commented on MECLIPSE-495: After looking through the code, I think a great solution w

[jira] Created: (MECLIPSE-495) excludes should support *

excludes should support * - Key: MECLIPSE-495 URL: http://jira.codehaus.org/browse/MECLIPSE-495 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.5.1 Environment: Windows Vista, Maven

[jira] Created: (MCLEAN-36) filesets with an absolute path directory are ignored when !project.isExecutionRoot()

filesets with an absolute path directory are ignored when !project.isExecutionRoot() Key: MCLEAN-36 URL: http://jira.codehaus.org/browse/MCLEAN-36 Project: Maven 2.x

[jira] Commented: (MCLEAN-27) fileset directory does not work as expected when cleaning "modules" in sub-directories

[ http://jira.codehaus.org/browse/MCLEAN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146734#action_146734 ] Will Horn commented on MCLEAN-27: - Note that this fix breaks absolute directory paths. I had to look

[jira] Commented: (MCLEAN-31) Always resolve relative path against the project's base directory

[ http://jira.codehaus.org/browse/MCLEAN-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146733#action_146733 ] Will Horn commented on MCLEAN-31: - Is there a reason why absolute paths are not addressed? In my case