THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- http://jira.codehaus.org/browse/MNG-2381 Improved control over the repositories in the POM
Unsure what the ask is here - http://jira.codehaus.org/browse/MNG-3474 Add parameter --internet to test Internet access with and without using proxy defined in settings.xml
Any takers... looks like a nice small feature to add
- 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-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-5207 [Regression] Maven 3 fails to calculate proper build order
- http://jira.codehaus.org/browse/MNG-5265 enforce repository url verification for passing authz
Should be an easy fix for somebody to add a warning during the pom/settings parsing?
...
- http://jira.codehaus.org/browse/MNG-5353 Ignore pre-releases in exclusive upper bound [lw,up)
ACTION: jvzyl will we be upping Aether to M4, in which case that will expose an alternative version range syntax that resolves this issue... OTOH that new syntax may cause issues for existing pom readers... in which case this becomes a push back to 4.x
http://jira.codehaus.org/browse/MNG-5389 AbstractMavenLifecycleParticipant need a afterSessionEnd
ACTION: jvzyl to provide status update - http://jira.codehaus.org/browse/MNG-5205 Memory leak in StringSearchModelInterpolator
- ACTION: krosenv to provide status update
...