[ANN] Apache Maven Enforcer Plugin 3.5.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.5.0 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https

[ANN] Apache Maven Enforcer Plugin 3.4.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.4.1 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https

[ANN] Apache Maven Enforcer Plugin 3.4.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.4.0 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https

[ANN] Apache Maven Enforcer Plugin 3.3.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.3.0 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https

[ANN] Apache Maven Enforcer Plugin 3.2.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.2.1 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https

[ANN] Apache Maven Enforcer Plugin 3.1.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.1.0 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user created rules. https

[Enforcer plugin] Snapshot update of currently analyzed module

Hello, I've got a question regarding the Maven Enforcer Plugin. There is a behaviour I do not fully understand with the dependency convergence rule. When the enforcer plugin launches, it tries to download the maven-metadata.xml of the module it tries to enforce. I would expect it to download

Re: Maven enforcer plugin regarding child module's groupId

n Tue, 31 Aug 2021 at 16:29, David Hoffer wrote: > > > > > I'd love to see that added to the included rules in the enforcer > plugin. > > > > > > -Dave > > > > > > On Tue, Aug 31, 2021 at 6:53 AM Matt Benson > wrote: > > > >

Re: Maven enforcer plugin regarding child module's groupId

outset? > > ${project.parent.groupId}.${project.parent.artifactId} > > Delany > > > On Tue, 31 Aug 2021 at 16:29, David Hoffer wrote: > > > I'd love to see that added to the included rules in the enforcer plugin. > > > > -Dave > > > > On Tue, Aug 31, 2021 at 6:53 AM

Re: Maven enforcer plugin regarding child module's groupId

Instead of policing deviations with a rule, why not make this possible at the outset? ${project.parent.groupId}.${project.parent.artifactId} Delany On Tue, 31 Aug 2021 at 16:29, David Hoffer wrote: > I'd love to see that added to the included rules in the enforcer plugin. > &

Re: Maven enforcer plugin regarding child module's groupId

I'd love to see that added to the included rules in the enforcer plugin. -Dave On Tue, Aug 31, 2021 at 6:53 AM Matt Benson wrote: > On Tue, Aug 31, 2021, 3:28 AM Delany wrote: > > > Good question. There seems no way to do this dynamically in Maven 3.x > > Delany > >

Re: Maven enforcer plugin regarding child module's groupId

On Tue, Aug 31, 2021, 3:28 AM Delany wrote: > Good question. There seems no way to do this dynamically in Maven 3.x > Delany > > On Mon, 30 Aug 2021 at 20:45, David Hoffer wrote: > > > How to enforce that child modules append to the parent groupId per the > > Maven > > Guide to Naming

Re: Maven enforcer plugin regarding child module's groupId

Good question. There seems no way to do this dynamically in Maven 3.x Delany On Mon, 30 Aug 2021 at 20:45, David Hoffer wrote: > How to enforce that child modules append to the parent groupId per the > Maven > Guide to Naming Conventions >

Maven enforcer plugin regarding child module's groupId

How to enforce that child modules append to the parent groupId per the Maven Guide to Naming Conventions ? -Dave

[Enforcer Plugin] DependencyConvergence of a "provided" deendency?

Hi, I ran into a significant difference between maven-enforcer-plugin versions 3.0.0-M3 and 3.0.0 in the way "provided" dependencies are handled. I'm wondering if this is intended (and I would like to understand why) or a regression which should be reported. I have several projects

Re: [ANN] Apache Maven Enforcer Plugin + Extension 3.0.0 Released

See https://github.com/mojohaus/extra-enforcer-rules/issues/131#issuecomment-890329715 On Sun, 1 Aug 2021, 05:34 Alexander Kriegisch, wrote: > It looks like class EnforceBytecodeVersion is part of > org.codehaus.mojo:extra-enforcer-rules:1.3 which is a dependency in my > Enforc

Re: [ANN] Apache Maven Enforcer Plugin + Extension 3.0.0 Released

It looks like class EnforceBytecodeVersion is part of org.codehaus.mojo:extra-enforcer-rules:1.3 which is a dependency in my Enforcer plugin configuration. Is that extension no longer compatible with Enforcer? Or has it been replaced by something else, which I am unaware of? Like I said, in M3

