maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@codehaus.org>
Subject [jira] (MSITE-405) Having distributionManagement repository url with dav protocol, result to corrupt staging directory structure
Date Tue, 17 Jun 2014 20:21:10 GMT

     [ https://jira.codehaus.org/browse/MSITE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Scholte closed MSITE-405.
--------------------------------

    Resolution: Not A Bug
      Assignee: Robert Scholte

As said by Dennis, this is not a bug of the maven-site-plugin

> Having distributionManagement repository url with dav protocol, result to corrupt staging
directory structure
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-405
>                 URL: https://jira.codehaus.org/browse/MSITE-405
>             Project: Maven Site Plugin
>          Issue Type: Bug
>          Components: site:stage(-deploy)
>    Affects Versions: 2.0
>         Environment: windows XP
>            Reporter: Albert Kurucz
>            Assignee: Robert Scholte
>
> {code:xml}
>     <distributionManagement>
>         <!-- this is where binaries are deployed -->
>         <repository>
>             <id>codehaus.org</id>
>             <name>JTStand Repository</name>
>             <url>dav:https://dav.codehaus.org/repository/jtstand/</url>
>         </repository>
>         <!-- NOTE: the uniqueVersion element tells Maven to keep only a single version
of a SNAPSHOT -->
>         <snapshotRepository>
>             <id>codehaus.org</id>
>             <uniqueVersion>false</uniqueVersion>
>             <name>JTStand Snapshot Repository</name>
>             <url>dav:https://dav.codehaus.org/snapshots.repository/jtstand/</url>
>         </snapshotRepository>
> ...
> {code}
> {{site:stage}} results to:
> target/staging/https/odehaus.org/jtstand ...
> The "odehaus" is not a typo here, I think this is the bug.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message