[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=co... ] Michael Waldvogel commented on HBX-734: --------------------------------------- I downloaded the .zip file from sourceforge via download section of www.hibernate.org. I did not use the update manager ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=co... ] Michael Waldvogel commented on HBX-734: --------------------------------------- Okay; I will immediately test it after release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=all ] Max Rydahl Andersen reopened HBX-734: ------------------------------------- were do you get that error ? I do not get it on a clean install... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=co... ] Michael Waldvogel commented on HBX-734: --------------------------------------- Help->Software Updates->Manage Configuration When I have a look at the entry "Hibernate Tools 3.2beta7" then there is a red cross attached to the Icon left. By having a look on Properties->Status you will get the list of missing plugins. Please consider the following: a) Make a fresh install WITHOUT WTP 1.5 or b) Install WTP 1.5 but install Hibernate Tools to a differen Eclipse Extension Point In both cases the missing plugins will be reported. When you have installed WTP 1.5 in the same folder as Hibernate Tools (by just copying everything together to one folder as most users do), Eclipse is not capable to assign the plugins to the installed components and cannot determine that in reality reported plugins are missing and NOT belonging to Hibernate Tools 3.2beta7. This might the reason why you probably don't see that bug. I splitted up the directories for various plugins, that I faster can switch between the versions WITHOUT decompressing the whole Eclipse new .... [And I admit I don't use Update Manager because I don't want to download the huge packages on every computer again ....] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=co... ] Michael Waldvogel commented on HBX-734: --------------------------------------- Nice :) / Not alone with my splitting idea ;) I personally patched the feature.xml and moved everything from GEF, EMF and WTP from plugin declarations to import declarations (except the real Hibernate plugins). My proposal would be, to split up Hibernate Tools into two features. One into the initial package (consisting of the seven Hibernate Tools plugins) and one, which contains all the plugins needed for Hibernate Tools. If somebody does install WTP 1.5, then he also MUST install EMF and GEF because WTP 1.5 doesn't work without them (dependencies). People like us could just drop the second feature and the belonging plugins [that is easy; only patching feature.xml with any new version costs time]. Usual users wouldn't even realize, as both features are packaged in the same archive! :) Further there is actually really one big drawback by including some WTP 1.5 binaries into the package : package versions differ little. That can cause a plugin to be loaded more than once, if they differ just in one little change ... :( What do you think about that solution? I just attach my feature.xml for Hibernate 3.2beta7 (I did not build another feature, because I don't need it ;) ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=co... ] Max Rydahl Andersen commented on HBX-734: ----------------------------------------- i want to have a one feature that is *correct* in its usage (e.g. import instead of plugin that is not part of the feature) and then have a download that is hibernatetools-x.y.z.zip and a hibernatetools-nodeps-x.y.z.zip where the last one would be the one you would download and the first one those who just want it to work out of the box. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-734?page=all ] Max Rydahl Andersen closed HBX-734: ----------------------------------- Resolution: Fixed changed from plugin to import in feature.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira