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
> 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 that you've found the real issue there. It's the same one a
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 Aether; this would seem to be a userland
>> tool conventio
s Emerick [mailto:c...@cemerick.com]
Sent: Thursday, February 23, 2012 7:38 AM
To: Maven Developers List
Subject: Re: Functional distinction between install and deploy
operations
On Feb 23, 2012, at 1:01 AM, Chris Graham wrote:
Remember that 'deploy' still calls 'install'.
Ve
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 Aether; this would seem to be a userland tool
convention, and not a fundamental characteristic of the 'deploy' operation.
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
l Message-
> >> From: Chas Emerick [mailto:c...@cemerick.com]
> >> Sent: Thursday, February 23, 2012 7:38 AM
> >> To: Maven Developers List
> >> Subject: Re: Functional distinction between install and deploy
> >> operations
> >>
> &
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
ailto:c...@cemerick.com]
> Sent: Thursday, February 23, 2012 7:38 AM
> To: Maven Developers List
> Subject: Re: Functional distinction between install and deploy
> operations
>
>
> On Feb 23, 2012, at 1:01 AM, Chris Graham wrote:
>
> > Remember that 'deploy'
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
Remember that 'deploy' still calls 'install'.
-Chris
On Thu, Feb 23, 2012 at 4:35 PM, Chas Emerick wrote:
>
> 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
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 applicable for all Maven tools…bu
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
applicable for all Maven tools…but let me know if I should simply bounce to the
Aether ML.
In
13 matches
Mail list logo
