On Mon, 14 Apr 2008 05:53:50 David Jencks wrote:
> a. Put the parent pom somewhere else, like in plugins/trunk/plugin-
> parent. The pom in plugins/trunk would just have the modules element.
>
> I prefer (a) because then tagging the parent pom wont copy the entire
> set of plugins in a unreleased
On Apr 13, 2008, at 1:21 AM, Benjamin Bentmann wrote:
Brian E. Fox wrote:
I saw leave it as it is because that is the normal scenario and
the one
users are most likely to have. This way we see and fix the same
things
they will need.
+1. The reactor was meant for exactly those aggregating
Brian E. Fox wrote:
I saw leave it as it is because that is the normal scenario and the one
users are most likely to have. This way we see and fix the same things
they will need.
+1. The reactor was meant for exactly those aggregating builds. The usual
way to disable recursive builds is the -N
Subject: Re: [regression] Cannot release plugins parent!
For a situation like this where a "parent" is also being used
sometimes for building all the "children" although that is not its
primary purpose, how about putting the modules in a profile that e.g.
hudson can use?
r
release and put it back after, then that's ok.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 5:55 PM
To: Maven Developers List
Subject: Re: [regression] Cannot release plugins parent!
Is that to prevent you from having to set up 39 ind
ut it back after, then that's ok.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 5:55 PM
To: Maven Developers List
Subject: Re: [regression] Cannot release plugins parent!
Is that to prevent you from having to set up 39 individual p
, 2008 8:47 AM
To: Maven Developers List
Subject: Re: [regression] Cannot release plugins parent!
What is the purpose of having a element for our plugins?
It's
not like we want to build all plugins in one go, is it?
Hudson used to do this if I remember correctly (the plugin ITs seem to
Hudson uses this to detect the children so we need this in there.
-Original Message-
From: Benjamin Bentmann [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 8:47 AM
To: Maven Developers List
Subject: Re: [regression] Cannot release plugins parent!
> What is the purpose
What is the purpose of having a element for our plugins? It's
not like we want to build all plugins in one go, is it?
Hudson used to do this if I remember correctly (the plugin ITs seem to have
been removed recently).
Benjamin
To: Maven Developers List
Subject: [regression] Cannot release plugins parent!
I've stumbled upon some kind of regression trying to release the plugins
parent. I'm not sure where the regression is though. Sigh!
I have to use Maven 2.0.8, because maven-javadoc-plugin apparently
requires 2
ut at
least if
it's reproducible we can attempt to fix it there.
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Tuesday,
April 01, 2008 3:13 PM
To: Maven Developers List
Subject: [regression] Cannot release plugins parent!
I've stumbled upon some kin
st
Subject: [regression] Cannot release plugins parent!
I've stumbled upon some kind of regression trying to release the plugins
parent. I'm not sure where the regression is though. Sigh!
I have to use Maven 2.0.8, because maven-javadoc-plugin apparently
requires 2.0.8 now. But if I do the
annot release plugins parent!
I've stumbled upon some kind of regression trying to release the plugins
parent. I'm not sure where the regression is though. Sigh!
I have to use Maven 2.0.8, because maven-javadoc-plugin apparently
requires 2.0.8 now. But if I do the build fails with an erro
I've stumbled upon some kind of regression trying to release the plugins
parent. I'm not sure where the regression is though. Sigh!
I have to use Maven 2.0.8, because maven-javadoc-plugin apparently
requires 2.0.8 now. But if I do the build fails with an error because of
a circular dependency.
14 matches
Mail list logo
