Generally, prodding is enough. Sometimes, it might require multiple
attempts.
Archetype is particularly problematic, though, as the current trunk
has a limited future as there is some work ongoing to rewrite it, but
with no timeline for it replacing the current implementation. It's
obviou
Does anybody have an answer for this? I enjoy submitting patches, but I'm not
really willing to do them if they are going into a black hole.
Thanks,
Matt
- Original Message
From: Matthew Flower <[EMAIL PROTECTED]>
To: dev@maven.apache.org
Sent: Wednesday, October 24, 2007 3:46:05 PM
Su
On 10/29/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> +1
> and if you add the deployment of site too even better
+1, I've been wanting this for ages
+1 to site docs too (I assume the snapshot site docs reside in
somewhere other that maven.apache.org)
---
+1
and if you add the deployment of site too even better
On 10/28/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> I've just been trying to build a few things here and there today, and
> found a mass of snapshots not deployed to the repository.
>
> Given that Continuum has quietly been been performin
I've just been trying to build a few things here and there today, and
found a mass of snapshots not deployed to the repository.
Given that Continuum has quietly been been performing reliably on the
zone and producing these snapshots, and is being properly monitored,
I'd like to have it ship
On 29/10/2007, at 3:22 PM, Jason van Zyl wrote:
On 28 Oct 07, at 8:19 PM 28 Oct 07, Brett Porter wrote:
I've done this, with the exception of maven-script since it now
seems to depend on Maven trunk, which would block us releasing
anything under there.
I just took the copy from trunk,
On 28 Oct 07, at 8:19 PM 28 Oct 07, Brett Porter wrote:
I've done this, with the exception of maven-script since it now
seems to depend on Maven trunk, which would block us releasing
anything under there.
I just took the copy from trunk, if it is coupled to trunk I'll fix
that as it sh
... and the maven-plugin-testing-tools since they depend on snapshots
of the invoker and test-tools, neither of which are deployed, and the
invoker doesn't build because of failed tests.
- Brett
On 29/10/2007, at 2:19 PM, Brett Porter wrote:
I've done this, with the exception of maven-scrip
I've done this, with the exception of maven-script since it now seems
to depend on Maven trunk, which would block us releasing anything
under there.
- Brett
On 20/09/2007, at 11:31 AM, Brett Porter wrote:
I'd like to do what we did for surefire and bring all the following
into one tree, c
That's the ideal scenario, but pom changes mean 2.1. I can't think of
any other way to handle this without causing even more havoc.
-Original Message-
From: William Ferguson [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 28, 2007 8:25 PM
To: Maven Developers List
Subject: MNG-3244 [was R
Brian, are you suggesting that a POM property be used invoke the new
behaviour, and lack of it invokes existing behaviour? I'd be happy with
that.
William
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Thursday, 25 October 2007 10:09 PM
To: Maven Developers List
I disagree, if there's no pom it's to allow other people to contribute it
Maybe it's our fault for not adding a check to the release plugin and
fail when poms are missing, but it's like people making releases with
repositories other than central that have things messed up or jars
that are not in ce
Just wait till I'll start using it! :)
On 10/28/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>
> Damn, you caught me ;-)
>
> -Original Message-
> From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
> Sent: Sunday, October 28, 2007 4:26 AM
> To: Maven Developers List
> Subject: Re: [ANN] Maven R
Hi,
I have the same issue with the site plugin when I have added an it.
Have a look at the pom [1] to see how goals are invoked :
${project.groupId}:${project.artifactId}:${project.version
}:site
With this notation no harcoding in the it poms.
--
Olivier
[1]
https://svn.apache.org/repos/asf/maven
Damn, you caught me ;-)
-Original Message-
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 28, 2007 4:26 AM
To: Maven Developers List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-7 Released
On 10/28/07, Arik Kfir <[EMAIL PROTECTED]> wrote:
> There's a mistake in
Hi,
Olivier has added recently the structure for IT tests which is a great
idea. I've faced a very annoying issue however. It seems that the
invoker does not use the current development version of the plugin but
the latest release (2.1-alpha-1).
I had to hard code the current dev version to make
On 10/28/07, Arik Kfir <[EMAIL PROTECTED]> wrote:
> There's a mistake in the text - it should read "release of the Maven
> ReleasePlugin", not the "
> WAR plugin"...
> Probably something in the POM plugin configuration that was once
> copy-pasted... ;-)
Well No. Brian did the copy pasting for sure
Oh... :)
On 10/28/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
>
> On 10/28/07, Arik Kfir <[EMAIL PROTECTED]> wrote:
> > There's a mistake in the text - it should read "release of the Maven
> > ReleasePlugin", not the "
> > WAR plugin"...
> > Probably something in the POM plugin configuration th
There's a mistake in the text - it should read "release of the Maven
ReleasePlugin", not the "
WAR plugin"...
Probably something in the POM plugin configuration that was once
copy-pasted... ;-)
On 10/27/07, Brian Fox <[EMAIL PROTECTED]> wrote:
>
> The Maven team is pleased to announce the release
19 matches
Mail list logo
