[jira] [Commented] (MRESOLVER-184) Destroy Redisson semaphores if not used anymore
[
https://issues.apache.org/jira/browse/MRESOLVER-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362599#comment-17362599
]
Hudson commented on MRESOLVER-184:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #84
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/84/
> Destroy Redisson semaphores if not used anymore
> ---
>
> Key: MRESOLVER-184
> URL: https://issues.apache.org/jira/browse/MRESOLVER-184
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Affects Versions: 1.7.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.7.1
>
>
> Instead of leaving garbage in Redis, delete the key for a {{RSemaphore}} when
> it is not necessary anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MRESOLVER-185) Upgrade Redisson to 3.15.6
[ https://issues.apache.org/jira/browse/MRESOLVER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362598#comment-17362598 ] Hudson commented on MRESOLVER-185: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » update-maven-in-demos #5 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/update-maven-in-demos/5/ > Upgrade Redisson to 3.15.6 > -- > > Key: MRESOLVER-185 > URL: https://issues.apache.org/jira/browse/MRESOLVER-185 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.1 > > > It contains a fix for https://github.com/redisson/redisson/issues/3573. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-183) Don't require optional dependencies for Redisson
[ https://issues.apache.org/jira/browse/MRESOLVER-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362597#comment-17362597 ] Hudson commented on MRESOLVER-183: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » update-maven-in-demos #5 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/update-maven-in-demos/5/ > Don't require optional dependencies for Redisson > > > Key: MRESOLVER-183 > URL: https://issues.apache.org/jira/browse/MRESOLVER-183 > Project: Maven Resolver > Issue Type: Task > Components: Resolver >Affects Versions: 1.7.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.1 > > > According to [this > statement|https://github.com/redisson/redisson/issues/3613#issuecomment-841842000] > several dependencies are optional and not necessary to run Redisson for us. > Don't list them as required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MRESOLVER-185) Upgrade Redisson to 3.15.6
[ https://issues.apache.org/jira/browse/MRESOLVER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362595#comment-17362595 ] Hudson commented on MRESOLVER-185: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-resolver » master #83 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-resolver/job/master/83/ > Upgrade Redisson to 3.15.6 > -- > > Key: MRESOLVER-185 > URL: https://issues.apache.org/jira/browse/MRESOLVER-185 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.1 > > > It contains a fix for https://github.com/redisson/redisson/issues/3573. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MRESOLVER-184) Destroy Redisson semaphores if not used anymore
[
https://issues.apache.org/jira/browse/MRESOLVER-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MRESOLVER-184.
Resolution: Fixed
Fixed with
[69fd9f38d75fe5fd62c3a6b8d70b1018b67f7a68|https://gitbox.apache.org/repos/asf?p=maven-resolver.git=commit=69fd9f38d75fe5fd62c3a6b8d70b1018b67f7a68].
> Destroy Redisson semaphores if not used anymore
> ---
>
> Key: MRESOLVER-184
> URL: https://issues.apache.org/jira/browse/MRESOLVER-184
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
>Affects Versions: 1.7.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.7.1
>
>
> Instead of leaving garbage in Redis, delete the key for a {{RSemaphore}} when
> it is not necessary anymore.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362592#comment-17362592
]
Michael Osipov edited comment on MNG-7165 at 6/13/21, 7:30 PM:
---
I appreciate your feedback, but both issues aren't related. If you hijack a
closed ticket the issue you experience will disappear in oblivion. Please
create an issue, this will make your effort publically visiable.
was (Author: michael-o):
I appreciate your feedback, but both issues aren't related. If you hijack a
closed ticket the issue you experience will disappear in oblivion.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362592#comment-17362592
]
Michael Osipov edited comment on MNG-7165 at 6/13/21, 7:30 PM:
---
I appreciate your feedback, but both issues aren't related. If you hijack a
closed ticket the issue you experience will disappear in oblivion. Please
create an issue, this will make your effort publically visibile.
was (Author: michael-o):
I appreciate your feedback, but both issues aren't related. If you hijack a
closed ticket the issue you experience will disappear in oblivion. Please
create an issue, this will make your effort publically visiable.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
>
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362592#comment-17362592
]
Michael Osipov commented on MNG-7165:
-
I appreciate your feedback, but both issues aren't related. If you hijack a
closed ticket the issue you experience will disappear in oblivion.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.annotation-api-1.3.2.jar
> constituent[30]:
>
[jira] [Updated] (MPOM-263) Enforce building with Java 8+
[ https://issues.apache.org/jira/browse/MPOM-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MPOM-263: Summary: Enforce building with Java 8+ (was: Enforce building with Java8+) > Enforce building with Java 8+ > - > > Key: MPOM-263 > URL: https://issues.apache.org/jira/browse/MPOM-263 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-24 >Reporter: Konrad Windszus >Priority: Major > > Several plugins require Java 8 or newer. This should be enforced with a > dedicated enforcer rule. Compare with > https://lists.apache.org/thread.html/r7981e9863a55d9cf10657c1f98b6be41080adf91caf8d76d1881ef19%40%3Cdev.maven.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MPOM-263) Enforce building with Java8+
[ https://issues.apache.org/jira/browse/MPOM-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated MPOM-263: - Description: Several plugins require Java 8 or newer. This should be enforced with a dedicated enforcer rule. Compare with https://lists.apache.org/thread.html/r7981e9863a55d9cf10657c1f98b6be41080adf91caf8d76d1881ef19%40%3Cdev.maven.apache.org%3E (was: Several plugin require Java 8 or newer. This should be enforced with dedicated enforcer rule. Compare with https://lists.apache.org/thread.html/r7981e9863a55d9cf10657c1f98b6be41080adf91caf8d76d1881ef19%40%3Cdev.maven.apache.org%3E) > Enforce building with Java8+ > > > Key: MPOM-263 > URL: https://issues.apache.org/jira/browse/MPOM-263 > Project: Maven POMs > Issue Type: Improvement > Components: asf >Affects Versions: ASF-24 >Reporter: Konrad Windszus >Priority: Major > > Several plugins require Java 8 or newer. This should be enforced with a > dedicated enforcer rule. Compare with > https://lists.apache.org/thread.html/r7981e9863a55d9cf10657c1f98b6be41080adf91caf8d76d1881ef19%40%3Cdev.maven.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362585#comment-17362585
]
Konrad Windszus commented on MNG-7165:
--
[~michael-o] I was trying to provide constructive feedback in the context of
this issue, as to me it seemed related. Do whatever you want with that. I don't
invest more time in it just to get harsh reactions...
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.annotation-api-1.3.2.jar
>
[jira] [Commented] (SUREFIRE-1919) JUnit test discovery fails with reuseForks=false but works when reuseForks=true
[
https://issues.apache.org/jira/browse/SUREFIRE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362583#comment-17362583
]
Jan Mosig commented on SUREFIRE-1919:
-
Nevermind ^^ I found the problem: When specifying
{{false}}, the tests run directly in the mvn JVM. This
means, the argLine cannot be passed to some JVM, because it is already running.
The solution is to use {{MAVEN_OPTS="--add-modules .. mvn clean verify"}}.
> JUnit test discovery fails with reuseForks=false but works when
> reuseForks=true
> ---
>
> Key: SUREFIRE-1919
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1919
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 3.0.0-M5
> Environment: * java version "16.0.1" 2021-04-20
> * Java(TM) SE Runtime Environment (build 16.0.1+9-24)
> * Java HotSpot(TM) 64-Bit Server VM (build 16.0.1+9-24, mixed mode, sharing)
> * Microsoft Windows [Version 10.0.19043.1052]
> * Maven 3.6.3
> * Surefire 3.0.0-M5
> * JUnit (Jupiter) 5.7.2
>Reporter: Jan Mosig
>Priority: Major
>
> Hi there,
> the other day I was playing around with incubator code from JDK16 and noticed
> odd behavior wrt the reuseForks configuration.
>
> In order to compile and run tests, my project needs the jdk.incubator.foreign
> module. So I configured it like this:
> {code:java}
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
> false
> 1
> -Dforeign.restricted=permit
> --add-modules=jdk.incubator.foreign
>
>
> {code}
> Which results in
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
> on project de.itemis.mosig.sfrf: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed:
> org.junit.platform.commons.JUnitException: TestEngine with ID 'junit-jupiter'
> failed to discover tests: ClassSelector [className =
> 'de.itemis.mosig.sfrf.AppTest'] resolution failed:
> jdk/incubator/foreign/MemoryLayout: jdk.incubator.foreign.MemoryLayout ->
> [Help 1]
> {code}
> Whereas setting {{reuseForks}} to {{true}} works.
> Please note that the project itself is not modularized, i. e. it does not
> have a module-info.java specification (on purpose).
> I provided a demo for this over at GitHub:
> https://github.com/JanMosigItemis/sfrf
> Any thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MRESOLVER-185) Upgrade Redisson to 3.15.6
[ https://issues.apache.org/jira/browse/MRESOLVER-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MRESOLVER-185. Resolution: Fixed Fixed with [c256c20b77fd1f1ed512c79ef3de0b81b3b5ccb4|https://gitbox.apache.org/repos/asf?p=maven-resolver.git=commit=c256c20b77fd1f1ed512c79ef3de0b81b3b5ccb4]. > Upgrade Redisson to 3.15.6 > -- > > Key: MRESOLVER-185 > URL: https://issues.apache.org/jira/browse/MRESOLVER-185 > Project: Maven Resolver > Issue Type: Dependency upgrade > Components: Resolver >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 1.7.1 > > > It contains a fix for https://github.com/redisson/redisson/issues/3573. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SUREFIRE-1919) JUnit test discovery fails with reuseForks=false but works when reuseForks=true
Jan Mosig created SUREFIRE-1919:
---
Summary: JUnit test discovery fails with reuseForks=false but
works when reuseForks=true
Key: SUREFIRE-1919
URL: https://issues.apache.org/jira/browse/SUREFIRE-1919
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 3.0.0-M5
Environment: * java version "16.0.1" 2021-04-20
* Java(TM) SE Runtime Environment (build 16.0.1+9-24)
* Java HotSpot(TM) 64-Bit Server VM (build 16.0.1+9-24, mixed mode, sharing)
* Microsoft Windows [Version 10.0.19043.1052]
* Maven 3.6.3
* Surefire 3.0.0-M5
* JUnit (Jupiter) 5.7.2
Reporter: Jan Mosig
Hi there,
the other day I was playing around with incubator code from JDK16 and noticed
odd behavior wrt the reuseForks configuration.
In order to compile and run tests, my project needs the jdk.incubator.foreign
module. So I configured it like this:
{code:java}
org.apache.maven.plugins
maven-surefire-plugin
false
1
-Dforeign.restricted=permit
--add-modules=jdk.incubator.foreign
{code}
Which results in
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test) on
project de.itemis.mosig.sfrf: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test failed:
org.junit.platform.commons.JUnitException: TestEngine with ID 'junit-jupiter'
failed to discover tests: ClassSelector [className =
'de.itemis.mosig.sfrf.AppTest'] resolution failed:
jdk/incubator/foreign/MemoryLayout: jdk.incubator.foreign.MemoryLayout -> [Help
1]
{code}
Whereas setting {{reuseForks}} to {{true}} works.
Please note that the project itself is not modularized, i. e. it does not have
a module-info.java specification (on purpose).
I provided a demo for this over at GitHub:
https://github.com/JanMosigItemis/sfrf
Any thoughts?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362578#comment-17362578
]
Michael Osipov commented on MNG-7165:
-
[~kwin], this issue is addressed. Don't hijack. Open a new one. Library signing
is a macOS issue, nothing we can solve here. The purpose of the expanded
directory is to avoid constant extraction, clutter and deletion.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.annotation-api-1.3.2.jar
>
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362569#comment-17362569
]
Michael Osipov commented on MNG-7165:
-
The exploaded directory must stay.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.annotation-api-1.3.2.jar
> constituent[30]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-spi-1.7.0.jar
> constituent[31]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362537#comment-17362537
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 4:43 PM:
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
But it seems the issue with orphaned tmp files has been solved meanwhile
https://github.com/fusesource/jansi/issues/98.
In any case the binaries are not signed at all.
{code}
codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64
xattr
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
com.apple.quarantine
xattr /Users/konradwindszus/Downloads/apache-maven/lib/jansi-2.3.3.jar
com.apple.quarantine
{code}
was (Author: kwin):
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
But it seems the issue with orphaned tmp files has been solved meanwhile
https://github.com/fusesource/jansi/issues/98.
In any case the binaries are not signed at all.
{code}
codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64
{code}
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362537#comment-17362537
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 4:41 PM:
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
But it seems the issue with orphaned tmp files has been solved meanwhile
https://github.com/fusesource/jansi/issues/98.
In any case the binaries are not signed at all.
{code}
codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64
{code}
was (Author: kwin):
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
{code}
codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64
{code}
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362537#comment-17362537
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 4:40 PM:
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
{code}
codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64
{code}
was (Author: kwin):
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
{{codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64}}
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362537#comment-17362537
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 4:39 PM:
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
I think GateKeeper prevents loading binaries downloaded from a browser
(https://support.blackfire.io/en/articles/3669492-issues-with-macos-catalina).
I don't know why the temp files extracted from the JAR on demand don't suffer
from that issue.
{{codesign -
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code object is not signed at all
In architecture: x86_64}}
was (Author: kwin):
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362537#comment-17362537
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 4:17 PM:
3.8.1 works fine without any warnings and also the warning vanish from
4.0.0-alpha1 SNAPSHOT once I remove the folder {{lib/jansi-native}}.
was (Author: kwin):
3.8.1 works fine without any warnings.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
>
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362537#comment-17362537
]
Konrad Windszus commented on MNG-7165:
--
3.8.1 works fine without any warnings.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.annotation-api-1.3.2.jar
> constituent[30]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-spi-1.7.0.jar
> constituent[31]:
>
[jira] [Commented] (MSHADE-36) Add option to include dependency reduced POM instead of original one
[ https://issues.apache.org/jira/browse/MSHADE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362533#comment-17362533 ] Michael Osipov commented on MSHADE-36: -- Waiting for the PR to be updated... > Add option to include dependency reduced POM instead of original one > > > Key: MSHADE-36 > URL: https://issues.apache.org/jira/browse/MSHADE-36 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Mark Hobson >Assignee: Michael Osipov >Priority: Major > Fix For: 3.3.0 > > > The dependency reduced pom needs to replace the packaged pom at: > META-INF/maven///pom.xml > This will allow tools that use this metadata to read the correct shaded > dependencies (e.g. maven-runtime). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MSHADE-36) Add option to include dependency reduced POM instead of original one
[ https://issues.apache.org/jira/browse/MSHADE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MSHADE-36: Assignee: Michael Osipov > Add option to include dependency reduced POM instead of original one > > > Key: MSHADE-36 > URL: https://issues.apache.org/jira/browse/MSHADE-36 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Mark Hobson >Assignee: Michael Osipov >Priority: Major > Fix For: 3.3.0 > > > The dependency reduced pom needs to replace the packaged pom at: > META-INF/maven///pom.xml > This will allow tools that use this metadata to read the correct shaded > dependencies (e.g. maven-runtime). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-36) Add option to include dependency reduced POM instead of original one
[ https://issues.apache.org/jira/browse/MSHADE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHADE-36: - Summary: Add option to include dependency reduced POM instead of original one (was: Dependency reduced pom does not replace the packaged META-INF/maven version) > Add option to include dependency reduced POM instead of original one > > > Key: MSHADE-36 > URL: https://issues.apache.org/jira/browse/MSHADE-36 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Mark Hobson >Priority: Major > Fix For: 3.3.0 > > > The dependency reduced pom needs to replace the packaged pom at: > META-INF/maven///pom.xml > This will allow tools that use this metadata to read the correct shaded > dependencies (e.g. maven-runtime). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-36) Dependency reduced pom does not replace the packaged META-INF/maven version
[ https://issues.apache.org/jira/browse/MSHADE-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHADE-36: - Issue Type: New Feature (was: Bug) > Dependency reduced pom does not replace the packaged META-INF/maven version > --- > > Key: MSHADE-36 > URL: https://issues.apache.org/jira/browse/MSHADE-36 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 1.1 >Reporter: Mark Hobson >Priority: Major > Fix For: 3.3.0 > > > The dependency reduced pom needs to replace the packaged pom at: > META-INF/maven///pom.xml > This will allow tools that use this metadata to read the correct shaded > dependencies (e.g. maven-runtime). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MSHADE-252) shadeSourcesContent is broken when combined with partial relocation
[
https://issues.apache.org/jira/browse/MSHADE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MSHADE-252:
-
Assignee: Herve Boutemy
> shadeSourcesContent is broken when combined with partial relocation
> ---
>
> Key: MSHADE-252
> URL: https://issues.apache.org/jira/browse/MSHADE-252
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.4.3, 3.0.0
>Reporter: Zhenyu Yang
>Assignee: Herve Boutemy
>Priority: Major
> Labels: easyfix
> Fix For: 3.3.0
>
>
> per description in
> https://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#shadeSourcesContent,
> when set it to true,
> "it will attempt to shade the contents of the java source files when creating
> the sources jar." However, it seems will blindly shade all the source files
> include those are excluded from relocation rules.
> This could be illustrated with a simple example:
> Assume there are two classes defined in two packages as below:
> {code:title=A.java}
> package com.fake.fooA;
> import com.fake.fooB;
> public Class A {}
> {code}
> {code:title=B.java}
> package com.fake.fooB;
> import com.fake.fooA;
> public class B {}
> {code}
> and the maven config looks like:
> {code:xml}
>
> org.apache.maven.plugins
> maven-shade-plugin
> 2.4.3
>
>
>
> package
>
> shade
>
>
> false
> true
> true
>
>
> com.fake
> .com.fake.shaded
>
> com.fake.fooA.*
>
>
>
> {code}
> Then the shade plugin will modify the B's source file to be:
> {code}
> package com.fake.shaded.fooB;
> import com.fake.shaded.fooA;
> public class B {}
> {code}
> Notice that package A's path was also updated, which is wrong as it's not got
> relocated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-390) Implement Sisu index transformer
[
https://issues.apache.org/jira/browse/MSHADE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHADE-390:
--
Summary: Implement Sisu index transformer (was: Implement SISU index
transformer)
> Implement Sisu index transformer
>
>
> Key: MSHADE-390
> URL: https://issues.apache.org/jira/browse/MSHADE-390
> Project: Maven Shade Plugin
> Issue Type: Task
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.3.0
>
>
> The {{META-INF/sisu/javax.inject.Named}} resources needs to be transformed as
> well, if SISU Index used with relocated classes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-390) Implement Sisu index transformer
[
https://issues.apache.org/jira/browse/MSHADE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHADE-390:
--
Description: The {{META-INF/sisu/javax.inject.Named}} resources needs to be
transformed as well, if Sisu index used with relocated classes. (was: The
{{META-INF/sisu/javax.inject.Named}} resources needs to be transformed as well,
if SISU Index used with relocated classes.)
> Implement Sisu index transformer
>
>
> Key: MSHADE-390
> URL: https://issues.apache.org/jira/browse/MSHADE-390
> Project: Maven Shade Plugin
> Issue Type: Task
>Reporter: Tamás Cservenák
>Assignee: Tamás Cservenák
>Priority: Major
> Fix For: 3.3.0
>
>
> The {{META-INF/sisu/javax.inject.Named}} resources needs to be transformed as
> well, if Sisu index used with relocated classes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-170) Outstanding questions about MSHADE-124
[
https://issues.apache.org/jira/browse/MSHADE-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHADE-170:
--
Fix Version/s: (was: backlog)
> Outstanding questions about MSHADE-124
> --
>
> Key: MSHADE-170
> URL: https://issues.apache.org/jira/browse/MSHADE-170
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Gili
>Priority: Minor
>
> MSHADE-124 is marked as fixed but as Anthony Whitford points out:
> # If this is fixed, why does the documentation still warn about this?
> http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#dependencyReducedPomLocation
> # Shouldn't the default location be under project.build.directory instead of
> basedir? Then {{mvn clean}} would be more effective, and the {{Maven
> Release}} plugin wouldn't give an error saying, "Cannot prepare the release
> because you have local modifications."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MSHADE-268) improving inclusion of open source code referenced by java projects.
[ https://issues.apache.org/jira/browse/MSHADE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHADE-268: -- Fix Version/s: (was: waiting-for-feedback) > improving inclusion of open source code referenced by java projects. > - > > Key: MSHADE-268 > URL: https://issues.apache.org/jira/browse/MSHADE-268 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: Sunil Kumar Singh >Priority: Major > > All the details are on git hub at: > https://github.com/ksunilsingh/code-collector > This is an idea on improving inclusion of open source code referenced by java > projects. Currently when we use a java build system (such as maven or > gradle), the build system downloads the jar files referenced by a java > project. What I am proposing here is a replacement for that: > Find out all the classes referenced by the classes in a java project (say, > project A). > Download the source code for these dependencies recursively and include the > downloaded source code in the source tree of project A. > Remove the dependency(ies) from project build configuration file (e.g. > pom.xml) and build the project. > The resulting jar file would be smaller in size than if the full jar for the > dependency is included as is. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-297) Including feature.xml in shaded jar
[ https://issues.apache.org/jira/browse/MSHADE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MSHADE-297: -- Fix Version/s: (was: waiting-for-feedback) > Including feature.xml in shaded jar > --- > > Key: MSHADE-297 > URL: https://issues.apache.org/jira/browse/MSHADE-297 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Pratiksha Tiwari >Priority: Major > > I am trying to use feature.xml as a dependency in my project. The maven shade > plugin while including the jars gives the following error : Failed to execute > goal org.apache.maven.plugins:maven-shade-plugin:2.2:shade (default) on > project: Error creating shaded jar: error in opening zip file > /feature.xml > Is it possible to include this using shade plugin? Otherwise what alternative > method can be used? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-200) Property in parent.artifactId isn't interpolated
[
https://issues.apache.org/jira/browse/MSHADE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MSHADE-200:
--
Fix Version/s: (was: waiting-for-feedback)
> Property in parent.artifactId isn't interpolated
>
>
> Key: MSHADE-200
> URL: https://issues.apache.org/jira/browse/MSHADE-200
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 2.4.1
>Reporter: Chiwan Park
>Assignee: Robert Scholte
>Priority: Major
>
> I'm using property in project artifact id to support multiple scala version
> like following:
> {code:xml}
> org.apache.flink
> flink-parent${scala.suffix}
> 0.10-SNAPSHOT
> {code}
> So child pom have to direct parent with property.
> {code:xml}
>
> org.apache.flink
> flink-parent${scala.suffix}
> 0.10-SNAPSHOT
> ..
>
> flink-scala${scala.suffix}
> flink-scala
> {code}
> In dependency reduced pom, I expected that property in parent artifactId is
> interpolated. But I found that there is untouched property expression.
> {code:xml}
>
> flink-parent${scala.suffix}
> org.apache.flink
> 0.10-SNAPSHOT
> ../../pom.xml
>
> 4.0.0
> flink-scala_2.11
> flink-scala
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362528#comment-17362528
]
Robert Scholte commented on MNG-7165:
-
[~kwin] thanks for your feedback. Just to be sure: you don't see these issues
with Maven 3.8.1?
The libs/jansi-native are extracted from the jansi jar by
https://github.com/apache/maven/blob/master/apache-maven/src/assembly/maven/component.xml#L66-L73.
Either [~gnodet] or [~hboutemy] needs to verify this, maybe these lines can be
removed.
I do remember we explicitly extracted them, otherwise JAnsi would do it, always
creating temp files (without removing them).
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362521#comment-17362521
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 11:00 AM:
-
With the latest SNAPSHOT (downloaded from
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/169/artifact/org/apache/maven/apache-maven/4.0.0-alpha-1-SNAPSHOT/apache-maven-4.0.0-alpha-1-SNAPSHOT-bin.tar.gz)
I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
Also it seems that two different versions of jansi native libraries are now
shipped: The ones contained in lib/jansi-2.3.3.jar and the ones in
lib/jansi-native. The latter are deprecated
(https://github.com/fusesource/jansi-native#deprecation) and the warning goes
away once I remove lib/jansi-native.
was (Author: kwin):
With the latest SNAPSHOT I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
Also it seems that two different versions of jansi native libraries are now
shipped: The ones contained in lib/jansi-2.3.3.jar and the ones in
lib/jansi-native. The latter are deprecated
(https://github.com/fusesource/jansi-native#deprecation) and the warning goes
away once I remove lib/jansi-native.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362521#comment-17362521
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 10:57 AM:
-
With the latest SNAPSHOT I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
Also it seems that two different versions of jansi native libraries are now
shipped: The ones contained in lib/jansi-2.3.3.jar and the ones in
lib/jansi-native. The latter are deprecated
(https://github.com/fusesource/jansi-native#deprecation) and the warning goes
away once I remove lib/jansi-native.
was (Author: kwin):
With the latest SNAPSHOT I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
Also it seems that two different versions of jansi native libraries are now
shipped: The ones contained in lib/jansi-2.3.3.jar and the ones in
lib/jansi-native...
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
>
[jira] [Comment Edited] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362521#comment-17362521
]
Konrad Windszus edited comment on MNG-7165 at 6/13/21, 10:55 AM:
-
With the latest SNAPSHOT I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
Also it seems that two different versions of jansi native libraries are now
shipped: The ones contained in lib/jansi-2.3.3.jar and the ones in
lib/jansi-native...
was (Author: kwin):
With the latest SNAPSHOT I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
>
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362521#comment-17362521
]
Konrad Windszus commented on MNG-7165:
--
With the latest SNAPSHOT I get
{code}
./mvn --version
Failed to load native library:libjansi.jnilib. osinfo: Mac/x86_64
java.lang.UnsatisfiedLinkError:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
dlopen(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib,
1): no suitable image found. Did find:
/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib:
code signature in
(/Users/konradwindszus/Downloads/apache-maven/lib/jansi-native/Mac/x86_64/libjansi.jnilib)
not valid for use in process using Library Validation: library load disallowed
by system policy
Apache Maven 4.0.0-alpha-1-SNAPSHOT (371faf7a49298bd1752632c2675aa499fee64667)
Maven home: /Users/konradwindszus/Downloads/apache-maven
Java version: 11.0.11, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
Default locale: en_DE, platform encoding: UTF-8
OS name: "mac os x", version: "11.4", arch: "x86_64", family: "mac"
{code}
And Mac OS shows a warning {{“libjansi.jnilib” cannot be opened because the
developer cannot be verified.}}.
Is the last version of JAnsi included in Maven properly signed?
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
>
[jira] [Commented] (MNG-7165) Maven does not start if there is no Jansi native library available
[
https://issues.apache.org/jira/browse/MNG-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17362489#comment-17362489
]
Michael Osipov commented on MNG-7165:
-
I can confirm now that this issue is fixed.
> Maven does not start if there is no Jansi native library available
> --
>
> Key: MNG-7165
> URL: https://issues.apache.org/jira/browse/MNG-7165
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-1
>Reporter: Michael Osipov
>Assignee: Robert Scholte
>Priority: Blocker
> Fix For: 4.0.0, 4.0.0-alpha-1
>
>
> Compiled Maven from 5c45b3fe22d8ec4270b2cf1016581b8927d2913d and started on:
> {noformat}
> $ uname -a
> HP-UX deblndw0 B.11.31 U ia64 HP-UX
> $ java -version
> java version "1.8.0.21-hp-ux"
> Java(TM) SE Runtime Environment (build 1.8.0.21-hp-ux-b1)
> Java HotSpot(TM) Server VM (build 25.21-b1, mixed mode)
> {noformat}
> with following result:
> {noformat}
> $ ~/apache-maven-4.0.0-alpha-1-SNAPSHOT/bin/mvn
> ---
> constituent[0]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/conf/logging/
> constituent[1]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-embedder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[2]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[3]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-settings-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[4]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-plugin-api-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[5]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[6]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-builder-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[7]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-builder-support-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[8]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-api-1.7.0.jar
> constituent[9]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-util-1.7.0.jar
> constituent[10]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-shared-utils-3.3.4.jar
> constituent[11]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-io-2.6.jar
> constituent[12]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-slf4j-wrapper-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[13]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guice-4.2.3-no_aop.jar
> constituent[14]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/guava-30.1-jre.jar
> constituent[15]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/failureaccess-1.0.1.jar
> constituent[16]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.inject-1.jar
> constituent[17]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/jsr250-api-1.0.jar
> constituent[18]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-utils-3.3.0.jar
> constituent[19]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/plexus-sec-dispatcher-1.4.jar
> constituent[20]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/slf4j-api-1.7.30.jar
> constituent[21]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/commons-lang3-3.8.1.jar
> constituent[22]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-core-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[23]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-repository-metadata-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[24]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-artifact-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[25]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-model-transform-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[26]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-provider-4.0.0-alpha-1-SNAPSHOT.jar
> constituent[27]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-impl-1.7.0.jar
> constituent[28]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-named-locks-1.7.0.jar
> constituent[29]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/javax.annotation-api-1.3.2.jar
> constituent[30]:
> file:/net/home/osipovmi/apache-maven-4.0.0-alpha-1-SNAPSHOT/lib/maven-resolver-spi-1.7.0.jar
> constituent[31]:
>
[jira] [Created] (MPOM-263) Enforce building with Java8+
Konrad Windszus created MPOM-263: Summary: Enforce building with Java8+ Key: MPOM-263 URL: https://issues.apache.org/jira/browse/MPOM-263 Project: Maven POMs Issue Type: Improvement Components: asf Affects Versions: ASF-24 Reporter: Konrad Windszus Several plugin require Java 8 or newer. This should be enforced with dedicated enforcer rule. Compare with https://lists.apache.org/thread.html/r7981e9863a55d9cf10657c1f98b6be41080adf91caf8d76d1881ef19%40%3Cdev.maven.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005)
