Re: [VOTE] Release Maven Resolver version 1.6.1

Am 2020-10-02 um 20:32 schrieb Michael Osipov: Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348853 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissues

Plugin ITs with toolchain on ci-builds.a.o

Hi all, I'm trying to create a IT that uses toolchain. I've configured it in the test's pom [1] and in invoker.properties [2]. Locally, the IT executed, but on ci-builds.a.o the test "MPMD-304-toolchain-support" is skipped "due to Toolchain" [3]. I was assuming, that the toolchains configured by

[VOTE] Release Maven Resolver version 1.6.1

Hi, We solved 25 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12348853 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissues Staging repo:

Re: Maven Sign Plugin

Targeting to maven 3.7.0-SNAPSHOT makes easier access to Transformer api. So one issue is need to resolve: https://issues.apache.org/jira/browse/MNG-6992 Of course it is clear that all "uploaded" files must be signed. Question is - if we should use transformer api only for POM or for all? pt., 2

Re: Maven Sign Plugin

All "uploaded" files must be signed, see for instance  https://repo1.maven.org/maven2/org/apache/maven/maven-core/3.6.3/ And don't care about older Maven versions, for now just set the prerequisite for Maven to 3.7.0-SNAPSHOT in the pom. On 2-10-2020 14:21:02, Slawomir Jaranowski wrote: But on

Re: Maven Sign Plugin

But on the other side, plugins must sign other artifacts associated with a given project. So in this way we have two different processes - one for pom with transformation and ather for rest artifacts. Maybe all project artifacts should go through the transformation process then we can have one

(un)stable builds and Java upgrade

Now that Java 15 is the latest release and Java 16-ea is available, we should upgrade that on our Jenkins server[1][2] (I see somebody reduced the number of versions, we shouldn't do that!) However, as long as we don't have our builds stable, we can't be sure if the Java upgrade has a negative

JDK 16 EA build 18 is now available

Hi Robert , OpenJDK 16 Early Access build 18**is now available at http://jdk.java.net/16 * These early-access , open-source builds are provided under the o GNU General Public License, version 2, with the Classpath Exception . *

Re: Maven Sign Plugin

In the end a signer is just another file transformer, so we need to achieve something like this: local pom >> build/consumer pom (distribute) >> sign (distribute) The plugin must be able to register a SignFileTransformer, which should only be called during deploy. For the latter I can imagine we