You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/05/09 23:46:12 UTC

[jira] Commented: (MSITE-405) Having distributionManagement repository url with dav protocol, result to corrupt staging directory structure

    [ http://jira.codehaus.org/browse/MSITE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=220602#action_220602 ] 

Dennis Lundberg commented on MSITE-405:
---------------------------------------

Staging is used for testing and you should *not* include a staged site in your distribution. What you need is the Assembly Plugin in cooperation with the site:jar goal.

> Having distributionManagement repository url with dav protocol, result to corrupt staging directory structure
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-405
>                 URL: http://jira.codehaus.org/browse/MSITE-405
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: windows XP
>            Reporter: Albert Kurucz
>
>     <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>
> ...
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira