[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&focusedCommentId=16239416#comment-16239416 ] Hervé Boutemy commented on MNG-6118: bq. solution to mark goals for a specific module IM

[jira] [Updated] (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:all-tabpanel ] Hervé Boutemy updated MNG-6118: --- Description: Suppose we have a multimodule which results in a war. In the end we want to run this war i

[jira] [Commented] (MSHADE-265) correct merging of module-info in shades

[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239301#comment-16239301 ] Robert Scholte commented on MSHADE-265: --- Let's define the usecases first (maybe with

[jira] [Commented] (MSHADE-265) correct merging of module-info in shades

[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239270#comment-16239270 ] Romain Manni-Bucau commented on MSHADE-265: --- I know but it literally means "dont

[jira] [Commented] (MSHADE-264) handle module-info merge in shades for java 9 support

[ https://issues.apache.org/jira/browse/MSHADE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239267#comment-16239267 ] Robert Scholte commented on MSHADE-264: --- duplicate of MSHADE-265? > handle module-i

[jira] [Commented] (MSHADE-265) correct merging of module-info in shades

[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239265#comment-16239265 ] Robert Scholte commented on MSHADE-265: --- We had this discussion with a couple of Mav

[jira] [Commented] (MNG-2971) Variables are not replaced into installed pom file

[ https://issues.apache.org/jira/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239224#comment-16239224 ] Peng Cheng commented on MNG-2971: - Why I'm still observing this in maven 3.5.0? I thought it

[jira] [Updated] (MSHADE-265) correct merging of module-info in shades

[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated MSHADE-265: -- Description: Should work by merging of the encountered module info jut also automatic mo

[jira] [Created] (MSHADE-265) correct merging of module-info in shades

Romain Manni-Bucau created MSHADE-265: - Summary: correct merging of module-info in shades Key: MSHADE-265 URL: https://issues.apache.org/jira/browse/MSHADE-265 Project: Maven Shade Plugin

[jira] [Created] (MSHADE-264) handle module-info merge in shades for java 9 support

Romain Manni-Bucau created MSHADE-264: - Summary: handle module-info merge in shades for java 9 support Key: MSHADE-264 URL: https://issues.apache.org/jira/browse/MSHADE-264 Project: Maven Shade Plu

[jira] [Commented] (MSHADE-234) support java 9 modules (jigsaw)

[ https://issues.apache.org/jira/browse/MSHADE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239140#comment-16239140 ] Romain Manni-Bucau commented on MSHADE-234: --- up? > support java 9 modules (jigs

[jira] [Commented] (MJLINK-4) NPE on execution

[ https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239058#comment-16239058 ] Hudson commented on MJLINK-4: - SUCCESS: Integrated in Jenkins build maven-plugins #9184 (See [h

[jira] [Commented] (MENFORCER-281) RequirePluginVersions broken with "CI Friendly versions"

[ https://issues.apache.org/jira/browse/MENFORCER-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239045#comment-16239045 ] Simon Tunnat commented on MENFORCER-281: Thank you for your e-mail. I will be

[jira] [Commented] (MENFORCER-281) RequirePluginVersions broken with "CI Friendly versions"

[ https://issues.apache.org/jira/browse/MENFORCER-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239042#comment-16239042 ] ASF GitHub Bot commented on MENFORCER-281: -- jtnord opened a new pull request #

[jira] [Commented] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps

[ https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239043#comment-16239043 ] ASF GitHub Bot commented on MENFORCER-276: -- oleg-nenashev opened a new pull re

[jira] [Commented] (DOXIATOOLS-58) switch to Git

[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239012#comment-16239012 ] Hudson commented on DOXIATOOLS-58: -- SUCCESS: Integrated in Jenkins build doxia-all #35

[jira] [Closed] (DOXIATOOLS-58) switch to Git

[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIATOOLS-58. --- Resolution: Fixed > switch to Git > - > > Key: DOXIATOOLS-58 >

[jira] [Commented] (DOXIATOOLS-58) switch to Git

[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238993#comment-16238993 ] Hudson commented on DOXIATOOLS-58: -- SUCCESS: Integrated in Jenkins build doxia-all #35

[jira] [Commented] (DOXIATOOLS-58) switch to Git

[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238988#comment-16238988 ] Hudson commented on DOXIATOOLS-58: -- SUCCESS: Integrated in Jenkins build doxia-all #35

[jira] [Created] (DOXIATOOLS-58) switch to Git

Hervé Boutemy created DOXIATOOLS-58: --- Summary: switch to Git Key: DOXIATOOLS-58 URL: https://issues.apache.org/jira/browse/DOXIATOOLS-58 Project: Maven Doxia Tools Issue Type: Task

[jira] [Commented] (MSKINS-136) switch to Git

[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238964#comment-16238964 ] Hudson commented on MSKINS-136: --- SUCCESS: Integrated in Jenkins build maven-fluido-skin #2 (

[jira] [Closed] (MSKINS-136) switch to Git

[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MSKINS-136. Resolution: Fixed Fix Version/s: default-1.3 > switch to Git > - > >

[jira] [Commented] (MSKINS-136) switch to Git

[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238963#comment-16238963 ] Hudson commented on MSKINS-136: --- SUCCESS: Integrated in Jenkins build maven-default-skin #3

[jira] [Updated] (MSKINS-136) switch to Git

[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSKINS-136: - Description: https://gitbox.apache.org/repos/asf/maven-default-skin.git https://gitbox.apache.org/

[jira] [Commented] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules

[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238922#comment-16238922 ] Hudson commented on MJAVADOC-494: - SUCCESS: Integrated in Jenkins build maven-plugins #9

[jira] [Closed] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules

[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MJAVADOC-494. --- Resolution: Fixed Fixed in [r1814274|http://svn.apache.org/viewvc?rev=1814274&view=rev] This

[jira] [Commented] (MSKINS-136) switch to Git

[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238910#comment-16238910 ] Hudson commented on MSKINS-136: --- FAILURE: Integrated in Jenkins build maven-skins #278 (See

[jira] [Created] (MSKINS-136) switch to Git

Hervé Boutemy created MSKINS-136: Summary: switch to Git Key: MSKINS-136 URL: https://issues.apache.org/jira/browse/MSKINS-136 Project: Maven Skins Issue Type: Task Components: Defa

[jira] [Updated] (MPOM-171) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-171: --- Description: https://gitbox.apache.org/repos/asf/maven-parent.git CI: https://builds.apache.org/view/M-

[jira] [Updated] (MPOM-171) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-171: --- Environment: (was: https://gitbox.apache.org/repos/asf/maven-parent.git CI: https://builds.apache.or

[jira] [Closed] (MPOM-171) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-171. -- Resolution: Fixed > migrate to Git > -- > > Key: MPOM-171 > UR

[jira] [Commented] (MPOM-171) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238885#comment-16238885 ] Hudson commented on MPOM-171: - SUCCESS: Integrated in Jenkins build maven-parent #2098 (See [ht

[jira] [Commented] (MPOM-170) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238883#comment-16238883 ] Hudson commented on MPOM-170: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #172 (See [h

[jira] [Commented] (MPOM-171) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238880#comment-16238880 ] Hudson commented on MPOM-171: - FAILURE: Integrated in Jenkins build maven-parent #2095 (See [ht

[jira] [Created] (MPOM-171) migrate to Git

Hervé Boutemy created MPOM-171: -- Summary: migrate to Git Key: MPOM-171 URL: https://issues.apache.org/jira/browse/MPOM-171 Project: Maven POMs Issue Type: Task Components: doxia-tools,

[jira] [Closed] (MPOM-170) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-170. -- Resolution: Fixed Assignee: Hervé Boutemy > migrate to Git > -- > > Key:

[jira] [Commented] (MPOM-170) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238873#comment-16238873 ] Hudson commented on MPOM-170: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #170 (See [h

[jira] [Commented] (MPOM-170) migrate to Git

[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238861#comment-16238861 ] Hudson commented on MPOM-170: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #167 (See [h

[jira] [Created] (MPOM-170) migrate to Git

Hervé Boutemy created MPOM-170: -- Summary: migrate to Git Key: MPOM-170 URL: https://issues.apache.org/jira/browse/MPOM-170 Project: Maven POMs Issue Type: Task Components: asf Affe

[jira] [Created] (MNG-6300) Multi module release creates empty directories in war file instead of jars

Andreas Kurth created MNG-6300: -- Summary: Multi module release creates empty directories in war file instead of jars Key: MNG-6300 URL: https://issues.apache.org/jira/browse/MNG-6300 Project: Maven