pluginManagement is not definition of the plugin, and really should
only be used when the plugin is defined in a build, so it really
shouldn't matter... but I am still not sure if mvn will like that or
not.
And really the two stage build is only a hack around this problem...
other mvnisms like the release plugin don't know anything about the
two stages, and thus mvn release:perform will fail because of this.
Please make sure that moving this to the top-level pom does not break
anything.
--jason
On Dec 20, 2006, at 5:23 PM, anita kulshreshtha wrote:
As we have discussed before, if a plugin (with extensions) is used
*anywhere* in the build tree , maven makes sure that it is available
even before the projects are sorted. But that is not a problem with
our
two stage build, i.e. it builds modules and plugins first from modules
and plugins directory.
I will move it from configs pom to top level pom.
Thanks
Anita
--- Jason Dillon <[EMAIL PROTECTED]> wrote:
Check if the pluginManagement element from configs/pom.xml can be
moved to the project pom. It might work there, not sure if it does
any validation of that plugin to make sure it exists or not at the
top or only where used. If its the later than moving the element to
the parent will work. Else... have to redefine that pluginManagement
section in assemblies/pom.xml since the version of mvn that we are
using can't handle configuration of plugin which is an extension
that built and used by a project.
Though... I would expect that using the car plugin with out a version
would only pick a released version... it should not pick up a
SNAPSHOT, so perhaps there is another mvn bug hiding in this
scenario... like its half configured, found a version, then looses
that information and then tries to do some resolution based on what
artifacts it has found. Either way its broken.
Try moving this:
<pluginManagement>
<plugins>
<plugin>
<groupId>org.apache.geronimo.plugins</groupId>
<artifactId>car-maven-plugin</artifactId>
<version>${version}</version>
<extensions>true</extensions>
</plugin>
</plugins>
</pluginManagement>
to the project pom.xml and see if it works as expected or not. Be
sure to validate on a clean repo though...
--jason
On Dec 20, 2006, at 4:24 PM, anita kulshreshtha wrote:
The car plugin version is defined in configs pom. This
definition
is not inherited by assemblies pom and hence by boilerplate-j2ee
assembly. In the absence of a version maven picks up an available
version. This would explain the recent problems building two
different
versions of geronimo, e.g. branhes/1.2 and trunk. We need to add
<version>${version}</version> to assemblies pom or the top level
pom.
Thanks
Anita
--- anita kulshreshtha <[EMAIL PROTECTED]> wrote:
Does anyone know why boilerplate-j2ee assembly (trunk) is
using
1.2-SNAPSHOT version of car-maven-plugin?
Thanks
Anita
[INFO]
----------------------------------------------------------------------
------
[INFO] Building Geronimo Assemblies :: Boilerplate J2EE
[INFO] task-segment: [clean, install]
[INFO]
----------------------------------------------------------------------
------
[INFO] artifact org.apache.geronimo.plugins:car-maven-plugin:
checking
for updates from co
dehaus
[INFO] snapshot
org.apache.geronimo.plugins:car-maven-plugin:1.2-SNAPSHOT:
checking
for
up
dates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:car-maven-plugin:1.2-SNAPSHOT:
checking
for
up
dates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:maven-plugins:1.2-SNAPSHOT:
checking for updat
es from apache-snapshots
[INFO] snapshot
org.apache.geronimo.plugins:maven-plugins:1.2-SNAPSHOT:
checking for updat
es from codehaus-snapshots
[INFO] snapshot org.apache.geronimo:geronimo:1.2-SNAPSHOT:
checking
for
updates from apach
e-snapshots
[INFO] snapshot org.apache.geronimo:geronimo:1.2-SNAPSHOT:
checking
for
updates from codeh
aus-snapshots
[INFO] [clean:clean]
[INFO] Deleting directory
C:\anita\geronimo\g2.0\assemblies\geronimo-boilerplate-j2ee\targ
et
[INFO] Deleting directory
C:\anita\geronimo\g2.0\assemblies\geronimo-boilerplate-j2ee\targ
et\classes
[INFO] Deleting directory
C:\anita\geronimo\g2.0\assemblies\geronimo-boilerplate-j2ee\targ
et\test-classes
[INFO] [tools:require-java-version {execution:
validate-java-version}]
[INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] Created dir:
C:\anita\geronimo\g2.0\assemblies\geronimo-boilerplate-j2ee\target\cla
sses\META-INF
[INFO] Copying 2 files to
C:\anita\geronimo\g2.0\assemblies\geronimo-boilerplate-j2ee\targ
et\classes\META-INF
[INFO] [dependency:unpack {execution: unpack-boilerplate}]
[INFO] Configured Artifact:
org.apache.geronimo.assemblies:geronimo-boilerplate-minimal:nu
ll:2.0-SNAPSHOT:jar
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-boilerplate-minimal:2.0-
SNAPSHOT:
checking for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-boilerplate-minimal:2.0-
SNAPSHOT:
checking for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-boilerplate-minimal:2.0-
SNAPSHOT:
checking for updates from apache.snapshots
[INFO] Expanding: C:\Documents and
Settings\Anita\.m2\repository\org\apache\geronimo\assem
blies\geronimo-boilerplate-minimal\2.0-SNAPSHOT\geronimo-
boilerplate-minimal-2.0-SNAPSHOT.
jar into
C:\anita\geronimo\g2.0\assemblies\geronimo-boilerplate-j2ee\target
\boilerplate
[INFO] [antrun:run {execution: extend-boilerplate}]
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
