You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2008/07/01 20:50:45 UTC

[jira] Commented: (GERONIMO-3963) Remote deployment using the --inPlace option

    [ https://issues.apache.org/jira/browse/GERONIMO-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609679#action_12609679 ] 

Jarek Gawor commented on GERONIMO-3963:
---------------------------------------

I committed some changes to trunk (revision 673170) and branches/2.1 (revision 673171) to ensure that the deployment operation will fail if remote in-place deployment is attempted. 


> Remote deployment using the --inPlace option
> --------------------------------------------
>
>                 Key: GERONIMO-3963
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3963
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0.x
>         Environment: Tested on Windows XP but Linux should be the same except the drive constraint
>            Reporter: Jacques Le Roux
>            Assignee: Jarek Gawor
>            Priority: Minor
>
> Remote deployment using the --inPlace option (for a totally exploded EAR with exploded and only exploded WARs inside) is only possible if you exactly replicate the deployed directory structure on both the client and the server machine. If you are on Windows you must even replicate the drive.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.