You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2014/01/07 13:43:02 UTC
3.2.0 Bug Scrub
AFAIU this is the current list of bugs:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
I propose that the following issues all require a change to the model
version, and thus should be pushed back to 4.0.0 (or later)
http://jira.codehaus.org/browse/MNG-1977 Global dependency
exclusions<http://jira.codehaus.org/browse/MNG-1977>
http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
attributes<http://jira.codehaus.org/browse/MNG-3397>
http://jira.codehaus.org/browse/MNG-5102 Mixin POM
fragments<http://jira.codehaus.org/browse/MNG-5102>
http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported for
parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
http://jira.codehaus.org/browse/MNG-2216 Add default encodings section to
POM <http://jira.codehaus.org/browse/MNG-2216>
http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
project version matches a regex <http://jira.codehaus.org/browse/MNG-3826>
http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
dependencies that implement an API or provide other dependencies
http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation Configuration
http://jira.codehaus.org/browse/MNG-2557 Various enhancements to profiles
http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
support overriding project.build.directory (WONTFIX candidate?)
http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
declaration of IRC channels
The following issues require that the deployed pom be different from the
on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again I
think these should be pushed back to 4.0.0 (or later)
http://jira.codehaus.org/browse/MNG-624 Automatic parent
versioning<http://jira.codehaus.org/browse/MNG-624>
I would propose that we move these issues into a 4.0 bucket... that will
bring us down to 31 issues open for 3.2.0
Thoughts?
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
On 7 January 2014 12:43, Stephen Connolly
<st...@gmail.com>wrote:
> AFAIU this is the current list of bugs:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>
> I propose that the following issues all require a change to the model
> version, and thus should be pushed back to 4.0.0 (or later)
>
> http://jira.codehaus.org/browse/MNG-1977 Global dependency exclusions<http://jira.codehaus.org/browse/MNG-1977>
> http://jira.codehaus.org/browse/MNG-2297 Change the POM to use attributes<http://jira.codehaus.org/browse/MNG-3397>
>
^^^ typo http://jira.codehaus.org/browse/MNG-3397 Change the POM to use
attributes <http://jira.codehaus.org/browse/MNG-3397>
>
> http://jira.codehaus.org/browse/MNG-5102 Mixin POM fragments<http://jira.codehaus.org/browse/MNG-5102>
> http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported for
> parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
> http://jira.codehaus.org/browse/MNG-2216 Add default encodings section to
> POM <http://jira.codehaus.org/browse/MNG-2216>
> http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
> project version matches a regex <http://jira.codehaus.org/browse/MNG-3826>
> http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
> dependencies that implement an API or provide other dependencies
> http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
> Configuration
> http://jira.codehaus.org/browse/MNG-2557 Various enhancements to profiles
> http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
> support overriding project.build.directory (WONTFIX candidate?)
> http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
> declaration of IRC channels
>
> The following issues require that the deployed pom be different from the
> on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again I
> think these should be pushed back to 4.0.0 (or later)
>
> http://jira.codehaus.org/browse/MNG-624 Automatic parent versioning<http://jira.codehaus.org/browse/MNG-624>
>
> I would propose that we move these issues into a 4.0 bucket... that will
> bring us down to 31 issues open for 3.2.0
>
> Thoughts?
>
Re: 3.2.0 Bug Scrub
Posted by Anders Hammar <an...@hammar.net>.
Sounds good to me.
/Anders
On Tue, Jan 7, 2014 at 1:43 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> AFAIU this is the current list of bugs:
>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>
> I propose that the following issues all require a change to the model
> version, and thus should be pushed back to 4.0.0 (or later)
>
> http://jira.codehaus.org/browse/MNG-1977 Global dependency
> exclusions<http://jira.codehaus.org/browse/MNG-1977>
> http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
> attributes<http://jira.codehaus.org/browse/MNG-3397>
> http://jira.codehaus.org/browse/MNG-5102 Mixin POM
> fragments<http://jira.codehaus.org/browse/MNG-5102>
> http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported for
> parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
> http://jira.codehaus.org/browse/MNG-2216 Add default encodings section to
> POM <http://jira.codehaus.org/browse/MNG-2216>
> http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
> project version matches a regex <http://jira.codehaus.org/browse/MNG-3826>
> http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
> dependencies that implement an API or provide other dependencies
> http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
> Configuration
> http://jira.codehaus.org/browse/MNG-2557 Various enhancements to profiles
> http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
> support overriding project.build.directory (WONTFIX candidate?)
> http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
> declaration of IRC channels
>
> The following issues require that the deployed pom be different from the
> on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again I
> think these should be pushed back to 4.0.0 (or later)
>
> http://jira.codehaus.org/browse/MNG-624 Automatic parent
> versioning<http://jira.codehaus.org/browse/MNG-624>
>
> I would propose that we move these issues into a 4.0 bucket... that will
> bring us down to 31 issues open for 3.2.0
>
> Thoughts?
>
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@tesla.io>.
For everything that is not claimed in a couple days can move to 3.2.x and that gets it out of the 3.2.0 bucket, and from there you can percolate up to 4.x.
On Jan 7, 2014, at 11:47 AM, Stephen Connolly <st...@gmail.com> wrote:
> * http://jira.codehaus.org/browse/MNG-656 lazily resolve extensions
>
> Not sure that this is a reasonable ask. Moving to 4.x anyway
>
> * 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-5205 Memory leak in
> StringSearchModelInterpolator
>
> ACTION: krosenv to provide status update
>
> * 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
>
>
> On 7 January 2014 16:39, Stephen Connolly
> <st...@gmail.com>wrote:
>
>> * 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-5366 [Regression] resolveAlways
>> does not force dependency resolution in Maven 3.0.4
>>
>> Seems legit
>>
>> ACTION: rfscholte to update status as from comments seems to have a
>> handle on this one
>>
>> * http://jira.codehaus.org/browse/MNG-5494 Add a license file that
>> corresponds to each GAV in the distribution
>>
>> I think jvzyl has this one under control. Can be pushed back if
>> necessary as what we have currently works, if somewhat sub-optimal
>>
>> * http://jira.codehaus.org/browse/MNG-5265 enforce repository url
>> verification for passing authz
>>
>> ACTION: olamy to provide status update, unclear from comment if 3.0.5
>> prints a warning (in which case I vote we close this issue) or if the
>> intention was to add printing a warning to 3.0.5
>>
>> * http://jira.codehaus.org/browse/MNG-3526 Small change to artifact
>> version parsing.
>>
>> I have committed this issue
>>
>>
>> On 7 January 2014 16:02, Stephen Connolly <stephen.alan.connolly@gmail.com
>>> wrote:
>>
>>> * http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
>>>
>>> ACTION: krosenv to provide status update
>>>
>>> * 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-5356 Make encrypt/decrypt logic
>>> pluggable
>>>
>>> Seems like something that could be in scope. Any takers?
>>>
>>> * http://jira.codehaus.org/browse/MNG-5389 AbstractMavenLifecycleParticipant
>>> need a afterSessionEnd
>>>
>>> ACTION: jvzyl to provide status update
>>>
>>> * 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...
>>>
>>>
>>> On 7 January 2014 15:55, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> * 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-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-3825 Dependencies with classifier
>>>> should not always require a version.
>>>>
>>>> Same as MNG-3695
>>>>
>>>> * 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...
>>>>
>>>>
>>>> On 7 January 2014 15:45, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>>> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
>>>>> directories to super POM
>>>>>
>>>>> Moved to 4.x bucket as requires pom model change
>>>>>
>>>>> * 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
>>>>>
>>>>>
>>>>> On 7 January 2014 15:39, Stephen Connolly <
>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>
>>>>>> * 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-4506 Split site deployment URLs
>>>>>> into release vs. snapshot, just like artifacts
>>>>>>
>>>>>> Moved to 4.x bucket as requires pom model change
>>>>>>
>>>>>> * 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-3879 Dependency map and
>>>>>> documentation
>>>>>>
>>>>>> Moved to 4.x bucket as requires a pom model change
>>>>>>
>>>>>> ACTION: bmargulies - split the issue and rename existing issue so
>>>>>> that the pom change is the title
>>>>>>
>>>>>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
>>>>>> property of java.util.Properties is a lot more clumsy than that for Map
>>>>>>
>>>>>> Unsure what the ask is here... seems like it's really a plexus
>>>>>> compatibility layer issue
>>>>>>
>>>>>> * 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-2916 Default message and
>>>>>> profile help messages
>>>>>>
>>>>>> Moved to 4.x bucket as requires pom model change
>>>>>>
>>>>>>
>>>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>
>>>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>>>> some more?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>
>>>>>>>> Done
>>>>>>>>
>>>>>>>>
>>>>>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>>>>>>
>>>>>>>>> Seems reasonable. Go for it.
>>>>>>>>>
>>>>>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> AFAIU this is the current list of bugs:
>>>>>>>>>>
>>>>>>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>>>>>>>
>>>>>>>>>> I propose that the following issues all require a change to the
>>>>>>>>> model
>>>>>>>>>> version, and thus should be pushed back to 4.0.0 (or later)
>>>>>>>>>>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>>>>>>>> exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>>>>>>>> attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>>>>>>>> fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>>>>>>> supported for
>>>>>>>>>> parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>>>>>>> section to
>>>>>>>>>> POM <http://jira.codehaus.org/browse/MNG-2216>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-3826 Add profile activation
>>>>>>>>> when
>>>>>>>>>> project version matches a regex <
>>>>>>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>>>>>>>> dependencies that implement an API or provide other dependencies
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>>>>>>> Configuration
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>>>>>>> profiles
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>>>>>>> should
>>>>>>>>>> support overriding project.build.directory (WONTFIX candidate?)
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-3726 Extend POM model to
>>>>>>>>> support
>>>>>>>>>> declaration of IRC channels
>>>>>>>>>>
>>>>>>>>>> The following issues require that the deployed pom be different
>>>>>>>>> from the
>>>>>>>>>> on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>>>>>>> again I
>>>>>>>>>> think these should be pushed back to 4.0.0 (or later)
>>>>>>>>>>
>>>>>>>>>> http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>>>>>>>> versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>>>>>>>
>>>>>>>>>> I would propose that we move these issues into a 4.0 bucket...
>>>>>>>>> that will
>>>>>>>>>> bring us down to 31 issues open for 3.2.0
>>>>>>>>>>
>>>>>>>>>> Thoughts?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Jason
>>>>>>>>>
>>>>>>>>> ----------------------------------------------------------
>>>>>>>>> Jason van Zyl
>>>>>>>>> Founder, Apache Maven
>>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>>> ---------------------------------------------------------
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
* http://jira.codehaus.org/browse/MNG-656 lazily resolve extensions
Not sure that this is a reasonable ask. Moving to 4.x anyway
* 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-5205 Memory leak in
StringSearchModelInterpolator
ACTION: krosenv to provide status update
* 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
On 7 January 2014 16:39, Stephen Connolly
<st...@gmail.com>wrote:
> * 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-5366 [Regression] resolveAlways
> does not force dependency resolution in Maven 3.0.4
>
> Seems legit
>
> ACTION: rfscholte to update status as from comments seems to have a
> handle on this one
>
> * http://jira.codehaus.org/browse/MNG-5494 Add a license file that
> corresponds to each GAV in the distribution
>
> I think jvzyl has this one under control. Can be pushed back if
> necessary as what we have currently works, if somewhat sub-optimal
>
> * http://jira.codehaus.org/browse/MNG-5265 enforce repository url
> verification for passing authz
>
> ACTION: olamy to provide status update, unclear from comment if 3.0.5
> prints a warning (in which case I vote we close this issue) or if the
> intention was to add printing a warning to 3.0.5
>
> * http://jira.codehaus.org/browse/MNG-3526 Small change to artifact
> version parsing.
>
> I have committed this issue
>
>
> On 7 January 2014 16:02, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> * http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
>>
>> ACTION: krosenv to provide status update
>>
>> * 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-5356 Make encrypt/decrypt logic
>> pluggable
>>
>> Seems like something that could be in scope. Any takers?
>>
>> * http://jira.codehaus.org/browse/MNG-5389 AbstractMavenLifecycleParticipant
>> need a afterSessionEnd
>>
>> ACTION: jvzyl to provide status update
>>
>> * 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...
>>
>>
>> On 7 January 2014 15:55, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> * 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-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-3825 Dependencies with classifier
>>> should not always require a version.
>>>
>>> Same as MNG-3695
>>>
>>> * 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...
>>>
>>>
>>> On 7 January 2014 15:45, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
>>>> directories to super POM
>>>>
>>>> Moved to 4.x bucket as requires pom model change
>>>>
>>>> * 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
>>>>
>>>>
>>>> On 7 January 2014 15:39, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>>> * 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-4506 Split site deployment URLs
>>>>> into release vs. snapshot, just like artifacts
>>>>>
>>>>> Moved to 4.x bucket as requires pom model change
>>>>>
>>>>> * 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-3879 Dependency map and
>>>>> documentation
>>>>>
>>>>> Moved to 4.x bucket as requires a pom model change
>>>>>
>>>>> ACTION: bmargulies - split the issue and rename existing issue so
>>>>> that the pom change is the title
>>>>>
>>>>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
>>>>> property of java.util.Properties is a lot more clumsy than that for Map
>>>>>
>>>>> Unsure what the ask is here... seems like it's really a plexus
>>>>> compatibility layer issue
>>>>>
>>>>> * 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-2916 Default message and
>>>>> profile help messages
>>>>>
>>>>> Moved to 4.x bucket as requires pom model change
>>>>>
>>>>>
>>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>
>>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>>> some more?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>
>>>>>>> Done
>>>>>>>
>>>>>>>
>>>>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>>>>>
>>>>>>>> Seems reasonable. Go for it.
>>>>>>>>
>>>>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>>
>>>>>>>> > AFAIU this is the current list of bugs:
>>>>>>>> >
>>>>>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>>>>> >
>>>>>>>> > I propose that the following issues all require a change to the
>>>>>>>> model
>>>>>>>> > version, and thus should be pushed back to 4.0.0 (or later)
>>>>>>>> >
>>>>>>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>>>>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>>>>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>>>>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>>>>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>>>>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>>>>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>>>>>> supported for
>>>>>>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>>>>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>>>>>> section to
>>>>>>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>>>>>>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation
>>>>>>>> when
>>>>>>>> > project version matches a regex <
>>>>>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>>>>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>>>>>> > dependencies that implement an API or provide other dependencies
>>>>>>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>>>>>> Configuration
>>>>>>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>>>>>> profiles
>>>>>>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>>>>>> should
>>>>>>>> > support overriding project.build.directory (WONTFIX candidate?)
>>>>>>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to
>>>>>>>> support
>>>>>>>> > declaration of IRC channels
>>>>>>>> >
>>>>>>>> > The following issues require that the deployed pom be different
>>>>>>>> from the
>>>>>>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>>>>>> again I
>>>>>>>> > think these should be pushed back to 4.0.0 (or later)
>>>>>>>> >
>>>>>>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>>>>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>>>>> >
>>>>>>>> > I would propose that we move these issues into a 4.0 bucket...
>>>>>>>> that will
>>>>>>>> > bring us down to 31 issues open for 3.2.0
>>>>>>>> >
>>>>>>>> > Thoughts?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Jason
>>>>>>>>
>>>>>>>> ----------------------------------------------------------
>>>>>>>> Jason van Zyl
>>>>>>>> Founder, Apache Maven
>>>>>>>> http://twitter.com/jvanzyl
>>>>>>>> ---------------------------------------------------------
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
* 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-5366 [Regression] resolveAlways does
not force dependency resolution in Maven 3.0.4
Seems legit
ACTION: rfscholte to update status as from comments seems to have a
handle on this one
* http://jira.codehaus.org/browse/MNG-5494 Add a license file that
corresponds to each GAV in the distribution
I think jvzyl has this one under control. Can be pushed back if
necessary as what we have currently works, if somewhat sub-optimal
* http://jira.codehaus.org/browse/MNG-5265 enforce repository url
verification for passing authz
ACTION: olamy to provide status update, unclear from comment if 3.0.5
prints a warning (in which case I vote we close this issue) or if the
intention was to add printing a warning to 3.0.5
* http://jira.codehaus.org/browse/MNG-3526 Small change to artifact version
parsing.
I have committed this issue
On 7 January 2014 16:02, Stephen Connolly
<st...@gmail.com>wrote:
> * http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
>
> ACTION: krosenv to provide status update
>
> * 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-5356 Make encrypt/decrypt logic
> pluggable
>
> Seems like something that could be in scope. Any takers?
>
> * http://jira.codehaus.org/browse/MNG-5389 AbstractMavenLifecycleParticipant
> need a afterSessionEnd
>
> ACTION: jvzyl to provide status update
>
> * 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...
>
>
> On 7 January 2014 15:55, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> * 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-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-3825 Dependencies with classifier
>> should not always require a version.
>>
>> Same as MNG-3695
>>
>> * 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...
>>
>>
>> On 7 January 2014 15:45, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
>>> directories to super POM
>>>
>>> Moved to 4.x bucket as requires pom model change
>>>
>>> * 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
>>>
>>>
>>> On 7 January 2014 15:39, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> * 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-4506 Split site deployment URLs
>>>> into release vs. snapshot, just like artifacts
>>>>
>>>> Moved to 4.x bucket as requires pom model change
>>>>
>>>> * 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-3879 Dependency map and
>>>> documentation
>>>>
>>>> Moved to 4.x bucket as requires a pom model change
>>>>
>>>> ACTION: bmargulies - split the issue and rename existing issue so
>>>> that the pom change is the title
>>>>
>>>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
>>>> property of java.util.Properties is a lot more clumsy than that for Map
>>>>
>>>> Unsure what the ask is here... seems like it's really a plexus
>>>> compatibility layer issue
>>>>
>>>> * 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-2916 Default message and profile
>>>> help messages
>>>>
>>>> Moved to 4.x bucket as requires pom model change
>>>>
>>>>
>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>> some more?
>>>>>
>>>>>
>>>>>
>>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>
>>>>>> Done
>>>>>>
>>>>>>
>>>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>>>>
>>>>>>> Seems reasonable. Go for it.
>>>>>>>
>>>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>
>>>>>>> > AFAIU this is the current list of bugs:
>>>>>>> >
>>>>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>>>> >
>>>>>>> > I propose that the following issues all require a change to the
>>>>>>> model
>>>>>>> > version, and thus should be pushed back to 4.0.0 (or later)
>>>>>>> >
>>>>>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>>>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>>>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>>>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>>>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>>>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>>>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>>>>> supported for
>>>>>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>>>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>>>>> section to
>>>>>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>>>>>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation
>>>>>>> when
>>>>>>> > project version matches a regex <
>>>>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>>>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>>>>> > dependencies that implement an API or provide other dependencies
>>>>>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>>>>> Configuration
>>>>>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>>>>> profiles
>>>>>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>>>>> should
>>>>>>> > support overriding project.build.directory (WONTFIX candidate?)
>>>>>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to
>>>>>>> support
>>>>>>> > declaration of IRC channels
>>>>>>> >
>>>>>>> > The following issues require that the deployed pom be different
>>>>>>> from the
>>>>>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>>>>> again I
>>>>>>> > think these should be pushed back to 4.0.0 (or later)
>>>>>>> >
>>>>>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>>>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>>>> >
>>>>>>> > I would propose that we move these issues into a 4.0 bucket...
>>>>>>> that will
>>>>>>> > bring us down to 31 issues open for 3.2.0
>>>>>>> >
>>>>>>> > Thoughts?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder, Apache Maven
>>>>>>> http://twitter.com/jvanzyl
>>>>>>> ---------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@tesla.io>.
I'm going to work on the couple issues have assigned to me, and possibly work on one issue with Robert. Most likely be wrapped up by the end of the week. I'm going to wait until Aether 1.0.0 before I update it again.
On Jan 7, 2014, at 11:02 AM, Stephen Connolly <st...@gmail.com> wrote:
> * http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
>
> ACTION: krosenv to provide status update
>
> * 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-5356 Make encrypt/decrypt logic
> pluggable
>
> Seems like something that could be in scope. Any takers?
>
> * http://jira.codehaus.org/browse/MNG-5389 AbstractMavenLifecycleParticipant
> need a afterSessionEnd
>
> ACTION: jvzyl to provide status update
>
> * 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...
>
>
> On 7 January 2014 15:55, Stephen Connolly
> <st...@gmail.com>wrote:
>
>> * 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-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-3825 Dependencies with classifier
>> should not always require a version.
>>
>> Same as MNG-3695
>>
>> * 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...
>>
>>
>> On 7 January 2014 15:45, Stephen Connolly <stephen.alan.connolly@gmail.com
>>> wrote:
>>
>>> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
>>> directories to super POM
>>>
>>> Moved to 4.x bucket as requires pom model change
>>>
>>> * 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
>>>
>>>
>>> On 7 January 2014 15:39, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> * 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-4506 Split site deployment URLs
>>>> into release vs. snapshot, just like artifacts
>>>>
>>>> Moved to 4.x bucket as requires pom model change
>>>>
>>>> * 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-3879 Dependency map and
>>>> documentation
>>>>
>>>> Moved to 4.x bucket as requires a pom model change
>>>>
>>>> ACTION: bmargulies - split the issue and rename existing issue so
>>>> that the pom change is the title
>>>>
>>>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
>>>> property of java.util.Properties is a lot more clumsy than that for Map
>>>>
>>>> Unsure what the ask is here... seems like it's really a plexus
>>>> compatibility layer issue
>>>>
>>>> * 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-2916 Default message and profile
>>>> help messages
>>>>
>>>> Moved to 4.x bucket as requires pom model change
>>>>
>>>>
>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>> some more?
>>>>>
>>>>>
>>>>>
>>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>
>>>>>> Done
>>>>>>
>>>>>>
>>>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>>>>
>>>>>>> Seems reasonable. Go for it.
>>>>>>>
>>>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>>
>>>>>>>> AFAIU this is the current list of bugs:
>>>>>>>>
>>>>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>>>>>
>>>>>>>> I propose that the following issues all require a change to the
>>>>>>> model
>>>>>>>> version, and thus should be pushed back to 4.0.0 (or later)
>>>>>>>>
>>>>>>>> http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>>>>>> exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>>>>>> http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>>>>>> attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>>>>>> http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>>>>>> fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>>>>>> http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>>>>> supported for
>>>>>>>> parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>>>>>> http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>>>>> section to
>>>>>>>> POM <http://jira.codehaus.org/browse/MNG-2216>
>>>>>>>> http://jira.codehaus.org/browse/MNG-3826 Add profile activation
>>>>>>> when
>>>>>>>> project version matches a regex <
>>>>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>>>>>> http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>>>>>> dependencies that implement an API or provide other dependencies
>>>>>>>> http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>>>>> Configuration
>>>>>>>> http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>>>>> profiles
>>>>>>>> http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>>>>> should
>>>>>>>> support overriding project.build.directory (WONTFIX candidate?)
>>>>>>>> http://jira.codehaus.org/browse/MNG-3726 Extend POM model to
>>>>>>> support
>>>>>>>> declaration of IRC channels
>>>>>>>>
>>>>>>>> The following issues require that the deployed pom be different
>>>>>>> from the
>>>>>>>> on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>>>>> again I
>>>>>>>> think these should be pushed back to 4.0.0 (or later)
>>>>>>>>
>>>>>>>> http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>>>>>> versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>>>>>
>>>>>>>> I would propose that we move these issues into a 4.0 bucket... that
>>>>>>> will
>>>>>>>> bring us down to 31 issues open for 3.2.0
>>>>>>>>
>>>>>>>> Thoughts?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jason
>>>>>>>
>>>>>>> ----------------------------------------------------------
>>>>>>> Jason van Zyl
>>>>>>> Founder, Apache Maven
>>>>>>> http://twitter.com/jvanzyl
>>>>>>> ---------------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: 3.2.0 Bug Scrub
Posted by Anders Hammar <an...@hammar.net>.
>
> * http://jira.codehaus.org/browse/MNG-5356 Make encrypt/decrypt logic
> pluggable
>
> Seems like something that could be in scope. Any takers?
>
We already have a (I think) working fix for this in the git repo linked to
in the comments. However, jvz suggested moving this to a separate component
which would be some extra work/thinking.
I did move this to the 4.x line as I'm not sure how much time I have to put
into this the near future. But it could always be moved back to 3.2. It
would be very good to get in there.
/Anders
>
> * http://jira.codehaus.org/browse/MNG-5389AbstractMavenLifecycleParticipant
> need a afterSessionEnd
>
> ACTION: jvzyl to provide status update
>
> * 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...
>
>
> On 7 January 2014 15:55, Stephen Connolly
> <st...@gmail.com>wrote:
>
> > * 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-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-3825 Dependencies with classifier
> > should not always require a version.
> >
> > Same as MNG-3695
> >
> > * 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...
> >
> >
> > On 7 January 2014 15:45, Stephen Connolly <
> stephen.alan.connolly@gmail.com
> > > wrote:
> >
> >> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
> >> directories to super POM
> >>
> >> Moved to 4.x bucket as requires pom model change
> >>
> >> * 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
> >>
> >>
> >> On 7 January 2014 15:39, Stephen Connolly <
> >> stephen.alan.connolly@gmail.com> wrote:
> >>
> >>> * 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-4506 Split site deployment URLs
> >>> into release vs. snapshot, just like artifacts
> >>>
> >>> Moved to 4.x bucket as requires pom model change
> >>>
> >>> * 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-3879 Dependency map and
> >>> documentation
> >>>
> >>> Moved to 4.x bucket as requires a pom model change
> >>>
> >>> ACTION: bmargulies - split the issue and rename existing issue so
> >>> that the pom change is the title
> >>>
> >>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
> >>> property of java.util.Properties is a lot more clumsy than that for Map
> >>>
> >>> Unsure what the ask is here... seems like it's really a plexus
> >>> compatibility layer issue
> >>>
> >>> * 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-2916 Default message and profile
> >>> help messages
> >>>
> >>> Moved to 4.x bucket as requires pom model change
> >>>
> >>>
> >>> On 7 January 2014 15:25, Stephen Connolly <
> >>> stephen.alan.connolly@gmail.com> wrote:
> >>>
> >>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
> >>>> some more?
> >>>>
> >>>>
> >>>>
> >>>> On 7 January 2014 15:25, Stephen Connolly <
> >>>> stephen.alan.connolly@gmail.com> wrote:
> >>>>
> >>>>> Done
> >>>>>
> >>>>>
> >>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
> >>>>>
> >>>>>> Seems reasonable. Go for it.
> >>>>>>
> >>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
> >>>>>> stephen.alan.connolly@gmail.com> wrote:
> >>>>>>
> >>>>>> > AFAIU this is the current list of bugs:
> >>>>>> >
> >>>>>>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
> >>>>>> >
> >>>>>> > I propose that the following issues all require a change to the
> >>>>>> model
> >>>>>> > version, and thus should be pushed back to 4.0.0 (or later)
> >>>>>> >
> >>>>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
> >>>>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
> >>>>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
> >>>>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
> >>>>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
> >>>>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
> >>>>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not
> >>>>>> supported for
> >>>>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
> >>>>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
> >>>>>> section to
> >>>>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
> >>>>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation
> >>>>>> when
> >>>>>> > project version matches a regex <
> >>>>>> http://jira.codehaus.org/browse/MNG-3826>
> >>>>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
> >>>>>> > dependencies that implement an API or provide other dependencies
> >>>>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
> >>>>>> Configuration
> >>>>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
> >>>>>> profiles
> >>>>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
> >>>>>> should
> >>>>>> > support overriding project.build.directory (WONTFIX candidate?)
> >>>>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to
> >>>>>> support
> >>>>>> > declaration of IRC channels
> >>>>>> >
> >>>>>> > The following issues require that the deployed pom be different
> >>>>>> from the
> >>>>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
> >>>>>> again I
> >>>>>> > think these should be pushed back to 4.0.0 (or later)
> >>>>>> >
> >>>>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
> >>>>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
> >>>>>> >
> >>>>>> > I would propose that we move these issues into a 4.0 bucket...
> that
> >>>>>> will
> >>>>>> > bring us down to 31 issues open for 3.2.0
> >>>>>> >
> >>>>>> > Thoughts?
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Jason
> >>>>>>
> >>>>>> ----------------------------------------------------------
> >>>>>> Jason van Zyl
> >>>>>> Founder, Apache Maven
> >>>>>> http://twitter.com/jvanzyl
> >>>>>> ---------------------------------------------------------
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
* http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
ACTION: krosenv to provide status update
* 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-5356 Make encrypt/decrypt logic
pluggable
Seems like something that could be in scope. Any takers?
* http://jira.codehaus.org/browse/MNG-5389 AbstractMavenLifecycleParticipant
need a afterSessionEnd
ACTION: jvzyl to provide status update
* 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...
On 7 January 2014 15:55, Stephen Connolly
<st...@gmail.com>wrote:
> * 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-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-3825 Dependencies with classifier
> should not always require a version.
>
> Same as MNG-3695
>
> * 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...
>
>
> On 7 January 2014 15:45, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
>> directories to super POM
>>
>> Moved to 4.x bucket as requires pom model change
>>
>> * 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
>>
>>
>> On 7 January 2014 15:39, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> * 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-4506 Split site deployment URLs
>>> into release vs. snapshot, just like artifacts
>>>
>>> Moved to 4.x bucket as requires pom model change
>>>
>>> * 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-3879 Dependency map and
>>> documentation
>>>
>>> Moved to 4.x bucket as requires a pom model change
>>>
>>> ACTION: bmargulies - split the issue and rename existing issue so
>>> that the pom change is the title
>>>
>>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
>>> property of java.util.Properties is a lot more clumsy than that for Map
>>>
>>> Unsure what the ask is here... seems like it's really a plexus
>>> compatibility layer issue
>>>
>>> * 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-2916 Default message and profile
>>> help messages
>>>
>>> Moved to 4.x bucket as requires pom model change
>>>
>>>
>>> On 7 January 2014 15:25, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>> some more?
>>>>
>>>>
>>>>
>>>> On 7 January 2014 15:25, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>>> Done
>>>>>
>>>>>
>>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>>>
>>>>>> Seems reasonable. Go for it.
>>>>>>
>>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>>
>>>>>> > AFAIU this is the current list of bugs:
>>>>>> >
>>>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>>> >
>>>>>> > I propose that the following issues all require a change to the
>>>>>> model
>>>>>> > version, and thus should be pushed back to 4.0.0 (or later)
>>>>>> >
>>>>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>>>> supported for
>>>>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>>>> section to
>>>>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>>>>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation
>>>>>> when
>>>>>> > project version matches a regex <
>>>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>>>> > dependencies that implement an API or provide other dependencies
>>>>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>>>> Configuration
>>>>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>>>> profiles
>>>>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>>>> should
>>>>>> > support overriding project.build.directory (WONTFIX candidate?)
>>>>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to
>>>>>> support
>>>>>> > declaration of IRC channels
>>>>>> >
>>>>>> > The following issues require that the deployed pom be different
>>>>>> from the
>>>>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>>>> again I
>>>>>> > think these should be pushed back to 4.0.0 (or later)
>>>>>> >
>>>>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>>> >
>>>>>> > I would propose that we move these issues into a 4.0 bucket... that
>>>>>> will
>>>>>> > bring us down to 31 issues open for 3.2.0
>>>>>> >
>>>>>> > Thoughts?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> ----------------------------------------------------------
>>>>>> Jason van Zyl
>>>>>> Founder, Apache Maven
>>>>>> http://twitter.com/jvanzyl
>>>>>> ---------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
* 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-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-3825 Dependencies with classifier
should not always require a version.
Same as MNG-3695
* 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...
On 7 January 2014 15:45, Stephen Connolly
<st...@gmail.com>wrote:
> * http://jira.codehaus.org/browse/MNG-2478 add filtered resource
> directories to super POM
>
> Moved to 4.x bucket as requires pom model change
>
> * 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
>
>
> On 7 January 2014 15:39, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> * 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-4506 Split site deployment URLs
>> into release vs. snapshot, just like artifacts
>>
>> Moved to 4.x bucket as requires pom model change
>>
>> * 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-3879 Dependency map and
>> documentation
>>
>> Moved to 4.x bucket as requires a pom model change
>>
>> ACTION: bmargulies - split the issue and rename existing issue so
>> that the pom change is the title
>>
>> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
>> property of java.util.Properties is a lot more clumsy than that for Map
>>
>> Unsure what the ask is here... seems like it's really a plexus
>> compatibility layer issue
>>
>> * 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-2916 Default message and profile
>> help messages
>>
>> Moved to 4.x bucket as requires pom model change
>>
>>
>> On 7 January 2014 15:25, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> OK we are now at 38 open issues.... anyone else feel like scrubbing some
>>> more?
>>>
>>>
>>>
>>> On 7 January 2014 15:25, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> Done
>>>>
>>>>
>>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>>
>>>>> Seems reasonable. Go for it.
>>>>>
>>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>>
>>>>> > AFAIU this is the current list of bugs:
>>>>> >
>>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>> >
>>>>> > I propose that the following issues all require a change to the model
>>>>> > version, and thus should be pushed back to 4.0.0 (or later)
>>>>> >
>>>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>>> supported for
>>>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>>> section to
>>>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>>>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
>>>>> > project version matches a regex <
>>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>>> > dependencies that implement an API or provide other dependencies
>>>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>>> Configuration
>>>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>>> profiles
>>>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>>> should
>>>>> > support overriding project.build.directory (WONTFIX candidate?)
>>>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
>>>>> > declaration of IRC channels
>>>>> >
>>>>> > The following issues require that the deployed pom be different from
>>>>> the
>>>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>>> again I
>>>>> > think these should be pushed back to 4.0.0 (or later)
>>>>> >
>>>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>> >
>>>>> > I would propose that we move these issues into a 4.0 bucket... that
>>>>> will
>>>>> > bring us down to 31 issues open for 3.2.0
>>>>> >
>>>>> > Thoughts?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jason
>>>>>
>>>>> ----------------------------------------------------------
>>>>> Jason van Zyl
>>>>> Founder, Apache Maven
>>>>> http://twitter.com/jvanzyl
>>>>> ---------------------------------------------------------
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
* http://jira.codehaus.org/browse/MNG-2478 add filtered resource
directories to super POM
Moved to 4.x bucket as requires pom model change
* 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
On 7 January 2014 15:39, Stephen Connolly
<st...@gmail.com>wrote:
> * 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-4506 Split site deployment URLs
> into release vs. snapshot, just like artifacts
>
> Moved to 4.x bucket as requires pom model change
>
> * 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-3879 Dependency map and
> documentation
>
> Moved to 4.x bucket as requires a pom model change
>
> ACTION: bmargulies - split the issue and rename existing issue so that
> the pom change is the title
>
> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
> property of java.util.Properties is a lot more clumsy than that for Map
>
> Unsure what the ask is here... seems like it's really a plexus
> compatibility layer issue
>
> * 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-2916 Default message and profile
> help messages
>
> Moved to 4.x bucket as requires pom model change
>
>
> On 7 January 2014 15:25, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> OK we are now at 38 open issues.... anyone else feel like scrubbing some
>> more?
>>
>>
>>
>> On 7 January 2014 15:25, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> Done
>>>
>>>
>>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>>
>>>> Seems reasonable. Go for it.
>>>>
>>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>> > AFAIU this is the current list of bugs:
>>>> >
>>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>> >
>>>> > I propose that the following issues all require a change to the model
>>>> > version, and thus should be pushed back to 4.0.0 (or later)
>>>> >
>>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not
>>>> supported for
>>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>>> section to
>>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
>>>> > project version matches a regex <
>>>> http://jira.codehaus.org/browse/MNG-3826>
>>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>> > dependencies that implement an API or provide other dependencies
>>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>>> Configuration
>>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>>> profiles
>>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
>>>> should
>>>> > support overriding project.build.directory (WONTFIX candidate?)
>>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
>>>> > declaration of IRC channels
>>>> >
>>>> > The following issues require that the deployed pom be different from
>>>> the
>>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>>> again I
>>>> > think these should be pushed back to 4.0.0 (or later)
>>>> >
>>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>>>> >
>>>> > I would propose that we move these issues into a 4.0 bucket... that
>>>> will
>>>> > bring us down to 31 issues open for 3.2.0
>>>> >
>>>> > Thoughts?
>>>>
>>>> Thanks,
>>>>
>>>> Jason
>>>>
>>>> ----------------------------------------------------------
>>>> Jason van Zyl
>>>> Founder, Apache Maven
>>>> http://twitter.com/jvanzyl
>>>> ---------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stuart McCulloch <mc...@gmail.com>.
On 7 Jan 2014, at 15:39, Stephen Connolly <st...@gmail.com> wrote:
> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a property of java.util.Properties is a lot more clumsy than that for Map
>
> Unsure what the ask is here... seems like it's really a plexus compatibility layer issue
FYI, this alternative form of configuration is already possible - it was implemented by Benjamin a few years ago under https://issues.sonatype.org/browse/SISU-61
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
* 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-4506 Split site deployment URLs into
release vs. snapshot, just like artifacts
Moved to 4.x bucket as requires pom model change
* 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-3879 Dependency map and documentation
Moved to 4.x bucket as requires a pom model change
ACTION: bmargulies - split the issue and rename existing issue so that
the pom change is the title
* http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a
property of java.util.Properties is a lot more clumsy than that for Map
Unsure what the ask is here... seems like it's really a plexus
compatibility layer issue
* 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-2916 Default message and profile help
messages
Moved to 4.x bucket as requires pom model change
On 7 January 2014 15:25, Stephen Connolly
<st...@gmail.com>wrote:
> OK we are now at 38 open issues.... anyone else feel like scrubbing some
> more?
>
>
>
> On 7 January 2014 15:25, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> Done
>>
>>
>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>
>>> Seems reasonable. Go for it.
>>>
>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>> > AFAIU this is the current list of bugs:
>>> >
>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>> >
>>> > I propose that the following issues all require a change to the model
>>> > version, and thus should be pushed back to 4.0.0 (or later)
>>> >
>>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported
>>> for
>>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
>>> section to
>>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
>>> > project version matches a regex <
>>> http://jira.codehaus.org/browse/MNG-3826>
>>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>> > dependencies that implement an API or provide other dependencies
>>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>> Configuration
>>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>> profiles
>>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
>>> > support overriding project.build.directory (WONTFIX candidate?)
>>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
>>> > declaration of IRC channels
>>> >
>>> > The following issues require that the deployed pom be different from
>>> the
>>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
>>> again I
>>> > think these should be pushed back to 4.0.0 (or later)
>>> >
>>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>>> >
>>> > I would propose that we move these issues into a 4.0 bucket... that
>>> will
>>> > bring us down to 31 issues open for 3.2.0
>>> >
>>> > Thoughts?
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Anders Hammar <an...@hammar.net>.
I stepped up big time and moved MNG-5356 (Make encrypt/decrypt logic
pluggable) to the 4.x list. :-)
/Anders
On Tue, Jan 7, 2014 at 4:25 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> OK we are now at 38 open issues.... anyone else feel like scrubbing some
> more?
>
>
>
> On 7 January 2014 15:25, Stephen Connolly
> <st...@gmail.com>wrote:
>
> > Done
> >
> >
> > On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
> >
> >> Seems reasonable. Go for it.
> >>
> >> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
> >> stephen.alan.connolly@gmail.com> wrote:
> >>
> >> > AFAIU this is the current list of bugs:
> >> >
> >>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
> >> >
> >> > I propose that the following issues all require a change to the model
> >> > version, and thus should be pushed back to 4.0.0 (or later)
> >> >
> >> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
> >> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
> >> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
> >> > attributes<http://jira.codehaus.org/browse/MNG-3397>
> >> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
> >> > fragments<http://jira.codehaus.org/browse/MNG-5102>
> >> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported
> >> for
> >> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
> >> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings
> section
> >> to
> >> > POM <http://jira.codehaus.org/browse/MNG-2216>
> >> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
> >> > project version matches a regex <
> >> http://jira.codehaus.org/browse/MNG-3826>
> >> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
> >> > dependencies that implement an API or provide other dependencies
> >> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
> >> Configuration
> >> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
> >> profiles
> >> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM
> should
> >> > support overriding project.build.directory (WONTFIX candidate?)
> >> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
> >> > declaration of IRC channels
> >> >
> >> > The following issues require that the deployed pom be different from
> the
> >> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0...
> again
> >> I
> >> > think these should be pushed back to 4.0.0 (or later)
> >> >
> >> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
> >> > versioning<http://jira.codehaus.org/browse/MNG-624>
> >> >
> >> > I would propose that we move these issues into a 4.0 bucket... that
> will
> >> > bring us down to 31 issues open for 3.2.0
> >> >
> >> > Thoughts?
> >>
> >> Thanks,
> >>
> >> Jason
> >>
> >> ----------------------------------------------------------
> >> Jason van Zyl
> >> Founder, Apache Maven
> >> http://twitter.com/jvanzyl
> >> ---------------------------------------------------------
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >
>
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@tesla.io>.
I will scrub throughout the day, I have removed all issues assigned to me I'm not planning on working on.
On Jan 7, 2014, at 10:25 AM, Stephen Connolly <st...@gmail.com> wrote:
> OK we are now at 38 open issues.... anyone else feel like scrubbing some
> more?
>
>
>
> On 7 January 2014 15:25, Stephen Connolly
> <st...@gmail.com>wrote:
>
>> Done
>>
>>
>> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>>
>>> Seems reasonable. Go for it.
>>>
>>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> AFAIU this is the current list of bugs:
>>>>
>>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>>>>
>>>> I propose that the following issues all require a change to the model
>>>> version, and thus should be pushed back to 4.0.0 (or later)
>>>>
>>>> http://jira.codehaus.org/browse/MNG-1977 Global dependency
>>>> exclusions<http://jira.codehaus.org/browse/MNG-1977>
>>>> http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>>>> attributes<http://jira.codehaus.org/browse/MNG-3397>
>>>> http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>>>> fragments<http://jira.codehaus.org/browse/MNG-5102>
>>>> http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported
>>> for
>>>> parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>>>> http://jira.codehaus.org/browse/MNG-2216 Add default encodings section
>>> to
>>>> POM <http://jira.codehaus.org/browse/MNG-2216>
>>>> http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
>>>> project version matches a regex <
>>> http://jira.codehaus.org/browse/MNG-3826>
>>>> http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>>>> dependencies that implement an API or provide other dependencies
>>>> http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>>> Configuration
>>>> http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>>> profiles
>>>> http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
>>>> support overriding project.build.directory (WONTFIX candidate?)
>>>> http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
>>>> declaration of IRC channels
>>>>
>>>> The following issues require that the deployed pom be different from the
>>>> on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again
>>> I
>>>> think these should be pushed back to 4.0.0 (or later)
>>>>
>>>> http://jira.codehaus.org/browse/MNG-624 Automatic parent
>>>> versioning<http://jira.codehaus.org/browse/MNG-624>
>>>>
>>>> I would propose that we move these issues into a 4.0 bucket... that will
>>>> bring us down to 31 issues open for 3.2.0
>>>>
>>>> Thoughts?
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> ----------------------------------------------------------
>>> Jason van Zyl
>>> Founder, Apache Maven
>>> http://twitter.com/jvanzyl
>>> ---------------------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: 3.2.0 Bug Scrub
Posted by Jörg Schaible <jo...@gmx.de>.
Stephen Connolly wrote:
> Added... now how come it wasn't on the issue tracker list
Thanks!
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
Added... now how come it wasn't on the issue tracker list
On 13 January 2014 19:09, Jörg Schaible <jo...@gmx.de> wrote:
> Hi Stephen,
>
> Stephen Connolly wrote:
>
> > I have added a wiki page summary of this discussion:
> >
> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>
> I miss MNG-5207 bitterly on the radar. M3 is not able to calculate a proper
> build sequence and uses either a stale SNAPSHOT or the build breaks
> completely.
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: 3.2.0 Bug Scrub
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Stephen,
Stephen Connolly wrote:
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
I miss MNG-5207 bitterly on the radar. M3 is not able to calculate a proper
build sequence and uses either a stale SNAPSHOT or the build breaks
completely.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Olivier Lamy <ol...@apache.org>.
Even this an old problem...
I still believe http://jira.codehaus.org/browse/MNG-5265 is a
potential security issue.
But no time ATM to work on that.
On 14 January 2014 00:24, Stephen Connolly
<st...@gmail.com> wrote:
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>
> Reminder, I pegged some action items against Benson, Olivier, Kristian &
> Jason... See the action required section... mostly just status updates.
>
>
> On 7 January 2014 22:03, Stephen Connolly <st...@gmail.com>
> wrote:
>>
>> I like "Nike" style issues (just commit it)
>>
>>
>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>
>>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>>>
>>>> Add it if you promise to implement it, otherwise put it against 3.2.x
>>>> for
>>>> the patch releases.
>>>
>>>
>>> That is not going to be a problem because I have a patch and can commit
>>> right away.
>>>
>>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>
>>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>>>
>>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>>> some
>>>>>> more?
>>>>>>
>>>>>
>>>>> I'd like to add another issue to 3.2:
>>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
>>>>> 8601-style manner
>>>>>
>>>>> It adds readability to the time output.
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> --
>> Sent from my phone
>
>
--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
No problem, I just want to keep us moving forward... either trimming the
scope or getting things done until we can cut 3.2.0 and start thinking
about useful problems for the community, such as model version 5.0.0 ;-)
On 13 January 2014 15:43, Jason van Zyl <ja...@tesla.io> wrote:
> I need another few hours to finish one thing I'm working on, and then I'll
> take another walk through JIRA. I have 8 customer branches I need to rebase
> and clean up before I get to it.
>
> On Jan 13, 2014, at 8:24 AM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>
> Reminder, I pegged some action items against Benson, Olivier, Kristian &
> Jason... See the action required section... mostly just status updates.
>
>
> On 7 January 2014 22:03, Stephen Connolly <stephen.alan.connolly@gmail.com
> > wrote:
>
>> I like "Nike" style issues (just commit it)
>>
>>
>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>
>>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>>
>>>> Add it if you promise to implement it, otherwise put it against 3.2.x
>>>> for
>>>> the patch releases.
>>>>
>>>
>>> That is not going to be a problem because I have a patch and can commit
>>> right away.
>>>
>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>
>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>>>
>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>>> some
>>>>>> more?
>>>>>>
>>>>>>
>>>>> I'd like to add another issue to 3.2:
>>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
>>>>> 8601-style manner
>>>>>
>>>>> It adds readability to the time output.
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> --
>> Sent from my phone
>>
>
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
>
>
>
>
>
>
>
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@tesla.io>.
I need another few hours to finish one thing I'm working on, and then I'll take another walk through JIRA. I have 8 customer branches I need to rebase and clean up before I get to it.
On Jan 13, 2014, at 8:24 AM, Stephen Connolly <st...@gmail.com> wrote:
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>
> Reminder, I pegged some action items against Benson, Olivier, Kristian & Jason... See the action required section... mostly just status updates.
>
>
> On 7 January 2014 22:03, Stephen Connolly <st...@gmail.com> wrote:
> I like "Nike" style issues (just commit it)
>
>
> On Tuesday, 7 January 2014, Michael Osipov wrote:
> Am 2014-01-07 22:38, schrieb Stephen Connolly:
> Add it if you promise to implement it, otherwise put it against 3.2.x for
> the patch releases.
>
> That is not going to be a problem because I have a patch and can commit right away.
>
> On Tuesday, 7 January 2014, Michael Osipov wrote:
>
> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>
> OK we are now at 38 open issues.... anyone else feel like scrubbing some
> more?
>
>
> I'd like to add another issue to 3.2:
> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
> 8601-style manner
>
> It adds readability to the time output.
>
> Mike
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> --
> Sent from my phone
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
On Monday, 13 January 2014, Benson Margulies wrote:
> In XML Schema, these aren't 'comments', these are 'comment nodes' --
>
> <documentation>This is not the type you are looking for</documentation>
>
> which is what I'm suggesting is reasonable,
Yep I agree... But it's out of scope for 3.2.0... Let's discuss in a few
weeks when 3.2.0 is out the door and we are starting the 4.0.0 sprint
as opposed to capturing
> text from <!-- Ceçi n'est pas documentation. --> comments. If I've
> missed something I'd be happy to be educated.
>
>
> On Mon, Jan 13, 2014 at 12:56 PM, Paul Benedict <pb...@apache.org>
> wrote:
> > Dedicated comments nodes can be useful. For example, both XML Schema
> format
> > and the Spring Framework schemas allow dedicated comment nodes. I don't
> have
> > any opinion if dedicated comment nodes are useful for Maven POMs but I am
> > willing to listen and learn.
> >
> >
> > On Mon, Jan 13, 2014 at 10:59 AM, Stephen Connolly
> > <st...@gmail.com> wrote:
> >>
> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
> wrote:
> >>
> >> > Why isn't this copied to the dev list?
> >> >
> >>
> >> It was, check the headers
> >>
> >>
> >> >
> >> >
> >>
> >> > I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
> >> > remotely under consideration.
> >>
> >>
> >> I moved MNG-3879 to 4.0 backlog.
> >>
> >> Your action was to split out the second issue... should really live in
> the
> >> dependency plugin and depend on MNG-3879
> >>
> >> > The second part is a goal that I would propose to call
> 'dependency-map'.
> >> This would produce a formatted map of the dependency tree – enriched, of
> >> course, by the comments in the first part.
> >>
> >>
> >>
> >> > It is a proposal, to start with, to add
> >> > an element to the POM:
> >> >
> >> > <dependency>
> >> > <explanation>some text </explanation>
> >> > ...
> >> > </dependency>
> >> >
> >> > which would make it a job for 4.0. It was never my intention to
> >> > propose to capture <!-- --> XML comments, that's evil in my view.
> >> >
> >> > So far, the feedback I've received is that the stuff I've written
> >> > about POM evolution is crap. Fine, it's crap.
> >>
> >>
> >> I don't think necessarily so... once 3.2.0 is out we will be looking at
> >> model version 5.0.0 and pom evolution is on the cards. I like the idea
> of
> >> dedicated documentation nodes in the pom as otherwise it can be harder
> to
> >> maintain comments etc, when people use formatting tools etc. The great
> >> thing with a descriptive text node is that everyone except tooling can
> >> ignore it
> >>
> >>
> >> > So JIRAs like this
> >> > should just be closed down when they have my name on them.
> >> >
> >> > On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
> >> > <st...@gmail.com> wrote:
> >> > > I have added a wiki page summary of this discussion:
> >> > >
> >> > >
> >> > >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
> >> > >
> >> > > Reminder, I pegged some action items against Benson, Olivier,
> Kristian
> >> > > &
> >> > > Jason... See the action required section... mostly just status
> >> > > updates.
> >> > >
> >> > >
> >> > > On 7 January 2014 22:03, Stephen Connolly <
> >> > stephen.alan.connolly@gmail.com>
> >> > > wrote:
> >> > >>
> >> > >> I like "Nike" style issues (just commit it)
> >> > >>
> >> > >>
> >> > >> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >> > >>>
> >> > >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
> >> > >>>>
> >> > >>>> Add it if you promise to implement it, otherwise put it against
> >> > >>>> 3.2.x
> >> > >>>> for
> >> > >>>> the patch releases.
> >> > >>>
>
--
Sent from my phone
Re: 3.2.0 Bug Scrub
Posted by Benson Margulies <bi...@gmail.com>.
In XML Schema, these aren't 'comments', these are 'comment nodes' --
<documentation>This is not the type you are looking for</documentation>
which is what I'm suggesting is reasonable, as opposed to capturing
text from <!-- Ceçi n'est pas documentation. --> comments. If I've
missed something I'd be happy to be educated.
On Mon, Jan 13, 2014 at 12:56 PM, Paul Benedict <pb...@apache.org> wrote:
> Dedicated comments nodes can be useful. For example, both XML Schema format
> and the Spring Framework schemas allow dedicated comment nodes. I don't have
> any opinion if dedicated comment nodes are useful for Maven POMs but I am
> willing to listen and learn.
>
>
> On Mon, Jan 13, 2014 at 10:59 AM, Stephen Connolly
> <st...@gmail.com> wrote:
>>
>> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com> wrote:
>>
>> > Why isn't this copied to the dev list?
>> >
>>
>> It was, check the headers
>>
>>
>> >
>> >
>>
>> > I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>> > remotely under consideration.
>>
>>
>> I moved MNG-3879 to 4.0 backlog.
>>
>> Your action was to split out the second issue... should really live in the
>> dependency plugin and depend on MNG-3879
>>
>> > The second part is a goal that I would propose to call 'dependency-map'.
>> This would produce a formatted map of the dependency tree – enriched, of
>> course, by the comments in the first part.
>>
>>
>>
>> > It is a proposal, to start with, to add
>> > an element to the POM:
>> >
>> > <dependency>
>> > <explanation>some text </explanation>
>> > ...
>> > </dependency>
>> >
>> > which would make it a job for 4.0. It was never my intention to
>> > propose to capture <!-- --> XML comments, that's evil in my view.
>> >
>> > So far, the feedback I've received is that the stuff I've written
>> > about POM evolution is crap. Fine, it's crap.
>>
>>
>> I don't think necessarily so... once 3.2.0 is out we will be looking at
>> model version 5.0.0 and pom evolution is on the cards. I like the idea of
>> dedicated documentation nodes in the pom as otherwise it can be harder to
>> maintain comments etc, when people use formatting tools etc. The great
>> thing with a descriptive text node is that everyone except tooling can
>> ignore it
>>
>>
>> > So JIRAs like this
>> > should just be closed down when they have my name on them.
>> >
>> > On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>> > <st...@gmail.com> wrote:
>> > > I have added a wiki page summary of this discussion:
>> > >
>> > >
>> > > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>> > >
>> > > Reminder, I pegged some action items against Benson, Olivier, Kristian
>> > > &
>> > > Jason... See the action required section... mostly just status
>> > > updates.
>> > >
>> > >
>> > > On 7 January 2014 22:03, Stephen Connolly <
>> > stephen.alan.connolly@gmail.com>
>> > > wrote:
>> > >>
>> > >> I like "Nike" style issues (just commit it)
>> > >>
>> > >>
>> > >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>> > >>>
>> > >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>> > >>>>
>> > >>>> Add it if you promise to implement it, otherwise put it against
>> > >>>> 3.2.x
>> > >>>> for
>> > >>>> the patch releases.
>> > >>>
>> > >>>
>> > >>> That is not going to be a problem because I have a patch and can
>> > >>> commit
>> > >>> right away.
>> > >>>
>> > >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>> > >>>>
>> > >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>> > >>>>>
>> > >>>>>> OK we are now at 38 open issues.... anyone else feel like
>> > >>>>>> scrubbing
>> > >>>>>> some
>> > >>>>>> more?
>> > >>>>>>
>> > >>>>>
>> > >>>>> I'd like to add another issue to 3.2:
>> > >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an
>> > ISO
>> > >>>>> 8601-style manner
>> > >>>>>
>> > >>>>> It adds readability to the time output.
>> > >>>>>
>> > >>>>> Mike
>> > >>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>> ---------------------------------------------------------------------
>> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>> > >>>>>
>> > >>>>>
>> > >>>>
>> > >>>
>> > >>>
>> > >>>
>> > >>> ---------------------------------------------------------------------
>> > >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> > >>> For additional commands, e-mail: dev-help@maven.apache.org
>> > >>>
>> > >>
>> > >>
>> > >> --
>> > >> Sent from my phone
>> > >
>> > >
>> >
>
>
>
>
> --
> Cheers,
> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Paul Benedict <pb...@apache.org>.
Dedicated comments nodes can be useful. For example, both XML Schema format
and the Spring Framework schemas allow dedicated comment nodes. I don't
have any opinion if dedicated comment nodes are useful for Maven POMs but I
am willing to listen and learn.
On Mon, Jan 13, 2014 at 10:59 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com> wrote:
>
> > Why isn't this copied to the dev list?
> >
>
> It was, check the headers
>
>
> >
> >
> > I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
> > remotely under consideration.
>
>
> I moved MNG-3879 to 4.0 backlog.
>
> Your action was to split out the second issue... should really live in the
> dependency plugin and depend on MNG-3879
>
> > The second part is a goal that I would propose to call 'dependency-map'.
> This would produce a formatted map of the dependency tree – enriched, of
> course, by the comments in the first part.
>
>
>
> > It is a proposal, to start with, to add
> > an element to the POM:
> >
> > <dependency>
> > <explanation>some text </explanation>
> > ...
> > </dependency>
> >
> > which would make it a job for 4.0. It was never my intention to
> > propose to capture <!-- --> XML comments, that's evil in my view.
> >
> > So far, the feedback I've received is that the stuff I've written
> > about POM evolution is crap. Fine, it's crap.
>
>
> I don't think necessarily so... once 3.2.0 is out we will be looking at
> model version 5.0.0 and pom evolution is on the cards. I like the idea of
> dedicated documentation nodes in the pom as otherwise it can be harder to
> maintain comments etc, when people use formatting tools etc. The great
> thing with a descriptive text node is that everyone except tooling can
> ignore it
>
>
> > So JIRAs like this
> > should just be closed down when they have my name on them.
> >
> > On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
> > <st...@gmail.com> wrote:
> > > I have added a wiki page summary of this discussion:
> > >
> > >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
> > >
> > > Reminder, I pegged some action items against Benson, Olivier, Kristian
> &
> > > Jason... See the action required section... mostly just status updates.
> > >
> > >
> > > On 7 January 2014 22:03, Stephen Connolly <
> > stephen.alan.connolly@gmail.com>
> > > wrote:
> > >>
> > >> I like "Nike" style issues (just commit it)
> > >>
> > >>
> > >> On Tuesday, 7 January 2014, Michael Osipov wrote:
> > >>>
> > >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
> > >>>>
> > >>>> Add it if you promise to implement it, otherwise put it against
> 3.2.x
> > >>>> for
> > >>>> the patch releases.
> > >>>
> > >>>
> > >>> That is not going to be a problem because I have a patch and can
> commit
> > >>> right away.
> > >>>
> > >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
> > >>>>
> > >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
> > >>>>>
> > >>>>>> OK we are now at 38 open issues.... anyone else feel like
> scrubbing
> > >>>>>> some
> > >>>>>> more?
> > >>>>>>
> > >>>>>
> > >>>>> I'd like to add another issue to 3.2:
> > >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an
> > ISO
> > >>>>> 8601-style manner
> > >>>>>
> > >>>>> It adds readability to the time output.
> > >>>>>
> > >>>>> Mike
> > >>>>>
> > >>>>>
> > >>>>>
> ---------------------------------------------------------------------
> > >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >>> For additional commands, e-mail: dev-help@maven.apache.org
> > >>>
> > >>
> > >>
> > >> --
> > >> Sent from my phone
> > >
> > >
> >
>
--
Cheers,
Paul
Re: 3.2.0 Bug Scrub
Posted by Robert Scholte <rf...@apache.org>.
Op Sun, 19 Jan 2014 09:59:25 +0100 schreef Stephen Connolly
<st...@gmail.com>:
> On Saturday, 18 January 2014, Jason van Zyl <ja...@takari.io> wrote:
>
>> I don't think you want the CI element propagating. In the case of a
>> multi-module project you're likely only to have one CI job for that set
>> of
>> projects.
>
>
> But in the multi module case, the CI for the multi-module *is the exact
> same* as for the children.
>
>
It's not that one-on-one.
A CI-plan/job checks out a specific scm-root and executes that. All
children are just part of that execution.
So if you follow the link from a module and it would inherit the value,
you'll end up on a different folder. So I agree with Jason here.
Maybe the real question is: when is this element used? If it is a
project-info-report, we can improve it by saying something like: "Is part
of ...".
I'm not aware of other usages of this element.
Robert
>> I don't think it makes sense to inherit this. In our lineage for all
>> the
>> Maven projects it probably would work, or be useful, to inherit
>> anything.
>> We need to define the jobs in each project and I wouldn't want to try to
>> guess inheritance rules for various CI systems. We'll end up with the
>> same
>> nonsense trying to inherent SCM path elements.
>
>
> I wouldn't do the path additions at all.
>
>
>>
>> So I would say close MNG-2807 as won't fix.
>
>
> I have no strong view either way... What is the opinion of others?
>
>
>>
>> Mailing lists is debatable. I don't really have a strong opinion.
>
>
> The counter-argument against mailing list is an uber-parent pom that has
> its own mailing list for discussing what goes in that uber-parent...
>
> I think modelVersion 5.0.0 should have an <inherit> tag for these things
> so
> that parents can differentiate correctly...
>
> Which now that I think about it makes me suggest push back to
> modelVersion
> bump?
>
>
>>
>> On Jan 17, 2014, at 11:04 AM, Robert Scholte <rf...@apache.org>
>> wrote:
>>
>> > Hi,
>> >
>> > Regarding MNG-3124 (Inherit mailing lists from parent POM) and
>> MNG-2807
>> (ciManagement from parent is not merging with children)
>> > See MavenModelMerger[1]. This class extends the ModelMerger[2], a
>> class
>> which is a handcrafted class as if it was generated by modello.
>> > It seems like Benjamin wanted wanted to change the default behavior of
>> the ModelMerger for some good reason.
>> > So it seems intended, maybe we need to dig a bit deeper to find out
>> the
>> actual reason.
>> >
>> > Robert
>> >
>> > [1]
>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/merge/MavenModelMerger.java;hb=HEAD
>> > [2]
>> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model/src/main/java/org/apache/maven/model/merge/ModelMerger.java;hb=HEAD
>> >
>> >
>> > Op Fri, 17 Jan 2014 12:41:40 +0100 schreef Stephen Connolly <
>> stephen.alan.connolly@gmail.com>:
>> >
>> >> Done... we are now down to 17 issues still in scope for 3.2.0
>> >>
>> >>
>> >> On 17 January 2014 11:38, Stephen Connolly
>> >> <st...@gmail.com>wrote:
>> >>
>> >>> OK, 4 days and no objections... these are being pushed out of scope
>> for
>> >>> 3.2.0
>> >>>
>> >>>
>> >>> On 13 January 2014 18:07, Stephen Connolly <
>> >>> stephen.alan.connolly@gmail.com> wrote:
>> >>>
>> >>>> The following issues I proposed to move to 4.x. I have not heard
>> anything
>> >>>> to the contrary... shall I pull the trigger on these?
>> >>>>
>> >>>> - http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error
>> if
>> >>>> pom contains a dependency with two different versions.
>> >>>> - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings
>> should
>> >>>> specify phase bindings in terms of general functionality type
>> >>>>
>> >>>>
>> >>>> - http://jira.codehaus.org/browse/MNG-841 Support customization
>> of
>> >>>> default excludes
>> >>>>
>> >>>>
>> >>>> - http://jira.codehaus.org/browse/MNG-193 symmetry for outputs
>> of a
>> >>>> plugin
>> >>>>
>> >>>>
>> >>>> - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies'
>> scopes
>> >>>> to be managed without explicit versions
>> >>>> - http://jira.codehaus.org/browse/MNG-3825 Dependencies with
>> >>>> classifier should not always require a version.
>> >>>> - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or
>> >>>> execution
>> >>>> -
>> >>>> - 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
>> >>>>
>> >>>>
>> >>>> - http://jira.codehaus.org/browse/MNG-1867 deprecate system
>> scope,
>> >>>> analyse other use cases
>> >>>> - <http://jira.codehaus.org/browse/MNG-4508>Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
On Saturday, 18 January 2014, Jason van Zyl <ja...@takari.io> wrote:
> I don't think you want the CI element propagating. In the case of a
> multi-module project you're likely only to have one CI job for that set of
> projects.
But in the multi module case, the CI for the multi-module *is the exact
same* as for the children.
> I don't think it makes sense to inherit this. In our lineage for all the
> Maven projects it probably would work, or be useful, to inherit anything.
> We need to define the jobs in each project and I wouldn't want to try to
> guess inheritance rules for various CI systems. We'll end up with the same
> nonsense trying to inherent SCM path elements.
I wouldn't do the path additions at all.
>
> So I would say close MNG-2807 as won't fix.
I have no strong view either way... What is the opinion of others?
>
> Mailing lists is debatable. I don't really have a strong opinion.
The counter-argument against mailing list is an uber-parent pom that has
its own mailing list for discussing what goes in that uber-parent...
I think modelVersion 5.0.0 should have an <inherit> tag for these things so
that parents can differentiate correctly...
Which now that I think about it makes me suggest push back to modelVersion
bump?
>
> On Jan 17, 2014, at 11:04 AM, Robert Scholte <rf...@apache.org> wrote:
>
> > Hi,
> >
> > Regarding MNG-3124 (Inherit mailing lists from parent POM) and MNG-2807
> (ciManagement from parent is not merging with children)
> > See MavenModelMerger[1]. This class extends the ModelMerger[2], a class
> which is a handcrafted class as if it was generated by modello.
> > It seems like Benjamin wanted wanted to change the default behavior of
> the ModelMerger for some good reason.
> > So it seems intended, maybe we need to dig a bit deeper to find out the
> actual reason.
> >
> > Robert
> >
> > [1]
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/merge/MavenModelMerger.java;hb=HEAD
> > [2]
> https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model/src/main/java/org/apache/maven/model/merge/ModelMerger.java;hb=HEAD
> >
> >
> > Op Fri, 17 Jan 2014 12:41:40 +0100 schreef Stephen Connolly <
> stephen.alan.connolly@gmail.com>:
> >
> >> Done... we are now down to 17 issues still in scope for 3.2.0
> >>
> >>
> >> On 17 January 2014 11:38, Stephen Connolly
> >> <st...@gmail.com>wrote:
> >>
> >>> OK, 4 days and no objections... these are being pushed out of scope for
> >>> 3.2.0
> >>>
> >>>
> >>> On 13 January 2014 18:07, Stephen Connolly <
> >>> stephen.alan.connolly@gmail.com> wrote:
> >>>
> >>>> The following issues I proposed to move to 4.x. I have not heard
> anything
> >>>> to the contrary... shall I pull the trigger on these?
> >>>>
> >>>> - http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error
> if
> >>>> pom contains a dependency with two different versions.
> >>>> - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should
> >>>> specify phase bindings in terms of general functionality type
> >>>>
> >>>>
> >>>> - http://jira.codehaus.org/browse/MNG-841 Support customization of
> >>>> default excludes
> >>>>
> >>>>
> >>>> - http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a
> >>>> plugin
> >>>>
> >>>>
> >>>> - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies'
> scopes
> >>>> to be managed without explicit versions
> >>>> - http://jira.codehaus.org/browse/MNG-3825 Dependencies with
> >>>> classifier should not always require a version.
> >>>> - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or
> >>>> execution
> >>>> -
> >>>> - 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
> >>>>
> >>>>
> >>>> - http://jira.codehaus.org/browse/MNG-1867 deprecate system scope,
> >>>> analyse other use cases
> >>>> - <http://jira.codehaus.org/browse/MNG-4508>Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
>
>
>
>
>
>
>
--
Sent from my phone
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@takari.io>.
I don't think you want the CI element propagating. In the case of a multi-module project you're likely only to have one CI job for that set of projects. I don't think it makes sense to inherit this. In our lineage for all the Maven projects it probably would work, or be useful, to inherit anything. We need to define the jobs in each project and I wouldn't want to try to guess inheritance rules for various CI systems. We'll end up with the same nonsense trying to inherent SCM path elements.
So I would say close MNG-2807 as won't fix.
Mailing lists is debatable. I don't really have a strong opinion.
On Jan 17, 2014, at 11:04 AM, Robert Scholte <rf...@apache.org> wrote:
> Hi,
>
> Regarding MNG-3124 (Inherit mailing lists from parent POM) and MNG-2807 (ciManagement from parent is not merging with children)
> See MavenModelMerger[1]. This class extends the ModelMerger[2], a class which is a handcrafted class as if it was generated by modello.
> It seems like Benjamin wanted wanted to change the default behavior of the ModelMerger for some good reason.
> So it seems intended, maybe we need to dig a bit deeper to find out the actual reason.
>
> Robert
>
> [1] https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/merge/MavenModelMerger.java;hb=HEAD
> [2] https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model/src/main/java/org/apache/maven/model/merge/ModelMerger.java;hb=HEAD
>
>
> Op Fri, 17 Jan 2014 12:41:40 +0100 schreef Stephen Connolly <st...@gmail.com>:
>
>> Done... we are now down to 17 issues still in scope for 3.2.0
>>
>>
>> On 17 January 2014 11:38, Stephen Connolly
>> <st...@gmail.com>wrote:
>>
>>> OK, 4 days and no objections... these are being pushed out of scope for
>>> 3.2.0
>>>
>>>
>>> On 13 January 2014 18:07, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> The following issues I proposed to move to 4.x. I have not heard anything
>>>> to the contrary... shall I pull the trigger on these?
>>>>
>>>> - http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if
>>>> pom contains a dependency with two different versions.
>>>> - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should
>>>> specify phase bindings in terms of general functionality type
>>>>
>>>>
>>>> - http://jira.codehaus.org/browse/MNG-841 Support customization of
>>>> default excludes
>>>>
>>>>
>>>> - http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a
>>>> plugin
>>>>
>>>>
>>>> - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies' scopes
>>>> to be managed without explicit versions
>>>> - http://jira.codehaus.org/browse/MNG-3825 Dependencies with
>>>> classifier should not always require a version.
>>>> - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or
>>>> execution
>>>> -
>>>> - 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
>>>>
>>>>
>>>> - http://jira.codehaus.org/browse/MNG-1867 deprecate system scope,
>>>> analyse other use cases
>>>> - http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding
>>>> artifactId to site urls
>>>>
>>>>
>>>> I would like some discussion on this one before making a call one way or
>>>> the other
>>>>
>>>> - http://jira.codehaus.org/browse/MNG-4173 Remove automatic version
>>>> resolution for POM plugins
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On 13 January 2014 18:02, Stephen Connolly <
>>>> stephen.alan.connolly@gmail.com> wrote:
>>>>
>>>>> wiki updated ;-)
>>>>>
>>>>>
>>>>> On 13 January 2014 17:56, Benson Margulies <bi...@gmail.com>wrote:
>>>>>
>>>>>> Done.
>>>>>>
>>>>>> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
>>>>>> <bi...@gmail.com> wrote:
>>>>>> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
>>>>>> > <st...@gmail.com> wrote:
>>>>>> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
>>>>>> wrote:
>>>>>> >>>
>>>>>> >>> Why isn't this copied to the dev list?
>>>>>> >>
>>>>>> >>
>>>>>> >> It was, check the headers
>>>>>> >
>>>>>> > I see. GMail has learned a new prank, which is to skip 'dev' in the
>>>>>> > brief listing of who is on the email.
>>>>>> >
>>>>>> >>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>>
>>>>>> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>>>>>> >>> remotely under consideration.
>>>>>> >>
>>>>>> >>
>>>>>> >> I moved MNG-3879 to 4.0 backlog.
>>>>>> >>
>>>>>> >> Your action was to split out the second issue... should really live
>>>>>> in the
>>>>>> >> dependency plugin and depend on MNG-3879
>>>>>> >
>>>>>> > OK, seems less that wildly important, but I'll do it.
>>>>>> >
>>>>>> >>
>>>>>> >>> The second part is a goal that I would propose to call
>>>>>> 'dependency-map'.
>>>>>> >>> This would produce a formatted map of the dependency tree –
>>>>>> enriched, of
>>>>>> >>> course, by the comments in the first part.
>>>>>> >>
>>>>>> >>
>>>>>> >>>
>>>>>> >>> It is a proposal, to start with, to add
>>>>>> >>> an element to the POM:
>>>>>> >>>
>>>>>> >>> <dependency>
>>>>>> >>> <explanation>some text </explanation>
>>>>>> >>> ...
>>>>>> >>> </dependency>
>>>>>> >>>
>>>>>> >>> which would make it a job for 4.0. It was never my intention to
>>>>>> >>> propose to capture <!-- --> XML comments, that's evil in my view.
>>>>>> >>>
>>>>>> >>> So far, the feedback I've received is that the stuff I've written
>>>>>> >>> about POM evolution is crap. Fine, it's crap.
>>>>>> >>
>>>>>> >>
>>>>>> >> I don't think necessarily so... once 3.2.0 is out we will be looking
>>>>>> at
>>>>>> >> model version 5.0.0 and pom evolution is on the cards. I like the
>>>>>> idea of
>>>>>> >> dedicated documentation nodes in the pom as otherwise it can be
>>>>>> harder to
>>>>>> >> maintain comments etc, when people use formatting tools etc. The
>>>>>> great thing
>>>>>> >> with a descriptive text node is that everyone except tooling can
>>>>>> ignore it
>>>>>> >>
>>>>>> >>>
>>>>>> >>> So JIRAs like this
>>>>>> >>> should just be closed down when they have my name on them.
>>>>>> >>>
>>>>>> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>>>>>> >>> <st...@gmail.com> wrote:
>>>>>> >>> > I have added a wiki page summary of this discussion:
>>>>>> >>> >
>>>>>> >>> >
>>>>>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>>>>>> >>> >
>>>>>> >>> > Reminder, I pegged some action items against Benson, Olivier,
>>>>>> Kristian &
>>>>>> >>> > Jason... See the action required section... mostly just status
>>>>>> updates.
>>>>>> >>> >
>>>>>> >>> >
>>>>>> >>> > On 7 January 2014 22:03, Stephen Connolly
>>>>>> >>> > <st...@gmail.com>
>>>>>> >>> > wrote:
>>>>>> >>> >>
>>>>>> >>> >> I like "Nike" style issues (just commit it)
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>>> >>> >>>
>>>>>> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>>>>> >>> >>>>
>>>>>> >>> >>>> Add it if you promise to implement it, otherwise put it
>>>>>> against 3.2.x
>>>>>> >>> >>>> for
>>>>>> >>> >>>> the patch releases.
>>>>>> >>> >>>
>>>>>> >>> >>>
>>>>>> >>> >>> That is not going to be a problem because I have a patch and can
>>>>>> >>> >>> commit
>>>>>> >>> >>> right away.
>>>>>> >>> >>>
>>>>>> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>>> >>> >>>>
>>>>>> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>>>> >>> >>>>>
>>>>>> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like
>>>>>> scrubbing
>>>>>> >>> >>>>>> some
>>>>>> >>> >>>>>> more?
>>>>>> >>> >>>>>>
>>>>>> >>> >>>>>
>>>>>> >>> >>>>> I'd like to add another issue to 3.2:
>>>>>> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times
>>>>>> in an
>>>>>> >>> >>>>> ISO
>>>>>> >>> >>>>> 8601-style manner
>>>>>> >>> >>>>>
>>>>>> >>> >>>>> It adds readability to the time output.
>>>>>> >>> >>>>>
>>>>>> >>> >>>>> Mike
>>>>>> >>> >>>>>
>>>>>> >>> >>>>>
>>>>>> >>> >>>>>
>>>>>> >>> >>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>> >>> >>>>>
>>>>>> >>> >>>>>
>>>>>> >>> >>>>
>>>>>> >>> >>>
>>>>>> >>> >>>
>>>>>> >>> >>>
>>>>>> ---------------------------------------------------------------------
>>>>>> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>> >>> >>>
>>>>>> >>> >>
>>>>>> >>> >>
>>>>>> >>> >> --
>>>>>> >>> >> Sent from my phone
>>>>>> >>> >
>>>>>> >>> >
>>>>>> >>
>>>>>> >>
>>>>>>
>>>>>
>>>>>
>>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: 3.2.0 Bug Scrub
Posted by Robert Scholte <rf...@apache.org>.
Hi,
Regarding MNG-3124 (Inherit mailing lists from parent POM) and MNG-2807
(ciManagement from parent is not merging with children)
See MavenModelMerger[1]. This class extends the ModelMerger[2], a class
which is a handcrafted class as if it was generated by modello.
It seems like Benjamin wanted wanted to change the default behavior of the
ModelMerger for some good reason.
So it seems intended, maybe we need to dig a bit deeper to find out the
actual reason.
Robert
[1]
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/merge/MavenModelMerger.java;hb=HEAD
[2]
https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model/src/main/java/org/apache/maven/model/merge/ModelMerger.java;hb=HEAD
Op Fri, 17 Jan 2014 12:41:40 +0100 schreef Stephen Connolly
<st...@gmail.com>:
> Done... we are now down to 17 issues still in scope for 3.2.0
>
>
> On 17 January 2014 11:38, Stephen Connolly
> <st...@gmail.com>wrote:
>
>> OK, 4 days and no objections... these are being pushed out of scope for
>> 3.2.0
>>
>>
>> On 13 January 2014 18:07, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> The following issues I proposed to move to 4.x. I have not heard
>>> anything
>>> to the contrary... shall I pull the trigger on these?
>>>
>>> - http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if
>>> pom contains a dependency with two different versions.
>>> - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should
>>> specify phase bindings in terms of general functionality type
>>>
>>>
>>> - http://jira.codehaus.org/browse/MNG-841 Support customization of
>>> default excludes
>>>
>>>
>>> - http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a
>>> plugin
>>>
>>>
>>> - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies'
>>> scopes
>>> to be managed without explicit versions
>>> - http://jira.codehaus.org/browse/MNG-3825 Dependencies with
>>> classifier should not always require a version.
>>> - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or
>>> execution
>>> -
>>> - 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
>>>
>>>
>>> - http://jira.codehaus.org/browse/MNG-1867 deprecate system scope,
>>> analyse other use cases
>>> - http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding
>>> artifactId to site urls
>>>
>>>
>>> I would like some discussion on this one before making a call one way
>>> or
>>> the other
>>>
>>> - http://jira.codehaus.org/browse/MNG-4173 Remove automatic version
>>> resolution for POM plugins
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 13 January 2014 18:02, Stephen Connolly <
>>> stephen.alan.connolly@gmail.com> wrote:
>>>
>>>> wiki updated ;-)
>>>>
>>>>
>>>> On 13 January 2014 17:56, Benson Margulies
>>>> <bi...@gmail.com>wrote:
>>>>
>>>>> Done.
>>>>>
>>>>> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
>>>>> <bi...@gmail.com> wrote:
>>>>> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
>>>>> > <st...@gmail.com> wrote:
>>>>> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
>>>>> wrote:
>>>>> >>>
>>>>> >>> Why isn't this copied to the dev list?
>>>>> >>
>>>>> >>
>>>>> >> It was, check the headers
>>>>> >
>>>>> > I see. GMail has learned a new prank, which is to skip 'dev' in the
>>>>> > brief listing of who is on the email.
>>>>> >
>>>>> >>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>>>>> >>> remotely under consideration.
>>>>> >>
>>>>> >>
>>>>> >> I moved MNG-3879 to 4.0 backlog.
>>>>> >>
>>>>> >> Your action was to split out the second issue... should really
>>>>> live
>>>>> in the
>>>>> >> dependency plugin and depend on MNG-3879
>>>>> >
>>>>> > OK, seems less that wildly important, but I'll do it.
>>>>> >
>>>>> >>
>>>>> >>> The second part is a goal that I would propose to call
>>>>> 'dependency-map'.
>>>>> >>> This would produce a formatted map of the dependency tree –
>>>>> enriched, of
>>>>> >>> course, by the comments in the first part.
>>>>> >>
>>>>> >>
>>>>> >>>
>>>>> >>> It is a proposal, to start with, to add
>>>>> >>> an element to the POM:
>>>>> >>>
>>>>> >>> <dependency>
>>>>> >>> <explanation>some text </explanation>
>>>>> >>> ...
>>>>> >>> </dependency>
>>>>> >>>
>>>>> >>> which would make it a job for 4.0. It was never my intention to
>>>>> >>> propose to capture <!-- --> XML comments, that's evil in my view.
>>>>> >>>
>>>>> >>> So far, the feedback I've received is that the stuff I've written
>>>>> >>> about POM evolution is crap. Fine, it's crap.
>>>>> >>
>>>>> >>
>>>>> >> I don't think necessarily so... once 3.2.0 is out we will be
>>>>> looking
>>>>> at
>>>>> >> model version 5.0.0 and pom evolution is on the cards. I like the
>>>>> idea of
>>>>> >> dedicated documentation nodes in the pom as otherwise it can be
>>>>> harder to
>>>>> >> maintain comments etc, when people use formatting tools etc. The
>>>>> great thing
>>>>> >> with a descriptive text node is that everyone except tooling can
>>>>> ignore it
>>>>> >>
>>>>> >>>
>>>>> >>> So JIRAs like this
>>>>> >>> should just be closed down when they have my name on them.
>>>>> >>>
>>>>> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>>>>> >>> <st...@gmail.com> wrote:
>>>>> >>> > I have added a wiki page summary of this discussion:
>>>>> >>> >
>>>>> >>> >
>>>>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>>>>> >>> >
>>>>> >>> > Reminder, I pegged some action items against Benson, Olivier,
>>>>> Kristian &
>>>>> >>> > Jason... See the action required section... mostly just status
>>>>> updates.
>>>>> >>> >
>>>>> >>> >
>>>>> >>> > On 7 January 2014 22:03, Stephen Connolly
>>>>> >>> > <st...@gmail.com>
>>>>> >>> > wrote:
>>>>> >>> >>
>>>>> >>> >> I like "Nike" style issues (just commit it)
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>> >>> >>>
>>>>> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>>>> >>> >>>>
>>>>> >>> >>>> Add it if you promise to implement it, otherwise put it
>>>>> against 3.2.x
>>>>> >>> >>>> for
>>>>> >>> >>>> the patch releases.
>>>>> >>> >>>
>>>>> >>> >>>
>>>>> >>> >>> That is not going to be a problem because I have a patch and
>>>>> can
>>>>> >>> >>> commit
>>>>> >>> >>> right away.
>>>>> >>> >>>
>>>>> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>> >>> >>>>
>>>>> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>>> >>> >>>>>
>>>>> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like
>>>>> scrubbing
>>>>> >>> >>>>>> some
>>>>> >>> >>>>>> more?
>>>>> >>> >>>>>>
>>>>> >>> >>>>>
>>>>> >>> >>>>> I'd like to add another issue to 3.2:
>>>>> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times
>>>>> in an
>>>>> >>> >>>>> ISO
>>>>> >>> >>>>> 8601-style manner
>>>>> >>> >>>>>
>>>>> >>> >>>>> It adds readability to the time output.
>>>>> >>> >>>>>
>>>>> >>> >>>>> Mike
>>>>> >>> >>>>>
>>>>> >>> >>>>>
>>>>> >>> >>>>>
>>>>> >>> >>>>>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>> >>> >>>>>
>>>>> >>> >>>>>
>>>>> >>> >>>>
>>>>> >>> >>>
>>>>> >>> >>>
>>>>> >>> >>>
>>>>> ---------------------------------------------------------------------
>>>>> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>> >>> >>>
>>>>> >>> >>
>>>>> >>> >>
>>>>> >>> >> --
>>>>> >>> >> Sent from my phone
>>>>> >>> >
>>>>> >>> >
>>>>> >>
>>>>> >>
>>>>>
>>>>
>>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
Done... we are now down to 17 issues still in scope for 3.2.0
On 17 January 2014 11:38, Stephen Connolly
<st...@gmail.com>wrote:
> OK, 4 days and no objections... these are being pushed out of scope for
> 3.2.0
>
>
> On 13 January 2014 18:07, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
>> The following issues I proposed to move to 4.x. I have not heard anything
>> to the contrary... shall I pull the trigger on these?
>>
>> - http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if
>> pom contains a dependency with two different versions.
>> - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should
>> specify phase bindings in terms of general functionality type
>>
>>
>> - http://jira.codehaus.org/browse/MNG-841 Support customization of
>> default excludes
>>
>>
>> - http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a
>> plugin
>>
>>
>> - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies' scopes
>> to be managed without explicit versions
>> - http://jira.codehaus.org/browse/MNG-3825 Dependencies with
>> classifier should not always require a version.
>> - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or
>> execution
>> -
>> - 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
>>
>>
>> - http://jira.codehaus.org/browse/MNG-1867 deprecate system scope,
>> analyse other use cases
>> - http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding
>> artifactId to site urls
>>
>>
>> I would like some discussion on this one before making a call one way or
>> the other
>>
>> - http://jira.codehaus.org/browse/MNG-4173 Remove automatic version
>> resolution for POM plugins
>>
>>
>>
>>
>>
>>
>> On 13 January 2014 18:02, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>>> wiki updated ;-)
>>>
>>>
>>> On 13 January 2014 17:56, Benson Margulies <bi...@gmail.com>wrote:
>>>
>>>> Done.
>>>>
>>>> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
>>>> <bi...@gmail.com> wrote:
>>>> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
>>>> > <st...@gmail.com> wrote:
>>>> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
>>>> wrote:
>>>> >>>
>>>> >>> Why isn't this copied to the dev list?
>>>> >>
>>>> >>
>>>> >> It was, check the headers
>>>> >
>>>> > I see. GMail has learned a new prank, which is to skip 'dev' in the
>>>> > brief listing of who is on the email.
>>>> >
>>>> >>
>>>> >>>
>>>> >>>
>>>> >>>
>>>> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>>>> >>> remotely under consideration.
>>>> >>
>>>> >>
>>>> >> I moved MNG-3879 to 4.0 backlog.
>>>> >>
>>>> >> Your action was to split out the second issue... should really live
>>>> in the
>>>> >> dependency plugin and depend on MNG-3879
>>>> >
>>>> > OK, seems less that wildly important, but I'll do it.
>>>> >
>>>> >>
>>>> >>> The second part is a goal that I would propose to call
>>>> 'dependency-map'.
>>>> >>> This would produce a formatted map of the dependency tree –
>>>> enriched, of
>>>> >>> course, by the comments in the first part.
>>>> >>
>>>> >>
>>>> >>>
>>>> >>> It is a proposal, to start with, to add
>>>> >>> an element to the POM:
>>>> >>>
>>>> >>> <dependency>
>>>> >>> <explanation>some text </explanation>
>>>> >>> ...
>>>> >>> </dependency>
>>>> >>>
>>>> >>> which would make it a job for 4.0. It was never my intention to
>>>> >>> propose to capture <!-- --> XML comments, that's evil in my view.
>>>> >>>
>>>> >>> So far, the feedback I've received is that the stuff I've written
>>>> >>> about POM evolution is crap. Fine, it's crap.
>>>> >>
>>>> >>
>>>> >> I don't think necessarily so... once 3.2.0 is out we will be looking
>>>> at
>>>> >> model version 5.0.0 and pom evolution is on the cards. I like the
>>>> idea of
>>>> >> dedicated documentation nodes in the pom as otherwise it can be
>>>> harder to
>>>> >> maintain comments etc, when people use formatting tools etc. The
>>>> great thing
>>>> >> with a descriptive text node is that everyone except tooling can
>>>> ignore it
>>>> >>
>>>> >>>
>>>> >>> So JIRAs like this
>>>> >>> should just be closed down when they have my name on them.
>>>> >>>
>>>> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>>>> >>> <st...@gmail.com> wrote:
>>>> >>> > I have added a wiki page summary of this discussion:
>>>> >>> >
>>>> >>> >
>>>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>>>> >>> >
>>>> >>> > Reminder, I pegged some action items against Benson, Olivier,
>>>> Kristian &
>>>> >>> > Jason... See the action required section... mostly just status
>>>> updates.
>>>> >>> >
>>>> >>> >
>>>> >>> > On 7 January 2014 22:03, Stephen Connolly
>>>> >>> > <st...@gmail.com>
>>>> >>> > wrote:
>>>> >>> >>
>>>> >>> >> I like "Nike" style issues (just commit it)
>>>> >>> >>
>>>> >>> >>
>>>> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>> >>> >>>
>>>> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>>> >>> >>>>
>>>> >>> >>>> Add it if you promise to implement it, otherwise put it
>>>> against 3.2.x
>>>> >>> >>>> for
>>>> >>> >>>> the patch releases.
>>>> >>> >>>
>>>> >>> >>>
>>>> >>> >>> That is not going to be a problem because I have a patch and can
>>>> >>> >>> commit
>>>> >>> >>> right away.
>>>> >>> >>>
>>>> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>> >>> >>>>
>>>> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>> >>> >>>>>
>>>> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like
>>>> scrubbing
>>>> >>> >>>>>> some
>>>> >>> >>>>>> more?
>>>> >>> >>>>>>
>>>> >>> >>>>>
>>>> >>> >>>>> I'd like to add another issue to 3.2:
>>>> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times
>>>> in an
>>>> >>> >>>>> ISO
>>>> >>> >>>>> 8601-style manner
>>>> >>> >>>>>
>>>> >>> >>>>> It adds readability to the time output.
>>>> >>> >>>>>
>>>> >>> >>>>> Mike
>>>> >>> >>>>>
>>>> >>> >>>>>
>>>> >>> >>>>>
>>>> >>> >>>>>
>>>> ---------------------------------------------------------------------
>>>> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>> >>> >>>>>
>>>> >>> >>>>>
>>>> >>> >>>>
>>>> >>> >>>
>>>> >>> >>>
>>>> >>> >>>
>>>> ---------------------------------------------------------------------
>>>> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>>>> >>> >>>
>>>> >>> >>
>>>> >>> >>
>>>> >>> >> --
>>>> >>> >> Sent from my phone
>>>> >>> >
>>>> >>> >
>>>> >>
>>>> >>
>>>>
>>>
>>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
OK, 4 days and no objections... these are being pushed out of scope for
3.2.0
On 13 January 2014 18:07, Stephen Connolly
<st...@gmail.com>wrote:
> The following issues I proposed to move to 4.x. I have not heard anything
> to the contrary... shall I pull the trigger on these?
>
> - http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if
> pom contains a dependency with two different versions.
> - http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should
> specify phase bindings in terms of general functionality type
>
>
> - http://jira.codehaus.org/browse/MNG-841 Support customization of
> default excludes
>
>
> - http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a
> plugin
>
>
> - http://jira.codehaus.org/browse/MNG-3695 Allow dependencies' scopes
> to be managed without explicit versions
> - http://jira.codehaus.org/browse/MNG-3825 Dependencies with
> classifier should not always require a version.
> - http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or execution
> -
> - 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
>
>
> - http://jira.codehaus.org/browse/MNG-1867 deprecate system scope,
> analyse other use cases
> - http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding
> artifactId to site urls
>
>
> I would like some discussion on this one before making a call one way or
> the other
>
> - http://jira.codehaus.org/browse/MNG-4173 Remove automatic version
> resolution for POM plugins
>
>
>
>
>
>
> On 13 January 2014 18:02, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
>> wiki updated ;-)
>>
>>
>> On 13 January 2014 17:56, Benson Margulies <bi...@gmail.com> wrote:
>>
>>> Done.
>>>
>>> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
>>> <bi...@gmail.com> wrote:
>>> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
>>> > <st...@gmail.com> wrote:
>>> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
>>> wrote:
>>> >>>
>>> >>> Why isn't this copied to the dev list?
>>> >>
>>> >>
>>> >> It was, check the headers
>>> >
>>> > I see. GMail has learned a new prank, which is to skip 'dev' in the
>>> > brief listing of who is on the email.
>>> >
>>> >>
>>> >>>
>>> >>>
>>> >>>
>>> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>>> >>> remotely under consideration.
>>> >>
>>> >>
>>> >> I moved MNG-3879 to 4.0 backlog.
>>> >>
>>> >> Your action was to split out the second issue... should really live
>>> in the
>>> >> dependency plugin and depend on MNG-3879
>>> >
>>> > OK, seems less that wildly important, but I'll do it.
>>> >
>>> >>
>>> >>> The second part is a goal that I would propose to call
>>> 'dependency-map'.
>>> >>> This would produce a formatted map of the dependency tree –
>>> enriched, of
>>> >>> course, by the comments in the first part.
>>> >>
>>> >>
>>> >>>
>>> >>> It is a proposal, to start with, to add
>>> >>> an element to the POM:
>>> >>>
>>> >>> <dependency>
>>> >>> <explanation>some text </explanation>
>>> >>> ...
>>> >>> </dependency>
>>> >>>
>>> >>> which would make it a job for 4.0. It was never my intention to
>>> >>> propose to capture <!-- --> XML comments, that's evil in my view.
>>> >>>
>>> >>> So far, the feedback I've received is that the stuff I've written
>>> >>> about POM evolution is crap. Fine, it's crap.
>>> >>
>>> >>
>>> >> I don't think necessarily so... once 3.2.0 is out we will be looking
>>> at
>>> >> model version 5.0.0 and pom evolution is on the cards. I like the
>>> idea of
>>> >> dedicated documentation nodes in the pom as otherwise it can be
>>> harder to
>>> >> maintain comments etc, when people use formatting tools etc. The
>>> great thing
>>> >> with a descriptive text node is that everyone except tooling can
>>> ignore it
>>> >>
>>> >>>
>>> >>> So JIRAs like this
>>> >>> should just be closed down when they have my name on them.
>>> >>>
>>> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>>> >>> <st...@gmail.com> wrote:
>>> >>> > I have added a wiki page summary of this discussion:
>>> >>> >
>>> >>> >
>>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>>> >>> >
>>> >>> > Reminder, I pegged some action items against Benson, Olivier,
>>> Kristian &
>>> >>> > Jason... See the action required section... mostly just status
>>> updates.
>>> >>> >
>>> >>> >
>>> >>> > On 7 January 2014 22:03, Stephen Connolly
>>> >>> > <st...@gmail.com>
>>> >>> > wrote:
>>> >>> >>
>>> >>> >> I like "Nike" style issues (just commit it)
>>> >>> >>
>>> >>> >>
>>> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>> >>> >>>
>>> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>> >>> >>>>
>>> >>> >>>> Add it if you promise to implement it, otherwise put it against
>>> 3.2.x
>>> >>> >>>> for
>>> >>> >>>> the patch releases.
>>> >>> >>>
>>> >>> >>>
>>> >>> >>> That is not going to be a problem because I have a patch and can
>>> >>> >>> commit
>>> >>> >>> right away.
>>> >>> >>>
>>> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>> >>> >>>>
>>> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>> >>> >>>>>
>>> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like
>>> scrubbing
>>> >>> >>>>>> some
>>> >>> >>>>>> more?
>>> >>> >>>>>>
>>> >>> >>>>>
>>> >>> >>>>> I'd like to add another issue to 3.2:
>>> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times
>>> in an
>>> >>> >>>>> ISO
>>> >>> >>>>> 8601-style manner
>>> >>> >>>>>
>>> >>> >>>>> It adds readability to the time output.
>>> >>> >>>>>
>>> >>> >>>>> Mike
>>> >>> >>>>>
>>> >>> >>>>>
>>> >>> >>>>>
>>> >>> >>>>>
>>> ---------------------------------------------------------------------
>>> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>> >>> >>>>>
>>> >>> >>>>>
>>> >>> >>>>
>>> >>> >>>
>>> >>> >>>
>>> >>> >>>
>>> ---------------------------------------------------------------------
>>> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>>> >>> >>>
>>> >>> >>
>>> >>> >>
>>> >>> >> --
>>> >>> >> Sent from my phone
>>> >>> >
>>> >>> >
>>> >>
>>> >>
>>>
>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
The following issues I proposed to move to 4.x. I have not heard anything
to the contrary... shall I pull the trigger on these?
- http://jira.codehaus.org/browse/MNG-4622 Throw Validation Error if pom
contains a dependency with two different versions.
- http://jira.codehaus.org/browse/MNG-683 Lifecycle mappings should
specify phase bindings in terms of general functionality type
- http://jira.codehaus.org/browse/MNG-841 Support customization of
default excludes
- http://jira.codehaus.org/browse/MNG-193 symmetry for outputs of a
plugin
- http://jira.codehaus.org/browse/MNG-3695 Allow dependencies' scopes to
be managed without explicit versions
- http://jira.codehaus.org/browse/MNG-3825 Dependencies with classifier
should not always require a version.
- http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/or execution
-
- 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
- http://jira.codehaus.org/browse/MNG-1867 deprecate system scope,
analyse other use cases
- http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding
artifactId to site urls
I would like some discussion on this one before making a call one way or
the other
- http://jira.codehaus.org/browse/MNG-4173 Remove automatic version
resolution for POM plugins
On 13 January 2014 18:02, Stephen Connolly
<st...@gmail.com>wrote:
> wiki updated ;-)
>
>
> On 13 January 2014 17:56, Benson Margulies <bi...@gmail.com> wrote:
>
>> Done.
>>
>> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
>> <bi...@gmail.com> wrote:
>> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
>> > <st...@gmail.com> wrote:
>> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
>> wrote:
>> >>>
>> >>> Why isn't this copied to the dev list?
>> >>
>> >>
>> >> It was, check the headers
>> >
>> > I see. GMail has learned a new prank, which is to skip 'dev' in the
>> > brief listing of who is on the email.
>> >
>> >>
>> >>>
>> >>>
>> >>>
>> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>> >>> remotely under consideration.
>> >>
>> >>
>> >> I moved MNG-3879 to 4.0 backlog.
>> >>
>> >> Your action was to split out the second issue... should really live in
>> the
>> >> dependency plugin and depend on MNG-3879
>> >
>> > OK, seems less that wildly important, but I'll do it.
>> >
>> >>
>> >>> The second part is a goal that I would propose to call
>> 'dependency-map'.
>> >>> This would produce a formatted map of the dependency tree – enriched,
>> of
>> >>> course, by the comments in the first part.
>> >>
>> >>
>> >>>
>> >>> It is a proposal, to start with, to add
>> >>> an element to the POM:
>> >>>
>> >>> <dependency>
>> >>> <explanation>some text </explanation>
>> >>> ...
>> >>> </dependency>
>> >>>
>> >>> which would make it a job for 4.0. It was never my intention to
>> >>> propose to capture <!-- --> XML comments, that's evil in my view.
>> >>>
>> >>> So far, the feedback I've received is that the stuff I've written
>> >>> about POM evolution is crap. Fine, it's crap.
>> >>
>> >>
>> >> I don't think necessarily so... once 3.2.0 is out we will be looking at
>> >> model version 5.0.0 and pom evolution is on the cards. I like the idea
>> of
>> >> dedicated documentation nodes in the pom as otherwise it can be harder
>> to
>> >> maintain comments etc, when people use formatting tools etc. The great
>> thing
>> >> with a descriptive text node is that everyone except tooling can
>> ignore it
>> >>
>> >>>
>> >>> So JIRAs like this
>> >>> should just be closed down when they have my name on them.
>> >>>
>> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>> >>> <st...@gmail.com> wrote:
>> >>> > I have added a wiki page summary of this discussion:
>> >>> >
>> >>> >
>> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>> >>> >
>> >>> > Reminder, I pegged some action items against Benson, Olivier,
>> Kristian &
>> >>> > Jason... See the action required section... mostly just status
>> updates.
>> >>> >
>> >>> >
>> >>> > On 7 January 2014 22:03, Stephen Connolly
>> >>> > <st...@gmail.com>
>> >>> > wrote:
>> >>> >>
>> >>> >> I like "Nike" style issues (just commit it)
>> >>> >>
>> >>> >>
>> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>> >>> >>>
>> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>> >>> >>>>
>> >>> >>>> Add it if you promise to implement it, otherwise put it against
>> 3.2.x
>> >>> >>>> for
>> >>> >>>> the patch releases.
>> >>> >>>
>> >>> >>>
>> >>> >>> That is not going to be a problem because I have a patch and can
>> >>> >>> commit
>> >>> >>> right away.
>> >>> >>>
>> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>> >>> >>>>
>> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>> >>> >>>>>
>> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like
>> scrubbing
>> >>> >>>>>> some
>> >>> >>>>>> more?
>> >>> >>>>>>
>> >>> >>>>>
>> >>> >>>>> I'd like to add another issue to 3.2:
>> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in
>> an
>> >>> >>>>> ISO
>> >>> >>>>> 8601-style manner
>> >>> >>>>>
>> >>> >>>>> It adds readability to the time output.
>> >>> >>>>>
>> >>> >>>>> Mike
>> >>> >>>>>
>> >>> >>>>>
>> >>> >>>>>
>> >>> >>>>>
>> ---------------------------------------------------------------------
>> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>> >>>>>
>> >>> >>>>>
>> >>> >>>>
>> >>> >>>
>> >>> >>>
>> >>> >>>
>> ---------------------------------------------------------------------
>> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>> >>>
>> >>> >>
>> >>> >>
>> >>> >> --
>> >>> >> Sent from my phone
>> >>> >
>> >>> >
>> >>
>> >>
>>
>
>
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@tesla.io>.
Just starting the integration test for the participant, once done I'm going to push the refactor for the build strategies.
On Jan 13, 2014, at 1:02 PM, Stephen Connolly <st...@gmail.com> wrote:
> wiki updated ;-)
>
>
> On 13 January 2014 17:56, Benson Margulies <bi...@gmail.com> wrote:
> Done.
>
> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
> <bi...@gmail.com> wrote:
> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
> > <st...@gmail.com> wrote:
> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com> wrote:
> >>>
> >>> Why isn't this copied to the dev list?
> >>
> >>
> >> It was, check the headers
> >
> > I see. GMail has learned a new prank, which is to skip 'dev' in the
> > brief listing of who is on the email.
> >
> >>
> >>>
> >>>
> >>>
> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
> >>> remotely under consideration.
> >>
> >>
> >> I moved MNG-3879 to 4.0 backlog.
> >>
> >> Your action was to split out the second issue... should really live in the
> >> dependency plugin and depend on MNG-3879
> >
> > OK, seems less that wildly important, but I'll do it.
> >
> >>
> >>> The second part is a goal that I would propose to call 'dependency-map'.
> >>> This would produce a formatted map of the dependency tree – enriched, of
> >>> course, by the comments in the first part.
> >>
> >>
> >>>
> >>> It is a proposal, to start with, to add
> >>> an element to the POM:
> >>>
> >>> <dependency>
> >>> <explanation>some text </explanation>
> >>> ...
> >>> </dependency>
> >>>
> >>> which would make it a job for 4.0. It was never my intention to
> >>> propose to capture <!-- --> XML comments, that's evil in my view.
> >>>
> >>> So far, the feedback I've received is that the stuff I've written
> >>> about POM evolution is crap. Fine, it's crap.
> >>
> >>
> >> I don't think necessarily so... once 3.2.0 is out we will be looking at
> >> model version 5.0.0 and pom evolution is on the cards. I like the idea of
> >> dedicated documentation nodes in the pom as otherwise it can be harder to
> >> maintain comments etc, when people use formatting tools etc. The great thing
> >> with a descriptive text node is that everyone except tooling can ignore it
> >>
> >>>
> >>> So JIRAs like this
> >>> should just be closed down when they have my name on them.
> >>>
> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
> >>> <st...@gmail.com> wrote:
> >>> > I have added a wiki page summary of this discussion:
> >>> >
> >>> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
> >>> >
> >>> > Reminder, I pegged some action items against Benson, Olivier, Kristian &
> >>> > Jason... See the action required section... mostly just status updates.
> >>> >
> >>> >
> >>> > On 7 January 2014 22:03, Stephen Connolly
> >>> > <st...@gmail.com>
> >>> > wrote:
> >>> >>
> >>> >> I like "Nike" style issues (just commit it)
> >>> >>
> >>> >>
> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >>> >>>
> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
> >>> >>>>
> >>> >>>> Add it if you promise to implement it, otherwise put it against 3.2.x
> >>> >>>> for
> >>> >>>> the patch releases.
> >>> >>>
> >>> >>>
> >>> >>> That is not going to be a problem because I have a patch and can
> >>> >>> commit
> >>> >>> right away.
> >>> >>>
> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >>> >>>>
> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
> >>> >>>>>
> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
> >>> >>>>>> some
> >>> >>>>>> more?
> >>> >>>>>>
> >>> >>>>>
> >>> >>>>> I'd like to add another issue to 3.2:
> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an
> >>> >>>>> ISO
> >>> >>>>> 8601-style manner
> >>> >>>>>
> >>> >>>>> It adds readability to the time output.
> >>> >>>>>
> >>> >>>>> Mike
> >>> >>>>>
> >>> >>>>>
> >>> >>>>>
> >>> >>>>> ---------------------------------------------------------------------
> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>> >>>>>
> >>> >>>>>
> >>> >>>>
> >>> >>>
> >>> >>>
> >>> >>> ---------------------------------------------------------------------
> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>> >>>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Sent from my phone
> >>> >
> >>> >
> >>
> >>
>
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
wiki updated ;-)
On 13 January 2014 17:56, Benson Margulies <bi...@gmail.com> wrote:
> Done.
>
> On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
> <bi...@gmail.com> wrote:
> > On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
> > <st...@gmail.com> wrote:
> >> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com>
> wrote:
> >>>
> >>> Why isn't this copied to the dev list?
> >>
> >>
> >> It was, check the headers
> >
> > I see. GMail has learned a new prank, which is to skip 'dev' in the
> > brief listing of who is on the email.
> >
> >>
> >>>
> >>>
> >>>
> >>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
> >>> remotely under consideration.
> >>
> >>
> >> I moved MNG-3879 to 4.0 backlog.
> >>
> >> Your action was to split out the second issue... should really live in
> the
> >> dependency plugin and depend on MNG-3879
> >
> > OK, seems less that wildly important, but I'll do it.
> >
> >>
> >>> The second part is a goal that I would propose to call
> 'dependency-map'.
> >>> This would produce a formatted map of the dependency tree – enriched,
> of
> >>> course, by the comments in the first part.
> >>
> >>
> >>>
> >>> It is a proposal, to start with, to add
> >>> an element to the POM:
> >>>
> >>> <dependency>
> >>> <explanation>some text </explanation>
> >>> ...
> >>> </dependency>
> >>>
> >>> which would make it a job for 4.0. It was never my intention to
> >>> propose to capture <!-- --> XML comments, that's evil in my view.
> >>>
> >>> So far, the feedback I've received is that the stuff I've written
> >>> about POM evolution is crap. Fine, it's crap.
> >>
> >>
> >> I don't think necessarily so... once 3.2.0 is out we will be looking at
> >> model version 5.0.0 and pom evolution is on the cards. I like the idea
> of
> >> dedicated documentation nodes in the pom as otherwise it can be harder
> to
> >> maintain comments etc, when people use formatting tools etc. The great
> thing
> >> with a descriptive text node is that everyone except tooling can ignore
> it
> >>
> >>>
> >>> So JIRAs like this
> >>> should just be closed down when they have my name on them.
> >>>
> >>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
> >>> <st...@gmail.com> wrote:
> >>> > I have added a wiki page summary of this discussion:
> >>> >
> >>> >
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
> >>> >
> >>> > Reminder, I pegged some action items against Benson, Olivier,
> Kristian &
> >>> > Jason... See the action required section... mostly just status
> updates.
> >>> >
> >>> >
> >>> > On 7 January 2014 22:03, Stephen Connolly
> >>> > <st...@gmail.com>
> >>> > wrote:
> >>> >>
> >>> >> I like "Nike" style issues (just commit it)
> >>> >>
> >>> >>
> >>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >>> >>>
> >>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
> >>> >>>>
> >>> >>>> Add it if you promise to implement it, otherwise put it against
> 3.2.x
> >>> >>>> for
> >>> >>>> the patch releases.
> >>> >>>
> >>> >>>
> >>> >>> That is not going to be a problem because I have a patch and can
> >>> >>> commit
> >>> >>> right away.
> >>> >>>
> >>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >>> >>>>
> >>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
> >>> >>>>>
> >>> >>>>>> OK we are now at 38 open issues.... anyone else feel like
> scrubbing
> >>> >>>>>> some
> >>> >>>>>> more?
> >>> >>>>>>
> >>> >>>>>
> >>> >>>>> I'd like to add another issue to 3.2:
> >>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in
> an
> >>> >>>>> ISO
> >>> >>>>> 8601-style manner
> >>> >>>>>
> >>> >>>>> It adds readability to the time output.
> >>> >>>>>
> >>> >>>>> Mike
> >>> >>>>>
> >>> >>>>>
> >>> >>>>>
> >>> >>>>>
> ---------------------------------------------------------------------
> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>> >>>>>
> >>> >>>>>
> >>> >>>>
> >>> >>>
> >>> >>>
> >>> >>>
> ---------------------------------------------------------------------
> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>> >>>
> >>> >>
> >>> >>
> >>> >> --
> >>> >> Sent from my phone
> >>> >
> >>> >
> >>
> >>
>
Re: 3.2.0 Bug Scrub
Posted by Benson Margulies <bi...@gmail.com>.
Done.
On Mon, Jan 13, 2014 at 12:53 PM, Benson Margulies
<bi...@gmail.com> wrote:
> On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
> <st...@gmail.com> wrote:
>> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com> wrote:
>>>
>>> Why isn't this copied to the dev list?
>>
>>
>> It was, check the headers
>
> I see. GMail has learned a new prank, which is to skip 'dev' in the
> brief listing of who is on the email.
>
>>
>>>
>>>
>>>
>>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>>> remotely under consideration.
>>
>>
>> I moved MNG-3879 to 4.0 backlog.
>>
>> Your action was to split out the second issue... should really live in the
>> dependency plugin and depend on MNG-3879
>
> OK, seems less that wildly important, but I'll do it.
>
>>
>>> The second part is a goal that I would propose to call 'dependency-map'.
>>> This would produce a formatted map of the dependency tree – enriched, of
>>> course, by the comments in the first part.
>>
>>
>>>
>>> It is a proposal, to start with, to add
>>> an element to the POM:
>>>
>>> <dependency>
>>> <explanation>some text </explanation>
>>> ...
>>> </dependency>
>>>
>>> which would make it a job for 4.0. It was never my intention to
>>> propose to capture <!-- --> XML comments, that's evil in my view.
>>>
>>> So far, the feedback I've received is that the stuff I've written
>>> about POM evolution is crap. Fine, it's crap.
>>
>>
>> I don't think necessarily so... once 3.2.0 is out we will be looking at
>> model version 5.0.0 and pom evolution is on the cards. I like the idea of
>> dedicated documentation nodes in the pom as otherwise it can be harder to
>> maintain comments etc, when people use formatting tools etc. The great thing
>> with a descriptive text node is that everyone except tooling can ignore it
>>
>>>
>>> So JIRAs like this
>>> should just be closed down when they have my name on them.
>>>
>>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>>> <st...@gmail.com> wrote:
>>> > I have added a wiki page summary of this discussion:
>>> >
>>> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>>> >
>>> > Reminder, I pegged some action items against Benson, Olivier, Kristian &
>>> > Jason... See the action required section... mostly just status updates.
>>> >
>>> >
>>> > On 7 January 2014 22:03, Stephen Connolly
>>> > <st...@gmail.com>
>>> > wrote:
>>> >>
>>> >> I like "Nike" style issues (just commit it)
>>> >>
>>> >>
>>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>> >>>
>>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>> >>>>
>>> >>>> Add it if you promise to implement it, otherwise put it against 3.2.x
>>> >>>> for
>>> >>>> the patch releases.
>>> >>>
>>> >>>
>>> >>> That is not going to be a problem because I have a patch and can
>>> >>> commit
>>> >>> right away.
>>> >>>
>>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>> >>>>
>>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>> >>>>>
>>> >>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>> >>>>>> some
>>> >>>>>> more?
>>> >>>>>>
>>> >>>>>
>>> >>>>> I'd like to add another issue to 3.2:
>>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an
>>> >>>>> ISO
>>> >>>>> 8601-style manner
>>> >>>>>
>>> >>>>> It adds readability to the time output.
>>> >>>>>
>>> >>>>> Mike
>>> >>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> ---------------------------------------------------------------------
>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>>> >>>
>>> >>
>>> >>
>>> >> --
>>> >> Sent from my phone
>>> >
>>> >
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Benson Margulies <bi...@gmail.com>.
On Mon, Jan 13, 2014 at 11:59 AM, Stephen Connolly
<st...@gmail.com> wrote:
> On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com> wrote:
>>
>> Why isn't this copied to the dev list?
>
>
> It was, check the headers
I see. GMail has learned a new prank, which is to skip 'dev' in the
brief listing of who is on the email.
>
>>
>>
>>
>> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
>> remotely under consideration.
>
>
> I moved MNG-3879 to 4.0 backlog.
>
> Your action was to split out the second issue... should really live in the
> dependency plugin and depend on MNG-3879
OK, seems less that wildly important, but I'll do it.
>
>> The second part is a goal that I would propose to call 'dependency-map'.
>> This would produce a formatted map of the dependency tree – enriched, of
>> course, by the comments in the first part.
>
>
>>
>> It is a proposal, to start with, to add
>> an element to the POM:
>>
>> <dependency>
>> <explanation>some text </explanation>
>> ...
>> </dependency>
>>
>> which would make it a job for 4.0. It was never my intention to
>> propose to capture <!-- --> XML comments, that's evil in my view.
>>
>> So far, the feedback I've received is that the stuff I've written
>> about POM evolution is crap. Fine, it's crap.
>
>
> I don't think necessarily so... once 3.2.0 is out we will be looking at
> model version 5.0.0 and pom evolution is on the cards. I like the idea of
> dedicated documentation nodes in the pom as otherwise it can be harder to
> maintain comments etc, when people use formatting tools etc. The great thing
> with a descriptive text node is that everyone except tooling can ignore it
>
>>
>> So JIRAs like this
>> should just be closed down when they have my name on them.
>>
>> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
>> <st...@gmail.com> wrote:
>> > I have added a wiki page summary of this discussion:
>> >
>> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>> >
>> > Reminder, I pegged some action items against Benson, Olivier, Kristian &
>> > Jason... See the action required section... mostly just status updates.
>> >
>> >
>> > On 7 January 2014 22:03, Stephen Connolly
>> > <st...@gmail.com>
>> > wrote:
>> >>
>> >> I like "Nike" style issues (just commit it)
>> >>
>> >>
>> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
>> >>>
>> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>> >>>>
>> >>>> Add it if you promise to implement it, otherwise put it against 3.2.x
>> >>>> for
>> >>>> the patch releases.
>> >>>
>> >>>
>> >>> That is not going to be a problem because I have a patch and can
>> >>> commit
>> >>> right away.
>> >>>
>> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>> >>>>
>> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>> >>>>>
>> >>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>> >>>>>> some
>> >>>>>> more?
>> >>>>>>
>> >>>>>
>> >>>>> I'd like to add another issue to 3.2:
>> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an
>> >>>>> ISO
>> >>>>> 8601-style manner
>> >>>>>
>> >>>>> It adds readability to the time output.
>> >>>>>
>> >>>>> Mike
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> ---------------------------------------------------------------------
>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>
>> >>
>> >>
>> >> --
>> >> Sent from my phone
>> >
>> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
On 13 January 2014 16:13, Benson Margulies <bi...@gmail.com> wrote:
> Why isn't this copied to the dev list?
>
It was, check the headers
>
>
> I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
> remotely under consideration.
I moved MNG-3879 to 4.0 backlog.
Your action was to split out the second issue... should really live in the
dependency plugin and depend on MNG-3879
> The second part is a goal that I would propose to call 'dependency-map'.
This would produce a formatted map of the dependency tree – enriched, of
course, by the comments in the first part.
> It is a proposal, to start with, to add
> an element to the POM:
>
> <dependency>
> <explanation>some text </explanation>
> ...
> </dependency>
>
> which would make it a job for 4.0. It was never my intention to
> propose to capture <!-- --> XML comments, that's evil in my view.
>
> So far, the feedback I've received is that the stuff I've written
> about POM evolution is crap. Fine, it's crap.
I don't think necessarily so... once 3.2.0 is out we will be looking at
model version 5.0.0 and pom evolution is on the cards. I like the idea of
dedicated documentation nodes in the pom as otherwise it can be harder to
maintain comments etc, when people use formatting tools etc. The great
thing with a descriptive text node is that everyone except tooling can
ignore it
> So JIRAs like this
> should just be closed down when they have my name on them.
>
> On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
> <st...@gmail.com> wrote:
> > I have added a wiki page summary of this discussion:
> >
> > https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
> >
> > Reminder, I pegged some action items against Benson, Olivier, Kristian &
> > Jason... See the action required section... mostly just status updates.
> >
> >
> > On 7 January 2014 22:03, Stephen Connolly <
> stephen.alan.connolly@gmail.com>
> > wrote:
> >>
> >> I like "Nike" style issues (just commit it)
> >>
> >>
> >> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >>>
> >>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
> >>>>
> >>>> Add it if you promise to implement it, otherwise put it against 3.2.x
> >>>> for
> >>>> the patch releases.
> >>>
> >>>
> >>> That is not going to be a problem because I have a patch and can commit
> >>> right away.
> >>>
> >>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
> >>>>
> >>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
> >>>>>
> >>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
> >>>>>> some
> >>>>>> more?
> >>>>>>
> >>>>>
> >>>>> I'd like to add another issue to 3.2:
> >>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an
> ISO
> >>>>> 8601-style manner
> >>>>>
> >>>>> It adds readability to the time output.
> >>>>>
> >>>>> Mike
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >>
> >> --
> >> Sent from my phone
> >
> >
>
Re: 3.2.0 Bug Scrub
Posted by Benson Margulies <bi...@gmail.com>.
Why isn't this copied to the dev list?
I don't see why http://jira.codehaus.org/browse/MNG-3879 is even
remotely under consideration. It is a proposal, to start with, to add
an element to the POM:
<dependency>
<explanation>some text </explanation>
...
</dependency>
which would make it a job for 4.0. It was never my intention to
propose to capture <!-- --> XML comments, that's evil in my view.
So far, the feedback I've received is that the stuff I've written
about POM evolution is crap. Fine, it's crap. So JIRAs like this
should just be closed down when they have my name on them.
On Mon, Jan 13, 2014 at 8:24 AM, Stephen Connolly
<st...@gmail.com> wrote:
> I have added a wiki page summary of this discussion:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
>
> Reminder, I pegged some action items against Benson, Olivier, Kristian &
> Jason... See the action required section... mostly just status updates.
>
>
> On 7 January 2014 22:03, Stephen Connolly <st...@gmail.com>
> wrote:
>>
>> I like "Nike" style issues (just commit it)
>>
>>
>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>
>>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>>>
>>>> Add it if you promise to implement it, otherwise put it against 3.2.x
>>>> for
>>>> the patch releases.
>>>
>>>
>>> That is not going to be a problem because I have a patch and can commit
>>> right away.
>>>
>>>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>>
>>>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>>>
>>>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>>> some
>>>>>> more?
>>>>>>
>>>>>
>>>>> I'd like to add another issue to 3.2:
>>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
>>>>> 8601-style manner
>>>>>
>>>>> It adds readability to the time output.
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>>
>> --
>> Sent from my phone
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
I have added a wiki page summary of this discussion:
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.2.0+Bug+Scrub
Reminder, I pegged some action items against Benson, Olivier, Kristian &
Jason... See the action required section... mostly just status updates.
On 7 January 2014 22:03, Stephen Connolly
<st...@gmail.com>wrote:
> I like "Nike" style issues (just commit it)
>
>
> On Tuesday, 7 January 2014, Michael Osipov wrote:
>
>> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>>
>>> Add it if you promise to implement it, otherwise put it against 3.2.x for
>>> the patch releases.
>>>
>>
>> That is not going to be a problem because I have a patch and can commit
>> right away.
>>
>> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>>
>>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>>
>>>> OK we are now at 38 open issues.... anyone else feel like scrubbing
>>>>> some
>>>>> more?
>>>>>
>>>>>
>>>> I'd like to add another issue to 3.2:
>>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
>>>> 8601-style manner
>>>>
>>>> It adds readability to the time output.
>>>>
>>>> Mike
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> --
> Sent from my phone
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
I like "Nike" style issues (just commit it)
On Tuesday, 7 January 2014, Michael Osipov wrote:
> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>
>> Add it if you promise to implement it, otherwise put it against 3.2.x for
>> the patch releases.
>>
>
> That is not going to be a problem because I have a patch and can commit
> right away.
>
> On Tuesday, 7 January 2014, Michael Osipov wrote:
>>
>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>>
>>> OK we are now at 38 open issues.... anyone else feel like scrubbing some
>>>> more?
>>>>
>>>>
>>> I'd like to add another issue to 3.2:
>>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
>>> 8601-style manner
>>>
>>> It adds readability to the time output.
>>>
>>> Mike
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Sent from my phone
Re: 3.2.0 Bug Scrub
Posted by Michael Osipov <mi...@apache.org>.
Am 2014-01-07 22:38, schrieb Stephen Connolly:
> Add it if you promise to implement it, otherwise put it against 3.2.x for
> the patch releases.
That is not going to be a problem because I have a patch and can commit
right away.
> On Tuesday, 7 January 2014, Michael Osipov wrote:
>
>> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>>
>>> OK we are now at 38 open issues.... anyone else feel like scrubbing some
>>> more?
>>>
>>
>> I'd like to add another issue to 3.2:
>> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
>> 8601-style manner
>>
>> It adds readability to the time output.
>>
>> Mike
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
Add it if you promise to implement it, otherwise put it against 3.2.x for
the patch releases.
On Tuesday, 7 January 2014, Michael Osipov wrote:
> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>
>> OK we are now at 38 open issues.... anyone else feel like scrubbing some
>> more?
>>
>
> I'd like to add another issue to 3.2:
> https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
> 8601-style manner
>
> It adds readability to the time output.
>
> Mike
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Sent from my phone
Re: 3.2.0 Bug Scrub
Posted by Michael Osipov <mi...@apache.org>.
Am 2014-01-07 16:25, schrieb Stephen Connolly:
> OK we are now at 38 open issues.... anyone else feel like scrubbing some
> more?
I'd like to add another issue to 3.2:
https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
8601-style manner
It adds readability to the time output.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
OK we are now at 38 open issues.... anyone else feel like scrubbing some
more?
On 7 January 2014 15:25, Stephen Connolly
<st...@gmail.com>wrote:
> Done
>
>
> On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
>
>> Seems reasonable. Go for it.
>>
>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>> stephen.alan.connolly@gmail.com> wrote:
>>
>> > AFAIU this is the current list of bugs:
>> >
>> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>> >
>> > I propose that the following issues all require a change to the model
>> > version, and thus should be pushed back to 4.0.0 (or later)
>> >
>> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
>> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
>> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
>> > attributes<http://jira.codehaus.org/browse/MNG-3397>
>> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
>> > fragments<http://jira.codehaus.org/browse/MNG-5102>
>> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported
>> for
>> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
>> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings section
>> to
>> > POM <http://jira.codehaus.org/browse/MNG-2216>
>> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
>> > project version matches a regex <
>> http://jira.codehaus.org/browse/MNG-3826>
>> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
>> > dependencies that implement an API or provide other dependencies
>> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
>> Configuration
>> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
>> profiles
>> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
>> > support overriding project.build.directory (WONTFIX candidate?)
>> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
>> > declaration of IRC channels
>> >
>> > The following issues require that the deployed pom be different from the
>> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again
>> I
>> > think these should be pushed back to 4.0.0 (or later)
>> >
>> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
>> > versioning<http://jira.codehaus.org/browse/MNG-624>
>> >
>> > I would propose that we move these issues into a 4.0 bucket... that will
>> > bring us down to 31 issues open for 3.2.0
>> >
>> > Thoughts?
>>
>> Thanks,
>>
>> Jason
>>
>> ----------------------------------------------------------
>> Jason van Zyl
>> Founder, Apache Maven
>> http://twitter.com/jvanzyl
>> ---------------------------------------------------------
>>
>>
>>
>>
>>
>>
>>
>>
>
Re: 3.2.0 Bug Scrub
Posted by Stephen Connolly <st...@gmail.com>.
Done
On 7 January 2014 14:43, Jason van Zyl <ja...@tesla.io> wrote:
> Seems reasonable. Go for it.
>
> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
> stephen.alan.connolly@gmail.com> wrote:
>
> > AFAIU this is the current list of bugs:
> >
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
> >
> > I propose that the following issues all require a change to the model
> > version, and thus should be pushed back to 4.0.0 (or later)
> >
> > http://jira.codehaus.org/browse/MNG-1977 Global dependency
> > exclusions<http://jira.codehaus.org/browse/MNG-1977>
> > http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
> > attributes<http://jira.codehaus.org/browse/MNG-3397>
> > http://jira.codehaus.org/browse/MNG-5102 Mixin POM
> > fragments<http://jira.codehaus.org/browse/MNG-5102>
> > http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported
> for
> > parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
> > http://jira.codehaus.org/browse/MNG-2216 Add default encodings section
> to
> > POM <http://jira.codehaus.org/browse/MNG-2216>
> > http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
> > project version matches a regex <
> http://jira.codehaus.org/browse/MNG-3826>
> > http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
> > dependencies that implement an API or provide other dependencies
> > http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation
> Configuration
> > http://jira.codehaus.org/browse/MNG-2557 Various enhancements to
> profiles
> > http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
> > support overriding project.build.directory (WONTFIX candidate?)
> > http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
> > declaration of IRC channels
> >
> > The following issues require that the deployed pom be different from the
> > on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again I
> > think these should be pushed back to 4.0.0 (or later)
> >
> > http://jira.codehaus.org/browse/MNG-624 Automatic parent
> > versioning<http://jira.codehaus.org/browse/MNG-624>
> >
> > I would propose that we move these issues into a 4.0 bucket... that will
> > bring us down to 31 issues open for 3.2.0
> >
> > Thoughts?
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder, Apache Maven
> http://twitter.com/jvanzyl
> ---------------------------------------------------------
>
>
>
>
>
>
>
>
Re: 3.2.0 Bug Scrub
Posted by Jason van Zyl <ja...@tesla.io>.
Seems reasonable. Go for it.
On Jan 7, 2014, at 7:43 AM, Stephen Connolly <st...@gmail.com> wrote:
> AFAIU this is the current list of bugs:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
>
> I propose that the following issues all require a change to the model
> version, and thus should be pushed back to 4.0.0 (or later)
>
> http://jira.codehaus.org/browse/MNG-1977 Global dependency
> exclusions<http://jira.codehaus.org/browse/MNG-1977>
> http://jira.codehaus.org/browse/MNG-2297 Change the POM to use
> attributes<http://jira.codehaus.org/browse/MNG-3397>
> http://jira.codehaus.org/browse/MNG-5102 Mixin POM
> fragments<http://jira.codehaus.org/browse/MNG-5102>
> http://jira.codehaus.org/browse/MNG-2199 Version ranges not supported for
> parent artifacts <http://jira.codehaus.org/browse/MNG-2199>
> http://jira.codehaus.org/browse/MNG-2216 Add default encodings section to
> POM <http://jira.codehaus.org/browse/MNG-2216>
> http://jira.codehaus.org/browse/MNG-3826 Add profile activation when
> project version matches a regex <http://jira.codehaus.org/browse/MNG-3826>
> http://jira.codehaus.org/browse/MNG-2316 Add info to the poms for
> dependencies that implement an API or provide other dependencies
> http://jira.codehaus.org/browse/MNG-3326 Profile Deactivation Configuration
> http://jira.codehaus.org/browse/MNG-2557 Various enhancements to profiles
> http://jira.codehaus.org/browse/MNG-2598 Profile element in POM should
> support overriding project.build.directory (WONTFIX candidate?)
> http://jira.codehaus.org/browse/MNG-3726 Extend POM model to support
> declaration of IRC channels
>
> The following issues require that the deployed pom be different from the
> on-disk pom, i.e. the same problem we had with 2.1.0 and 2.2.0... again I
> think these should be pushed back to 4.0.0 (or later)
>
> http://jira.codehaus.org/browse/MNG-624 Automatic parent
> versioning<http://jira.codehaus.org/browse/MNG-624>
>
> I would propose that we move these issues into a 4.0 bucket... that will
> bring us down to 31 issues open for 3.2.0
>
> Thoughts?
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------