Regarding component usage in maven-assembly-plugin

[Mantas Gridinas]

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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

RE: Regarding component usage in maven-assembly-plugin

[Jean-Pierre Urkens]

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";
  xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
http://maven.apache.org/xsd/assembly-2.1.0.xsd";>


-Original Message-
From: Mantas Gridinas 
Sent: maandag 22 februari 2021 15:20
To: users@maven.apache.org
Subject: 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: 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: Regarding component usage in maven-assembly-plugin

[Mantas Gridinas]

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 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";
>   xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
> http://maven.apache.org/xsd/assembly-2.1.0.xsd";>
>
>
> -Original Message-
> From: Mantas Gridinas 
> Sent: maandag 22 februari 2021 15:20
> To: users@maven.apache.org
> Subject: 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: 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

Maven superpom, JUnit 5 and Spring

[Tilman Hausherr]

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 JUnit 5 users:
https://stackoverflow.com/a/66313961/535646
who don't read the manual. Should I create a JIRA issue that the super 
pom should be updated? Or is another plugin to "blame" for the default 
version?


Tilman


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

Re: Maven superpom, JUnit 5 and Spring

[Anthony Whitford]

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 build 
> to guarantee the build reproducibility. A good practice is to specify them in 
> the  elements for each build plugins. 
> (Generally, you will define a  element in a parent POM.) 
> For reporting plugins, specify each version in the 
>  elements (and surely in the 
>  elements too).


In other words, do not rely on the implied Super Parent Pom for defining plugin 
versions because it will not guarantee build reproducibility.  Instead, your 
pom hierarchy should explicitly declare the plugin versions to use.  
(Maintaining a corporate pom that may be used across projects might be a wise 
approach.)


> On Feb 22, 2021, at 11:11 AM, Tilman Hausherr  wrote:
> 
> 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 JUnit 5 users:
> https://stackoverflow.com/a/66313961/535646
> who don't read the manual. Should I create a JIRA issue that the super pom 
> should be updated? Or is another plugin to "blame" for the default version?
> 
> Tilman
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
> 

Re: Maven superpom, JUnit 5 and Spring

[Greg Chabala]

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 comes from having to specify versions for
plugins, including plugins that are part of the default lifecycle.

If we agree that Maven follows a convention over configuration design,
perhaps the Super POM should be updated to some more sensible defaults.
While it may not be as reproducible to leave them unspecified, it would
reduce the surprise to beginners when now very outdated plugin versions are
used by default.

Greg

On Mon, Feb 22, 2021 at 3:44 PM Anthony Whitford 
wrote:

> I recommend reading the “Important Note” found here:
> https://maven.apache.org/guides/mini/guide-configuring-plugins.html#introduction
> <
> https://maven.apache.org/guides/mini/guide-configuring-plugins.html#introduction
> >
>
> > Important Note: Always define each version of the plugins used by the
> build to guarantee the build reproducibility. A good practice is to specify
> them in the  elements for each build
> plugins. (Generally, you will define a  element in a
> parent POM.) For reporting plugins, specify each version in the
>  elements (and surely in the
>  elements too).
>
>
> In other words, do not rely on the implied Super Parent Pom for defining
> plugin versions because it will not guarantee build reproducibility.
> Instead, your pom hierarchy should explicitly declare the plugin versions
> to use.  (Maintaining a corporate pom that may be used across projects
> might be a wise approach.)
>
>
> > On Feb 22, 2021, at 11:11 AM, Tilman Hausherr 
> wrote:
> >
> > 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 JUnit 5 users:
> > https://stackoverflow.com/a/66313961/535646
> > who don't read the manual. Should I create a JIRA issue that the super
> pom should be updated? Or is another plugin to "blame" for the default
> version?
> >
> > Tilman
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>
>

maven.java.net - Certificate expired

[lucas bakalian]

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 at org.apache.hbase:hbase-server:jar:2.3.0 -> 
org.glassfish.web:javax.servlet.jsp:jar:2.3.2 -> 
org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT: Failed to read artifact 
descriptor for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT: Could not 
transfer artifact org.glassfish:javax.el:pom:3.0.1-b06-SNAPSHOT from/to 
jvnet-nexus-snapshots (https://maven.java.net/content/repositories/snapshots): 
Transfer failed for 
https://maven.java.net/content/repositories/snapshots/org/glassfish/javax.el/3.0.1-b06-SNAPSHOT/javax.el-3.0.1-b06-SNAPSHOT.pom:
 sun.security.validator.ValidatorException: PKIX path validation failed: 
java.security.cert.CertPathValidatorException: validity check failed: NotAfter: 
Fri Feb 19 13:00:00 CET 2021 -> [Help 1]

Which means that the nexus server’s certificate expired

Could you renew it ? Or do you need some help we need it for build our release.

Best regards,

Lucas BAKALIAN
Big Data System Architect
Professional Services
CEO - LUC DATA - PARIS
+336 15.88.1555

Re: maven.java.net - Certificate expired

[Anders Hammar]

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 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 at org.apache.hbase:hbase-server:jar:2.3.0 ->
> org.glassfish.web:javax.servlet.jsp:jar:2.3.2 ->
> org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT: Failed to read artifact
> descriptor for org.glassfish:javax.el:jar:3.0.1-b06-SNAPSHOT: Could not
> transfer artifact org.glassfish:javax.el:pom:3.0.1-b06-SNAPSHOT from/to
> jvnet-nexus-snapshots (
> https://maven.java.net/content/repositories/snapshots): Transfer failed
> for
> https://maven.java.net/content/repositories/snapshots/org/glassfish/javax.el/3.0.1-b06-SNAPSHOT/javax.el-3.0.1-b06-SNAPSHOT.pom:
> sun.security.validator.ValidatorException: PKIX path validation failed:
> java.security.cert.CertPathValidatorException: validity check failed:
> NotAfter: Fri Feb 19 13:00:00 CET 2021 -> [Help 1]
>
> Which means that the nexus server’s certificate expired
>
> Could you renew it ? Or do you need some help we need it for build our
> release.
>
> Best regards,
>
> Lucas BAKALIAN
> Big Data System Architect
> Professional Services
> CEO - LUC DATA - PARIS
> +336 15.88.1555
>
>