On 9 Feb 07, at 12:46 PM 9 Feb 07, Dennis Lundberg wrote:
Jason van Zyl wrote:
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 *dire
Jason van Zyl wrote:
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
enabl
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* releas
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.
Not everybody has
On 6 Feb 07, at 10:49 PM 6 Feb 07, Wendy Smoak wrote:
On 2/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
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 reposito
On 2/6/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
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
On 07/02/2007, at 11:58 AM, 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 unt
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
th
On 6 Feb 07, at 5:54 PM 6 Feb 07, Carlos Sanchez wrote:
what is the status on this?
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.
Actually on the repository copying Joakim was going to help me tr
On 6 Feb 07, at 5:54 PM 6 Feb 07, Carlos Sanchez wrote:
what is the status on this?
Just working on the repository copying/merging but the rest of it
works. If someone wants to release something now then I can flip it
back to releasing directly but I wanted to move toward having a real
what is the status on this?
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 th
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
+0 on this
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
+1 for both.
Emmanuel
Brett Porter a écrit :
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:
+1 for both
Arnaud
On 1/27/07, Brett Porter <[EMAIL PROTECTED]> 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
On 28 Jan 07, at 10:02 AM 28 Jan 07, Stephane Nicoll wrote:
Folks,
I won't have time today to do this and I am not sure I'll be able to
handle this short term. If anyone can do it, that would be good. Let
us know.
I'll start taking care of it now. I was going to anyway, but if
anyone can
Folks,
I won't have time today to do this and I am not sure I'll be able to
handle this short term. If anyone can do it, that would be good. Let
us know.
Thanks,
Stéphane
On 1/28/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
You can:
1) Update the Maven Project POM with this:
http://idisk.mav
You can:
1) Update the Maven Project POM with this:
http://idisk.maven.org/jvanzyl/Public/release/release-snippet.txt
2) Update the documentation here:
http://idisk.maven.org/jvanzyl/Public/release/release-snippet.txt
You need to document the new way which strictly uses the new profile
and
+1 if we can get my name in there, looks like I forgot to commit it
when I added myself in there :)
jesse
On 1/28/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
All right. Who's responsible for fixing this? Can I help?
I have two plugin releases waiting for that and if there's anything I
can
All right. Who's responsible for fixing this? Can I help?
I have two plugin releases waiting for that and if there's anything I
can do to speed this up, let me know.
Thanks,
Séphane
On 1/28/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 27 Jan 07, at 1:21 PM 27 Jan 07, Brett Porter wrote:
On 27 Jan 07, at 1:21 PM 27 Jan 07, Brett Porter wrote:
On 28/01/2007, at 2:51 AM, Jason van Zyl wrote:
1) Be in one place not an admixture of something in the parent POM
and something elsewhere. It's too confusing to know where things
come from. Unfortunately the help:effecective-pom com
+1 (to both)
- Joakim
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 revis
On 28/01/2007, at 2:51 AM, Jason van Zyl wrote:
1) Be in one place not an admixture of something in the parent POM
and something elsewhere. It's too confusing to know where things
come from. Unfortunately the help:effecective-pom command doesn't
provide the source for the bits and pieces m
On 27 Jan 07, at 3:43 AM 27 Jan 07, 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.
+1
Stéphane
On 1/27/07, Brett Porter <[EMAIL PROTECTED]> 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.
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.114
26 matches
Mail list logo
