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 2009/05/15 17:45:44 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=176638#action_176638 ]
Dennis Lundberg commented on MSITE-405:
---------------------------------------
The Site Plugin doesn't use the <repository/> element from <distributionManagement/> at all. It does however use the <distributionManagement> / <site> / <url> which is probably what you mean.
I have seen that in a staging path as well. Apart from the fact that it looks a bit ugly, is there a problem with it? It's only used for staging the site. Nobody except the people doing QA will ever see it.
> 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