[ANN] Apache Maven Compiler Plugin Version 3.8.1
The Apache Maven team is pleased to announce the release of the Apache Maven Compiler Plugin Version 3.8.1 https://maven.apache.org/plugins/maven-compiler-plugin/ You should specify the version in your project's plugin configuration: Important Notes since Version 3.8.0 * The default value for source/target has been lifted from 1.5 to 1.6 see MCOMPILER-335. org.apache.maven.plugins maven-compiler-plugin 3.8.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-compiler-plugin/download.cgi Release Notes Maven Compiler Plugin 3.8.1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12343484 Bugs: * [MCOMPILER-306] - Incorrect `compilerArgs` example usage * [MCOMPILER-349] - maven-compiler-plugin does not recompile a module if a dependency module has been updated & recompiled * [MCOMPILER-360] - NPE when calculating modulepath with invalid entries * [MCOMPILER-379] - Fatal error compiling: basedir ... arget/generated-sources/annotations does not exist Improvements: * [MCOMPILER-322] - Set the JPMS module version * [MCOMPILER-366] - Warning about automodules should provide the list of offending libraries Enjoy, - The Apache Maven team Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Profile] - Merge from parent
Hi Hervé, Thanks for your help! I'm confuse because when I performed the release yesterday it doesn't work and now when I try, it works... May be something with my home cache maven repository. Sorry for the noise ;) Regards, François Papon fpa...@apache.org Le 02/05/2019 à 09:36, Hervé BOUTEMY a écrit : > Hi François, > > I just checked, and the profile merging is perfectly happening. > If you run: > $ mvn -Papache-release > org.apache.maven.plugins:maven-help-plugin:3.2.0:effective-pom -Dverbose -N > > you'll see the checksum-maven-plugin injected in plugins section > > Perhaps what is confusing you is that you don't see the parent injection as > part of the profile itself: it's the way inheritance works in Maven, profiles > are injected into the pom before inheritance, then you never really see the > inherited profile itself. > > Regards, > > Hervé > > Le jeudi 2 mai 2019, 05:50:37 CEST Francois Papon a écrit : >> Hi, >> >> In Apache Shiro we are using the Apache pom parent in version 21 and in >> this version there is the algorithm configuration for the checksum >> generation of the release artifact. >> >> The id of the profile is "apache-release" and we already have a profile >> with the same id in our root pom. >> >> We can see that when using this profile, the Apache parent profile is >> not use or aggregate with the root one. >> >> Is there any option like inheritence for plugin configuration? >> >> regards, > > > > > - > 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
How to change Maven dependency version range behavior
Hi there, I have come to the conclusion that what I need in my life is for Maven to resolve dependency ranges like: [1.2.0,2.0.0) to effectively mean [1.2.0]. Specifically when deciding which version of a direct dependency to use. How would I go about changing Maven's behavior for my project? Would I be able to do this by writing a special type of plugin (extension maybe)? Basically, at some point Maven gets a list of versions inside the version range, and has to pick one. Where exactly is that happening and can I override that choice? Thanks K - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
