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

Albert Kurucz commented on MSITE-405:
-------------------------------------

I would like to develop my project packaging, to pack the the full staging 
directory with the distributable.

(Reason? Because I would like my desktop app to have access to documents even 
if the app is installed onto a workstation which is disattached from any of 
network or internet. This way providing help to the users).

I could setup the packaging's parameters to look for the site on this ugly 
location, but I don't want.
I hope ugly will not become our standard!

How is the dir computed from the url?

> 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

        

Reply via email to