[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-2470) No error announcement when building project archive.

[Edward Pilipczuk (JIRA)]

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

Edward Pilipczuk commented on JBIDE-2470:
-----------------------------------------

Sorry, I haven't checked logs.
To reproduce the situation I can provide the following prescription:
1. Use sftp client from putty package ( http://the.earth.li/~sgtatham/putty/latest/x86/psftp.exe )
2. Open session to the remote site and try upload the archive to non-existent directory, like to "ext/" here:
-------------------------------
psftp: no hostname specified; use "open host.name" to connect
psftp> open edx at helios
Using username "edx".
edx at 10.60.69.203's password:
Remote working directory is /home/edx
psftp> put "C:\Documents and Settings\pilipce\workspace\cbs\cbs.ear" ext/cbs.ear

/home/edx/ext/cbs.ear: open for write: no such file or directory
psftp>
--------------------------------
After that operation cbs.ear archive is somehow  "locked" by psftp (it is wrong behaviour anyway :)) and overwriting it by JBossTools with new image is never succeded until psftp window is active in the system.

> No error announcement when building project archive.
> ----------------------------------------------------
>
>                 Key: JBIDE-2470
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-2470
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Archives
>         Environment: WindowsXP/Intel Core T730 Duo CPU @2GHz / Eclipse Version: 3.3.1.1, Build id: M20071023-1652 / 
> JBossTools-200806242226-nightly-ALL-win32.zip
>            Reporter: Edward Pilipczuk
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.0.0.alpha
>
>
> Condition: The old archive file (e.g. jar file) is opened exclusively by the other process in windows environment.
> When building then the new version of the project archive this task is accomplished silently without compliants.
> However the new archive is not created nor the user is warned that the file archive has not been updated with new image on the disk.
> Only file timestamp and its size indicates that nothing has changed.
> I think that IO exception thrown during file updates shall be reported to the user via popup window.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira