You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2019/04/22 10:10:00 UTC

[jira] [Updated] (MPOM-208) upgrade m-scm-publish-p

     [ https://issues.apache.org/jira/browse/MPOM-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy updated MPOM-208:
-------------------------------
    Description: 
to benefit from MSCMPUB-37 (important when you publish site documentation from Linux) that benefits in fact from SCM-763

if m-scm-publish-p is not yet release and we want to release ASF parent POM, just adding an upgraded dependency on maven-scm-provider-svnexe can do the job (I tested)

  was:
to benefit from MSCMPUB-37 (important when you publish site documentation from Linux) thath benefits in fact from SCM-763

if m-scm-publish-p is not yet release and we want to release ASF parent POM, just adding an upgraded dependency on maven-scm-provider-svnexe can do the job (I tested)


> upgrade m-scm-publish-p
> -----------------------
>
>                 Key: MPOM-208
>                 URL: https://issues.apache.org/jira/browse/MPOM-208
>             Project: Maven POMs
>          Issue Type: Dependency upgrade
>          Components: asf
>    Affects Versions: ASF-21
>            Reporter: Hervé Boutemy
>            Priority: Major
>             Fix For: ASF-22
>
>
> to benefit from MSCMPUB-37 (important when you publish site documentation from Linux) that benefits in fact from SCM-763
> if m-scm-publish-p is not yet release and we want to release ASF parent POM, just adding an upgraded dependency on maven-scm-provider-svnexe can do the job (I tested)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)