9:20 a.m.
Artifacts deployed onto wrong volume on Windows platform
--------------------------------------------------------
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: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8070) Artifacts deployed onto wrong volume on Windows platform
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Bernhard Hurzeler updated JBIDE-8070:
-------------------------------------
Attachment: screenshot-1.jpg
I have the same issue. If the JBossDeveloperStudio 4.0.0 Beta2 is installed on C and the
JBossAS5.1 is on D (Windows 7) then some jar files of a SeamWeb Project (WAR) are not
copied over (core.jar, itext.jar, jboss-seam.jar and mvel2.jar) i.e. they are missing in
WEB-INF/lib.
The deployment works however if JDS and JBossAS is on the same drive.
Artifacts deployed onto wrong volume on Windows platform
--------------------------------------------------------
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: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: 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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:54 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8070) Artifacts deployed onto wrong volume on Windows platform
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Bernhard Hurzeler updated JBIDE-8070:
-------------------------------------
Attachment: Server Log.jpg
Artifacts deployed onto wrong volume on Windows platform
--------------------------------------------------------
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: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: 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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:05 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8070) Artifacts deployed onto wrong volume on Windows platform
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Max Andersen commented on JBIDE-8070:
-------------------------------------
I've just reproduced this issue on non-windows.
Simply just use a different deploy location and the same bug occurs. Ill update title to
reflect the non-platform problem.
Artifacts deployed onto wrong volume on Windows platform
--------------------------------------------------------
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: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: 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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:07 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Max Andersen updated JBIDE-8070:
--------------------------------
Summary: Artifacts deployed wrongly when not using standard deploy path OR
separate drive volumes (was: Artifacts deployed onto wrong volume on Windows platform)
Description:
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!
was:
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.
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: Rob Stryker
Priority: Blocker
Fix For: 3.2.0.CR1
Attachments: 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
9:12 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Snjezana Peco updated JBIDE-8070:
---------------------------------
Attachment: JBIDE-8070.patch
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: Rob Stryker
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
9:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-8070:
--------------------------------------
The attached patch fixes the problem on Windows when Eclipse and JBoss AS are installed on
different drives.
The problem is similar to the problem described in JBIDE-7517.
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: Rob Stryker
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
11:48 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8070:
------------------------------------
I've committed snjezana's patch which was perfect, and added some small changes
for other errors in the same class that were logging incorrect things to the server log.
Specifically for child modules it was returning error every time even when the file was
successfully published. Also, a succcessful publish was returning an Unknown Event Type
and was confusing to the user
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: Rob Stryker
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
6:38 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
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
10:10 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-8070.
--------------------------------
Resolution: Done
fixed, verified by dominik
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
10:20 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-8070) Artifacts deployed wrongly when not using standard deploy path OR separate drive volumes
[
https://issues.jboss.org/browse/JBIDE-8070?page=com.atlassian.jira.plugin...
]
Dominik Pospisil closed JBIDE-8070.
-----------------------------------
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
5564
days inactive
5568
days old
jbosstools-issues@lists.jboss.org
10 comments
5 participants
participants (5)
-
Bernhard Hurzeler (JIRA) -
Dominik Pospisil (JIRA)
-
Max Andersen (JIRA)
-
Rob Stryker (JIRA)
-
Snjezana Peco (JIRA)