Reproducing MRESOURCES-132

2018-06-16 Thread Behrang 
I noticed this bug has been closed and marked as cannot reproduce:
https://issues.apache.org/jira/browse/MRESOURCES-132

Which is a bit odd, as it is very easy to produce.

Here is a sample project to reproduce it using Docker:
https://github.com/behrangsa/bugreport-mresources-132

After cloning it, if you run `docker build .`

It can be seen that the original permissions on script.sh are 775:

Step 8/9 : RUN *ls -alh src/main/resources/script.sh*
 ---> Running in c07cdcbe268a
*-rwxrwxr-x* 1 root root 24 Jun 16 14:17 src/main/resources/script.sh

But after the script.sh is copied to target/classes, the "x" and "w" bits
are dropped from the file's group and other attributes:

Step 9/9 : RUN *ls -alh target/classes/script.sh*
 ---> Running in 3708b2d6116a
*-rw-r--r--* 1 root root 24 Jun 16 14:27 target/classes/script.sh

This should help with reproducing (and reopening) the bug.

[ANN] Apache Maven Enforcer Plugin 3.0.0-M2 Released

2018-06-16 Thread Robert Scholte 
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 created rules.


https://maven.apache.org/enforcer/maven-enforcer-plugin/

You should specify the version in your project's plugin configuration:


  org.apache.maven.plugins
  maven-enforcer-plugin
  3.0.0-M2


You can download the appropriate sources etc. from the download page:

https://maven.apache.org/enforcer/download.cgi


Release Notes - Maven Enforcer Plugin - Version 3.0.0-M2 (including  
3.0.0-M1)


** Bug
* [MENFORCER-234] - Link to plugin's web site is reported as  
redirected by maven linkcheck plugin.
* [MENFORCER-239] - Fix link in navigation  
(enforcer/maven-enforcer-plugin/index.html) RESOURCES

* [MENFORCER-240] - Link to page does not work
* [MENFORCER-265] - Get site generation working
* [MENFORCER-268] - Usage of CI friendly version placeholders does not  
work
* [MENFORCER-274] - Use of RequireJavaVersion with Java-9 breaking  
starting at b175
* [MENFORCER-281] - RequirePluginVersions broken with "CI Friendly  
versions"


** New Feature
* [MENFORCER-204] - Add new rule: should be able to make sure that  
project artifact is a Snapshot

* [MENFORCER-247] - Add a "require file checksum" rule
* [MENFORCER-273] - RequireUpperBoundDeps.excludes
* [MENFORCER-282] - Add RequireProfileIdsExist to ensure al mentioned  
cmdline profiles exist


** Improvement
* [MENFORCER-228] - DependencyConvergence: Simplify logging errors
* [MENFORCER-253] - Upgrade maven-shared-components parent to version  
30
* [MENFORCER-259] - The rule BanDuplicatePomDependencyVersions is not  
documented

* [MENFORCER-263] - Upgrade mrm-maven-plugin to 1.0.0
* [MENFORCER-266] - Remove usage of prerequisites in parent pom
* [MENFORCER-291] - Cleanup ReactorModuleConvergence implementation
* [MENFORCER-292] - Remove getModelsRecursively from EnforcerRuleUtils
* [MENFORCER-293] - Remove deprecated marked ignoreParent from  
BanDistributionManagement


** Task
* [MENFORCER-221] - Removed deprecated marked constructor from  
EnforcerExpressionEvaluator

* [MENFORCER-272] - Allow site generation to work
* [MENFORCER-284] - switch to Git
* [MENFORCER-296] - Update URL for CI System

** Dependency upgrade
* [MENFORCER-278] - Upgrade mockito to 2.X to prevent JDK 9 WARNINGs
* [MENFORCER-289] - Upgrade maven-plugin-plugin to 3.5
* [MENFORCER-290] - Upgrade plexus-utils 3.1.0
* [MENFORCER-297] - Upgrade parent to 31
* [MENFORCER-303] - Upgrade mave-surefire/failsafe-plugin 2.21.0


Enjoy,

-The Apache Maven team

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

Re: When does a Maven plugin uses the POM in the current directory?

2018-06-16 Thread Oliver B. Fischer 

Thank you all for your support. Now it works as I need it.

Am 12.06.18 um 17:20 schrieb Oliver B. Fischer:

Dear all,

I use the Versions Maven Plugin to check for updates of my dependencies. 
Therefore I added the following lines to my pom.xml:



     org.codehaus.mojo
     versions-maven-plugin
     ${versions-plugin.version}
     
     classpath:///rules.xml
     
     
     
     versionrules
     versionrules
     1-SNAPSHOT
     
     


But this configuration is not used if I run the Versions Maven Plugin in 
the same directory as the pom.xml. The only way to my own configuration 
is to put this plugin configuration in a profil and execute this profil 
during the Maven run.


Is there a way to run the Versions plugin on the commandline and to 
configure it via the pom.xml?


Bye,

Oliver

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



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