[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=all ] Anton Klimkovich updated JBIDE-2250: ------------------------------------ Attachment: exception.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=comments#action_12413986 ] Dima Geraskov commented on JBIDE-2250: -------------------------------------- Creation Seam Ear web project calls creation new console configuration in the projects folder. This point differs from the hibernate console configuration creation - it is created in the '.workspace' folder. When we rename project all project's files moves into other folder (and '.lauch' file too). When hibernate's LaunchConfigrationResourceNameChange try to change old launch configuration the exception happens because '.launch' file has been already moved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=all ] Dima Geraskov updated JBIDE-2250: --------------------------------- Attachment: PropertyDialogPatch_JBIDE-1913.txt workingCopy#setContainer() didn't help because in the case our workingCopy rewrites previously changed launch configuration. LaunchMahager also doesn't know that the launch configuration was moved and get LaunchConfiguration by name - leads to blind alley. So we need to check that our launch configuration exists before make changes. If it is not exists we need to calculate it's new path and get new launch configuration object which already changed by other Changes (do it by ILaunchConfiguration#getLaunchConfiguration(IFile)) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=all ] Dima Geraskov reassigned JBIDE-2250: ------------------------------------ Assignee: Anton Klimkovich (was: Dima Geraskov) Commited in trunc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=all ] Anton Klimkovich updated JBIDE-2250: ------------------------------------ Attachment: exception2.txt exception3.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=all ] Dima Geraskov reassigned JBIDE-2250: ------------------------------------ Assignee: Anton Klimkovich There were a few exceptions with project renaming. Exception from exception2.txt is not a HibernateException. Please create another bug (it is SeamELValidator exception). Exception from exception3.txt may be the consequence of exception from exception2.txt. To check that hibernate refactoring participant works check that JBIDE-2256 fixed. If JBIDE-2256 is fixed, than this bug can be closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=comments#action_12418076 ] Dima Geraskov commented on JBIDE-2250: -------------------------------------- Ups, I didn't noteced that it is not fixed in 2.1.2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=all ] Max Rydahl Andersen updated JBIDE-2250: --------------------------------------- Fix Version/s: 3.0.alpha Assumed to be 3.0.alpha -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=comments#action_12418103 ] Anton Klimkovich commented on JBIDE-2250: ----------------------------------------- Can I close this issue If fix fersion 3.0 alpha and create one more about anothe exceptions? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-2250?page=comments#action_12418746 ] Anton Klimkovich commented on JBIDE-2250: ----------------------------------------- Verified on 200806231717-nightly. *launch* file changes. There is no exception "Hibernate Console Internal". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira