On 9 Feb 07, at 12:22 PM 9 Feb 07, Dennis Lundberg wrote:
I must have misunderstood what you were trying to accomplish Jason.
I was under the impression that the changes to the parent poms were
made so that *direct* releases would work well. After that, the
work on enabling *staged* releases would start. That is what I
would prefer.
Both work.
Not everybody has the need for staging (or the possibility to set
it up), so we shouldn't force that on users. There are benefits to
staged releases, but it should be offered as an alternative to
direct releases - not a replacement.
This is only for us and we have decided to do staging. This is why I
moved to a completely externalized profile which we are using that no
one else has to.
Jason.
Jason van Zyl wrote:
On 6 Feb 07, at 5:54 PM 6 Feb 07, Carlos Sanchez wrote:
what is the status on this?
Actually in the short term what's there will work without staging
with one small change. Basically point the staging repository to
the real repository until we get the repository copying working.
So if this is fine with folks we can release the Maven POM as it
is and for people who don't want to stage can just release directly.
Doing the staging is not overly convenient but I can document that
as well if we want to enforce staging. You basically have to
install Maven on people.apache.org and install the repository
tools plugin and use it from your account on the Maven box. Until
the bug in the SCP wagon is fixed this is the only way you can
move the artifacts from the staging repository to the production
repository.
So if we release it as it is now it works fine. If you want to
stage you can, if you want to release it directly we can allow
that for the time being until the copying fully works conveniently.
Jason.
there are plugin releases waiting for it. I think we should make the
release Brett suggested and then with more time do another one if
needed.
On 1/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 31 Jan 07, at 12:30 PM 31 Jan 07, Dennis Lundberg wrote:
> +0 on this
>
I have all day tomorrow set aside for release goop. I will start in
the wee hours PST and go until the release stuff is in the POM,
doco'd and then I'll pump out the other stuff. At that point anyone
should be able to do a release.
Jason.
> If Jason says go then go.
>
> Unfortunately I haven't been able to verify the poms myself.
Can't
> seem to find enough time right now between day job and a crashing
> computer at home :(
>
> Brett Porter wrote:
>> Hi,
>> This is a dependency for upcoming plugin releases. The
changes to
>> each are attached to this message - it shifts the release
profile
>> to the maven POM, adds some developers, and removes the need for
>> the plugin surrogate parent.
>> SVN revision: 500513
>> Maven Snapshot version: 5-20070127.114244-3
>> Maven Plugins Snapshot version: 8-20070127.114249-2
>> [ ] +1
>> [ ] +0
>> [ ] -1
>> Cheers,
>> Brett
>
> --
> Dennis Lundberg
>
>
-------------------------------------------------------------------
--
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
