You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jason van Zyl <ja...@maven.org> on 2007/02/07 18:58:10 UTC
Testing new POMs
Hi,
Stephane and I are going to try out the new POMs but in order to do
that we need to release them. So I'm going to release them, and we'll
try them so if there's something wrong we'll release them again. I
think this is an indication that profiles for releasing stuff should
not be in parent POMs as this is problematic and rapid change or
improvement is a PITA.
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Testing new POMs
Posted by Brett Porter <br...@apache.org>.
On 08/02/2007, at 5:57 AM, Jason van Zyl wrote:
>>
>> Can't you "release" them to a fake repository?
>>
>
> I don't think it matters really. We'll try a couple things, if it
> doesn't work we'll release them again and no one will reference the
> old stuff.
Sound like famous last words when diddling with a 'production system' :)
As long as at the end of the day anyone can cut a release without
needing snapshots of maven/release plugin/poms/etc., then I'm happy.
>
>>> I think this is an indication that profiles for releasing stuff
>>> should not be in parent POMs as this is problematic and rapid
>>> change or improvement is a PITA.
>>
>> Where should they be if not in the parent POM? Or are you
>> referring to the super POM?
>>
>
> A mixin profile stored in a repository as we've chatted about before.
Sorry to digress, but while I totally agree in concept - how does
this allow you to more rapidly change or improve it, while still
retaining strong versioning? Presumably by overriding it in the child
POMs?
Aside from that, I'd rather not see rapid change or improvement in
the release process in the future :) Once it works as desired, it
should be stable for a long time to come. This was really the impetus
behind me wanting to retain the existing process until this was fully
baked.
But I'm glad it's getting there. Staging stuff is important. Thanks
for doing it.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Testing new POMs
Posted by Jason van Zyl <ja...@maven.org>.
On 7 Feb 07, at 1:20 PM 7 Feb 07, Brett Porter wrote:
> On 08/02/2007, at 4:58 AM, Jason van Zyl wrote:
>
>> Hi,
>>
>> Stephane and I are going to try out the new POMs but in order to
>> do that we need to release them. So I'm going to release them, and
>> we'll try them so if there's something wrong we'll release them
>> again.
>
> Can't you "release" them to a fake repository?
>
I don't think it matters really. We'll try a couple things, if it
doesn't work we'll release them again and no one will reference the
old stuff.
>> I think this is an indication that profiles for releasing stuff
>> should not be in parent POMs as this is problematic and rapid
>> change or improvement is a PITA.
>
> Where should they be if not in the parent POM? Or are you referring
> to the super POM?
>
A mixin profile stored in a repository as we've chatted about before.
> - Brett
>
> ---------------------------------------------------------------------
> 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: Testing new POMs
Posted by Brett Porter <br...@apache.org>.
On 08/02/2007, at 4:58 AM, Jason van Zyl wrote:
> Hi,
>
> Stephane and I are going to try out the new POMs but in order to do
> that we need to release them. So I'm going to release them, and
> we'll try them so if there's something wrong we'll release them again.
Can't you "release" them to a fake repository?
> I think this is an indication that profiles for releasing stuff
> should not be in parent POMs as this is problematic and rapid
> change or improvement is a PITA.
Where should they be if not in the parent POM? Or are you referring
to the super POM?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org