On Feb 23, 2012, at 8:35 PM, Chris Graham wrote:
>> I can imagine that many of the Maven-interoperability issues that ivy
>> had/has (I've not been near it for some years) are attributable to the lack
>> of a usable specification of repository layouts, operational semantics, etc.
>
> I think t
On Feb 23, 2012, at 12:29 PM, Manfred Moser wrote:
> On 12-02-23 04:37 AM, Chas Emerick wrote:
>> On Feb 23, 2012, at 1:01 AM, Chris Graham wrote:
>>
>>> Remember that 'deploy' still calls 'install'.
>> Very true for `mvn`. Not true in
Yeah, I'll post over there shortly.
However, while Aether is the now-canonical implementation of these operations,
many other tools exist (and will exist) that create, update, and access Apache
Maven repository data. It seems like having well-defined semantics for such
things separate from any
think you mean something
> else when you say "deploy operation".
>
>> -Original Message-
>> From: Chas Emerick [mailto:c...@cemerick.com]
>> Sent: Thursday, February 23, 2012 7:38 AM
>> To: Maven Developers List
>> Subject: Re: Functional distincti
On Feb 23, 2012, at 1:01 AM, Chris Graham wrote:
> Remember that 'deploy' still calls 'install'.
Very true for `mvn`. Not true in Aether; this would seem to be a userland tool
convention, and not a fundamental characteristic of the 'deploy' operation.
However, even Aether leaves some resolver
On Feb 22, 2012, at 11:54 PM, Manfred Moser wrote:
> On 12-02-22 08:11 PM, Chas Emerick wrote:
>> I am working on a Clojure facade for Aether,[1] and would like to clarify
>> some semantics. Though I'm working with Aether, I think this question is
>> generally appl
I am working on a Clojure facade for Aether,[1] and would like to clarify some
semantics. Though I'm working with Aether, I think this question is generally
applicable for all Maven tools…but let me know if I should simply bounce to the
Aether ML.
In short, I'd like to know what the functional
For what it's worth, working around Maven not having had a release since the
1.12 release of Aether has been an unwelcome hassle. (FYI, I reported one
of the issues Jason mentioned, MNG-5087.)
I don't have much perspective on the intricacies or history of the licensing
and governance issues that
