Second for --fail-on-severity

2019-12-18 Thread Robert Scholte
Please review (and support) the following:
https://issues.apache.org/jira/browse/MNG-6065


https://github.com/apache/maven/pull/287

https://github.com/apache/maven-integration-testing/pull/48


https://builds.apache.org/job/maven-box/job/maven/job/MNG-6065/


thanks,
Robert

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

2019-12-18 Thread Robert Scholte
Hi Mark,

Based on the exception you're missing maven-release-api (or this file is 
corrupt).
There's no documentation regarding MRELEASE-956 (yet), but it shouldn't effect 
the default (2.5.3) behavior of the plugin.

thanks,
Robert

On 18-12-2019 22:40:36, Mark Derricutt  wrote:
On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:

org.apache.maven.plugins
maven-release-plugin
3.0.0-M1

Him, updating my projects to use this and got:
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project smx3.bill-of-materials: Execution default-cli of goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare: 
org/apache/maven/shared/release/env/ReleaseEnvironment
This is configured in an import tile from out tiles project configured as:
 default 
 ...  org.apache.maven.plugins 
maven-release-plugin 2.5.3 
  clean reproducible:apply sortpom:sort 
tidy:pom rangeresolver:lock-deps install  
deploy  reproducible:clear sortpom:sort 
tidy:pom  
${projectVersionPolicyId} 
true 
false true 
   com.smxemail 
qualified-version-policy 1.0.2 
  
We do have a custom projectVersionPolicy that we configure, defaulting to 
'default'.
I note in the changeling:
* [MRELEASE-975] - NPE when using an unknown project versionpolicy id * 
[MRELEASE-956] - Release Strategy Interface
Is there a documented set of changes? MRELEASE-956 seems to imply the the 
current API is still there?
Mark
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time." — Mark 
Reinhold.
Mark Derricutt
http://www.theoryinpractice.net [http://www.theoryinpractice.net]
http://www.chaliceofblood.net [http://www.chaliceofblood.net]
http://plus.google.com/+MarkDerricutt [http://plus.google.com/+MarkDerricutt]
http://twitter.com/talios [http://twitter.com/talios]
http://facebook.com/mderricutt [http://facebook.com/mderricutt]

Re: [ANN] Apache Maven Release Plugin 3.0.0-M1 Released

2019-12-18 Thread Mark Derricutt
On 16 Dec 2019, at 21:02, Hervé Boutemy wrote:

> 
>   org.apache.maven.plugins
>   maven-release-plugin
>   3.0.0-M1
> 

Him, updating my projects to use this and got:

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare (default-cli) on 
project smx3.bill-of-materials: Execution default-cli of goal 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare failed: A 
required class was missing while executing 
org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:prepare: 
org/apache/maven/shared/release/env/ReleaseEnvironment

This is configured in an import tile from out tiles project configured as:

  
default
  
  ...
  
org.apache.maven.plugins
maven-release-plugin
2.5.3

  
clean
reproducible:apply
sortpom:sort
tidy:pom
rangeresolver:lock-deps
install
  
  deploy
  
reproducible:clear
sortpom:sort
tidy:pom
  
  
${projectVersionPolicyId}
  true
  false
  true


  
com.smxemail
qualified-version-policy
1.0.2
  

  

We do have a custom projectVersionPolicy that we configure, defaulting to 
'default'.

I note in the changeling:

* [MRELEASE-975] - NPE when using an unknown project versionpolicy id
* [MRELEASE-956] - Release Strategy Interface

Is there a documented set of changes? MRELEASE-956 seems to imply the the 
current API is still there?

Mark





---
"The ease with which a change can be implemented has no relevance at all to 
whether it is the right change for the (Java) Platform for all time." — 
Mark Reinhold.

Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
http://twitter.com/talios
http://facebook.com/mderricutt


signature.asc
Description: OpenPGP digital signature


Accessing a pgp signature file from plugin

2019-12-18 Thread Slawomir Jaranowski
Hi,

I'm author of pgpverify-maven-plugin, this plugin check pgp signatures of
project dependencies.

I have problem how to access/download "asc" signature file from mojo.

Currently I use repositorySystem.resolve(...), for artifact with changed
file name, but in logs I see, eg:

Could not validate integrity of download from
  
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-ejb-plugin/3.0.1/maven-ejb-plugin-3.0.1.jar.asc:
  Checksum validation failed, no checksums available

My problem code are here:
https://github.com/s4u/pgpverify-maven-plugin/blob/master/src/main/java/org/simplify4u/plugins/ArtifactResolver.java#L111
https://github.com/s4u/pgpverify-maven-plugin/blob/master/src/main/java/org/simplify4u/plugins/AscArtifactHandler.java#L56


-- 
Sławomir Jaranowski


Bug Triage Thoughts

2019-12-18 Thread Elliotte Rusty Harold
This is the list of issues currently scheduled for autoclosure:

https://issues.apache.org/jira/browse/MRELEASE-971?jql=category%20%3D%20Maven%20AND%20updated%20%3C%3D%20-153w%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20created%20DESC

There are 376 right now. That's after I knocked a hundred, give or
take, off the list by closing them, commenting on them, or
recategorizing them. If any are closed incorrectly, please do reopen
them. The main goal is to bring attention to issues that need
attention, and get the rest out of our way.

There are definitely some valid requests and bugs in the remaining
issues, along with issues that are done and issues that shouldn't be
done.

It would be very helpful to look at that list and check on any that
you, yourself, reported to see if you want them to remain open. If so,
just add a comment. Otherwise, resolve it if it's done or moot. To
find them  add "AND reporter = currentUser()" to the query.

It would also be helpful if folks could look at issues for specific
plugins you're familiar with. To do this add a project field to the
JQL query on the search box. E.g.

project = "Maven Shade Plugin"

Jira will autocomplete project names.

Thanks.

-- 
Elliotte Rusty Harold
elh...@ibiblio.org

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