Last week we had some heated discussions on this list revolving around
Ralph's veto that was prompted by a license change to a dependency
used by Maven Core.
Two things have come from this:
1) The PMC voted to pass a new policy to cover external dependencies:
all core dependencies must be either
*
The projectbuilder comes to mind.
On Wed, Feb 2, 2011 at 11:29 AM, Moser, Christian wrote:
> I'm currently developing a custom enforcer rule.
>
>
>
> How can I get object references to all modules of a parent pom ?
>
>
>
> final List modulesRelativePath = parentProject.getModules();
>
>
>
> deliv
You could simply add a flag or alternate mojo to the dependency plugin
to allow it to fail. IIRC the analyze goal already does this. IOW it's
not a requirement that every mojo that fails a build be rolled into
the enforcer plugin. Failing that, you'd have to pull all the logic
out into a shared com
I'm currently developing a custom enforcer rule.
How can I get object references to all modules of a parent pom ?
final List modulesRelativePath = parentProject.getModules();
delivers only the relative path to the project pom. I need something
like :
final List subSystemProjects =
b
Hi folks,
I'd like to work on MENFORCER-19,
org.apache.maven.plugin.dependency.AnalyzeDepMgt has all the necessary code
to create an EnforcerRule "EnforceDependencyManagement", but I wonder how we
should manage such code duplication. Copy/paste some hundred lines from
dependency plugin into enforc
On Wed, Feb 2, 2011 at 3:11 PM, Jonthan DeMaagd wrote:
> Maven 3.0.2 was installed correctly on Windows Vista.
>
>
>
>
>
> Check for correct installation of maven results:
>
>
>
> mvn -v
>
> Apache Maven 3.0.2 (r1056850; 2011-01-08 19:58:10-0500)
>
> Java version: 1.6.0_23, vendor: Sun Microsystem
