Ah-Ha! Thank you so much.
I think that is the best solution yet! Although, even better would be
if maven had an additional param on <plugin> in which it meant
inherited, but not run. And then I wouldn't even have to put the
definition there. One can dream...
Thanks again,
-Ben
Brad Szabo wrote:
Have you considered using the build/pluginManagement element to define
common inheritable plugin configurations instead of using profiles?
-Brad
On Tue, 2007-02-27 at 14:15 -0500, Ben Tatham wrote:
basically, I have a parent pom...ie a maven project with
<packaging>pom</packaging>
Each of my projects use that as the <parent>.
Option one sounds interesting...do submodules have to be
subdirectories? Does the top-level pom module have to be able to build
on its own, because it won't in my configuration because it expects
certain directories to exist that don't exist except for in the real
projects.
Thanks for your continuing assistance...
-Ben
Mick Knutson wrote:
Hmm. Not sure I understand.
But you can always create a master pom, and have each of your projects
create a sub module on your project that way they will always extend your
master pom.xml for everyone.
You could also mandate that each pom.xml only have access to your remote
repo not the main maven repo, thus they will only have access to the
plugins
you have in your repo. But that does not help with the config of the
plugins.
On 2/27/07, Ben Tatham <[EMAIL PROTECTED]> wrote:
between projects -- we don't use modules. and the projects are pretty
separate except for the build tools required.
Is it possible to make my own plugin of plugins easily...with just xml?
is there another solution for this?
-Ben
Mick Knutson wrote:
Are you trying to share plugin info between projects, or modules?
On 2/27/07, Ben Tatham <[EMAIL PROTECTED]> wrote:
Nope. Apparently profiles are not inherited. Excerpt from POM
Reference:
The elements in the parent POM that are inherited by its children
are:
* dependencies
* developers and contributors
* plugin lists
* reports lists
* plugin executions with matching ids
* plugin configuration
Not profiles. Doh. Any other suggestions on how to share plugin
setups
between multiple projects?
Thanks,
Ben
Mick Knutson wrote:
try mvn -P build-web install -e
On 2/27/07, Ben Tatham <[EMAIL PROTECTED]> wrote:
Hello All,
I am having trouble getting a profile to activate.
My scenario is as follows...I have a complicated build process for
making webapps that includes xdoclet and jspc. I have all the
necessary
plugins defined in a profile on parent pom. I can't define those
plugins in the normal <build><plugins> section or the install
of the
parent pom itself fails.
I have tried two ways to activate the pom. One is to use:
<id>build-web-profile</id>
<activation>
<activeByDefault>false</activeByDefault>
<property>
<name>build-web</name>
<value>true</value>
</property>
</activation>
in my parent pom. Then I set
<properties>
<build-web>true</build-web>
</properties>
in the child pom. Doesn't work. Doesn't show up on
help:active-profiles either. I even tried adding that property to
my
settings.xml and still nothing.
Also tried using a file activation, which also fails. I read
somewhere
that that activation is still buggy though.
Anybody have any other ideas on how to do this?
Thanks in advance,
Ben
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
