>So if they wanted to we can't stop them using what's available in Aether APIs
>anyway. So I >suppose we could leave it up to them. I don't see the big deal
>really.
Sure but lets give them a standard to follow for this and try to
prevent it from exploding randomly.
On Nov 4, 2010, at 7:04 PM, Brian Fox wrote:
> I'm not sure I understand. Is the proposal here to deploy non-XML project
> descriptors to the repository in addition to the standard pom? If so,
> what is the point?
In the case of the Clojure dialect there will be two othe
On 4 November 2010 18:04, Brian Fox wrote:
> I'm not sure I understand. Is the proposal here to deploy non-XML project
> descriptors to the repository in addition to the standard pom? If so,
> what is the point?
In the case of the Clojure dialect there will be two other im
I'm not sure I understand. Is the proposal here to deploy non-XML project
descriptors to the repository in addition to the standard pom? If so,
what is the point?
>>>
>>> In the case of the Clojure dialect there will be two other implementations
>>> using the same dialect. Lein,
On Nov 2, 2010, at 8:25 AM, Brett Porter wrote:
> On 01/11/2010, at 6:37 PM, Jason van Zyl wrote:
>
>> At any rate if anyone has ideas or documents I'll integrate it into the
>> proposal I'm writing. I'm moving pretty fast and I plan to release a version
>> of the Maven Shell next week, and th
On Nov 2, 2010, at 4:12 AM, Ralph Goers wrote:
>
> On Nov 1, 2010, at 7:36 PM, Jason van Zyl wrote:
>
>>
>> On Nov 2, 2010, at 3:29 AM, Ralph Goers wrote:
>>
>>> I'm not sure I understand. Is the proposal here to deploy non-XML project
>>> descriptors to the repository in addition to the sta
On 01/11/2010, at 6:37 PM, Jason van Zyl wrote:
> At any rate if anyone has ideas or documents I'll integrate it into the
> proposal I'm writing. I'm moving pretty fast and I plan to release a version
> of the Maven Shell next week, and then a couple weeks later a version with
> Polyglot capabi
On Nov 1, 2010, at 7:36 PM, Jason van Zyl wrote:
>
> On Nov 2, 2010, at 3:29 AM, Ralph Goers wrote:
>
>> I'm not sure I understand. Is the proposal here to deploy non-XML project
>> descriptors to the repository in addition to the standard pom? If so, what
>> is the point?
>
> In the case
gets committed.
Interoperability is step 1. Without figuring that out nothing gets
changed/added.
> However, I agree that a 4.0.0 pom should be generated from the new model.
>
> Ralph
>
> On Nov 1, 2010, at 3:37 PM, Jason van Zyl wrote:
>
>> I am working on a re
iscussed before code gets
committed. However, I agree that a 4.0.0 pom should be generated from the new
model.
Ralph
On Nov 1, 2010, at 3:37 PM, Jason van Zyl wrote:
> I am working on a release of Polyglot Maven and the only tangible thing
> stopping me is having a plan for POM int
eady make a
>> reduced dependency POM if you like.
>>
>>> 3. Backwards compat.
>>>
>>
>> Sure, which is 2) when we start making changes to the POM.
>>
>>> 4. Properties behaving badly
>>>
>>
>> You'll hav
ly
>>
>
> You'll have to explain here. I honestly don't know what you mean here.
>
>> -Stephen
>>
>> On 1 November 2010 22:37, Jason van Zyl wrote:
>>> I am working on a release of Polyglot Maven and the only tangible thing
>>> stoppin
I honestly don't know what you mean here.
> -Stephen
>
> On 1 November 2010 22:37, Jason van Zyl wrote:
>> I am working on a release of Polyglot Maven and the only tangible thing
>> stopping me is having a plan for POM interoperability between:
>>
>> 1) Di
. Backwards compat.
4. Properties behaving badly
-Stephen
On 1 November 2010 22:37, Jason van Zyl wrote:
> I am working on a release of Polyglot Maven and the only tangible thing
> stopping me is having a plan for POM interoperability between:
>
> 1) Different representations of t
I am working on a release of Polyglot Maven and the only tangible thing
stopping me is having a plan for POM interoperability between:
1) Different representations of the model for the same version of the model.
This is what I'd like for the first version of Polyglot Maven where I just wan
15 matches
Mail list logo