[jira] [Created] (MNG-7017) better deploy-file integration
Delany created MNG-7017: --- Summary: better deploy-file integration Key: MNG-7017 URL: https://issues.apache.org/jira/browse/MNG-7017 Project: Maven Issue Type: Improvement Components: Deployment Affects Versions: 3.6.3 Reporter: Delany I have a script which deploys hundreds of static JARs to a Nexus repo. I use the deploy-file goal, which requires the *url* and *repositoryId* properties. Currently I have to hard-code these into the script. I want to be able to use the repository url and id I set in the distributionManagement of my project. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJLINK-55) Pre Release Marker in Site must be changed
[ https://issues.apache.org/jira/browse/MJLINK-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230291#comment-17230291 ] Hudson commented on MJLINK-55: -- Build succeeded in Jenkins: Maven » Maven TLP » maven-jlink-plugin » master #35 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jlink-plugin/job/master/35/ > Pre Release Marker in Site must be changed > -- > > Key: MJLINK-55 > URL: https://issues.apache.org/jira/browse/MJLINK-55 > Project: Maven JLink Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.1 > > > Currently we have configured the site to be generated as pre-release which > needs to be changed into non pre-release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJLINK-55) Pre Release Marker in Site must be changed
[ https://issues.apache.org/jira/browse/MJLINK-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230288#comment-17230288 ] Karl Heinz Marbaise commented on MJLINK-55: --- Done in [5e2b1272727400d81eb64a3de50557f343097319|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=5e2b1272727400d81eb64a3de50557f343097319] > Pre Release Marker in Site must be changed > -- > > Key: MJLINK-55 > URL: https://issues.apache.org/jira/browse/MJLINK-55 > Project: Maven JLink Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.1 > > > Currently we have configured the site to be generated as pre-release which > needs to be changed into non pre-release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MJLINK-55) Pre Release Marker in Site must be changed
[ https://issues.apache.org/jira/browse/MJLINK-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJLINK-55. - Resolution: Done > Pre Release Marker in Site must be changed > -- > > Key: MJLINK-55 > URL: https://issues.apache.org/jira/browse/MJLINK-55 > Project: Maven JLink Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.1 > > > Currently we have configured the site to be generated as pre-release which > needs to be changed into non pre-release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJLINK-54) Compiler source/target for site generating does not work with 8
[
https://issues.apache.org/jira/browse/MJLINK-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230287#comment-17230287
]
Hudson commented on MJLINK-54:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-jlink-plugin » master #34
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jlink-plugin/job/master/34/
> Compiler source/target for site generating does not work with 8
> ---
>
> Key: MJLINK-54
> URL: https://issues.apache.org/jira/browse/MJLINK-54
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> It has to be changed to {{1.8}} to get site generation work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MJLINK-54) Compiler source/target for site generating does not work with 8
[
https://issues.apache.org/jira/browse/MJLINK-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJLINK-54.
-
Resolution: Done
> Compiler source/target for site generating does not work with 8
> ---
>
> Key: MJLINK-54
> URL: https://issues.apache.org/jira/browse/MJLINK-54
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> It has to be changed to {{1.8}} to get site generation work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJLINK-54) Compiler source/target for site generating does not work with 8
[
https://issues.apache.org/jira/browse/MJLINK-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230284#comment-17230284
]
Karl Heinz Marbaise commented on MJLINK-54:
---
Done in
[41240bb56f8bacc839bbcd02ae9a3289f1ed5daf|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=41240bb56f8bacc839bbcd02ae9a3289f1ed5daf]
> Compiler source/target for site generating does not work with 8
> ---
>
> Key: MJLINK-54
> URL: https://issues.apache.org/jira/browse/MJLINK-54
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> It has to be changed to {{1.8}} to get site generation work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MJLINK-54) Compiler source/target for site generating does not work with 8
[
https://issues.apache.org/jira/browse/MJLINK-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MJLINK-54:
-
Assignee: Karl Heinz Marbaise
> Compiler source/target for site generating does not work with 8
> ---
>
> Key: MJLINK-54
> URL: https://issues.apache.org/jira/browse/MJLINK-54
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.1
>
>
> It has to be changed to {{1.8}} to get site generation work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (MJLINK-55) Pre Release Marker in Site must be changed
[ https://issues.apache.org/jira/browse/MJLINK-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MJLINK-55: - Assignee: Karl Heinz Marbaise > Pre Release Marker in Site must be changed > -- > > Key: MJLINK-55 > URL: https://issues.apache.org/jira/browse/MJLINK-55 > Project: Maven JLink Plugin > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.0.1 > > > Currently we have configured the site to be generated as pre-release which > needs to be changed into non pre-release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6550) Packaging 'pom' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230278#comment-17230278 ] Hudson commented on MNG-6550: - Build unstable in Jenkins: Maven » Maven TLP » maven » master #54 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/54/ > Packaging 'pom' binding plugin upgrades > --- > > Key: MNG-6550 > URL: https://issues.apache.org/jira/browse/MNG-6550 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_pom_packaging]||target > version|| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6551) Packaging 'jar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230274#comment-17230274 ] Hudson commented on MNG-6551: - Build unstable in Jenkins: Maven » Maven TLP » maven » MNG-6754 #6 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/MNG-6754/6/ > Packaging 'jar' binding plugin upgrades > --- > > Key: MNG-6551 > URL: https://issues.apache.org/jira/browse/MNG-6551 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_jar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.2.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M5| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.2.0| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MNG-6551) Packaging 'jar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230273#comment-17230273 ] Hudson commented on MNG-6551: - Build unstable in Jenkins: Maven » Maven TLP » maven » master #53 See https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/master/53/ > Packaging 'jar' binding plugin upgrades > --- > > Key: MNG-6551 > URL: https://issues.apache.org/jira/browse/MNG-6551 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_jar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.2.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M5| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.2.0| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNG-6969) mvn clean install fails for helloworld projects with java-11
[ https://issues.apache.org/jira/browse/MNG-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6969. --- Fix Version/s: (was: 3.7.0-candidate) 3.7.0 Resolution: Fixed Resolved with MNG-6551. > mvn clean install fails for helloworld projects with java-11 > > > Key: MNG-6969 > URL: https://issues.apache.org/jira/browse/MNG-6969 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.6.3 >Reporter: solo turn >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > mvn clean install fails for hello world projects with java-11 with an error > caused by using a too old compiler plugin: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) > on project deploy-at-end-one: Compilation failure: Compilation failure: > [ERROR] Source option 5 is no longer supported. Use 6 or later. > [ERROR] Target option 1.5 is no longer supported. Use 1.6 or later. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > [http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException] > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNG-6169) Packaging plugin bindings version updates
[
https://issues.apache.org/jira/browse/MNG-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6169.
---
Fix Version/s: (was: 3.7.0-candidate)
3.7.0
Resolution: Fixed
All updates delivered, Core ITs modified when they required modification.
> Packaging plugin bindings version updates
> -
>
> Key: MNG-6169
> URL: https://issues.apache.org/jira/browse/MNG-6169
> Project: Maven
> Issue Type: Improvement
> Components: core, Dependencies
>Affects Versions: 3.3.9
>Reporter: Christian Schulte
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.7.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This is an umbrella ticket to track work up packaging plugin bindings version
> upgrades. The file is
> {{maven-core/src/main/resources/META-INF/plexus/default-bindings.xml}}.
> The work is structured in subtasks per packaging type.
> This requires MNG-6562 first, to avoid users to blindly rely on these
> versions, then be impacted by a change while changing Maven version used
> without really understanding that they should lock down their plugin versions
> in their poms (eventually via parent)
> This table will go away as soon as all tickets will have been created:
> Regular plugin update to absorb changes if plugin version is not specified in
> the client POM.
> ||groupId||artifactId||[previous
> version|http://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html]||target
> version||
> |-org.apache.maven.plugins-|-maven-clean-plugin-|-2.5-|MNG-6548|
> |-org.apache.maven.plugins-|-maven-site-plugin-|-3.3-|MNG-6548|
> |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1|
> |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1|
> |org.apache.maven.plugins|maven-resources-plugin|2.6|3.2.0|
> |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.1|
> |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M5|
> |org.apache.maven.plugins|maven-jar-plugin|2.4|3.0.2|
> |org.apache.maven.plugins|maven-ejb-plugin|2.3|2.5.1 (already 3.0+)|
> |org.apache.maven.plugins|maven-plugin-plugin|3.2|3.6.0|
> |org.apache.maven.plugins|maven-war-plugin|2.2|3.3.1|
> |org.apache.maven.plugins|maven-ear-plugin|2.8|3.0.1|
> |org.apache.maven.plugins|maven-rar-plugin|2.2|2.4 (needs 3.0 release (!))|
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MNG-6550) Packaging 'pom' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6550. --- Fix Version/s: (was: 3.7.0-candidate) 3.7.0 Resolution: Fixed Fixed with [207237223af3bafaf58cb9f57fb205bd306d2470|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=207237223af3bafaf58cb9f57fb205bd306d2470] > Packaging 'pom' binding plugin upgrades > --- > > Key: MNG-6550 > URL: https://issues.apache.org/jira/browse/MNG-6550 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_pom_packaging]||target > version|| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MJLINK-55) Pre Release Marker in Site must be changed
Karl Heinz Marbaise created MJLINK-55: - Summary: Pre Release Marker in Site must be changed Key: MJLINK-55 URL: https://issues.apache.org/jira/browse/MJLINK-55 Project: Maven JLink Plugin Issue Type: Bug Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Fix For: 3.0.1 Currently we have configured the site to be generated as pre-release which needs to be changed into non pre-release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MJLINK-54) Compiler source/target for site generating does not work with 8
Karl Heinz Marbaise created MJLINK-54:
-
Summary: Compiler source/target for site generating does not work
with 8
Key: MJLINK-54
URL: https://issues.apache.org/jira/browse/MJLINK-54
Project: Maven JLink Plugin
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Fix For: 3.0.1
It has to be changed to {{1.8}} to get site generation work.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (ARCHETYPE-614) Make maven-archetype-plugin threadSafe
[
https://issues.apache.org/jira/browse/ARCHETYPE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230256#comment-17230256
]
Michael Osipov commented on ARCHETYPE-614:
--
And you guarantee them to work thread safe?
> Make maven-archetype-plugin threadSafe
> --
>
> Key: ARCHETYPE-614
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-614
> Project: Maven Archetype
> Issue Type: Bug
>Reporter: Maciej Bryński
>Priority: Major
>
> Hi,
> I'm getting following warning:
> {code:java}
> [WARNING] The following goals are not marked @threadSafe in Flink :
> Quickstart : Java:
> [WARNING]
> org.apache.maven.plugins:maven-archetype-plugin:3.2.0:integration-test
> [WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:jar
> [WARNING]
> org.apache.maven.plugins:maven-archetype-plugin:3.2.0:update-local-catalog{code}
> Could you please mark this plugin as threadSafe ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MJLINK-47) Upgrade plexus-archiver to 4.2.3
[ https://issues.apache.org/jira/browse/MJLINK-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MJLINK-47: -- Fix Version/s: (was: 3.0.0) 3.0.1 > Upgrade plexus-archiver to 4.2.3 > > > Key: MJLINK-47 > URL: https://issues.apache.org/jira/browse/MJLINK-47 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.1 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJLINK-39) Add support for choosing vm
[
https://issues.apache.org/jira/browse/MJLINK-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJLINK-39:
--
Fix Version/s: (was: 3.0.0)
3.0.1
> Add support for choosing vm
> ---
>
> Key: MJLINK-39
> URL: https://issues.apache.org/jira/browse/MJLINK-39
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Nicolai Ehemann
>Priority: Major
> Fix For: 3.0.1
>
>
> With jlink it is possible to select which vm will be bundled:
> {code:java}
> --vm={client|server|minimal|all}
> Selects the HotSpot VM in the output image. Default is all{code}
> This should also be possible with the plugin.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MNG-6551) Packaging 'jar' binding plugin upgrades
[ https://issues.apache.org/jira/browse/MNG-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MNG-6551. --- Fix Version/s: (was: 3.7.0-candidate) 3.7.0 Resolution: Fixed Fixed with [7251b8dda876a35a1f0f6f4936fccc15353e3fb7|https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=7251b8dda876a35a1f0f6f4936fccc15353e3fb7] and [fcdeba0d322b24d00ea1940fd0f6e714aea17c71|https://gitbox.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=fcdeba0d322b24d00ea1940fd0f6e714aea17c71]. > Packaging 'jar' binding plugin upgrades > --- > > Key: MNG-6551 > URL: https://issues.apache.org/jira/browse/MNG-6551 > Project: Maven > Issue Type: Sub-task > Components: core, Dependencies >Affects Versions: 3.5.0, 3.6.0 >Reporter: Michael Osipov >Assignee: Michael Osipov >Priority: Major > Fix For: 3.7.0 > > > This affects: > ||groupId||artifactId||[previous > version|https://maven.apache.org/ref/3.5.0/maven-core/default-bindings.html#Plugin_bindings_for_jar_packaging]||target > version|| > |org.apache.maven.plugins|maven-resources-plugin|2.6|3.2.0| > |org.apache.maven.plugins|maven-compiler-plugin|3.1|3.8.1| > |org.apache.maven.plugins|maven-surefire-plugin|2.12.4|3.0.0-M5| > |org.apache.maven.plugins|maven-jar-plugin|2.4|3.2.0| > |org.apache.maven.plugins|maven-install-plugin|2.4|3.0.0-M1| > |org.apache.maven.plugins|maven-deploy-plugin|2.7|3.0.0-M1| -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (MNG-7015) Resume feature is broken when MNG-6551 is merged
[
https://issues.apache.org/jira/browse/MNG-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-7015.
---
Resolution: Fixed
Fixed with
[fcdeba0d322b24d00ea1940fd0f6e714aea17c71|https://gitbox.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=fcdeba0d322b24d00ea1940fd0f6e714aea17c71].
> Resume feature is broken when MNG-6551 is merged
>
>
> Key: MNG-7015
> URL: https://issues.apache.org/jira/browse/MNG-7015
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Priority: Major
> Attachments: log-branch.txt, log-master.txt,
> martin.bootstrap.log.txt, martin.mng-5760.first-invoc.log.txt
>
>
> [~mthmulders] or [~MartinKanters], please have a look at this and tell me
> what you think:
> * Clone both Maven and Core ITs from branch {{MNG-6169/MNG-6551}}, run its
> and what MNG-5760 fail.
> I have uploaded both log files.
> For some strange reason a different set of modules is excluded in both cases.
> I don't understand why.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (MNG-7014) MNG-6551 causes some tests to fail
[
https://issues.apache.org/jira/browse/MNG-7014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-7014.
---
Resolution: Fixed
Fixed with
[fcdeba0d322b24d00ea1940fd0f6e714aea17c71|https://gitbox.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=fcdeba0d322b24d00ea1940fd0f6e714aea17c71].
> MNG-6551 causes some tests to fail
> --
>
> Key: MNG-7014
> URL: https://issues.apache.org/jira/browse/MNG-7014
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Priority: Major
>
> Clone Maven + Core ITs from branches {{MNG-6169/MNG-6551}} and run ITs.
> Result is:
> {noformat}
> [ERROR] Tests run: 857, Failures: 1, Errors: 2, Skipped: 0, Time elapsed:
> 267.86 s <<< FAILURE! - in org.apache.maven.it.IntegrationTestSuite
> [ERROR]
> testItShouldWaitForConcurrentModulesToFinish(org.apache.maven.it.MavenITmng6720FailFastTest)
> Time elapsed: 0.947 s <<< FAILURE!
> junit.framework.AssertionFailedError
> at
> org.apache.maven.it.MavenITmng6720FailFastTest.testItShouldWaitForConcurrentModulesToFinish(MavenITmng6720FailFastTest.java:67)
> [ERROR]
> testRunCustomPomWithDot(org.apache.maven.it.MavenITmng6071GetResourceWithCustomPom)
> Time elapsed: 3.006 s <<< ERROR!
> org.apache.maven.it.VerificationException:
> Exit code was non-zero: 1; command line and log =
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/apache-maven/bin/mvn
> --global-settings
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/settings.xml
> -f ./pom.xml -e --batch-mode
> -Dmaven.repo.local=/usr/home/mosipov/var/Projekte/maven-integration-testing/repo
> verify
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< mng-6071:mng-6071
> >--
> [INFO] Building my-app 1.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [WARNING] Version not locked for default bindings plugins
> [maven-resources-plugin, maven-compiler-plugin, maven-jar-plugin], you should
> define versions in pluginManagement section of your pom.xml or parent
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> mng-6071 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6071/src/main/resources
> [INFO] skip non existing resourceDirectory
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6071/src/main/resources-filtered
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ mng-6071
> ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ mng-6071 ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6071/src/test/resources
> [INFO] skip non existing resourceDirectory
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6071/src/test/resources-filtered
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @
> mng-6071 ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6071/target/test-classes
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @ mng-6071 ---
> [INFO] Surefire report directory:
> /var/mosipov/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6071/target/surefire-reports
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [ERROR] java.lang.ClassNotFoundException:
> org.apache.maven.surefire.junit4.JUnit4Provider
> [INFO]
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.801 s
> [INFO] Finished at: 2020-11-10T14:33:17+01:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:3.0.0-M5:test (default-test)
>
[GitHub] [maven-jlink-plugin] sormuras closed pull request #12: [MJLINK-9] force NPE on empty sources.
sormuras closed pull request #12: URL: https://github.com/apache/maven-jlink-plugin/pull/12 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] sormuras commented on pull request #12: [MJLINK-9] force NPE on empty sources.
sormuras commented on pull request #12: URL: https://github.com/apache/maven-jlink-plugin/pull/12#issuecomment-725676743 Superseded by https://github.com/apache/maven-jlink-plugin/commit/a330205dbe1d95b475fceeea05d3a125bbf1d315 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MJLINK-9) Add support for multi module projects
[
https://issues.apache.org/jira/browse/MJLINK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230238#comment-17230238
]
Hudson commented on MJLINK-9:
-
Build failed in Jenkins: Maven » Maven TLP » maven-jlink-plugin » master #25
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-jlink-plugin/job/master/25/
> Add support for multi module projects
> -
>
> Key: MJLINK-9
> URL: https://issues.apache.org/jira/browse/MJLINK-9
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Vladimir Tsanev
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: intern, multimodule
> Fix For: 3.0.0
>
>
> I would like to have a multi module project something like
> {code:java}
> parent
> lib
> pom.xml
> app
> pom.xml
> dist
> pom.xml{code}
> where app is my application module that depends on a lib module and dist is a
> jlink module that depends on app.
>
> Currently I see a NPE because it cannot find app's jar. Seems like jars from
> reactor are not resolved
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
>
[jira] [Updated] (MJLINK-9) Add support for multi module projects
[
https://issues.apache.org/jira/browse/MJLINK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJLINK-9:
-
Fix Version/s: (was: 3.0.0-alpha-1)
3.0.0
> Add support for multi module projects
> -
>
> Key: MJLINK-9
> URL: https://issues.apache.org/jira/browse/MJLINK-9
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Vladimir Tsanev
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: intern, multimodule
> Fix For: 3.0.0
>
>
> I would like to have a multi module project something like
> {code:java}
> parent
> lib
> pom.xml
> app
> pom.xml
> dist
> pom.xml{code}
> where app is my application module that depends on a lib module and dist is a
> jlink module that depends on app.
>
> Currently I see a NPE because it cannot find app's jar. Seems like jars from
> reactor are not resolved
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain
[jira] [Closed] (MJLINK-9) Add support for multi module projects
[
https://issues.apache.org/jira/browse/MJLINK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MJLINK-9.
Resolution: Done
> Add support for multi module projects
> -
>
> Key: MJLINK-9
> URL: https://issues.apache.org/jira/browse/MJLINK-9
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Vladimir Tsanev
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: intern, multimodule
> Fix For: 3.0.0-alpha-1
>
>
> I would like to have a multi module project something like
> {code:java}
> parent
> lib
> pom.xml
> app
> pom.xml
> dist
> pom.xml{code}
> where app is my application module that depends on a lib module and dist is a
> jlink module that depends on app.
>
> Currently I see a NPE because it cannot find app's jar. Seems like jars from
> reactor are not resolved
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at
[jira] [Commented] (MJLINK-9) Add support for multi module projects
[
https://issues.apache.org/jira/browse/MJLINK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230232#comment-17230232
]
Karl Heinz Marbaise commented on MJLINK-9:
--
Done in
[a330205dbe1d95b475fceeea05d3a125bbf1d315|https://gitbox.apache.org/repos/asf?p=maven-jlink-plugin.git;a=commitdiff;h=a330205dbe1d95b475fceeea05d3a125bbf1d315]
> Add support for multi module projects
> -
>
> Key: MJLINK-9
> URL: https://issues.apache.org/jira/browse/MJLINK-9
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Vladimir Tsanev
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: intern, multimodule
> Fix For: 3.0.0-alpha-1
>
>
> I would like to have a multi module project something like
> {code:java}
> parent
> lib
> pom.xml
> app
> pom.xml
> dist
> pom.xml{code}
> where app is my application module that depends on a lib module and dist is a
> jlink module that depends on app.
>
> Currently I see a NPE because it cannot find app's jar. Seems like jars from
> reactor are not resolved
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at
[jira] [Updated] (MNG-7015) Resume feature is broken when MNG-6551 is merged
[
https://issues.apache.org/jira/browse/MNG-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7015:
Component/s: Integration Tests
> Resume feature is broken when MNG-6551 is merged
>
>
> Key: MNG-7015
> URL: https://issues.apache.org/jira/browse/MNG-7015
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Priority: Major
> Attachments: log-branch.txt, log-master.txt,
> martin.bootstrap.log.txt, martin.mng-5760.first-invoc.log.txt
>
>
> [~mthmulders] or [~MartinKanters], please have a look at this and tell me
> what you think:
> * Clone both Maven and Core ITs from branch {{MNG-6169/MNG-6551}}, run its
> and what MNG-5760 fail.
> I have uploaded both log files.
> For some strange reason a different set of modules is excluded in both cases.
> I don't understand why.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MJLINK-47) Upgrade plexus-archiver to 4.2.3
[ https://issues.apache.org/jira/browse/MJLINK-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MJLINK-47: -- Summary: Upgrade plexus-archiver to 4.2.3 (was: Upgrade plexus-archiver to 4.2.2) > Upgrade plexus-archiver to 4.2.3 > > > Key: MJLINK-47 > URL: https://issues.apache.org/jira/browse/MJLINK-47 > Project: Maven JLink Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MJLINK-9) Add support for multi module projects
[
https://issues.apache.org/jira/browse/MJLINK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJLINK-9:
-
Fix Version/s: 3.0.0-alpha-1
> Add support for multi module projects
> -
>
> Key: MJLINK-9
> URL: https://issues.apache.org/jira/browse/MJLINK-9
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Vladimir Tsanev
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: intern, multimodule
> Fix For: 3.0.0-alpha-1
>
>
> I would like to have a multi module project something like
> {code:java}
> parent
> lib
> pom.xml
> app
> pom.xml
> dist
> pom.xml{code}
> where app is my application module that depends on a lib module and dist is a
> jlink module that depends on app.
>
> Currently I see a NPE because it cannot find app's jar. Seems like jars from
> reactor are not resolved
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at
[jira] [Assigned] (MJLINK-9) Add support for multi module projects
[
https://issues.apache.org/jira/browse/MJLINK-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MJLINK-9:
Assignee: Karl Heinz Marbaise
> Add support for multi module projects
> -
>
> Key: MJLINK-9
> URL: https://issues.apache.org/jira/browse/MJLINK-9
> Project: Maven JLink Plugin
> Issue Type: New Feature
>Affects Versions: 3.0.0-alpha-1
>Reporter: Vladimir Tsanev
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Labels: intern, multimodule
>
> I would like to have a multi module project something like
> {code:java}
> parent
> lib
> pom.xml
> app
> pom.xml
> dist
> pom.xml{code}
> where app is my application module that depends on a lib module and dist is a
> jlink module that depends on app.
>
> Currently I see a NPE because it cannot find app's jar. Seems like jars from
> reactor are not resolved
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project dist: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main
[GitHub] [maven-integration-testing] michael-o commented on pull request #77: Mng 6754 version timestamp in multimodule build
michael-o commented on pull request #77: URL: https://github.com/apache/maven-integration-testing/pull/77#issuecomment-725621332 @mthmulders I have completely picked up your work and put even more validation on top of it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o closed pull request #76: [MNG-6754] Verify equal version timestamp in multi-module projects
michael-o closed pull request #76: URL: https://github.com/apache/maven-integration-testing/pull/76 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on pull request #76: [MNG-6754] Verify equal version timestamp in multi-module projects
michael-o commented on pull request #76: URL: https://github.com/apache/maven-integration-testing/pull/76#issuecomment-725619358 Superseded by #77. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o opened a new pull request #77: Mng 6754 version timestamp in multimodule build
michael-o opened a new pull request #77: URL: https://github.com/apache/maven-integration-testing/pull/77 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] sormuras edited a comment on pull request #12: [MJLINK-9] force NPE on empty sources.
sormuras edited a comment on pull request #12: URL: https://github.com/apache/maven-jlink-plugin/pull/12#issuecomment-725612414 Thanks for the PR, Ben. I converted it to a draft -- needs a fix for the NPE to be merged. 嵐 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] sormuras edited a comment on pull request #12: [MJLINK-9] force NPE on empty sources.
sormuras edited a comment on pull request #12: URL: https://github.com/apache/maven-jlink-plugin/pull/12#issuecomment-725612414 Thanks for the PR, Ben. I converted it to a draft -- needs a fix for the NPE to be merged. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-jlink-plugin] sormuras commented on pull request #12: [MJLINK-9] force NPE on empty sources.
sormuras commented on pull request #12: URL: https://github.com/apache/maven-jlink-plugin/pull/12#issuecomment-725612414 Thanks for PR, Ben. I converted it to a draft -- needs a fix for the NPE to be merged. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on pull request #76: [MNG-6754] Verify equal version timestamp in multi-module projects
michael-o commented on pull request #76: URL: https://github.com/apache/maven-integration-testing/pull/76#issuecomment-725518910 I gave it more thought and think this is incomplete. The purpose of this change is not only to align last updated field, but also to make snapshot timestamp consistent throughout the reactor. This is also the narrative of the JIRA issue. This one is good for part one. I will add part two to it. Stay tuned. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-6890) MavenITmng5669ReadPomsOnce is unreliable
[
https://issues.apache.org/jira/browse/MNG-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230024#comment-17230024
]
Hudson commented on MNG-6890:
-
Build failed in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/14/
> MavenITmng5669ReadPomsOnce is unreliable
>
>
> Key: MNG-6890
> URL: https://issues.apache.org/jira/browse/MNG-6890
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Affects Versions: 3.7.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The unreliability comes from the fact that no plugin has been fixed (version)
> in the parent POM of the test project. As soon as you update Maven from
> MNG-6169 the test starts to fail that lengths do not match. So this test
> relies on implicit declaration of plugin versions.
> Reproducer:
> 1. Build Maven from MNG-6169/MNG-6551
> 2. Run ITs from MNG-6551
> 3. See it fail
> One needs to remove {{-q}}, scan for plugins and fix their versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6118) Add option to execute goals on a specific module while building a multimodule project
[
https://issues.apache.org/jira/browse/MNG-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230022#comment-17230022
]
Hudson commented on MNG-6118:
-
Build failed in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/14/
> Add option to execute goals on a specific module while building a multimodule
> project
> -
>
> Key: MNG-6118
> URL: https://issues.apache.org/jira/browse/MNG-6118
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Plugins and Lifecycle
>Reporter: Robert Scholte
>Assignee: Martin Kanters
>Priority: Major
> Fix For: 3.7.0
>
>
> Suppose we have a multimodule which results in a war. In the end we want to
> run this war in a container like jetty. Up until now the {{jetty:run}} is
> executed on every module, which doesn't make sense for the other modules.
> This is just one of several examples where you want to control on which
> module to execute a specific goal. In case of wars, the plugin could check
> for the packaging type, but in case of jars this won't work.
> There should be a generic solution to mark goals for a specific module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MNG-6981) Add --recursive option
[
https://issues.apache.org/jira/browse/MNG-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17230023#comment-17230023
]
Hudson commented on MNG-6981:
-
Build failed in Jenkins: Maven » Maven TLP » maven-studies » maven-metrics #14
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-studies/job/maven-metrics/14/
> Add --recursive option
> --
>
> Key: MNG-6981
> URL: https://issues.apache.org/jira/browse/MNG-6981
> Project: Maven
> Issue Type: New Feature
> Components: Command Line
>Affects Versions: 3.6.3
>Reporter: Knut Wannheden
>Assignee: Martin Kanters
>Priority: Minor
> Fix For: 3.7.0
>
>
> Since there is already a {{\--non-recursive}} option a new {{\--recursive}}
> option might be confusing, but let me explain my use case. I often use the
> {{-pl}} option and in a multi-module Maven project with more than just two
> "levels", I would like to be able to build a project (or set of projects)
> including all child-modules. This is, AFAIK, currently not possible and what
> I would like to use the new {{\--recursive}} (or similar) option for.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARCHETYPE-614) Make maven-archetype-plugin threadSafe
[
https://issues.apache.org/jira/browse/ARCHETYPE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maciej Bryński updated ARCHETYPE-614:
-
Description:
Hi,
I'm getting following warning:
{code:java}
[WARNING] The following goals are not marked @threadSafe in Flink : Quickstart
: Java:
[WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:integration-test
[WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:jar
[WARNING]
org.apache.maven.plugins:maven-archetype-plugin:3.2.0:update-local-catalog{code}
Could you please mark this plugin as threadSafe ?
was:
Hi,
I'm getting following warning:
```
[WARNING] The following goals are not marked @threadSafe in Flink : Quickstart
: Java:
[WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:integration-test
[WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:jar
[WARNING]
org.apache.maven.plugins:maven-archetype-plugin:3.2.0:update-local-catalog
```
Could you please mark this plugin as threadSafe ?
> Make maven-archetype-plugin threadSafe
> --
>
> Key: ARCHETYPE-614
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-614
> Project: Maven Archetype
> Issue Type: Bug
>Reporter: Maciej Bryński
>Priority: Major
>
> Hi,
> I'm getting following warning:
> {code:java}
> [WARNING] The following goals are not marked @threadSafe in Flink :
> Quickstart : Java:
> [WARNING]
> org.apache.maven.plugins:maven-archetype-plugin:3.2.0:integration-test
> [WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:jar
> [WARNING]
> org.apache.maven.plugins:maven-archetype-plugin:3.2.0:update-local-catalog{code}
> Could you please mark this plugin as threadSafe ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARCHETYPE-614) Make maven-archetype-plugin threadSafe
Maciej Bryński created ARCHETYPE-614: Summary: Make maven-archetype-plugin threadSafe Key: ARCHETYPE-614 URL: https://issues.apache.org/jira/browse/ARCHETYPE-614 Project: Maven Archetype Issue Type: Bug Reporter: Maciej Bryński Hi, I'm getting following warning: ``` [WARNING] The following goals are not marked @threadSafe in Flink : Quickstart : Java: [WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:integration-test [WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:jar [WARNING] org.apache.maven.plugins:maven-archetype-plugin:3.2.0:update-local-catalog ``` Could you please mark this plugin as threadSafe ? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNG-7016) Some ITs still require outbound access
Michael Osipov created MNG-7016:
---
Summary: Some ITs still require outbound access
Key: MNG-7016
URL: https://issues.apache.org/jira/browse/MNG-7016
Project: Maven
Issue Type: Bug
Components: Integration Tests
Reporter: Michael Osipov
We require our integration tests to rune completely offline or register deps in
bootstrap to have them locally. To circumvent any download {{central}} is
rerouted to {target/null}}. Some projects still do download:
{noformat}
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.4/maven-enforcer-plugin-1.4.pom
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/enforcer/enforcer/1.4/enforcer-1.4.pom
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.4/maven-enforcer-plugin-1.4.jar
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/enforcer/enforcer-api/1.4/enforcer-api-1.4.pom
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/enforcer/enforcer-rules/1.4/enforcer-rules-1.4.pom
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/enforcer/enforcer-api/1.4/enforcer-api-1.4.jar
./core-it-suite/target/test-classes/mng-5840-relative-path-reactor-matching/child/log.txt:[INFO]
Downloading from central:
https://repo1.maven.org/maven2/org/apache/maven/enforcer/enforcer-rules/1.4/enforcer-rules-1.4.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.3/maven-surefire-plugin-2.3.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/surefire/surefire/2.3/surefire-2.3.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.3/maven-surefire-plugin-2.3.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream/1.2.2/xstream-1.2.2.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream-parent/1.2.2/xstream-parent-1.2.2.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/xpp3/xpp3_min/1.1.3.4.O/xpp3_min-1.1.3.4.O.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central: https://repo1.maven.org/maven2/jmock/jmock/1.2.0/jmock-1.2.0.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream/1.2.2/xstream-1.2.2.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/xpp3/xpp3_min/1.1.3.4.O/xpp3_min-1.1.3.4.O.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central: https://repo1.maven.org/maven2/jmock/jmock/1.2.0/jmock-1.2.0.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-booter/2.3/surefire-booter-2.3.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-api/2.3/surefire-api-2.3.pom
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-booter/2.3/surefire-booter-2.3.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/apache/maven/surefire/surefire-api/2.3/surefire-api-2.3.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
https://repo1.maven.org/maven2/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar
./core-it-suite/target/test-classes/mng-3259/log.txt:[INFO] Downloading from
central:
[GitHub] [maven-integration-testing] michael-o commented on pull request #76: [MNG-6754] Verify equal version timestamp in multi-module projects
michael-o commented on pull request #76: URL: https://github.com/apache/maven-integration-testing/pull/76#issuecomment-725449685 I have pushed an updated branch for gitbox based on your work. Will run a few more tests. If everything is fine, this is going to be merged. Thank you! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-integration-testing] michael-o commented on pull request #76: [MNG-6754] Verify equal version timestamp in multi-module projects
michael-o commented on pull request #76: URL: https://github.com/apache/maven-integration-testing/pull/76#issuecomment-725446401 I am going through performing some improvements. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MPMD-310) Unable to find referenced rule AvoidReassigningCatchVariables
[
https://issues.apache.org/jira/browse/MPMD-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229984#comment-17229984
]
Jacek Musial commented on MPMD-310:
---
I am sorry [~pzygielo] but I don't have option to do it.
> Unable to find referenced rule AvoidReassigningCatchVariables
> -
>
> Key: MPMD-310
> URL: https://issues.apache.org/jira/browse/MPMD-310
> Project: Maven PMD Plugin
> Issue Type: Bug
> Components: PMD
>Affects Versions: 3.13.0
> Environment: macOS Catalina 10.15.7, OpenJDK 11, Maven 3.6.3
>Reporter: Jacek Musial
>Priority: Major
> Attachments: stacktrace-pmd.txt
>
>
> I am getting following error when running
> {code:java}
> mvn clean install{code}
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-pmd-plugin:3.13.0:pmd (default-cli) on project
> pmd-issue: Execution default-cli of goal
> org.apache.maven.plugins:maven-pmd-plugin:3.13.0:pmd failed: Unable to find
> referenced rule AvoidReassigningCatchVariables; perhaps the rule name is
> mispelled? -> [Help 1]{code}
> The rule I want to add
> ([https://pmd.github.io/latest/pmd_rules_java_bestpractices.html#avoidreassigningcatchvariables)]
> was added in PMD 6.27.0 and Maven PMD Plugin is using 6.29.0 version of PMD.
> For this bug I have created very simple maven project with empty main java
> class and one ruleset "AvoidReassigningCatchVariables". Code is very simple.
> If you would prefer source code files as attachment, please let me know.
> src/main/java/com/example/*Main.java*
> {code:java}
> package com.example;
> public class Main { public static void main(String[] args) { } } {code}
> src/pmd/*checks.xml*
> {code:java}
>
> http://pmd.sourceforge.net/ruleset/2.0.0
> http://pmd.sourceforge.net/ruleset_2_0_0.xsd;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xmlns="http://pmd.sourceforge.net/ruleset/2.0.0; name="All Java Rules">
> PMD rules for Currency Cloud
> .*Test\.java
>
>
> {code}
>
> src/*pom.xml*
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> com.example
> pmd-issue
> 1.0-SNAPSHOT
>
> 11
> 11.
> UTF-8
> 11
>
>
>
>
>
> org.apache.maven.plugins
> maven-pmd-plugin
> 3.13.0
>
> ${project.build.sourceEncoding}
> 100
> ${version.java}
> true
> false
>
> src/pmd/checks.xml
>
>
>
>
> check
>
> validate
>
>
>
>
> src/main/pmd
>{code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-ear-plugin] mabrarov commented on pull request #24: [MEAR-153] skinnyModules option
mabrarov commented on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725395427 @hboutemy, > Please update your PR with that 3.2.0-SNAPSHOT, I'll do the Jira part PR updated as requested. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7010) omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the problem.
[ https://issues.apache.org/jira/browse/MNG-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229935#comment-17229935 ] Michael Osipov commented on MNG-7010: - [~elharo], let's just remove it. > omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the > problem. > - > > Key: MNG-7010 > URL: https://issues.apache.org/jira/browse/MNG-7010 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Got this message a bunch today: > > $ mvn verify > The JAVA_HOME environment variable is not defined correctly > This environment variable is needed to run this program > NB: JAVA_HOME should point to a JDK not a JRE > > fair enough. My JAVA_HOME is broken, for reasons. However the problem is > **not** that it points to a JDK instead of a JRE. Maven should omit "NB: > JAVA_HOME should point to a JDK not a JRE" except when that is the problem. > Also, I have no idea what NB means here. Nota bene perhaps? > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-ear-plugin] mabrarov commented on pull request #24: [MEAR-153] skinnyModules option
mabrarov commented on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725362303 @hboutemy > then also to start a release Please take a look at pull request #22 before that. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (MEAR-216) Unable to include dependencies of type test-jar
[
https://issues.apache.org/jira/browse/MEAR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MEAR-216:
---
Fix Version/s: 3.2.0
> Unable to include dependencies of type test-jar
> ---
>
> Key: MEAR-216
> URL: https://issues.apache.org/jira/browse/MEAR-216
> Project: Maven Ear Plugin
> Issue Type: Improvement
>Affects Versions: 2.10
>Reporter: Maxim Frolov
>Priority: Major
> Fix For: waiting-for-feedback, 3.2.0
>
> Attachments: test-jar-in-ear-2.zip, test-jar-in-ear.zip
>
>
> Please implement support for artifacts of type *test-jar*.
> One of the use cases would be to build a test EAR as a mix of production and
> test JARs where the test JARs are used to set up the test data used to test
> the production code.
> Currently including one or more dependencies of type test-jar causes
> *LifecycleExecutionException*:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
> (default-generate-application-xml) on project suite-systemtests-common-ear:
> Failed to initialize ear modules: Unknown artifact type[test-jar] for
> artifact_id -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-ear-plugin:2.10:generate-application-xml
> (default-generate-application-xml) on project suite-systemtests-common-ear:
> Failed to initialize ear modules
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to
> initialize ear modules
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:260)
> at
> org.apache.maven.plugin.ear.GenerateApplicationXmlMojo.execute(GenerateApplicationXmlMojo.java:162)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.plugin.ear.UnknownArtifactTypeException: Unknown
> artifact type[test-jar] for common-domain-impl
> at
> org.apache.maven.plugin.ear.EarModuleFactory.newEarModule(EarModuleFactory.java:88)
> at
> org.apache.maven.plugin.ear.AbstractEarMojo.execute(AbstractEarMojo.java:250)
> ... 22 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-ear-plugin] hboutemy commented on pull request #24: [MEAR-153] skinnyModules option
hboutemy commented on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725359072 great: yes, questioning on us...@maven.apache.org seems a good option defining the next version happens when working on an issue where it becomes clear that we're beyond bugfix: yours is like this Please update your PR with that 3.2.0-SNAPSHOT, I'll do the Jira part I'm waiting for your feedback to merge this PR, then also to start a release Thanks a lot, it's great to get such contribution This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] mabrarov edited a comment on pull request #24: [MEAR-153] skinnyModules option
mabrarov edited a comment on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725337460 Hi @hboutemy, > the new feature is triggered by a specific parameter: then can't break existing users configuration? Yes. That's one of my intentions - changes should not impact existing projects and the new behavior should work only for users who want / need and explicitly requested it through configuration. > shouldn't we update the version to 3.2.0? I believe version needs to be changed (3.2.0 looks like a good candidate), but I don't know how it is performed in this project. I thought version change is performed by maintainers when decision on new release is made. > I'm not a EAR user either I am still an EAR user due to my company legacy tasks which will keep using EARs for at least next 10 years :( Just curious who else can help. d...@maven.apache.org keeps silent. Maybe I need to try us...@maven.apache.org ? Waiting for the results of Roland Asmann's [testing](https://issues.apache.org/jira/browse/MEAR-153?focusedCommentId=17218596=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17218596), but I doubt we will get them soon. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] mabrarov edited a comment on pull request #24: [MEAR-153] skinnyModules option
mabrarov edited a comment on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725337460 Hi @hboutemy, > the new feature is triggered by a specific parameter: then can't break existing users configuration? Yes. That's one of my intentions - changes should not impact existing projects and the new behavior should work only for users who want / need and explicitly requested it through configuration. > shouldn't we update the version to 3.2.0? I believe version needs to be changed (3.2.0 looks like a good candidate), but I don't know how it is performed in this project. I thought version change is performed by maintainers when decision on new release is made. > I'm not a EAR user either I am still an EAR user due to my company legacy tasks which will keep using EARs for at least next 10 years :( Just curious who else can help. d...@maven.apache.org keeps silent. Maybe I need to try us...@maven.apache.org ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] mabrarov edited a comment on pull request #24: [MEAR-153] skinnyModules option
mabrarov edited a comment on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725337460 Hi @hboutemy, > the new feature is triggered by a specific parameter: then can't break existing users configuration? Yes. That's one of my intentions - changes should not impact existing projects and the new behavior should work only for users who want / need and explicitly requested it through configuration. > shouldn't we update the version to 3.2.0? I believe version needs to be changed (3.2.0 looks like a good candidate), but I don't know how it is performed in this project. I thought version change is performed by maintainers when decision on new release is made. > I'm not a EAR user either I am :( Just curious who else can help. d...@maven.apache.org keeps silent. Maybe I need to try us...@maven.apache.org ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] mabrarov edited a comment on pull request #24: [MEAR-153] skinnyModules option
mabrarov edited a comment on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725337460 Hi @hboutemy, > the new feature is triggered by a specific parameter: then can't break existing users configuration? Yes. That's one of my intentions - changes should not impact existing projects and the new behavior should work only for users who explicitly want / need it. > shouldn't we update the version to 3.2.0? I believe version needs to be changed (3.2.0 looks like a good candidate), but I don't know how it is performed in this project. I thought version change is performed by maintainers when decision on new release is made. > I'm not a EAR user either I am :( Just curious who else can help. d...@maven.apache.org keeps silent. Maybe I need to try us...@maven.apache.org ? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] mabrarov commented on pull request #24: [MEAR-153] skinnyModules option
mabrarov commented on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725337460 Hi @hboutemy, > the new feature is triggered by a specific parameter: then can't break existing users configuration? Yes. That's one of my intentions - changes should not impact existing projects and the new behavior should work only for users who explicitly want / need it. > shouldn't we update the version to 3.2.0? I believe version needs to be changed (3.2.0 looks like a good candidate), but I don't know how it is performed in this project. I thought version change is performed by maintainers when decision on new release is made. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] hboutemy edited a comment on pull request #24: [MEAR-153] skinnyModules option
hboutemy edited a comment on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725328892 sorry, I have been away these times... FYI, I'm not a EAR user either, then I don't have strong opinion on use cases, sorry. But I want to help people doing hard and good work like this one (unit tests, integration tests, documentation). I have 2 questions to evaluate before merging: 1. IIUC, the new feature is triggered by a specific parameter: then can't break existing users configuration? 2. shouldn't we update the version to 3.2.0? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-ear-plugin] hboutemy commented on pull request #24: [MEAR-153] skinnyModules option
hboutemy commented on pull request #24: URL: https://github.com/apache/maven-ear-plugin/pull/24#issuecomment-725328892 sorry, I have been away these times... FYI, I'm not a EAR user either, then I don't have strong opinion on use cases, sorry. But I want to help people doing hard and good work like this one. I have 2 questions to evaluate before merging: 1. IIUC, the new feature is triggered by a specific parameter: then can't break existing users configuration? 2. shouldn't we update the version to 3.2.0? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (MNG-7010) omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the problem.
[ https://issues.apache.org/jira/browse/MNG-7010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17229821#comment-17229821 ] Mark Thomas commented on MNG-7010: -- Yes, "NB" is an abbreviation of "Nota bene". The note was added in the context of Tomcat requiring a JDK at the time and users often using a JRE. YMMV. > omit "NB: JAVA_HOME should point to a JDK not a JRE" except when that is the > problem. > - > > Key: MNG-7010 > URL: https://issues.apache.org/jira/browse/MNG-7010 > Project: Maven > Issue Type: Improvement >Reporter: Elliotte Rusty Harold >Priority: Minor > > Got this message a bunch today: > > $ mvn verify > The JAVA_HOME environment variable is not defined correctly > This environment variable is needed to run this program > NB: JAVA_HOME should point to a JDK not a JRE > > fair enough. My JAVA_HOME is broken, for reasons. However the problem is > **not** that it points to a JDK instead of a JRE. Maven should omit "NB: > JAVA_HOME should point to a JDK not a JRE" except when that is the problem. > Also, I have no idea what NB means here. Nota bene perhaps? > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
