You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Benson Margulies <bi...@gmail.com> on 2011/07/17 23:33:13 UTC
the pom compatibility threads
Many threads lead back to the recent discussion, and all of its
predecessors, about preparing for a new version of the pom by allowing
for backwards compatibility.
How do we start this? There seemed a consensus on the design. Do we
need some branches of things?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: the pom compatibility threads
Posted by Benson Margulies <bi...@gmail.com>.
I do and I can't. The PMC chair (who's that, at the moment?) should
have karma to fix, if not I can ask Infra for help.
On Mon, Jul 18, 2011 at 4:23 AM, Mark Struberg <st...@yahoo.de> wrote:
> humm, it tells me that there are no restrictions setup for that very page. So once you have an account you should imo be able to edit that page.
>
> LieGrue,
> strub
>
> --- On Mon, 7/18/11, Arnaud Héritier <ah...@gmail.com> wrote:
>
>> From: Arnaud Héritier <ah...@gmail.com>
>> Subject: Re: the pom compatibility threads
>> To: "Maven Developers List" <de...@maven.apache.org>
>> Date: Monday, July 18, 2011, 6:11 AM
>> You can, but I don't know at all we
>> setup such rights :-)
>> Even PMCs aren't admin of the space.
>> I don't know how it is setup but I would hope that pmc
>> group in ldap was
>> admin and dev group users of this space.
>> Brett, others ?
>> Any ideas of the process to give access to Benson.
>>
>> On Mon, Jul 18, 2011 at 12:30 AM, Benson Margulies <bi...@gmail.com>wrote:
>>
>> > I don't seem to have karma for
>> >
>> > https://cwiki.apache.org/confluence/display/MAVEN/Proposals?showChildren=true#children
>> > .
>> > Can I?
>> >
>> > 2011/7/17 Arnaud Héritier <ah...@gmail.com>:
>> > > For me the first thing is to push some ideas in
>> the wiki and make them
>> > > challenged by developpers
>> > > I'm not so sure that there is a consensus and a
>> real proposal to solve
>> > that
>> > > upgrade taking care of all use cases
>> (previous/future versions of maven,
>> > > transitive dependencies, depMgt import,
>> inheritence ...)
>> > > The thing said by everybody is that we won't be
>> able to change the
>> > > format/version of *.pom files in shared
>> repositories but I saw no real
>> > > proposal to manage all cases listed above when
>> we'll have several
>> > versions
>> > > of POMs out (even if we just add new entries).
>> > >
>> > > Arnaud
>> > >
>> > > On Sun, Jul 17, 2011 at 11:33 PM, Benson
>> Margulies <
>> > bimargulies@gmail.com>wrote:
>> > >
>> > >> Many threads lead back to the recent
>> discussion, and all of its
>> > >> predecessors, about preparing for a new
>> version of the pom by allowing
>> > >> for backwards compatibility.
>> > >>
>> > >> How do we start this? There seemed a
>> consensus on the design. Do we
>> > >> need some branches of things?
>> > >>
>> > >>
>> ---------------------------------------------------------------------
>> > >> 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
>> >
>> >
>>
>
> ---------------------------------------------------------------------
> 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: the pom compatibility threads
Posted by Mark Struberg <st...@yahoo.de>.
humm, it tells me that there are no restrictions setup for that very page. So once you have an account you should imo be able to edit that page.
LieGrue,
strub
--- On Mon, 7/18/11, Arnaud Héritier <ah...@gmail.com> wrote:
> From: Arnaud Héritier <ah...@gmail.com>
> Subject: Re: the pom compatibility threads
> To: "Maven Developers List" <de...@maven.apache.org>
> Date: Monday, July 18, 2011, 6:11 AM
> You can, but I don't know at all we
> setup such rights :-)
> Even PMCs aren't admin of the space.
> I don't know how it is setup but I would hope that pmc
> group in ldap was
> admin and dev group users of this space.
> Brett, others ?
> Any ideas of the process to give access to Benson.
>
> On Mon, Jul 18, 2011 at 12:30 AM, Benson Margulies <bi...@gmail.com>wrote:
>
> > I don't seem to have karma for
> >
> > https://cwiki.apache.org/confluence/display/MAVEN/Proposals?showChildren=true#children
> > .
> > Can I?
> >
> > 2011/7/17 Arnaud Héritier <ah...@gmail.com>:
> > > For me the first thing is to push some ideas in
> the wiki and make them
> > > challenged by developpers
> > > I'm not so sure that there is a consensus and a
> real proposal to solve
> > that
> > > upgrade taking care of all use cases
> (previous/future versions of maven,
> > > transitive dependencies, depMgt import,
> inheritence ...)
> > > The thing said by everybody is that we won't be
> able to change the
> > > format/version of *.pom files in shared
> repositories but I saw no real
> > > proposal to manage all cases listed above when
> we'll have several
> > versions
> > > of POMs out (even if we just add new entries).
> > >
> > > Arnaud
> > >
> > > On Sun, Jul 17, 2011 at 11:33 PM, Benson
> Margulies <
> > bimargulies@gmail.com>wrote:
> > >
> > >> Many threads lead back to the recent
> discussion, and all of its
> > >> predecessors, about preparing for a new
> version of the pom by allowing
> > >> for backwards compatibility.
> > >>
> > >> How do we start this? There seemed a
> consensus on the design. Do we
> > >> need some branches of things?
> > >>
> > >>
> ---------------------------------------------------------------------
> > >> 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
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: the pom compatibility threads
Posted by Arnaud Héritier <ah...@gmail.com>.
You can, but I don't know at all we setup such rights :-)
Even PMCs aren't admin of the space.
I don't know how it is setup but I would hope that pmc group in ldap was
admin and dev group users of this space.
Brett, others ?
Any ideas of the process to give access to Benson.
On Mon, Jul 18, 2011 at 12:30 AM, Benson Margulies <bi...@gmail.com>wrote:
> I don't seem to have karma for
>
> https://cwiki.apache.org/confluence/display/MAVEN/Proposals?showChildren=true#children
> .
> Can I?
>
> 2011/7/17 Arnaud Héritier <ah...@gmail.com>:
> > For me the first thing is to push some ideas in the wiki and make them
> > challenged by developpers
> > I'm not so sure that there is a consensus and a real proposal to solve
> that
> > upgrade taking care of all use cases (previous/future versions of maven,
> > transitive dependencies, depMgt import, inheritence ...)
> > The thing said by everybody is that we won't be able to change the
> > format/version of *.pom files in shared repositories but I saw no real
> > proposal to manage all cases listed above when we'll have several
> versions
> > of POMs out (even if we just add new entries).
> >
> > Arnaud
> >
> > On Sun, Jul 17, 2011 at 11:33 PM, Benson Margulies <
> bimargulies@gmail.com>wrote:
> >
> >> Many threads lead back to the recent discussion, and all of its
> >> predecessors, about preparing for a new version of the pom by allowing
> >> for backwards compatibility.
> >>
> >> How do we start this? There seemed a consensus on the design. Do we
> >> need some branches of things?
> >>
> >> ---------------------------------------------------------------------
> >> 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: the pom compatibility threads
Posted by Benson Margulies <bi...@gmail.com>.
I don't seem to have karma for
https://cwiki.apache.org/confluence/display/MAVEN/Proposals?showChildren=true#children.
Can I?
2011/7/17 Arnaud Héritier <ah...@gmail.com>:
> For me the first thing is to push some ideas in the wiki and make them
> challenged by developpers
> I'm not so sure that there is a consensus and a real proposal to solve that
> upgrade taking care of all use cases (previous/future versions of maven,
> transitive dependencies, depMgt import, inheritence ...)
> The thing said by everybody is that we won't be able to change the
> format/version of *.pom files in shared repositories but I saw no real
> proposal to manage all cases listed above when we'll have several versions
> of POMs out (even if we just add new entries).
>
> Arnaud
>
> On Sun, Jul 17, 2011 at 11:33 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> Many threads lead back to the recent discussion, and all of its
>> predecessors, about preparing for a new version of the pom by allowing
>> for backwards compatibility.
>>
>> How do we start this? There seemed a consensus on the design. Do we
>> need some branches of things?
>>
>> ---------------------------------------------------------------------
>> 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: the pom compatibility threads
Posted by Benson Margulies <bi...@gmail.com>.
OK, I'm willing to write what I think I understood.
2011/7/17 Arnaud Héritier <ah...@gmail.com>:
> For me the first thing is to push some ideas in the wiki and make them
> challenged by developpers
> I'm not so sure that there is a consensus and a real proposal to solve that
> upgrade taking care of all use cases (previous/future versions of maven,
> transitive dependencies, depMgt import, inheritence ...)
> The thing said by everybody is that we won't be able to change the
> format/version of *.pom files in shared repositories but I saw no real
> proposal to manage all cases listed above when we'll have several versions
> of POMs out (even if we just add new entries).
>
> Arnaud
>
> On Sun, Jul 17, 2011 at 11:33 PM, Benson Margulies <bi...@gmail.com>wrote:
>
>> Many threads lead back to the recent discussion, and all of its
>> predecessors, about preparing for a new version of the pom by allowing
>> for backwards compatibility.
>>
>> How do we start this? There seemed a consensus on the design. Do we
>> need some branches of things?
>>
>> ---------------------------------------------------------------------
>> 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: the pom compatibility threads
Posted by Arnaud Héritier <ah...@gmail.com>.
For me the first thing is to push some ideas in the wiki and make them
challenged by developpers
I'm not so sure that there is a consensus and a real proposal to solve that
upgrade taking care of all use cases (previous/future versions of maven,
transitive dependencies, depMgt import, inheritence ...)
The thing said by everybody is that we won't be able to change the
format/version of *.pom files in shared repositories but I saw no real
proposal to manage all cases listed above when we'll have several versions
of POMs out (even if we just add new entries).
Arnaud
On Sun, Jul 17, 2011 at 11:33 PM, Benson Margulies <bi...@gmail.com>wrote:
> Many threads lead back to the recent discussion, and all of its
> predecessors, about preparing for a new version of the pom by allowing
> for backwards compatibility.
>
> How do we start this? There seemed a consensus on the design. Do we
> need some branches of things?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>