THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if pom contains a dependency with two different versions.
I think we risk breaking too much with this one, we already emit the warning, and my view is that we should consider this as a POM specification change... it was poor specification in 4.0.0 that lead to permitting duplicate versions of the same dependency... OTOH for dependencies which are resources, there may be legitimate reasons for two versions of the same dependency... e.g. two versions of jquery webjars to be included in a webapp
- http://jira.codehaus.org/browse/MNG-2893 Update the DefaultPluginManager to not use a project depMan for controlling it's transitive dependencies
Seems like a legitimate bug we should consider? - http://jira.codehaus.org/browse/MNG-426 create "maxmem" setting for all plugins to refer to
I think this is now out of scope for core... but I would be interested in what others think - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should specify phase bindings in terms of general functionality type
This issue seems DOA at present... do we want to push it out again?
- http://jira.codehaus.org/browse/MNG-841 Support customization of default excludes
The issue as currently written seems to imply a pom format change... OTOH this could be handled by a standard property name. Probably more an issue for plugins that slurp directories or for the plexus utils that do this.
- http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a plugin
Sounds like this is a Move to 4.x issue - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies' scopes to be managed without explicit versions
This does not affect the pom schema, but potentially affects other POM parsers. My instinct is that this is for 4.x not 3.2 - http://jira.codehaus.org/browse/MNG-3825 Dependencies with classifier should not always require a version.
Same as MNG-3695 - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or execution
After reading more closely, this seems to be changing the POM schema, at least with the current patch, move to 4.x? - http://jira.codehaus.org/browse/MNG-3124 Inherit mailing lists from parent POM
Sounds like an issue building the internal model. Additionally this would not be a change that affects other consumers and their processing of dependencies, so this looks like a valid candidate to me. - http://jira.codehaus.org/browse/MNG-2807 ciManagement from parent is not merging with children
Same as MNG-3124. Both issues are related it would seem - http://jira.codehaus.org/browse/MNG-4173 Remove automatic version resolution for POM plugins
This is somewhat reasonable, but we have already kicked this can down the road and it may hinder adoption. I would be happy to kick this one to 4.x on the basis that most existing poms were written with the assumption that you could avoid specifying the plugin version... and we even omit the plugin version in the asf parent pom for some stuff...
- http://jira.codehaus.org/browse/MNG-3092 Version ranges with non-snapshot bounds can contain snapshot versions
Do we have a decision as to what we will do with this one? It is one of the longest discussions we have... - http://jira.codehaus.org/browse/MNG-5185 Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
The attached patch does not address the real issue, namely being able to define specific repo id's as offline. I would be happy to take a stab at the real issue, but likely do not have the time. If nobody else has the time, we should move this to 3.2.x as it could be a patch level enhancement to the maven CLI options
- http://jira.codehaus.org/browse/MNG-1569 Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare
This seems like 4.x scope. Objections? - http://jira.codehaus.org/browse/MNG-1867 deprecate system scope, analyse other use cases
I vote move to 4.x http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding artifactId to site urls
I think this is a 4.x candidate... objections?http://jira.codehaus.org/browse/MNG-5207 [Regression] Maven 3 fails to calculate proper build order
Action required
- http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
ACTION: krosenv to provide status update
...