You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Yves Van Steen (JIRA)" <ji...@codehaus.org> on 2007/05/23 11:17:58 UTC

[jira] Issue Comment Edited: (MSITE-232) Deploy multi module site to windows share

    [ http://jira.codehaus.org/browse/MSITE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96825 ] 

Yves Van Steen edited comment on MSITE-232 at 5/23/07 4:17 AM:
---------------------------------------------------------------

Hey this works.
Thanx for you help.

It would be nice to get a failure when path is wrong or none existent.
And it is a little strang that to refer to a remote client you need to specify the localhost first.
And that is still deployed something and just not the subprojects.
And the deploying of jars works perfectly with the dubbel slash.

Maybe you can adapt the resolution to recognize the \\ after the file:// to see that it is in fact windowsshare name.
Because the extra initial / isn't really implied. It's also not mentioned anyware which just enhances the confusion and needless bugs being submitted.
In linux It's used for setting the path to the root of the filesystem and not work relative. Which probably everyone knows.
Just a suggestion.

I like to follow common patterns to minimize in confusion about the use of a product.
Thats why I love java. The community strives for this.


 was:
Hey this works.
Thanx for you help.

It would be nice to get a failure when path is wrong or none existent.
And it is a little strang that to refer to a remote client you need to specify the localhost first.
Maybe you can adapt the resolution to recognize the \\ after the file:// to see that it is in fact windowsshare name.
Because the extra initial / isn't really implied. It's also not mentioned anyware which just enhances the confusion and needless bugs being submitted.
In linux It's used for setting the path to the root of the filesystem and not work relative. Which probably everyone knows.
Just a suggestion.

I like to follow common patterns to minimize in confusion about the use of a product.
Thats why I love java. The community strives for this.

> Deploy multi module site to windows share
> -----------------------------------------
>
>                 Key: MSITE-232
>                 URL: http://jira.codehaus.org/browse/MSITE-232
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-4, 2.0-beta-5
>         Environment: windows xp sp 2
>            Reporter: Yves Van Steen
>
> I was unable to deploy the sites of my submodules to my windows share.  the windows share is one that is under a web path to my apache webserver.
> For the record some other posted bugs on the JIRA about deploy to windows share did'nt expect this kind of behaviour (the double backslash way, file:\\....\...). I did.  Don't really find it odd.
> It only works when you have a single module build.  When you have a reactor build (pom with modules) it only deploys the root (or top pom) but sub projects don't get deployed because maven starts to use slashes and not backslashes.
> Example :
> Deploy top = file://\\vam7225\repo\www\orbisbe (=> works)
> Deploy subproject = file://\\vam7225\repo\www\orbisbe/component1 (=> No deploy)
> Deploy subproject = file://\\vam7225\repo\www\orbisbe/component2 (=> No deploy)
> But It does NOT report a failure on the sub projects. And you can see the use of the normal slash above.
> Is there a fix available for this ??
> Thanx for any help

-- 
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