[jira] [Closed] (MASSEMBLY-837) Revise features page on site

[ https://issues.apache.org/jira/browse/MASSEMBLY-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MASSEMBLY-837. Resolution: Fixed page removed > Revise features page on site >

[jira] [Commented] (MASSEMBLY-756) escapeString doesn't work correctly for the 2nd filtering

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

[jira] [Closed] (MASSEMBLY-756) escapeString doesn't work correctly for the 2nd filtering

[ https://issues.apache.org/jira/browse/MASSEMBLY-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy (*$^¨%`£) closed MASSEMBLY-756. Resolution: Fixed use last plexus-interpolation 1.24 version > escapeStr

[jira] [Updated] (MSHADE-239) Shaded Source JAR not following finalName pattern

[ https://issues.apache.org/jira/browse/MSHADE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Rivera updated MSHADE-239: Attachment: source-jar-name.patch Patch file for applying the same value to the sources and tests

[jira] [Updated] (MSHADE-239) Shaded Source JAR not following finalName pattern

[ https://issues.apache.org/jira/browse/MSHADE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Rivera updated MSHADE-239: Attachment: (was: source-jar-name.patch) > Shaded Source JAR not following finalName pattern > -

[jira] [Issue Comment Deleted] (MSHADE-239) Shaded Source JAR not following finalName pattern

[ https://issues.apache.org/jira/browse/MSHADE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Rivera updated MSHADE-239: Comment: was deleted (was: Patch file for applying the same value to the sources JAR.) > Shaded So

[jira] [Updated] (MSHADE-239) Shaded Source JAR not following finalName pattern

[ https://issues.apache.org/jira/browse/MSHADE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Rivera updated MSHADE-239: Attachment: source-jar-name.patch Patch file for applying the same value to the sources JAR. > Sha

[jira] [Updated] (MSHADE-239) Shaded Source JAR not following finalName pattern

[ https://issues.apache.org/jira/browse/MSHADE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego Rivera updated MSHADE-239: Description: When enabling the and configurations, while also using a custom naming scheme in , t

[jira] [Created] (MSHADE-239) Shaded Source JAR not following finalName pattern

Diego Rivera created MSHADE-239: --- Summary: Shaded Source JAR not following finalName pattern Key: MSHADE-239 URL: https://issues.apache.org/jira/browse/MSHADE-239 Project: Maven Shade Plugin Is

[jira] [Commented] (MDEP-410) Add dependency:collect goal which prints the dependency list by resolving the POMs only

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

[jira] [Updated] (MDEP-410) Add dependency:collect goal which prints the dependency list by resolving the POMs only

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-410: Fix Version/s: 3.0 > Add dependency:collect goal which prints the dependency list by resolving the >

[jira] [Closed] (MDEP-410) Add dependency:collect goal which prints the dependency list by resolving the POMs only

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MDEP-410. --- Resolution: Fixed Fixed with [r1768770|http://svn.apache.org/r1768770]. > Add dependency:collect goal w

[jira] [Commented] (MDEP-409) dependency:tree fails for a multi-module project where one module depends on another and "mvn install" not run yet

[ https://issues.apache.org/jira/browse/MDEP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648623#comment-15648623 ] Michael Osipov commented on MDEP-409: - With the resolution of MDEP-410, can this be solv

[jira] [Assigned] (MDEP-410) Add dependency:collect goal which prints the dependency list by resolving the POMs only

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned MDEP-410: --- Assignee: Michael Osipov > Add dependency:collect goal which prints the dependency list by reso

[jira] [Updated] (MDEP-410) Add dependency:collect goal which prints the dependency list by resolving the POMs only

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-410: Summary: Add dependency:collect goal which prints the dependency list by resolving the POMs only (was

[jira] [Updated] (MDEP-410) Add dependency:collect which prints the dependency list by resolving the POMs only

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated MDEP-410: Summary: Add dependency:collect which prints the dependency list by resolving the POMs only (was: dep

[jira] [Commented] (MSKINS-132) Add option to skip adding the Date-Revision meta header

[ https://issues.apache.org/jira/browse/MSKINS-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648501#comment-15648501 ] Markus Kilås commented on MSKINS-132: - Thank you. > Add option to skip adding the Dat

[jira] [Commented] (DOXIASITETOOLS-171) DefaultSiteRenderer must use Package#getImplementationVersion to check for Doxia Sitetools prerequisite

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648483#comment-15648483 ] Hudson commented on DOXIASITETOOLS-171: --- SUCCESS: Integrated in Jenkins buil

[jira] [Commented] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet (solution: dependency:collect)

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648479#comment-15648479 ] Michael Osipov commented on MDEP-410: - If you think that, which obviously do, the docume

[jira] [Commented] (DOXIASITETOOLS-171) DefaultSiteRenderer must use Package#getImplementationVersion to check for Doxia Sitetools prerequisite

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648459#comment-15648459 ] Michael Osipov commented on DOXIASITETOOLS-171: --- You maybe misunders

[jira] [Closed] (DOXIASITETOOLS-171) DefaultSiteRenderer must use Package#getImplementationVersion to check for Doxia Sitetools prerequisite

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIASITETOOLS-171. Resolution: Fixed > DefaultSiteRenderer must use Package#getImplementationVe

[jira] [Commented] (DOXIASITETOOLS-171) DefaultSiteRenderer must use Package#getImplementationVersion to check for Doxia Sitetools prerequisite

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648426#comment-15648426 ] Hervé Boutemy commented on DOXIASITETOOLS-171: -- the change happened 1

[jira] [Comment Edited] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648227#comment-15648227 ] Guillaume Boué edited comment on MRELEASE-966 at 11/8/16 5:52 PM:

[jira] [Comment Edited] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648227#comment-15648227 ] Guillaume Boué edited comment on MRELEASE-966 at 11/8/16 5:48 PM:

[jira] [Commented] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648227#comment-15648227 ] Guillaume Boué commented on MRELEASE-966: - [~jgebal] Yes, thank you for the samp

[jira] [Commented] (MRELEASE-966) release plugin does not respect "mvn -f"

[ https://issues.apache.org/jira/browse/MRELEASE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648181#comment-15648181 ] Jacek Gebal commented on MRELEASE-966: -- [~gboue] Is the information I've provided s

[jira] [Comment Edited] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet (solution: dependency:collect)

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648088#comment-15648088 ] Eric Pabst edited comment on MDEP-410 at 11/8/16 5:18 PM: -- Actually

[jira] [Commented] (MDEP-410) dependency:resolve fails for a multi-module project where one module depends on another and "mvn install" not run yet (solution: dependency:collect)

[ https://issues.apache.org/jira/browse/MDEP-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15648088#comment-15648088 ] Eric Pabst commented on MDEP-410: - Actually, now that you put it that way, yes. I had been

[jira] [Commented] (MNG-5805) Custom packaging types: configuring DefaultLifecycleMapping mojo executions

[ https://issues.apache.org/jira/browse/MNG-5805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647051#comment-15647051 ] Dan Tran commented on MNG-5805: --- is there an example how to use this feature? > Custom packag

[jira] [Commented] (DOXIASITETOOLS-171) DefaultSiteRenderer must use Package#getImplementationVersion to check for Doxia Sitetools prerequisite

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646985#comment-15646985 ] Michael Osipov commented on DOXIASITETOOLS-171: --- The first issues we