[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes

[Dominik Pospisil (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574628#comment-12574628 ] 

Dominik Pospisil commented on JBIDE-8070:
-----------------------------------------

Verified (JBT 2011-01-11_04-39-35-H884).

> Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
> ----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-8070
>                 URL: https://issues.jboss.org/browse/JBIDE-8070
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta2
>         Environment: Windows 7
>            Reporter: Dominik Pospisil
>            Assignee: Dominik Pospisil
>            Priority: Blocker
>             Fix For: 3.2.0.CR1
>
>         Attachments: JBIDE-8070.patch, screenshot-1.jpg, Server Log.jpg
>
>
> Sometimes, artifacts are deployed onto wrong volume on Windows platform.
> Steps to reproduce:
> 1) Install JBT on first volume (e.g. C:)
> 2) setup AS runtime on different volume (e.g. D:) with deployment location set so server deploy dir
> 3) Try to stop/start server & deploy/undeploy artifacts
> Sometimes, artifacts are copied to wrong volume (C: in my case). The deploy folder si silently created on that volume, artifacts coppied. No error logged, JBT assumes everything went fine.
> For non-windows:
> Setting deploy folder to custom location, i.e. /Users/max/tmp/deploy instead of within the server default location similar problems are seen!

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira