Re: maven.java.net - Certificate expired

This issue was raised yesterday and Sonatype renewed it then. I just verified and the cert looks good from where I connect (Europe) to maven.java.net. /Anders On Tue, Feb 23, 2021 at 8:10 AM lucas bakalian wrote: > Hi, > > When trying to build Apache Phoenix 5.1 > > I encountered the following

maven.java.net - Certificate expired

Hi, When trying to build Apache Phoenix 5.1 I encountered the following problem [ERROR] Failed to execute goal on project phoenix-hbase-compat-2.3.0: Could not resolve dependencies for project org.apache.phoenix:phoenix-hbase-compat-2.3.0:jar:5.1.0.1.0.0.0-140: Failed to collect dependencies

Re: Maven superpom, JUnit 5 and Spring

I agree with the recommendations made by Anthony, and that best practice is to specify all versions explicitly. However, I am also empathetic to the concerns raised by Tilman. When people compare Maven to other build tools and complain about the verbosity of POM files, a lot of that verbosity

Re: Maven superpom, JUnit 5 and Spring

I recommend reading the “Important Note” found here: https://maven.apache.org/guides/mini/guide-configuring-plugins.html#introduction > Important Note: Always define each version of the plugins used by the

Maven superpom, JUnit 5 and Spring

Hello, I'm using maven 3.6.3 and the maven-surefire-plugin version used in a build is 2.12.4 when the version is not specified, the "effective" version is 2.10. For junit 5 one needs 2.22.2, see https://junit.org/junit5/docs/current/user-guide/#running-tests-build-maven this is a pitfall for

Re: Regarding component usage in maven-assembly-plugin

That file does not define top level element called component, hence the original question. On Mon, Feb 22, 2021 at 4:24 PM Jean-Pierre Urkens wrote: > > Have a look at http://maven.apache.org/xsd/assembly-2.1.0.xsd > Look in the example assembly files that come packaged with the plugin. In > the

RE: Regarding component usage in maven-assembly-plugin

Have a look at http://maven.apache.org/xsd/assembly-2.1.0.xsd Look in the example assembly files that come packaged with the plugin. In the xml assembly file you'll see a reference to: http://maven.apache.org/ASSEMBLY/2.1.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;

Regarding component usage in maven-assembly-plugin

Yo! I've recently started using the assembly plugin and noticed that the documentation does not specify the XSD files for component descriptor files. Is there a particular reason for this? Cheers! - To unsubscribe, e-mail: