Re: Maven 3.5.0 and the versions plugin

2017-04-13 Thread Karl Heinz Marbaise

Hi Mark,

for the versions-maven-plugin there is already an issue for that:

https://github.com/mojohaus/versions-maven-plugin/issues/56

Currently I'm working on a large number of the issues in the 
versions-maven-plugin ...


https://github.com/mojohaus/versions-maven-plugin/milestone/2?closed=1


It will take some time...

Kind regards
Karl Heinz Marbaise

On 13/04/17 23:00, Mark Eggers wrote:

Folks,

I'm working on upgrading an environment to maven 3.5.0. With
prerequisites in pom.xml, I get the expected message:

   [WARNING] The project org.mdeggers:CSEquity:war:1.0-SNAPSHOT
   uses prerequisites which is only intended for maven-plugin projects
   but not for non maven-plugin projects. For such purposes you should
   use the maven-enforcer-plugin. See
   https://maven.apache.org/enforcer/enforcer-
   rules/requireMavenVersion.html

I then remove the prerequisites tag and replace it with the
appropriately configured enforcer plugin. The project builds cleanly.

However, one of the things that we do in Jenkins is run a series of mvn
versions:display--updates (plugins, dependencies) and mail the
results to developers.

When I run mvn versions:display-plugin-updates, I get the expected
output as well as the following:

   [WARNING] Project does not define minimum Maven version, default is:
   2.0

   [ERROR] Project does not define required minimum version of Maven.
   [ERROR] Update the pom.xml to contain
   [ERROR] 
   [ERROR]   3.0
   [ERROR] 

Is there a way to resolve this? Should I file an issue with the maven
versions plugin?

. . . just my two cents
/mde/




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven 3.5.0 and the versions plugin

2017-04-13 Thread Manfred Moser
Yeah. Provided you have tested this with the latest version of the versions 
plugin and it still shows that problem... 

Mark Eggers wrote on 2017-04-13 14:00:

> Folks,
> 
> I'm working on upgrading an environment to maven 3.5.0. With
> prerequisites in pom.xml, I get the expected message:
> 
>   [WARNING] The project org.mdeggers:CSEquity:war:1.0-SNAPSHOT
>   uses prerequisites which is only intended for maven-plugin projects
>   but not for non maven-plugin projects. For such purposes you should
>   use the maven-enforcer-plugin. See
>   https://maven.apache.org/enforcer/enforcer-
>   rules/requireMavenVersion.html
> 
> I then remove the prerequisites tag and replace it with the
> appropriately configured enforcer plugin. The project builds cleanly.
> 
> However, one of the things that we do in Jenkins is run a series of mvn
> versions:display--updates (plugins, dependencies) and mail the
> results to developers.
> 
> When I run mvn versions:display-plugin-updates, I get the expected
> output as well as the following:
> 
>   [WARNING] Project does not define minimum Maven version, default is:
>   2.0
> 
>   [ERROR] Project does not define required minimum version of Maven.
>   [ERROR] Update the pom.xml to contain
>   [ERROR] 
>   [ERROR]   3.0
>   [ERROR] 
> 
> Is there a way to resolve this? Should I file an issue with the maven
> versions plugin?
> 
> . . . just my two cents
> /mde/
> 
> 


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Maven 3.5.0 and the versions plugin

2017-04-13 Thread Mark Eggers
Folks,

I'm working on upgrading an environment to maven 3.5.0. With
prerequisites in pom.xml, I get the expected message:

   [WARNING] The project org.mdeggers:CSEquity:war:1.0-SNAPSHOT
   uses prerequisites which is only intended for maven-plugin projects
   but not for non maven-plugin projects. For such purposes you should
   use the maven-enforcer-plugin. See
   https://maven.apache.org/enforcer/enforcer-
   rules/requireMavenVersion.html

I then remove the prerequisites tag and replace it with the
appropriately configured enforcer plugin. The project builds cleanly.

However, one of the things that we do in Jenkins is run a series of mvn
versions:display--updates (plugins, dependencies) and mail the
results to developers.

When I run mvn versions:display-plugin-updates, I get the expected
output as well as the following:

   [WARNING] Project does not define minimum Maven version, default is:
   2.0

   [ERROR] Project does not define required minimum version of Maven.
   [ERROR] Update the pom.xml to contain
   [ERROR] 
   [ERROR]   3.0
   [ERROR] 

Is there a way to resolve this? Should I file an issue with the maven
versions plugin?

. . . just my two cents
/mde/



signature.asc
Description: OpenPGP digital signature