[jira] Created: (MNG-3983) Plugin Repositories Not Injected From Profile

Plugin Repositories Not Injected From Profile - Key: MNG-3983 URL: http://jira.codehaus.org/browse/MNG-3983 Project: Maven 2 Issue Type: Bug Components: Profiles Affects Versions:

[jira] Commented: (MNG-3983) Plugin Repositories Not Injected From Profile

[ http://jira.codehaus.org/browse/MNG-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160762#action_160762 ] Shane Isbell commented on MNG-3983: --- Fix in, just need to add test. Plugin Repositories Not

[jira] Updated: (MNG-3983) Plugin Repositories Not Injected From Profile

[ http://jira.codehaus.org/browse/MNG-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3983: -- Fix Version/s: 3.0-alpha-2 Plugin Repositories Not Injected From Profile

[jira] Updated: (MNG-3984) Different types of ID Model containers joined if their ids match

[ http://jira.codehaus.org/browse/MNG-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3984: -- Fix Version/s: 3.0-alpha-2 Fix is in, still need test. Different types of ID Model containers joined if

[jira] Created: (MNG-3984) Different types of ID Model containers joined if their ids match

Different types of ID Model containers joined if their ids match Key: MNG-3984 URL: http://jira.codehaus.org/browse/MNG-3984 Project: Maven 2 Issue Type: Bug

[jira] Created: (MNG-3985) Missing repository and plugin repositories

Missing repository and plugin repositories -- Key: MNG-3985 URL: http://jira.codehaus.org/browse/MNG-3985 Project: Maven 2 Issue Type: Bug Components: Inheritance and Interpolation

[jira] Updated: (MNG-3985) Missing repository and plugin repositories

[ http://jira.codehaus.org/browse/MNG-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3985: -- Affects Version/s: (was: 3.0-alpha-2) 3.0-alpha-1 Fix Version/s: 3.0-alpha-2

[jira] Updated: (MNG-3986) Remote repos not being used if it is in a profile

[ http://jira.codehaus.org/browse/MNG-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3986: -- Fix Version/s: 3.0-alpha-2 Fixed, still need test. Remote repos not being used if it is in a profile

[jira] Created: (MNG-3986) Remote repos not being used if it is in a profile

Remote repos not being used if it is in a profile - Key: MNG-3986 URL: http://jira.codehaus.org/browse/MNG-3986 Project: Maven 2 Issue Type: Bug Components: Profiles Affects

[jira] Work started: (MNG-3984) Different types of ID Model containers joined if their ids match

[ http://jira.codehaus.org/browse/MNG-3984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3984 started by Shane Isbell. Different types of ID Model containers joined if their ids match

[jira] Work started: (MNG-3986) Remote repos not being used if it is in a profile

[ http://jira.codehaus.org/browse/MNG-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3986 started by Shane Isbell. Remote repos not being used if it is in a profile - Key: MNG-3986

[jira] Closed: (MNG-3963) Specifying how profiles should work

[ http://jira.codehaus.org/browse/MNG-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3963. - Resolution: Fixed Added in the profile matcher info and inserted profiles into the project building flow.

[jira] Updated: (MNG-3943) [regression] Inherited plugin executions are lost if child and parent specify different plugin versions

[ http://jira.codehaus.org/browse/MNG-3943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3943: -- Fix Version/s: 3.0-alpha-2 [regression] Inherited plugin executions are lost if child and parent specify

[jira] Closed: (MNG-3866) [regression] Plugin definitions from child and parent are not merged when version differs

[ http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3866. - Resolution: Fixed [regression] Plugin definitions from child and parent are not merged when version differs

[jira] Updated: (MNG-3900) [regression] Properties defined by active profiles are not used for POM interpolation

[ http://jira.codehaus.org/browse/MNG-3900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3900: -- Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-3 Moving this to alpha-3. We need to

[jira] Created: (MNG-3978) Parent Pom Dependency Scope overrides Child Pom Dependency Default Scope

Parent Pom Dependency Scope overrides Child Pom Dependency Default Scope Key: MNG-3978 URL: http://jira.codehaus.org/browse/MNG-3978 Project: Maven 2 Issue Type: Bug

[jira] Updated: (MNG-3978) Parent Pom Dependency Scope overrides Child Pom Dependency Default Scope

[ http://jira.codehaus.org/browse/MNG-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3978: -- Fix Version/s: 3.0-alpha-2 Parent Pom Dependency Scope overrides Child Pom Dependency Default Scope

[jira] Closed: (MNG-3978) Parent Pom Dependency Scope overrides Child Pom Dependency Default Scope

[ http://jira.codehaus.org/browse/MNG-3978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3978. - Resolution: Fixed Fixed but it also means that the behavior of dependencyManagement changes, as it can no

[jira] Work started: (MNG-3965) shade plugin error when compiling Mercury trunk

[ http://jira.codehaus.org/browse/MNG-3965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3965 started by Shane Isbell. shade plugin error when compiling Mercury trunk --- Key: MNG-3965

[jira] Updated: (MNG-3979) Join Failure on non-empty parent node and empty child node

[ http://jira.codehaus.org/browse/MNG-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3979: -- Affects Version/s: (was: 3.0-alpha-2) 3.0-alpha-1 Fix Version/s: 3.0-alpha-2

[jira] Created: (MNG-3979) Join Failure on non-empty parent node and empty child node

Join Failure on non-empty parent node and empty child node -- Key: MNG-3979 URL: http://jira.codehaus.org/browse/MNG-3979 Project: Maven 2 Issue Type: Bug Components:

[jira] Closed: (MNG-3944) [regression] POMs with unusual file names don't get ${basedir} interpolated

[ http://jira.codehaus.org/browse/MNG-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3944. - Resolution: Fixed Fix Version/s: 3.0-alpha-2 We can just use the existence of the project directory to

[jira] Commented: (MNG-3866) [regression] Plugin definitions from child and parent are not merged when version differs

[ http://jira.codehaus.org/browse/MNG-3866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160370#action_160370 ] Shane Isbell commented on MNG-3866: --- 3.x behavior seems correct to me. If there are different

[jira] Commented: (MNG-3856) Fix interpolation to correctly treat all interpolated variables

[ http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160214#action_160214 ] Shane Isbell commented on MNG-3856: --- Got to the root of this problem:

[jira] Closed: (MNG-3856) Fix interpolation to correctly treat all interpolated variables

[ http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3856. - Resolution: Fixed Fixed: r732286 - Just needed to replace the references of ModelProperty.getValue, with

[jira] Commented: (MNG-3973) MavenDependencyProcessor does not throw an Exception when parent pom not found

[ http://jira.codehaus.org/browse/MNG-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160221#action_160221 ] Shane Isbell commented on MNG-3973: --- Definitely need more information. The MavenDependencyProcessor

[jira] Closed: (MNG-3938) [regression] Plugin executions with default id are not always merged

[ http://jira.codehaus.org/browse/MNG-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3938. - Resolution: Fixed Added in default id for plugin executions without id into PomTransformer. [regression]

[jira] Work started: (MNG-3938) [regression] Plugin executions with default id are not always merged

[ http://jira.codehaus.org/browse/MNG-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MNG-3938 started by Shane Isbell. [regression] Plugin executions with default id are not always merged

[jira] Commented: (MNG-3886) [regression] Ordering of goals from a plugin execution is not respected if plugin management applies

[ http://jira.codehaus.org/browse/MNG-3886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160099#action_160099 ] Shane Isbell commented on MNG-3886: --- Plugin Management is applied after all the other inheritance

[jira] Commented: (MNG-3901) Merge all project building code into a single component

[ http://jira.codehaus.org/browse/MNG-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160103#action_160103 ] Shane Isbell commented on MNG-3901: --- Path translator is used by at least one of the plugins. That is

[jira] Created: (MNG-3972) core-it-plugins fails to build when using maven trunk

core-it-plugins fails to build when using maven trunk - Key: MNG-3972 URL: http://jira.codehaus.org/browse/MNG-3972 Project: Maven 2 Issue Type: Bug Components: General

[jira] Commented: (MNG-3856) Fix interpolation to correctly treat all interpolated variables

[ http://jira.codehaus.org/browse/MNG-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160110#action_160110 ] Shane Isbell commented on MNG-3856: --- The ${maven.version} interpolation is tricky. There are deployed

[jira] Closed: (MNG-3821) [regression] Project builder blows up when POM declares two plugins which use the same id for their executions/reportsets

[ http://jira.codehaus.org/browse/MNG-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3821. - Resolution: Fixed Fix Version/s: (was: 3.0-alpha-3) 3.0-alpha-1 We can't feed

[jira] Updated: (MNG-3848) Inheritance of project/site/scm URLs does not take child's relative location to parent into account

[ http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3848: -- Fix Version/s: (was: 3.0-alpha-1) 3.0-alpha-2 Inheritance of project/site/scm URLs

[jira] Reopened: (MNG-3848) Inheritance of project/site/scm URLs does not take child's relative location to parent into account

[ http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell reopened MNG-3848: --- Reopening. Need further discussion as to best way to handle URL paths. Inheritance of project/site/scm URLs

[jira] Commented: (MNG-3861) Publish specification on POM construction

[ http://jira.codehaus.org/browse/MNG-3861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=156074#action_156074 ] Shane Isbell commented on MNG-3861: --- I'm also updating this to be in line with current builder code.

[jira] Closed: (MNG-3822) POM interpolation does not use basedir-aligned build directories

[ http://jira.codehaus.org/browse/MNG-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3822. - Resolution: Fixed Fixed. POM interpolation does not use basedir-aligned build directories

[jira] Updated: (MNG-3848) Inheritance of project/site/scm URLs does not take child's relative location to parent into account

[ http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3848: -- Fix Version/s: 3.0-alpha-2 Inheritance of project/site/scm URLs does not take child's relative location to

[jira] Closed: (MNG-3848) Inheritance of project/site/scm URLs does not take child's relative location to parent into account

[ http://jira.codehaus.org/browse/MNG-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3848. - Resolution: Won't Fix Fix Version/s: (was: 3.0-alpha-2) 3.0-alpha-1 We had a

[jira] Updated: (MNG-3819) Plugins that don't declare dependency on plexus-utils no longer get plexus-utils:1.1

[ http://jira.codehaus.org/browse/MNG-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3819: -- Affects Version/s: (was: 3.0-alpha-1) 3.0-alpha-3 Plugins that don't declare

[jira] Updated: (MNG-3819) Plugins that don't declare dependency on plexus-utils no longer get plexus-utils:1.1

[ http://jira.codehaus.org/browse/MNG-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3819: -- Affects Version/s: (was: 3.0-alpha-3) 3.0-alpha-1 Fix Version/s: 3.0-alpha-3

[jira] Closed: (MNG-3829) 3.0-alpha-1 release: get the core ITs passing

[ http://jira.codehaus.org/browse/MNG-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3829. - Resolution: Fixed 3.0-alpha-1 release: get the core ITs passing -

[jira] Updated: (MNG-3872) Profiles not being activated for relocated POMs

[ http://jira.codehaus.org/browse/MNG-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3872: -- Fix Version/s: 3.0-alpha-2 Profiles not being activated for relocated POMs

[jira] Created: (MNG-3872) Profiles not being activated for relocated POMs

Profiles not being activated for relocated POMs --- Key: MNG-3872 URL: http://jira.codehaus.org/browse/MNG-3872 Project: Maven 2 Issue Type: Bug Components: Profiles Affects

[jira] Created: (MNG-3873) Execution goals not treated as collection

Execution goals not treated as collection - Key: MNG-3873 URL: http://jira.codehaus.org/browse/MNG-3873 Project: Maven 2 Issue Type: Bug Affects Versions: 3.0-alpha-1 Reporter: Shane

[jira] Updated: (MNG-3873) Execution goals not treated as collection

[ http://jira.codehaus.org/browse/MNG-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3873: -- Assignee: Shane Isbell Fix Version/s: 3.0-alpha-1 Execution goals not treated as collection

[jira] Closed: (MNG-3863) Maven erroneously assumes org.apache.maven.plugins for dependencies without groupId

[ http://jira.codehaus.org/browse/MNG-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3863. - Resolution: Fixed I added back in the fix and included default id for plugins in profiles as well. Maven

[jira] Updated: (MNG-3850) Integrate new Profile Activators

[ http://jira.codehaus.org/browse/MNG-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3850: -- Description: This is a complete replacement for the old profile activators. The new framework uses

[jira] Commented: (MNG-3850) Integrate new Profile Activators

[ http://jira.codehaus.org/browse/MNG-3850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=154615#action_154615 ] Shane Isbell commented on MNG-3850: --- Prototype of what this will look like:

[jira] Closed: (MNG-3827) Order of collection-valued plugin configuration parameters is reversed

[ http://jira.codehaus.org/browse/MNG-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3827. - Resolution: Fixed Fixed. The ordering of elements is reversed on ModelDataSource.join(..). Need to do a

[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build

[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3259: -- Affects Version/s: (was: 2.0.8) (was: 2.0.7) 3.0-alpha-1

[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build

[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3259: -- Fix Version/s: 2.0.9 Regression: Maven drops dependencies in multi-module build

[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build

[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3259: -- Affects Version/s: 2.0.7 2.0.8 Fix Version/s: (was: 2.0.9) Regression:

[jira] Closed: (MNG-3833) POM interpolation fails to fully interpolate chain of dependent properties

[ http://jira.codehaus.org/browse/MNG-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3833. - Assignee: Shane Isbell Resolution: Fixed Fix Version/s: 3.0-alpha-1 New implementation does

[jira] Commented: (MNG-3829) 3.0-alpha-1 release: get the core ITs passing

[ http://jira.codehaus.org/browse/MNG-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=153717#action_153717 ] Shane Isbell commented on MNG-3829: --- The following ITs are also failing: I'm not sure what the JIRA

[jira] Commented: (MNG-1995) filtering element in pom.xml ignore properties

[ http://jira.codehaus.org/browse/MNG-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=151538#action_151538 ] Shane Isbell commented on MNG-1995: --- Fixed. filtering element in pom.xml ignore properties

[jira] Closed: (MNG-3391) StackOverflowError in DefaultMavenProjectBuilder

[ http://jira.codehaus.org/browse/MNG-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3391. - Resolution: Fixed StackOverflowError in DefaultMavenProjectBuilder

[jira] Closed: (MNG-1906) properties not being replaced before being passed to plugins (specificaly the surefire plugin)

[ http://jira.codehaus.org/browse/MNG-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-1906. - Resolution: Fixed Fix Version/s: (was: 3.0) 3.0-alpha-1 properties not being

[jira] Closed: (MNG-2764) Refactor MavenProjectBuilder

[ http://jira.codehaus.org/browse/MNG-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-2764. - Resolution: Fixed Fix Version/s: (was: 3.0) 3.0-alpha-1 Refactor

[jira] Closed: (MNG-889) m2 should warn (fail?) if a parent POM is discovered in the USD with a different version to the one requested

[ http://jira.codehaus.org/browse/MNG-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-889. Resolution: Fixed Fix Version/s: (was: 3.0) 3.0-alpha-1 m2 should warn (fail?) if a

[jira] Commented: (MNG-3392) NullPointerException if pom has no groupId

[ http://jira.codehaus.org/browse/MNG-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149532#action_149532 ] Shane Isbell commented on MNG-3392: --- I put in a fix. If everyone can verify it works for them, I'll

[jira] Commented: (MNG-3686) [regression] Can't build Wagon webdav provider

[ http://jira.codehaus.org/browse/MNG-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149584#action_149584 ] Shane Isbell commented on MNG-3686: --- This exception is occurring because 3.0 does not commons http

[jira] Commented: (MNG-3686) [regression] Can't build Wagon webdav provider

[ http://jira.codehaus.org/browse/MNG-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149590#action_149590 ] Shane Isbell commented on MNG-3686: --- I've added httpclient to maven distribution and it's working for

[jira] Commented: (MNG-3391) StackOverflowError in DefaultMavenProjectBuilder

[ http://jira.codehaus.org/browse/MNG-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149592#action_149592 ] Shane Isbell commented on MNG-3391: --- DefaultMavenProjectBuilder.mergeManagedDependencies has been

[jira] Commented: (MNG-1943) MavenProject::getParent() returns a MavenProject that is NOT interpolated

[ http://jira.codehaus.org/browse/MNG-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149602#action_149602 ] Shane Isbell commented on MNG-1943: --- 3.0 does interpolation of the parent. I wasn't able to get the

[jira] Commented: (MNG-2715) Maven does not comply to XML rules regarding prefixes.

[ http://jira.codehaus.org/browse/MNG-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149603#action_149603 ] Shane Isbell commented on MNG-2715: --- We will be able to get this supported pretty soon in trunk. For

[jira] Commented: (MNG-1906) properties not being replaced before being passed to plugins (specificaly the surefire plugin)

[ http://jira.codehaus.org/browse/MNG-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149604#action_149604 ] Shane Isbell commented on MNG-1906: --- This is fixed in 3.0. properties not being replaced before

[jira] Commented: (MNG-2764) Refactor MavenProjectBuilder

[ http://jira.codehaus.org/browse/MNG-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149605#action_149605 ] Shane Isbell commented on MNG-2764: --- Most of the MavenProjectBuilder has been gutted out and replaced

[jira] Commented: (MNG-889) m2 should warn (fail?) if a parent POM is discovered in the USD with a different version to the one requested

[ http://jira.codehaus.org/browse/MNG-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149607#action_149607 ] Shane Isbell commented on MNG-889: -- This is fixed for 3.0. It will warn if the parent version doesn't

[jira] Commented: (MNG-53) The model reader/writer used inside DefaultMavenProjectBuilder need to be components

[ http://jira.codehaus.org/browse/MNG-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149608#action_149608 ] Shane Isbell commented on MNG-53: - We are pretty close to eliminating modello with woodstox. I'm

[jira] Commented: (MNG-3556) XML entity not supported in Maven 2

[ http://jira.codehaus.org/browse/MNG-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149610#action_149610 ] Shane Isbell commented on MNG-3556: --- We are pretty close to having this fixed. Most of parsing for

[jira] Commented: (MNG-3638) Ability to evaluate expressions involving collections

[ http://jira.codehaus.org/browse/MNG-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=149611#action_149611 ] Shane Isbell commented on MNG-3638: --- In 3.0, we are converting the model into URI/value pairs: so the

[jira] Commented: (MNG-2562) expose current time as a property for POM interpolation

[ http://jira.codehaus.org/browse/MNG-2562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=134977#action_134977 ] Shane Isbell commented on MNG-2562: --- Bug fix here:

[jira] Commented: (MNG-3536) REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore

[ http://jira.codehaus.org/browse/MNG-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=134976#action_134976 ] Shane Isbell commented on MNG-3536: --- Bug fix here:

[jira] Commented: (MNG-3475) Some directories are not basedir aligned

[ http://jira.codehaus.org/browse/MNG-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=134978#action_134978 ] Shane Isbell commented on MNG-3475: --- Bug fix here:

[jira] Updated: (MNG-3536) REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore

[ http://jira.codehaus.org/browse/MNG-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3536: -- Attachment: interpolator.it.patch Interpolator patch containing IT tests. Apply to

[jira] Updated: (MNG-3536) REGRESSION: pom.build.sourceDirectory in Maven 2.0.9: it doesn't work anymore

[ http://jira.codehaus.org/browse/MNG-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3536: -- Attachment: core-integration-testing-plugins.patch Test mojo needed to verify patch. Apply to:

[jira] Commented: (MNG-3530) Regression: Properties get resolved before the LifeCycle is Forked.

[ http://jira.codehaus.org/browse/MNG-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=134842#action_134842 ] Shane Isbell commented on MNG-3530: --- I tried to run the attached project but received a build error:

[jira] Created: (MNG-3549) Integration Test Executor Fails to Find Maven Distribution

Integration Test Executor Fails to Find Maven Distribution -- Key: MNG-3549 URL: http://jira.codehaus.org/browse/MNG-3549 Project: Maven 2 Issue Type: Bug Components:

[jira] Updated: (MNG-3535) Valid properties which look self referential fail to resolve

[ http://jira.codehaus.org/browse/MNG-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3535: -- Attachment: model-int.patch Patch for this issue. If the system property starts with 'pom.' or 'project.'

[jira] Commented: (NMAVEN-119) Ability to generate pom.xml file from an existing Visual Studio solution file

[ http://jira.codehaus.org/browse/NMAVEN-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131013#action_131013 ] Shane Isbell commented on NMAVEN-119: - Just eyeballing this, it looks good. It needs the apache

[jira] Commented: (NMAVEN-118) Errors from .NET plugins are not recognized

[ http://jira.codehaus.org/browse/NMAVEN-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131014#action_131014 ] Shane Isbell commented on NMAVEN-118: - I'll get this one in today. Errors from .NET plugins are

[jira] Commented: (NMAVEN-113) Remove dependencies using VS NMaven Plugin

[ http://jira.codehaus.org/browse/NMAVEN-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129823#action_129823 ] Shane Isbell commented on NMAVEN-113: - When a user adds and deletes local assembly references

[jira] Commented: (NMAVEN-106) NMaven Service Embedder vs Simple Call of mvn.bat using dotnet System.Diagnostics.Process

[ http://jira.codehaus.org/browse/NMAVEN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129191#action_129191 ] Shane Isbell commented on NMAVEN-106: - One of the primary reasons for hosting the service on

[jira] Commented: (MNG-3431) Pom Extensions not supported for Toolchains

[ http://jira.codehaus.org/browse/MNG-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127114 ] Shane Isbell commented on MNG-3431: --- Using a scope of provided for my dotnet toolchain extension jar, solves the class cast

[jira] Created: (MNG-3457) Add Method to AbstractMojo for Obtaining Toolchain

Add Method to AbstractMojo for Obtaining Toolchain --- Key: MNG-3457 URL: http://jira.codehaus.org/browse/MNG-3457 Project: Maven 2 Issue Type: Improvement Affects Versions: 2.1-alpha-1

[jira] Created: (MNG-3458) Add Toolchain Requirements to Project Model

Add Toolchain Requirements to Project Model --- Key: MNG-3458 URL: http://jira.codehaus.org/browse/MNG-3458 Project: Maven 2 Issue Type: Improvement Components: POM Affects Versions:

[jira] Created: (MNG-3455) Expose Model From Toolchain Interface

Expose Model From Toolchain Interface - Key: MNG-3455 URL: http://jira.codehaus.org/browse/MNG-3455 Project: Maven 2 Issue Type: Improvement Affects Versions: 2.0.9 Reporter: Shane Isbell

[jira] Closed: (MNG-3455) Expose Model From Toolchain Interface

[ http://jira.codehaus.org/browse/MNG-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed MNG-3455. - Resolution: Won't Fix As suggested, adding my extension dependency using the provided scope solves the class

[jira] Commented: (MNG-3431) Pom Extensions not supported for Toolchains

[ http://jira.codehaus.org/browse/MNG-3431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126749 ] Shane Isbell commented on MNG-3431: --- I tried the toolchain in 2.1 and it looks as though the extensions work in that

[jira] Created: (MNG-3429) Toolchain classes not being picked up in uber jar

Toolchain classes not being picked up in uber jar - Key: MNG-3429 URL: http://jira.codehaus.org/browse/MNG-3429 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9

[jira] Created: (MNG-3430) Toolchain doesn't match Toolchain extensions

Toolchain doesn't match Toolchain extensions Key: MNG-3430 URL: http://jira.codehaus.org/browse/MNG-3430 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: Shane

[jira] Created: (MNG-3431) Pom Extensions not supported for Toolchains

Pom Extensions not supported for Toolchains --- Key: MNG-3431 URL: http://jira.codehaus.org/browse/MNG-3431 Project: Maven 2 Issue Type: Bug Affects Versions: 2.0.9 Reporter: Shane

[jira] Commented: (MNG-3394) Plugin versions inherited via pluginManagement cannot be overriden by build.plugins section of sub modules

[ http://jira.codehaus.org/browse/MNG-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126060 ] Shane Isbell commented on MNG-3394: --- I've look at the code. There is a problem in the

[jira] Created: (NMAVEN-105) NUnit Does not Work with Mono

NUnit Does not Work with Mono - Key: NMAVEN-105 URL: http://jira.codehaus.org/browse/NMAVEN-105 Project: NMaven Issue Type: Bug Reporter: Shane Isbell The compiled 2.4.x version of nunit framework

[jira] Closed: (NMAVEN-102) nmaven doesn't clean up compilation staging directories when source is deleted/renamed

[ http://jira.codehaus.org/browse/NMAVEN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-102. --- Resolution: Fixed Fix Version/s: 0.15 Patch applied. nmaven doesn't clean up compilation staging

[jira] Closed: (NMAVEN-84) Reseach feasability of SHFB plugin

[ http://jira.codehaus.org/browse/NMAVEN-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-84. -- Resolution: Won't Fix We can reopen this if there is interest to do so. Reseach feasability of SHFB plugin

[jira] Created: (MDEPLOY-71) DeployFile Mojo Does Not Handle Non-Core Artifact Types

DeployFile Mojo Does Not Handle Non-Core Artifact Types --- Key: MDEPLOY-71 URL: http://jira.codehaus.org/browse/MDEPLOY-71 Project: Maven 2.x Deploy Plugin Issue Type: Improvement

[jira] Commented: (NMAVEN-102) nmaven doesn't clean up compilation staging directories when source is deleted/renamed

[ http://jira.codehaus.org/browse/NMAVEN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118577 ] Shane Isbell commented on NMAVEN-102: - I'm thinking we should create a build-sources/generated-sources directory. Then

[jira] Commented: (NMAVEN-102) nmaven doesn't clean up compilation staging directories when source is deleted/renamed

[ http://jira.codehaus.org/browse/NMAVEN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118477 ] Shane Isbell commented on NMAVEN-102: - I think this patch may be conflicting with the AssemblyInfo generation. IT0016

<    1   2   3   4   5   >