[ https://jira.jboss.org/jira/browse/JBIDE-3308?page=com.atlassian.jira.plu... ] Adrian Mitev commented on JBIDE-3308: ------------------------------------- FWIW this doesn't happen with the nightly build from N200811201326. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3308?page=com.atlassian.jira.plu... ] Adrian Mitev commented on JBIDE-3308: ------------------------------------- I have a workspace created with N200811201326 and with that build it doesn't happen. With the same workspace and the current nightly build the problem appears. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3308?page=com.atlassian.jira.plu... ] Max Rydahl Andersen reopened JBIDE-3308: ---------------------------------------- We got this reported my more than one and it is apparently still happening in latest nightly builds. It looks like the URL is initialized wrongly (i.e. no separation of directories) With the updated check for directory existence what happens if the dir does not exist ? Is the user notified ? otherwise deployment will not work at all... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3308?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3308: ------------------------------------ Comment 1: I don't know what you mean about "initialized wrongly". There is no place where I'm "initializing" this url. And I don't know what you mean by "separation of directories". The user is always notified when a publish fails in the Event Log. The only API webtools offers me is to throw a CoreException, which is ALWAYS uninformative and provides no useful information to the user whatsoever so I don't do that. I put my messaging in the event log. Comment 2: 1) good point 2) If the folder doesn't exist, we currently ignore it during the pre-publish phase and the publish itself will fail. If you think I should fail immediately here in the pre-publish phase I'd be glad to. No, the server startup / shutdown should not fail if the deploy location is wrong. That would be ridiculous. Startup / shutdown are distinct from publish. 3) Yes we're (almost) always calling addURL. Adding the exact same url twice is safe. Adding one folder and then adding it's parent is not, though. I contend that it SHOULD be, but JBoss is being dumb. The times we do not call addURL are when the deploy folder is equal to the server's official deploy folder. Why don't I get the list and check the list? Because a) it's not necessary (adding same URL twice is not a problem) and b) more overhead / remote JMX calls. I've been unable to replicate this issue using an environment created in beta1. It's quite possible this issue is only happening for people who were using nightly builds often and one of those nightly builds mucked things up. I encourage any tester to test with a workspace created in a beta1 environment. People using nightly builds should know that workspaces created during those nightly builds may not be stable. The upgrade case we're looking to have work smoothly are 3.0.0.beta1 to CR1 and 2.1.2 to CR1. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3308?page=com.atlassian.jira.plu... ] Adrian Mitev commented on JBIDE-3308: ------------------------------------- The problem does not appear with the todays build (N200812042142) -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-3308?page=com.atlassian.jira.plu... ] Anton Klimkovich closed JBIDE-3308. ----------------------------------- Verified on JBossTools-3.0.0.CR1-N200812080252-ALL -- 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