Re: [ANN] Apache Maven Enforcer Plugin + Extension 3.0.0 Released

In a GitHub project, Dependabot suggested an update from 3.0.0-M3 to 3.0.0, but all CI builds fail with this error message: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0:enforce (enforce-bytecode-version) on project x: Unable to parse configuration of mojo

[ANN] Apache Maven Enforcer Plugin + Extension 3.0.0 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin and Extension, version 3.0.0 The Enforcer plugin is the Loving Iron Fist of Maven and provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along

Re: maven enforcer plugin questions

I go to > https://maven.apache.org/enforcer/maven-enforcer-plugin/ and see the link > to https://maven.apache.org/enforcer/maven-enforcer-plugin/mail-lists.html > I find that link is broken, so I will ask the question here. > > I have introduced the enforcer to the project I am working on a

Re: maven enforcer plugin questions

hi, Thank you Bernd for answering my question. I didn't know about the dedicated mailing list. However, when I go to https://maven.apache.org/enforcer/maven-enforcer-plugin/ and see the link to https://maven.apache.org/enforcer/maven-enforcer-plugin/mail-lists.html I find that link is broken, so

Re: maven enforcer plugin questions

Hello, Yes. this list can be used to reach users of maven, including maven plugins like the enforcer plugin (a official plugin has the name maven-something-plugin and is hosted on the Maven web site like https://maven.apache.org/enforcer/maven-enforcer-plugin/). But even if it where a third

maven enforcer plugin questions

Hello everyone, excuse me, is this the right place to discuss questions about the maven enforcer plugin please? -- Regards, Andrew Marlow http://www.andrewpetermarlow.co.uk

Re: Maven enforcer plugin failing with maven 3.6.1 but passing with maven 3.6.3

This has been answered in stackoverflow <https://stackoverflow.com/questions/63644201/why-is-maven-enforcer-plugin-failing-with-maven-version-3-6-1-but-passing-with-3> https://stackoverflow.com/questions/63644201/why-is-maven-enforcer-plugin-failing-with-maven-version-3-6-1-but-passing-

Re: Maven enforcer plugin failing with maven 3.6.1 but passing with maven 3.6.3

Debraj Manna wrote: >> > Hi >> > >> > In one of my project I am trying to use DependencyConvergence rule with >> > maven enforcer plugin. I am observing that if I use maven 3.6.1 then the >> > enforcer is failing with the below error but the same has been working

Re: Maven enforcer plugin failing with maven 3.6.1 but passing with maven 3.6.3

ned on SO the behaviour can't be reproduced with the > example project. > > Tested with Maven 3.6.0, 3.6.1, 3.6.2 and 3.6.3... > > Kind regards > Karl Heinz Marbaise > On 29.08.20 08:34, Debraj Manna wrote: > > Hi > > > > In one of my project I am trying to use DependencyCo

Re: Maven enforcer plugin failing with maven 3.6.1 but passing with maven 3.6.3

with maven enforcer plugin. I am observing that if I use maven 3.6.1 then the enforcer is failing with the below error but the same has been working fine with maven 3.6.3. Can someone let me know if this expected? If yes can someone point me to the relevant jira under which this issue is fixed in maven

Re: Maven enforcer plugin failing with maven 3.6.1 but passing with maven 3.6.3

Just to be more explicit with maven versions. I tried with maven version 3.6.1, 3.6.3 and 3.5.3. It worked fine only with 3.6.3. On Sat, Aug 29, 2020 at 12:04 PM Debraj Manna wrote: > Hi > > In one of my project I am trying to use DependencyConvergence rule with > maven enforcer

Maven enforcer plugin failing with maven 3.6.1 but passing with maven 3.6.3

Hi In one of my project I am trying to use DependencyConvergence rule with maven enforcer plugin. I am observing that if I use maven 3.6.1 then the enforcer is failing with the below error but the same has been working fine with maven 3.6.3. Can someone let me know if this expected? If yes can

Re: Problem with use of enforcer-plugin after upgrading the Apache parent POM (18->21)

ot;mvn help:effective-pom -Papache-release,release"? I don't see any differences with respect to the enforcer, but show: maven-enforcer-plugin 3.0.0-M2 enforce-maven-version

Re: Problem with use of enforcer-plugin after upgrading the Apache parent POM (18->21)

change that triggers the issue for us was between version 18 > and 19, which introduces the use of the enforcer plugin to check the > Maven version > (< > https://github.com/apache/maven-apache-parent/commit/35c824cfef4d8ae3ec7234365635e43f57b8e05a#diff-600376dffeb79835ede4a0b285078036

Problem with use of enforcer-plugin after upgrading the Apache parent POM (18->21)

he use of the enforcer plugin to check the Maven version (<https://github.com/apache/maven-apache-parent/commit/35c824cfef4d8ae3ec7234365635e43f57b8e05a#diff-600376dffeb79835ede4a0b285078036>, <https://issues.apache.org/jira/browse/MPOM-164>). In Oak, we use the enforcer plugin to check the size

AW: New release of the maven-enforcer-plugin?

-enforcer-plugin? Hi, I'm currently occupied with Maven Core Release / Install / Deploy plugin...but the next on my TODO list is Maven Enforcer plugin... I would say about 2-3 Weeks time frame...? would that help? Kind regards Karl Heinz Marbaise On 27/09/18 10:36, Böhme, Christoph wrote: >

Re: New release of the maven-enforcer-plugin?

Hi, I'm currently occupied with Maven Core Release / Install / Deploy plugin...but the next on my TODO list is Maven Enforcer plugin... I would say about 2-3 Weeks time frame...? would that help? Kind regards Karl Heinz Marbaise On 27/09/18 10:36, Böhme, Christoph wrote: Hi all

New release of the maven-enforcer-plugin?

Hi all, Are there any plans of building another milestone release of the maven-enforcer-plugin in the near future? I am asking because I'd like to use the recently added feature to specify rules on the command line in our CI-pipeline. I'd rather avoid having to create a custom in-house release

Re: Programmatic access to enforcer plugin

On Sat, Jul 21, 2018 at 9:27 AM Elliotte Rusty Harold wrote: > If anyone has sample code > that queries repos for dependencies without M2E, that would also be > helpful. I've put together a project that runs Maven/Aether dependency resolution internals in a CDI 2.0 SE container:

Re: Programmatic access to enforcer plugin

> Karl Heinz Marbaise > > > On 19/07/18 20:13, Elliotte Rusty Harold wrote: >> >> Short of forking the project, is any sort of programmatic API for the >> Maven enforcer plugin available? E.g. I'd like to point a rule at a >> dependency coordinates and get a repo

Re: Programmatic access to enforcer plugin

/18 20:13, Elliotte Rusty Harold wrote: Short of forking the project, is any sort of programmatic API for the Maven enforcer plugin available? E.g. I'd like to point a rule at a dependency coordinates and get a report back in a somewhat more structured form than System.out.println. Has anyone done

Programmatic access to enforcer plugin

Short of forking the project, is any sort of programmatic API for the Maven enforcer plugin available? E.g. I'd like to point a rule at a dependency coordinates and get a report back in a somewhat more structured form than System.out.println. Has anyone done something like this? Are there any

[ANN] Apache Maven Enforcer Plugin 3.0.0-M2 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.0.0-M2 The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more built-in rules and user

[ANN] Apache Maven Enforcer Plugin 3.0.0-M1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 3.0.0-M1 The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user

Re: maven-enforcer-plugin rules question

Martin __ From: Martin Gainty <mgai...@hotmail.com> Sent: Tuesday, January 10, 2017 12:05 PM To: Maven Users List Subject: Re: maven-enforcer-plugin rules question i couldnt get it this cycle failur

Re: maven-enforcer-plugin rules question

From: ctrueden.w...@gmail.com <ctrueden.w...@gmail.com> on behalf of > Curtis Rueden <ctrue...@wisc.edu> > Sent: Tuesday, January 10, 2017 12:13 PM > To: Maven Users List > Subject: Re: maven-enforcer-plugin rules question > > Hi Martin, > > I do not see how your exa

Re: maven-enforcer-plugin rules question

all: I need to catch a class cycle for example: package fubar; class classA { classB classb; //i need to detect this cycle } package fubar; class classB extends classA { classA classa; //ok since child class can reach to base class } does maven-enforcer-plugin have a rule which

Re: maven-enforcer-plugin rules question

ic de.andrena.tools.nopackagecycles.ClassB classB=null; //detect > this cycle! > } > > > what am i doing wrong? > > > Thanks Curtis > > Martin > __ > > > > From: ctrueden.w...@gmail.c

Re: maven-enforcer-plugin rules question

___ From: ctrueden.w...@gmail.com <ctrueden.w...@gmail.com> on behalf of Curtis Rueden <ctrue...@wisc.edu> Sent: Tuesday, January 10, 2017 11:02 AM To: Maven Users List Subject: Re: maven-enforcer-plugin rules question Hi Martin, A quick Google search revealed this: https

Re: maven-enforcer-plugin rules question

//detect this package cycle! > > } > class ClassB extends ClassA > > { > > } > > > which maven-enforcer-plugin rule will allow me to detect package cycle? > > > http://maven.apache.org/enforcer/enforcer-rules/index.html > > Apache Maven Enforcer R

maven-enforcer-plugin rules question

I need to detect package cycles such as what is seen here: class ClassA { ClassB classB; //detect this package cycle! } class ClassB extends ClassA { } which maven-enforcer-plugin rule will allow me to detect package cycle? http://maven.apache.org/enforcer/enforcer-rules/index.html

Re: Question about Java version range using in Maven Enforcer Plugin

the RequiredJavaVersion rule in Maven Enforcer Plugin with the requirement that using Java in versions 1.6, 1.7 and 1.8 is possible (independent of update version). So I set the value [1.6,1.8] in the property version in the RequiredJavaVersion rule. If I configure Java 8 in my JAVA_HOME, the build failed

Question about Java version range using in Maven Enforcer Plugin

Hi, I want to set the RequiredJavaVersion rule in Maven Enforcer Plugin with the requirement that using Java in versions 1.6, 1.7 and 1.8 is possible (independent of update version). So I set the value [1.6,1.8] in the property version in the RequiredJavaVersion rule. If I configure Java 8 in my

Re: Question about Java version range using in Maven Enforcer Plugin

/enforcer-rules/versionRanges.html On Tue, Jan 27, 2015 at 3:18 PM, Sandra Kosmalla skosma...@web.de wrote: Hi, I want to set the RequiredJavaVersion rule in Maven Enforcer Plugin with the requirement that using Java in versions 1.6, 1.7 and 1.8 is possible (independent of update version). So

How to detect dependency convergence violations between *independent* projects using maven enforcer plugin

but in in production, both plugins are deployed and there is a collision. Although both teams share CI, the enforcer plugin does not detect this collision since collisions are detected only if they share a common ancestor. (for example, if A also had: A - D - C (v 1.4), this would have been

Feature for Maven Enforcer Plugin Rule

Hi, I work for an Indian IT company(1,50,000+ employees) and we use Maven for many of our projects. Recently we used Maven Enforcer Plugin and Dependency Convergence Rule ( http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html). We needed the convergence to be checked

Re: Feature for Maven Enforcer Plugin Rule

Hi Basil, I work for an Indian IT company(1,50,000+ employees) and we use Maven for many of our projects. Recently we used Maven Enforcer Plugin and Dependency Convergence Rule ( http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html). We needed the convergence

Re: Enforcer plugin

Hi, it would be really nice having a test case which reproduces the wrong behaviour ... Kind regards Karl-Heinz Marbaise On 4/3/14 2:25 AM, Mark Eggers wrote: Folks, I've gotten my classifier artifact to build and install in our local repository. Specifying the classifier gets the

Re: Enforcer plugin

, or just hoping that a DEBUG classifier doesn't make it into a release)? Thanks, Mark /mde/ Works with 2.0-SNAPSHOT of the maven enforcer plugin. /mde/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org

Re: Enforcer plugin

and then the potential fix. Cheers I'll try to generate a sample project. Hopefully I can simulate this with a multi-module project. However, the following snippets of my pom.xml may be enough . . . Standard rule: This does not work as expected in 1.3.1 of maven-enforcer-plugin: plugin

Enforcer plugin

Folks, I've gotten my classifier artifact to build and install in our local repository. Specifying the classifier gets the appropriate artifact, and removing the classifier gets the [other] appropriate artifact. Now I'm a bit paranoid that the artifact with the classifier will leak out into

Re: Enforcer plugin

/ Works with 2.0-SNAPSHOT of the maven enforcer plugin. /mde/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org

Aw: Re: maven-enforcer-plugin problems with test dependency in multi module project

, should it? Best regards Matthias Gesendet: Donnerstag, 30. Januar 2014 um 17:13 Uhr Von: Karl Heinz Marbaise khmarba...@gmx.de An: users@maven.apache.org Betreff: Re: maven-enforcer-plugin problems with test dependency in multi module project Hi, based on the error message you have

maven-enforcer-plugin problems with test dependency in multi module project

    executions       execution     goals       goaltest-jar/goal     /goals     phasetest-compile/phase       /execution     /executions   /plugin /plugins In a parent pom the maven-enforcer-plugin is included and the RequireReleaseDeps rule is added to the list of rules. While

Re: maven-enforcer-plugin problems with test dependency in multi module project

/execution /executions /plugin /plugins In a parent pom the maven-enforcer-plugin is included and the RequireReleaseDeps rule is added to the list of rules. While running the Maven goal “compile” the project compilation of the test-child fails with the following message: [ERROR] Failed

Some help needed with maven-enforcer-plugin

artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions execution idenforce-banned-dependencies/id goals goalenforce/goal

Re: Some help needed with maven-enforcer-plugin

groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions execution idenforce-banned-dependencies/id goals

Re: Some help needed with maven-enforcer-plugin

requireSameVersions rule. Introducing the bannedDependencies rule was successful, but somehow I seem to not get the right configuration for requireSameVersion. Here is my config: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin

Re: Some help needed with maven-enforcer-plugin

was successful, but somehow I seem to not get the right configuration for requireSameVersion. Here is my config: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.3.1/version executions

[ANN] Apache Maven Enforcer Plugin 1.3.1 Released

The Apache Maven team is pleased to announce the release of the Apache Maven Enforcer Plugin, version 1.3.1 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules

Maven 3.0.5 - Strange Interaction/Regression: maven-enforcer-plugin vs. maven-assembly-plugin

Hi list. I just got hit by a weird interaction between two plugins, namely the maven-enforcer-plugin and the maven-assembly-plugin: I recently updated the versions for the plugins used in my build and suddenly the creation of an assembly broke with an NPE: [ERROR] Failed to execute goal

Re: Maven 3.0.5 - Strange Interaction/Regression: maven-enforcer-plugin vs. maven-assembly-plugin

/execution /executions /plugin plugin groupIdorg.apache.maven.**plugins/groupId artifactIdmaven-enforcer-**plugin/artifactId version${plugins.maven-**enforcer-plugin.version}/**version executions execution

Re: Maven 3.0.5 - Strange Interaction/Regression: maven-enforcer-plugin vs. maven-assembly-plugin

by a weird interaction between two plugins, namely the maven-enforcer-plugin and the maven-assembly-plugin: I recently updated the versions for the plugins used in my build and suddenly the creation of an assembly broke with an NPE: [ERROR] Failed to execute goal org.apache.maven.plugins:** maven

[ANN] Apache Maven Enforcer Plugin 1.3 Released

The Apache Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.3 The Enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules

maven-enforcer-plugin to ban a transitive provided dependency

depends on A:1.0 and this dependency is provided. I tried to use the maven-enforcer-plugin to break the build of A in case there is a transitive dependency whose groupId and artifactId are the same as A, but it doesn't work because the dependency A:1.0 is provided. Any suggestions? -- View

Re: maven-enforcer-plugin to ban a transitive provided dependency

on A:1.0 and this dependency is provided. I tried to use the maven-enforcer-plugin to break the build of A in case there is a transitive dependency whose groupId and artifactId are the same as A, but it doesn't work because the dependency A:1.0 is provided. Any suggestions? -- View

Re: maven-enforcer-plugin to ban a transitive provided dependency

Thank you Stephen! Does anybody knows if there is already a plugin able to this? David PS: Guys don't publish unrelated posts on this thread. -- View this message in context: http://maven.40175.n5.nabble.com/maven-enforcer-plugin-to-ban-a-transitive-provided-dependency-tp5752733p5752745

[ANN] Maven Enforcer Plugin 1.2 Released

The Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.2 The enforcer plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules. http

Re: Maven Enforcer plugin: can I make it be quiet?

On Thu, Jul 19, 2012 at 4:27 PM, Barrie Treloar baerr...@gmail.com wrote: Laird, can you try the snapshot and see if that fixes the problem? That does the trick; I'd be grateful if you would release it. Best, Laird -- http://about.me/lairdnelson

Maven Enforcer plugin: can I make it be quiet?

The Maven Enforcer plugin version 1.1.1 outputs a ton of information at the INFO level that seems to me to be repetitive and uninteresting. Here is an excerpt from a normal run: [INFO] javax.annotation:jsr250-api 1.0 1.0 [INFO] javax.inject:javax.inject 1 1 [INFO] javax.inject:javax.inject 1 1

Re: Maven Enforcer plugin: can I make it be quiet?

Which rule spits that out? This seems unusual. On Thu, Jul 19, 2012 at 6:11 PM, Laird Nelson ljnel...@gmail.com wrote: The Maven Enforcer plugin version 1.1.1 outputs a ton of information at the INFO level that seems to me to be repetitive and uninteresting. Here is an excerpt from a normal

Re: Maven Enforcer plugin: can I make it be quiet?

On Fri, Jul 20, 2012 at 8:53 AM, Brian Fox bri...@infinity.nu wrote: Which rule spits that out? This seems unusual. Its probably DependencyVersionMap.getVersion which was a bug since 1.0 See http://jira.codehaus.org/browse/MENFORCER-135 I've fixed it, but I haven't cut a new release. Laird,

Re: Maven Enforcer plugin: can I make it be quiet?

On Thu, Jul 19, 2012 at 4:27 PM, Barrie Treloar baerr...@gmail.com wrote: Laird, can you try the snapshot and see if that fixes the problem? Sure; which snapshot, now? 1.2-SNAPSHOT could not be found via oss.sonatype.org or repo1. Not sure what other repo to try? Best, Laird --

Re: Maven Enforcer plugin: can I make it be quiet?

https://repository.apache.org/index.html#nexus-search;gav~org.apache.maven.plugins~maven-enforcer-plugin~~~ it is RAO not OSO ;) On Fri, Jul 20, 2012 at 1:42 AM, Laird Nelson ljnel...@gmail.com wrote: On Thu, Jul 19, 2012 at 4:27 PM, Barrie Treloar baerr...@gmail.com wrote: Laird, can you

[ANN] Maven Enforcer Plugin 1.1.1 Released

The Maven team is pleased to announce the release of the Maven Enforcer Plugin, version 1.1.1 This plugin provides goals to control certain environmental constraints such as Maven version, JDK version and OS family along with many more standard rules and user created rules. http

maven-enforcer-plugin: requireProperty example with wrong regex for project.version?

Hello, I followed the instructions from http://maven.apache.org/enforcer/enforcer-rules/requireProperty.html and put the example configuration into my pom: requireProperty propertyproject.version/property

Possible to limit enforcer plugin to a lifecycle phase?

Hi, I'm using Maven 3.0.3. If my Maven run includes the verify phase, I want to check to see if certain properties were included at the command line. I've found the Maven enforcer plugin to be useful for this purpose (guaranteeing things are included and conform to a certain value), but I can't

Usage of Enforcer Plugin 1.1-SNAPSHOT

Hi, we have problems with maven using a wrong version of enforcer plugin. In the project's pom the enforcer plugin is specified like this: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId executions execution idenforce

Re: Usage of Enforcer Plugin 1.1-SNAPSHOT

I wonder why maven uses a SNAPSHOT version of the plugin? Which maven version you use? A build log will helps to understand your problem. -Guo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional

Re: Usage of Enforcer Plugin 1.1-SNAPSHOT

On Thu, Nov 10, 2011 at 8:42 PM, Guo Du mrdu...@duguo.org wrote: I wonder why maven uses a SNAPSHOT version of the plugin? Which maven version you use? A build log will helps to understand your problem. And best practice is to lock down the version numbers, which ironically enforcer will tell

Re: Usage of Enforcer Plugin 1.1-SNAPSHOT

Thanks. We fixed the problem by locking down the version number of enforcer plugin. We're using maven 2.2.1. But still I wonder about the behaviour when no version number has been specified... How are the version numbers determined by maven? How can it happen that maven uses a snapshot version

Re: enforcer plugin rules to prevent circular dependencies

On Mon, Mar 28, 2011 at 10:52 AM, Caoilte O'Connor caoi...@gmail.com wrote: Thanks for the detailed reply Philip, On Sat, Mar 26, 2011 at 3:43 AM, Phillip Hellewell ssh...@gmail.com wrote: In other words, if any of my dependencies are myself, then it throws an exception. Were you able to

Re: enforcer plugin rules to prevent circular dependencies

discovered the enforcer plugin and would like to use it to reduce our dependency conflicts but a bigger problem for us when it does turn up are circular dependencies. The Dependency Tree plugin spots these, but does anyone have any rules for the enforcer plugin to fail the build

enforcer plugin rules to prevent circular dependencies

Hi, I've just discovered the enforcer plugin and would like to use it to reduce our dependency conflicts but a bigger problem for us when it does turn up are circular dependencies. The Dependency Tree plugin spots these, but does anyone have any rules for the enforcer plugin to fail the build

maven-enforcer-plugin and Maven 3

Hello, the rule 'Require Plugin Versions' is discarded when run in Maven 3, not in Maven 2. Is there any reason and how to achieve the same behaviour using Maven 3 ? Thanks Jeff MAURY -- Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne

Re: enforcer plugin rules to prevent circular dependencies

On Fri, Mar 25, 2011 at 5:55 AM, Caoilte O'Connor caoi...@gmail.com wrote: Hi, I've just discovered the enforcer plugin and would like to use it to reduce our dependency conflicts but a bigger problem for us when it does turn up are circular dependencies. The Dependency Tree plugin spots

Re: maven-enforcer-plugin and Maven 3

There's already a bug report about this (You could vote for it): http://jira.codehaus.org/browse/MENFORCER-98 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:

Re: enforcer plugin rules to prevent circular dependencies

On Fri, Mar 25, 2011 at 8:45 AM, Wendy Smoak wsm...@gmail.com wrote: On Fri, Mar 25, 2011 at 5:55 AM, Caoilte O'Connor caoi...@gmail.com wrote: Hi, I've just discovered the enforcer plugin and would like to use it to reduce our dependency conflicts but a bigger problem for us when it does turn

[maven enforcer plugin] maven enforcer plugin - plugin using = version #

Using maven enforcer plugin, how can I ensure that all projects are using a a plugin version = than the one I defined? For example, I want to ensure all the projects in the company (we use a company super pom) use maven release plugin = 2.1 version In the company super pom we are using

Version 1.0 of maven-enforcer-plugin not deployed

Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the repo1.maven.org is empty. [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.0/maven-enforcer-plugin-1.0

Re: Version 1.0 of maven-enforcer-plugin not deployed

I can reach the artifact just fine. Vincent 2010/11/9 Johan Hedin johan.he...@mawell.com Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the repo1.maven.org is empty. [INFO] Downloading: http

Re: Version 1.0 of maven-enforcer-plugin not deployed

What goal did you specify? The plugin exists at Maven central. /Anders On Tue, Nov 9, 2010 at 00:09, Johan Hedin johan.he...@mawell.com wrote: Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the repo1.maven.org is empty. [INFO

Re: Version 1.0 of maven-enforcer-plugin not deployed

It can take a few hours to fully sync if it's more than 24 hours after the announcement, then it's time to start screaming! On 8 November 2010 23:09, Johan Hedin johan.he...@mawell.com wrote: Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the repo1.maven.org is empty

  1   2   >