On Jan 29, 2014, at 3:39 PM, Pyeron, Jason J CTR (US) 
<[email protected]> wrote:

>> -----Original Message-----
>> From: Jason van Zyl 
>> Sent: Wednesday, January 29, 2014 12:59 PM
>> 
>> High value is a matter of perspective. I'm personally not interested in
> 
> Yes it is a matter of perspective, but to evidence the value we have created 
> a patch and forked.
> 

Which we weigh against:

1) Our desire to integrate it, and it's something I don't see any of us wanting 
to encourage (although Hervé went out of his way to find you a solution)
2) We have to maintain the feature over time so do we see is as something in 
the interest of the majority of users

>> any feature that encourages or promotes putting binaries in your SCM.
> 
> I do not think SCM issues should be a value judgment made by the Maven 
> project. Nor is that the only use case.
> 

Storing JARs in the SCM is definitely something we collectively eschew. 

>> This is an outmoded definition of reproducibility IMO. I'm also not
>> interested in adjusting the whole system to support this. If adhering
>> to CMMI is a requirement you have, then you can make the necessary
>> adjustments.
> 
> And we have by forking, and enforcing that upon the developers and 
> contractors here. But, that is messy.

Not every feature request can be accommodated. It simply isn't a tenable option 
here.

> 
>> 
>> If you can see a clean way of providing an extension point in Maven
>> that provides the hooks you need to change the behaviour that would be
>> easier to digest. Then at least you don't need a forked version of
>> Maven but can drop in a JAR with your extension.
> 
> Last time I looked at the code base I did not see a way to do a drop in JAR 
> for this business logic. But I will look harder.
> 
> Are you suggesting the change would be to call an optional support module 
> instead to lookup what to do?

Yes, the code base since 3.x has supported injecting custom components. You 
might even be able to do it now with a custom local repository manager 
implementation.

> 
>> 
>> On Jan 29, 2014, at 12:03 PM, Jason Pyeron <[email protected]> wrote:
>> 
>>> This was closed as won't fix.
>>> 
>>> This is still something that is of high value. Can the close comment
>> be more
>>> substantiated and it be migrated to apache?
>>> 
>>> Respectfully,
>>> 
>>> Jason Pyeron
>>> 
>>> --
>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>> -                                                               -
>>> - Jason Pyeron                      PD Inc. http://www.pdinc.us -
>>> - Principal Consultant              10 West 24th Street #100    -
>>> - +1 (443) 269-1555 x333            Baltimore, Maryland 21218   -
>>> -                                                               -
>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>> This message is copyright PD Inc, subject to license 20080407P00.
>>> 
>>> 
>>> 
>>>> -----Original Message-----
>>>> From: Jason van Zyl (JIRA) [mailto:[email protected]]
>>>> Sent: Sunday, January 19, 2014 14:36
>>>> To: [email protected]
>>>> Subject: [jira] (MNG-5167) relative local repository settings
>>>> 
>>>> 
>>>>    [
>>>> https://jira.codehaus.org/browse/MNG-5167?page=com.atlassian.j
>>> ira.plugin.system.issuetabpanels:all-tabpanel ]
>>>> 
>>>> Jason van Zyl closed MNG-5167.
>>>> ------------------------------
>>>> 
>>>>   Resolution: Won't Fix
>>>> 
> 
> --
> Jason Pyeron
> 202-741-9397
> Systems Engineering & Architecture SME
> Program Executive Office for Mission Assurance
> Defense Information Systems Agency

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
---------------------------------------------------------

Simplex sigillum veri. (Simplicity is the seal of truth.)









Reply via email to