I haven't, and we just did some training using m2e this week and had
examples for exactly these scenarios.
-Original Message-
From: Lachlan Deck [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 02, 2008 7:24 PM
To: Maven Users List
Subject: Re: pluginManagement help (eclipse problem)
Hi.
Hi Is no one seeing this?
On 02/08/2008, at 9:14 PM, Lachlan Deck wrote:
Hi there,
I've noticed that with both m2eclipse and q4e that the
pluginManagement section of the uppermost parent is not inherited to
child modules.
So in a child module I have:
foo
The IZPack team is pleased to announce the availablity of IZPack
Standalone Compiler 4.0.1 and IZPack Maven Plugin 1.0-alpha-1
at Maven Central
http://repo1.maven.org/maven2/org/codehaus/izpack
The plugin allowsuser to build installater using IZPack the Maven way.
The site is at
http://izpack.c
Announcing the Maven CLI Plugin, which provides an interactive command
line interface to Maven plugins. The plugin allows you to execute
specific plugin goals, and alias common goal sets. The motivation for
this plugin is to reduce the amount of time executing Maven tasks,
specifically repeated go
I tried your POM. Here are my findings:
[WARNING] While downloading javax.xml:jaxws-api:2.0
This artifact has been relocated to javax.xml.ws:jaxws-api:2.0.
suggests that you should change the groupId for that dependency.
The following jars are not available in the central repo, so I had to
c
Hi there,
I've noticed that with both m2eclipse and q4e that the
pluginManagement section of the uppermost parent is not inherited to
child modules.
So in a child module I have:
foo
bar
Building from the command line works no problems. Bu