[jira] [Created] (MNG-5957) Configuration within lifecycle phase

Mario Krizmanic created MNG-5957: Summary: Configuration within lifecycle phase Key: MNG-5957 URL: https://issues.apache.org/jira/browse/MNG-5957 Project: Maven Issue Type: Improvement

[jira] [Updated] (MRELEASE-937) Git password is visible if commit fails

[ https://issues.apache.org/jira/browse/MRELEASE-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-937: Description: Git username and password is being visible during perform section when

[jira] [Commented] (MRELEASE-937) Git password is visible if commit fails

[ https://issues.apache.org/jira/browse/MRELEASE-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081750#comment-15081750 ] Robert Scholte commented on MRELEASE-937: - I'd say duplicate of SCM-811 > Git password is

[jira] [Commented] (MNG-5957) Configuration within lifecycle phase

[ https://issues.apache.org/jira/browse/MNG-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081558#comment-15081558 ] ASF GitHub Bot commented on MNG-5957: - GitHub user mkrizmanic opened a pull request:

[jira] [Updated] (MNG-5957) Configuration within lifecycle phase

[ https://issues.apache.org/jira/browse/MNG-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Krizmanic updated MNG-5957: - Description: The lifecycle phase can be configured as a comma-separated list of plugins specified

[jira] [Commented] (MRELEASE-928) exposing the password for SCM URL if build failed to commit files to SCM

[ https://issues.apache.org/jira/browse/MRELEASE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081757#comment-15081757 ] Robert Scholte commented on MRELEASE-928: - I'd say duplicate of SCM-811 (also contains the

[jira] [Closed] (MRELEASE-937) Git password is visible if commit fails

[ https://issues.apache.org/jira/browse/MRELEASE-937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-937. --- Resolution: Duplicate Assignee: Robert Scholte > Git password is visible if commit

[jira] [Created] (MRELEASE-937) Git password is visible if commit fails

vishal sahasrabuddhe created MRELEASE-937: - Summary: Git password is visible if commit fails Key: MRELEASE-937 URL: https://issues.apache.org/jira/browse/MRELEASE-937 Project: Maven Release

[jira] [Commented] (MJAVADOC-431) Allow Javadoc Jar to contain Maven descriptor

[ https://issues.apache.org/jira/browse/MJAVADOC-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081891#comment-15081891 ] Peter lynch commented on MJAVADOC-431: -- [~michael-o] Thanks for the MSHARED ticket link - I am

[jira] [Updated] (MNG-5957) Configuration within lifecycle phase

[ https://issues.apache.org/jira/browse/MNG-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mario Krizmanic updated MNG-5957: - Description: The lifecycle phase can be configured as a comma-separated list of plugins specified

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082042#comment-15082042 ] Michael Osipov commented on MSHARED-480: I had the very same idea recently. I am not very pleased

[jira] [Comment Edited] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082042#comment-15082042 ] Michael Osipov edited comment on MSHARED-480 at 1/4/16 11:54 PM: - I had

[jira] [Created] (MSHARED-488) Make input source file encoding default to platform encoding

Michael Osipov created MSHARED-488: -- Summary: Make input source file encoding default to platform encoding Key: MSHARED-488 URL: https://issues.apache.org/jira/browse/MSHARED-488 Project: Maven

[jira] [Closed] (MSHARED-393) AbstractMavenReportRenderer#linkPatternedText does not use any join string

[ https://issues.apache.org/jira/browse/MSHARED-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MSHARED-393. -- Resolution: Incomplete Can't remember the case to make up the example. >

[jira] [Commented] (MSHARED-430) Update JDK requirement to 1.6 / upgrade Maven Core dependencies to 3.0

[ https://issues.apache.org/jira/browse/MSHARED-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082052#comment-15082052 ] Michael Osipov commented on MSHARED-430: I think this change should be reverted. Hervé and I are

[jira] [Commented] (MRESOURCES-171) ISO8859-1 properties files get changed into UTF-8 when filtered

[ https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081867#comment-15081867 ] Aaron Digulla commented on MRESOURCES-171: -- [~afloom] Well, he can't use Maven and expect

[jira] [Created] (MSHARED-489) AbstractMavenReportRenderer#linkPatternedText ignores name if href is invalid

Michael Osipov created MSHARED-489: -- Summary: AbstractMavenReportRenderer#linkPatternedText ignores name if href is invalid Key: MSHARED-489 URL: https://issues.apache.org/jira/browse/MSHARED-489

[jira] [Updated] (DOXIASITETOOLS-93) request-scoped default Velocity Tools are not accessible

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated DOXIASITETOOLS-93: Fix Version/s: 1.7 > request-scoped default Velocity Tools are not

[jira] [Commented] (MRESOURCES-171) ISO8859-1 properties files get changed into UTF-8 when filtered

[ https://issues.apache.org/jira/browse/MRESOURCES-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082113#comment-15082113 ] Hervé Boutemy commented on MRESOURCES-171: -- IMHO, we should, yes, find some new solution to

[jira] [Comment Edited] (DOXIA-482) don't translate APT source comments into output comments

[ https://issues.apache.org/jira/browse/DOXIA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082173#comment-15082173 ] Hervé Boutemy edited comment on DOXIA-482 at 1/5/16 1:40 AM: - after thinking

[jira] [Commented] (MSHARED-489) AbstractMavenReportRenderer#linkPatternedText ignores name if href is invalid

[ https://issues.apache.org/jira/browse/MSHARED-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082197#comment-15082197 ] Hervé Boutemy commented on MSHARED-489: --- I think this issue should not be described as code change,

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082137#comment-15082137 ] Hervé Boutemy commented on MSHARED-480: --- bq. I do believe that skin-related must be in the default

[jira] [Closed] (DOXIA-501) Impossible to use ### header when also using Velocity

[ https://issues.apache.org/jira/browse/DOXIA-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIA-501. --- Resolution: Duplicate Assignee: Hervé Boutemy Fix Version/s: MSITE-756

[jira] [Commented] (DOXIASITETOOLS-67) Velocity ToolManager doesn't work for skins and custom templates

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082187#comment-15082187 ] Hervé Boutemy commented on DOXIASITETOOLS-67: - IIUC from investigations, this issue

[jira] [Updated] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSHARED-480: -- Description: currently, when a reporting mojo is not used as maven-site-plugin's report but

[jira] [Commented] (DOXIA-482) don't translate APT source comments into output comments

[ https://issues.apache.org/jira/browse/DOXIA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082173#comment-15082173 ] Hervé Boutemy commented on DOXIA-482: - after thinking more at it, I'd like to improve [Parser

[jira] [Commented] (MSHARED-430) Update JDK requirement to 1.6 / upgrade Maven Core dependencies to 3.0

[ https://issues.apache.org/jira/browse/MSHARED-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082144#comment-15082144 ] Hervé Boutemy commented on MSHARED-430: --- no need to revert: maven-reporting-impl is completely

[jira] [Commented] (DOXIASITETOOLS-144) split default-site.vm into 2 parts: default-site.vm and default-macros.vm

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082178#comment-15082178 ] Hervé Boutemy commented on DOXIASITETOOLS-144: -- yes: this issue is about the default

[jira] [Commented] (DOXIASITETOOLS-144) split default-site.vm into 2 parts: default-site.vm and default-macros.vm

[ https://issues.apache.org/jira/browse/DOXIASITETOOLS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081108#comment-15081108 ] Michael Osipov commented on DOXIASITETOOLS-144: --- I assume you want to improve this

[jira] [Commented] (MJARSIGNER-17) The plugin should pass proxy information to the jarsigner command.

[ https://issues.apache.org/jira/browse/MJARSIGNER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081089#comment-15081089 ] Riccardo commented on MJARSIGNER-17: Hello, sorry for writing here. I really need this patch but I

[jira] [Issue Comment Deleted] (MJARSIGNER-17) The plugin should pass proxy information to the jarsigner command.

[ https://issues.apache.org/jira/browse/MJARSIGNER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Riccardo updated MJARSIGNER-17: --- Comment: was deleted (was: Hello, sorry for writing here. I really need this patch but I do not

[jira] [Commented] (MRELEASE-937) Git password is visible if commit fails

[ https://issues.apache.org/jira/browse/MRELEASE-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081098#comment-15081098 ] Michael Osipov commented on MRELEASE-937: - Where is the bug? > Git password is visible if

[jira] [Commented] (MRELEASE-928) exposing the password for SCM URL if build failed to commit files to SCM

[ https://issues.apache.org/jira/browse/MRELEASE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081097#comment-15081097 ] Michael Osipov commented on MRELEASE-928: - Where is the bug? > exposing the password for SCM

[jira] [Comment Edited] (MJARSIGNER-17) The plugin should pass proxy information to the jarsigner command.

[ https://issues.apache.org/jira/browse/MJARSIGNER-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081089#comment-15081089 ] Riccardo edited comment on MJARSIGNER-17 at 1/4/16 12:38 PM: - Hello, sorry

[jira] [Commented] (SCM-811) m2 release plugin shows SCM git password if fatal occured during git push

[ https://issues.apache.org/jira/browse/SCM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082404#comment-15082404 ] vishal sahasrabuddhe commented on SCM-811: -- I am using git-client plugin 1.19.1 version. > m2

[jira] [Commented] (SCM-811) m2 release plugin shows SCM git password if fatal occured during git push

[ https://issues.apache.org/jira/browse/SCM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082405#comment-15082405 ] vishal sahasrabuddhe commented on SCM-811: -- I am using git-client plugin 1.19.1 version. > m2

[jira] [Commented] (MSHARED-234) fileset.mdo missing xmlns

[ https://issues.apache.org/jira/browse/MSHARED-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082577#comment-15082577 ] Mikolaj Izdebski commented on MSHARED-234: -- This was fixed in file-management version 3.0.0. You

[jira] [Created] (MSHARED-490) Plexus lookup test fails with Maven 3.1.0 or later

Mikolaj Izdebski created MSHARED-490: Summary: Plexus lookup test fails with Maven 3.1.0 or later Key: MSHARED-490 URL: https://issues.apache.org/jira/browse/MSHARED-490 Project: Maven Shared

[jira] [Updated] (MSHARED-490) Plexus lookup test fails with Maven 3.1.0 or later

[ https://issues.apache.org/jira/browse/MSHARED-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikolaj Izdebski updated MSHARED-490: - Attachment: 0001-Configure-Plexus-container-for-running-tests-with-Ma.patch > Plexus

[jira] [Commented] (SCM-811) m2 release plugin shows SCM git password if fatal occured during git push

[ https://issues.apache.org/jira/browse/SCM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082399#comment-15082399 ] vishal sahasrabuddhe commented on SCM-811: -- Hi, I am also facing similar issue with mvn release

[jira] [Commented] (MNG-5728) Switch the default checksum policy from "warn" to "fail"

[ https://issues.apache.org/jira/browse/MNG-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081231#comment-15081231 ] Nicolas Juneau commented on MNG-5728: - Hello Jason, I concur about the issue potentially affecting many

[jira] [Commented] (MRELEASE-928) exposing the password for SCM URL if build failed to commit files to SCM

[ https://issues.apache.org/jira/browse/MRELEASE-928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081918#comment-15081918 ] Michael Osipov commented on MRELEASE-928: - Yes, go ahead and close it. > exposing the password

[jira] [Commented] (MNG-5947) dependencyManagement import section does not resolve dependencies using "nearest" definition

[ https://issues.apache.org/jira/browse/MNG-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15081506#comment-15081506 ] ASF GitHub Bot commented on MNG-5947: - Github user akacme commented on the pull request: