Re: what means "The following artifacts could not be resolved: org.dom4j:dom4j:jar:2.1.3 (present, but unavailable)"
Hi, please check what You have in .m2/repository/org/dom4j/dom4j/2.1.3 in file _remote.repositories There will be references to the repo from where this artifact has been downloaded. BR Sylwester pon., 6 lis 2023 o 16:57 Tamás Cservenák napisał(a): > Howdy, > > Well, let me step back for a moment: > Maven2 did ignore "origin" and it caused various problems that were very > hard to diagnose. > Hence, Maven3 (from start, or almost, but very early) did implement the > "enhanced" local repository, that does track origin. > > In short, these kinds of errors means that your build depends on something > not described in build (so side effect). > > Best way to diagnose these: nuke local repository (as it should be > considered transient anyway), and a "good build" will just get whatever it > needs. > Otherwise, the build will fail as well, but with a different error: > "artifact X not found". > > With use of repository groups (virtual repo) this became more and more > apparent: Imagine this, you have two groups: > > group-a (consisting of central, remote-repo-a) > group-b (consisting of central, remote-repo-b) > > Here, if you start a build w/ settings "by the book" (having mirrorOf > group-a) and empty local repo, it will populate your local repo and all > cached artifacts will have the origin = "group-a". > Then, if you start another build w/ settings "by the book" using group-b, > Maven will go and recheck all, as "group-a" origin is != as "group-b" > origin (so yes, all the central artifacts as well, everything). > > Hence, in these scenarios is best to differentiate local repositories as > well (just like you differentiate groups). > > Also, if no origin check, an artifact coming from remote-repo-a, that is > totally out of sight in build consuming group-b could be picked up, causing > strange, and very hard to diagnose problems (it fails here but passes > there? It is a build that depends on the environment, and how is the used > local repo populated). > > So, ideally in these cases just use _other_ local repository, ideally 1:1, > each build consuming given group should have "own" local repository as > well. > > I cannot emphasize enough, how in these cases usually "nuking local repo" > just makes the issues pop out, and render builds fail, and it is a clear > indicator that the build has issues that need to be fixed. > > Again, you can "trick" Maven to use these "unavailable" artifacts, but it > is in your own interest to fix the actual build issues you have. > > On Mon, Nov 6, 2023 at 4:31 PM Francois Marot > wrote: > > > Hello Arno and Tamas > > > > and thank you for the detailed and very interesting explanation. > > One question arises though: is there any way to make Maven ignore the > > origin ? > > > > Have a good day > > François > > > > > > Le lun. 6 nov. 2023 à 13:20, Tamás Cservenák a > > écrit : > > > > > Howdy, > > > > > > The Maven local repository contains two kinds of artifacts lumped > > together: > > > - cached ones from remote > > > - locally built and installed > > > > > > This message matters the cached ones: "present but unavailable" means > > > following: > > > - file IS present (so it was cached) > > > - but is unavailable, as it was cached as part of some OTHER remote > > > repository than that exists in current execution > > > > > > Maven3 uses this implementation of local repository > > > > > > > > > https://maven.apache.org/resolver/apidocs/org/eclipse/aether/internal/impl/EnhancedLocalRepositoryManagerFactory.html > > > > > > And check out the javadoc it: it tracks the "origin" (basically remote > > > repository ID) of cached artifacts, and "emulates" physically separated > > > caches (same can be achieved "for real" with split local repository). > > > > > > In short: the repository ID that was stored as artifact origin is NOT > > > available in your subsequent build, hence, Maven3 does not use it (is > > > unavailable, but present physically in cache/local repository). > > > > > > HTH > > > T > > > > > > On Mon, Nov 6, 2023 at 1:10 PM Arno Schatz wrote: > > > > > > > Hi, > > > > > > > > I am trying to use the offline mode (mvn -o clean install) and > getting > > > the > > > > error message > > > > "The following artifacts could not be resolved: > > org.dom4j:dom4j:jar:2.1.3 > > > > (present, but unavailable)" > > > > for very many dependencies. > > > > > > > > My main computer and a VM share the same file system. The VM is > > connected > > > > to the company's repository (artefactory) > > > > through VPN. On the VM, I checkout the project and successfully build > > it > > > > and successfully ran "mvn dependency:go-offline". > > > > > > > > The I switched to my main computer and tried "mvn -o clean install" > but > > > it > > > > failed with the above error message. I also > > > > tried to set > > > > true > > > > in settings.xml in my main computer but that didnt change anything. > > > > What does the "(present, but unavailable)" in the error message mean? > > > >
Re: Maven Compiler plugins does not support 21 yet?
Switch to AWS Corretto, they offer Java 21 already Sylwester wt., 12 wrz 2023, 10:26 użytkownik hantsy bai napisał: > Oh, I think it is my fault, it seems Github actions does not support 21, I > was using *zulu* distribution. > > --- > > Regards, > > *Hantsy Bai* > > Self-employed consultant, fullstack developer, agile coach, > freelancer/remote worker > > GitHub: https://github.com/hantsy > > Twitter: https://twitter.com/@hantsy > Medium: https://medium.com/@hantsy > > > On Tue, Sep 12, 2023 at 3:25 PM Olivier Lamy wrote: > > > Hi > > Please run your build using option -e and have a look at the stack. > > I use 21, and it works fine. > > This might be some restrictions with spring boot parent. > > Or, according to the error message "error: release version 21 not > > supported" you might not using a jdk 21. > > > > On Tue, 12 Sept 2023 at 17:16, hantsy bai wrote: > > > > > > I tried to update the compiler release to 21, and got a compiler error > > like > > > this. > > > > > > Error: Failed to execute goal > > > org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile > > > (default-compile) on project spring6-sample-boot: Fatal error > compiling: > > > error: release version 21 not supported -> [Help 1] > > > --- > > > > > > Regards, > > > > > > *Hantsy Bai* > > > > > > Self-employed consultant, fullstack developer, agile coach, > > > freelancer/remote worker > > > > > > GitHub: https://github.com/hantsy > > > > > > Twitter: https://twitter.com/@hantsy > > > Medium: https://medium.com/@hantsy > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > >
Re: MavenCLI failing in Jenkins
Could You share output of running inside docker with verbose mode (-X)? Sylwester śr., 19 kwi 2023, 23:43 użytkownik Javier Ortiz Bultron < javier.ortiz...@gmail.com> napisał: > Code works perfectly on my Mac but not on Jenkins. I'm running this on the > Maven official image: maven:3.9.1-eclipse-temurin-11 > > I'm trying to figure out how to fix this issue: > > [2023-04-19 21:24:35.509] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:965] Plugin > org.apache.maven.plugins:maven-resources-plugin:3.3.0 or one of its > dependencies could not be resolved: Failed to read artifact descriptor > for org.apache.maven.plugins:maven-resources-plugin:jar:3.3.0: The > following artifacts could not be resolved: > org.apache.maven.plugins:maven-resources-plugin:pom:3.3.0 (present, > but unavailable): Could not transfer artifact > org.apache.maven.plugins:maven-resources-plugin:pom:3.3.0 from/to > central (https://repo.maven.apache.org/maven2): No connector factories > available -> [Help 1] > [2023-04-19 21:24:35.511] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:850] > [2023-04-19 21:24:35.512] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:853] To see the full stack trace of the errors, re-run > Maven with the -e switch. > [2023-04-19 21:24:35.512] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:858] Re-run Maven using the -X switch to enable full > debug logging. > [2023-04-19 21:24:35.513] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:863] > [2023-04-19 21:24:35.513] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:864] For more information about the errors and possible > solutions, please read the following articles: > [2023-04-19 21:24:35.514] [ERROR] [main] o.a.m.c.MavenCli > [MavenCli.java:868] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException >
Re: Maven Deploy fails
Please check one of available tutorials like https://www.digitalocean.com/community/tutorials/how-to-install-java-with-apt-on-ubuntu-22-04 Java 11 is good. You Just need an SDK and not only JRE. Sylwester sob., 12 lis 2022 o 15:36 Raivo Rebane napisał(a): > > Hi > > Sorry for late answer, but I feel yesterday and today moning yourself > sick and thought, that I got COVID. > > But now I feel better. > > I set environment variables and deploy starts to work. > > But compiling doesnot. It gives me : > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.6.0:compile > (default-compile) on project teamengine-realm: Compilation failure > [ERROR] No compiler is provided in this environment. Perhaps you are > running on a JRE rather than a JDK? > > And thats true. > > raivo@Hydra:~/teamengine$ java -version > openjdk version "11.0.16" 2022-07-19 > OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu120.04) > OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu120.04, > mixed mode, sharing) > > but > > JAVA_HOME=/usr/java/jre1.8.0_351/ > > I don't know how to set Java default version to Java8 in Ubuntu. > > What I have to do ? > > Regards > > Raivo > > On 11.11.22 12:52, Karl Heinz Marbaise wrote: > > Hi, > > On 11.11.22 08:40, e...@zusammenkunft.net wrote: > >> Hello, > >> > >> I think the /usr/bin/mvn (i.e. "not in path") and /usr/share/maven/ > >> points > >> to a non-pristine distribution shipped Maven (Debian?). > > > > The distro we are talking about is Ubuntu.. > > > > > >> > >> I would start with using an upstream Maven distribution archive to > >> make sure > >> its no packaging error. )And also use a supported JDK by fixin PATH > >> and JAVA_HOME. > >> > >> If its a packaging problem the Distribution would be the right place > >> to get support. > > > > It does not look like that... > > > > > > > >> (But we already mentioned a few ttimes as a developer you might want > >> to have multiple pristine maven installs independent of your > >> distribution anyway). > >> > >> Gruss > >> Bernd > >> > >> > > > > Kind regards > > Karl Heinz Marbaise > > > > - > > 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 > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to retrieve target folder or jar paths from multi-module Maven project
Maybe maven-deploy-plugin with custom deployment repository? https://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html Sylwester pt., 10 cze 2022, 08:05 użytkownik Delany napisał: > Building on this, you could try this bash script. It is very slow > > while read -r pom; do mvn help:evaluate > -Dexpression=project.build.directory -q -DforceStdout -f $pom && echo; done > < <(find . -iname pom.xml) > > > On Thu, 9 Jun 2022 at 21:20, Bernd Eckenfels > wrote: > > > The Maven Help Plugin has some functions, including printing evaluated > > project parameters. > > > > > > RESULT=$(mvn help:evaluate -Dexpression=project.version -q -DforceStdout) > > > > https://maven.apache.org/plugins/maven-help-plugin/evaluate-mojo.html > > > > > > -- > > http://bernd.eckenfels.net > > > > Von: Laurian Angelescu > > Gesendet: Tuesday, June 7, 2022 5:43:26 PM > > An: users@maven.apache.org > > Betreff: How to retrieve target folder or jar paths from multi-module > > Maven project > > > > Is it possible to invoke *mvn* on the command line to output either 1) > the > > paths to all target folders where jars get packaged or 2) the file paths > of > > the jars themselves? > > > > For example, in a multi-module project like > > https://github.com/apache/httpcomponents-core.git, I would like to > invoke: > > > > *mvn * > > > > and have output to standard out: > > > > //httpcore5/target/httpcore5-5.2-beta1.jar > > //httpcore5-h2/target/httpcore5-h2-5.2-beta1.jar > > ... > > etc. > > > > I want to essentially be able to get a list of the JARs created in *any > > *Maven > > multimodule project. > > >
Re: Ambari build
Also please check instructions here https://cwiki.apache.org/confluence/display/AMBARI/Installation+Guide+for+Ambari+2.7.6 pt., 7 sty 2022, 13:28 użytkownik Delany napisał: > Hi Marc > -DskipTests is case sensitive. You can also skip compilation of tests with > -Dmaven.test.skip > Eclipse is probably using a bundled JDK - version 11+ since you're getting > javax errors. > Intellij is using a bundled Maven since its complaining about https repos. > Check Intellij's Maven configuration page. > Delany > > > On Fri, 7 Jan 2022 at 14:16, Marc Hoppins wrote: > > > Hi all, > > > > This is a stock ambari 2.7.6 build attempt on Ubuntu 18.04. I am not a > > java entity but I am interested in understanding how these tools operate > > with a view to getting away from Cloudera. We currently run with CDH 6.3, > > the free/express version and this leaves us stuck with Centos7, or > > Ubuntu18, both of which are EOL, or fast approaching. Given the > exorbitant > > pricing per node for ANY version of Cloudera, it is prohibitive to > justify > > the cost when making money off data is not a thing we could possibly > > contemplate. > > > > Aside from the obvious fact that every build produces errors which seem > to > > have been ignored by whoever created this, I am mystified as to why the > > errors are different depending on how I run a build. > > > > I have OpenJDK 8 installed, as well as the general pre-requisites > > according to the Ambari documentation. > > > > Maven 3.6.0 > > Eclipse 2021-12 (4.22.0) > > IntelliJ IDEA 2021.3.1 (Community) > > > > Below are the output errors from OS CLI, Eclipse and IntelliJ. All three > > produce DIFFERENT errors and this is confusing as I thought they all used > > Maven. I run an INSTALL build with rat.skip as RAT seems to produce > > thousands of licence errors for every item in the project. If RAT is so > > important, why have these errors not been sorted? > > > > Also, if I have -Dskiptests, why do tests still get run? > > > > I am sure that there are folk who have successfully built Ambari but > > useful and successful attempts have not been published for any recent > > version. > > > > Any information would be helpful. > > > > Thanks. > > > > Marc > > > > ** When run from CLI ** > > > > mvn install -Drat.skip=true -Dskiptests=true -X > > [INFO] Running > > org.apache.ambari.server.metric.system.impl.MetricsServiceTest > > [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > > 0.359 s - in > org.apache.ambari.server.metric.system.impl.MetricsServiceTest > > [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > > 30.001 s - in > > org.apache.ambari.server.checks.AmbariMetricsHadoopSinkVersionCheckTest > > [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > > 6.232 s - in org.apache.ambari.server.upgrade.SchemaUpgradeHelperTest > > [WARNING] Tests run: 6, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: > > 5.677 s - in > org.apache.ambari.server.metric.system.impl.MetricsSourceTest > > [INFO] > > [INFO] Results: > > [INFO] > > [ERROR] Failures: > > [ERROR] ExecutionCommandWrapperTest.testGetExecutionCommand:247 > > [ERROR] AmbariErrorHandlerTest.testHandleInternalServerError:119 > Nothing > > captured yet > > [ERROR] Errors: > > [ERROR] > > > RootServiceComponentConfigurationResourceProviderTest.shouldUpdatePasswordInCredentialStoreIfSecurityPasswordEncryptionIsEnabled:534 > > > ConstructorNotFound > > [ERROR] > > > PasswordUtilsTest.shouldReadPasswordFromCredentialStoreOfAnAlias:67->setupBasicCredentialProviderExpectations:127 > > > ConstructorNotFound > > [ERROR] > > > PasswordUtilsTest.shouldResolveEncryptedPaswordIfWeStoreTheAliasInPasswordFile:103->setupBasicCredentialProviderExpectations:127 > > > ConstructorNotFound > > [INFO] > > [ERROR] Tests run: 5271, Failures: 2, Errors: 3, Skipped: 60 > > [INFO] > > [INFO] > > > > [INFO] Reactor Summary: > > [INFO] > > [INFO] Ambari Main 2.7.6.0.0 .. SUCCESS [ > > 0.651 s] > > [INFO] Apache Ambari Project POM 2.7.6.0.0 SUCCESS [ > > 0.009 s] > > [INFO] Ambari Web 2.7.6.0.0 ... SUCCESS > [01:20 > > min] > > [INFO] Ambari Views 2.7.6.0.0 . SUCCESS [ > > 1.149 s] > > [INFO] Ambari Admin View 2.7.6.0.0 SUCCESS [ > > 26.216 s] > > [INFO] ambari-utility 1.0.0.0-SNAPSHOT SUCCESS [ > > 2.062 s] > > [INFO] ambari-metrics 2.7.6.0.0 ... SUCCESS [ > > 0.109 s] > > [INFO] Ambari Metrics Common 2.7.6.0.0 SUCCESS [ > > 37.461 s] > > [INFO] Ambari Metrics Hadoop Sink 2.7.6.0.0 ... SUCCESS [ > > 6.900 s] > > [INFO] Ambari Metrics Flume Sink 2.7.6.0.0 SUCCESS [ > > 4.742 s] > > [INFO] Ambari Metrics Kafka Sink 2.7.6.0.0 SUCCESS [ > > 3.439 s] > > [INFO] Ambari
[ANN] Apache Maven Invoker Plugin 3.2.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Invoker Plugin, version 3.2.2 The Invoker Plugin is used to run a set of Maven projects. The plugin can determine whether each project execution is successful, and optionally can verify the output generated from the given project execution. This plugin is in particular handy to perform integration tests for other Maven plugins. The Invoker Plugin can be employed to run a set of test projects that have been designed to assert certain features of the plugin under test. https://maven.apache.org/plugins/maven-invoker-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-invoker-plugin 3.2.2 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-invoker-plugin/download.cgi Release Notes - Maven Invoker Plugin - Version 3.2.2 ** Bug * [MINVOKER-195] - Fast Build Configuration and mirrors in local settings.xml * [MINVOKER-260] - Option 'streamLogs' does not work properly for logs from intepreter * [MINVOKER-264] - Errors during maven site build * [MINVOKER-265] - option 'streamLogs' does not work properly for logs from groovy intepreter ** New Feature * [MINVOKER-250] - streamLogsOnFailures - parameter/option * [MINVOKER-251] - Allow options parallelThreads depends on available cores * [MINVOKER-255] - support environmentVariable in invokerPropertiesFile * [MINVOKER-268] - invoker:run skips invocation when the sources are unmodified ** Improvement * [MINVOKER-257] - Test code should meet checkstyle requirements * [MINVOKER-262] - GitHub Action confirm build on multiple jdk * [MINVOKER-272] - use Files.createTempDirectory(...) instead of custom code around File.createTempFile(...) ** Dependency upgrade * [MINVOKER-254] - Upgrade Groovy 2.4.21 * [MINVOKER-256] - upgrade parent pom to latest version - 34 * [MINVOKER-259] - upgrade Doxia Sitetools to 1.9.2 to remove dependency on Struts * [MINVOKER-267] - Update maven-script-interpreter to 1.3 * [MINVOKER-276] - Update maven-invoker to 3.1.0 * [MINVOKER-277] - Require Maven 3.1.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Common Artifact Filters 3.2.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Common Artifact Filters, version 3.2.0 A collection of ready-made filters to control inclusion/exclusion of artifacts during dependency resolution. https://maven.apache.org/shared/maven-common-artifact-filters/ You should specify the version in your project's configuration: org.apache.maven.shared maven-common-artifact-filters 3.2.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-common-artifact-filters/download.cgi Release Notes - Maven Shared Components - Version 3.2.0 ** Improvement * [MSHARED-975] - Big speed improvements for patterns that do not contain any wildcard ** Dependency upgrade * [MSHARED-974] - Set minimum enforced Maven version to 3.1.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Invoker 3.1.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Invoker, version 3.1.0 For information about the functionality of this lib - please check the website: https://maven.apache.org/shared/maven-invoker/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-invoker 3.1.0 You can download the appropriate sources etc. from the download page: http://maven.apache.org/shared/maven-invoker/download.cgi Release Notes - Maven Shared Components - Version maven-invoker-3.1.0 ** Improvement * [MSHARED-879] - make build Reproducible * [MSHARED-976] - Maven 3.1.1 prerequisite to run ( + move to JSR-330) * [MSHARED-978] - Add option to use the 'quiet' (-q) flag ** Dependency upgrade * [MSHARED-977] - Upgrade to maven-shared-utils to 3.3.3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Checkstyle Plugin version 3.1.2 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Checkstyle Plugin, version 3.1.2 The Checkstyle Plugin generates a report regarding the code style used by the developers https://maven.apache.org/plugins/maven-checkstyle-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-checkstyle-plugin 3.1.2 You can download the appropriate sources etc. from the download page: https://maven.apache.org/plugins/maven-checkstyle-plugin/download.cgi Release Notes - Maven Checkstyle Plugin - Version 3.1.2 ** Bug * [MCHECKSTYLE-392] - Update and backfill release notes ** Improvement * [MCHECKSTYLE-385] - Violation should be a value class ** Task * [MCHECKSTYLE-358] - Links to mailing lists in README are dead * [MCHECKSTYLE-387] - Deprecate method setUpCheckstyleClassloader in 3.1.2 * [MCHECKSTYLE-400] - Remove travis.org ci Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Common Artifact Filters version 3.1.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Common Artifact Filters, version 3.1.1 This shared component is a collection of ready-made filters to control the inclusion/exclusion of artifacts during dependency resolution. http://maven.apache.org/shared/maven-common-artifact-filters/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-common-artifact-filters 3.1.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-common-artifact-filters/download.cgi Release Notes - Maven Common Artifact Filters - Version 3.1.1 ** Bug * [MSHARED-942] - Update JIRA URL for maven-common-artifact-filters ** Improvement * [MSHARED-879] - make build Reproducible ** Dependency upgrade * [MSHARED-941] - Deprecate SonatypeAetherFilterTransformer and SonatypeAetherNode * [MSHARED-950] - Set minimum enforced Maven version to 3.1.0 * [MSHARED-959] - Upgrade Maven Shared Utils to 3.3.3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Archiver version 3.5.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Archiver, version 3..5.1 This shared lib is mainly used by plugins to handle packaging https://maven.apache.org/shared/maven-archiver/index.html You should specify the version in your project's dependency configuration: org.apache.maven maven-archiver 3.5.1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-archiver/download.cgi Release Notes - Maven Archiver - Version 3.5.1 ** Improvement * [MSHARED-879] - make build Reproducible ** Dependency upgrade * [MSHARED-944] - Set minimum Maven version to 3.1.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Resources, version 3 Released
The Maven team is pleased to announce the release of the Apache Maven Shared Resources, version 3 This is a collection of templates that are specific to the Maven project. https://maven.apache.org/shared/maven-shared-resources/ You should specify the version in your project's plugin dependency: org.apache.maven.shared maven-shared-resources 3 Release Notes - Apache Maven Shared Resources - Version 3 Bug [MSHARED-854] - 'cacheFile' property is removed from TreeWalker in Checkstyle 8.19 Improvement [MSHARED-879] - make build Reproducible [MSHARED-968] - Exclude module-info.java from default checkstyle checks Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Script Interpreter version 1.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Script Interpreter version 1.3 This component provides some utilities to interpret/execute some scripts for various implementations: Groovy or BeanShell. https://maven.apache.org/shared/maven-script-interpreter/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-script-interpreter 1.3 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-script-interpreter/download.cgi Release Notes - Apache Maven Script Interpreter - 1.3 ** Improvement * [MSHARED-828] - Require Java 7 * [MSHARED-879] - make build Reproducible * [MSHARED-906] - Add GitHub Action to confirm build PR * [MSHARED-907] - Output build log from script to maven mojo log * [MSHARED-910] - Redundant option failOnException * [MSHARED-911] - Replace AntClassLoader by RootLoader * [MSHARED-914] - Detailed message from failed script evaluation shouldn't be propagated * [MSHARED-917] - Remove dependency to plexus-component-annotations * [MSHARED-939] - Remove Apache Ivy from dependency ** Task * [MSHARED-960] - document how to use Grapes in a Groovy script Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
