From: Max R. A. (JIRA) <no...@at...> - 2006-07-24 21:01:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=comments#action_23750 ] Max Rydahl Andersen commented on HBX-709: ----------------------------------------- doesn't this prevent us from having an update site with all the files ? > Start distributing an eclipse Hibernate Tools runtime only JAR > -------------------------------------------------------------- > > Key: HBX-709 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-709 > Project: Hibernate Tools > Type: Task > Reporter: Darryl Miles > Attachments: feature.xml > > > http://forum.hibernate.org/viewtopic.php?t=962374 > Start to pickup and use Eclipse/WTP versioning within the features.xml/ > Plan of action as I see it: > * Copy features/org.eclipse.* and features.org.apache.* files as well as pre-requisite plugins/* when packaging. > * Move <plugin ...> into <import ...> in features/org.hibernate.eclipse.feature_3.2.0.beta6a/feature.xml (see attached sample of this working for me) > * Modify build and packaging process to now create two JARs. > JAR one contains (this is the runtime only JAR): > features/org.hibernate.eclipse.feature* > plugins/org.hibernate.eclipse* > plugins/org.jboss.ide.eclipse.freemarker* > JAR two contains (this is the equivalent of what is distrubuted now, hibernate tools, with WTP/XSD/GEF/JEM pre-requisites, without Eclipse Platform) > All the files in JAR one above, plus > plugins/org.eclipse.gef* > plugins/org.eclipse.wst.xml_core.feature.* > plugins/org.eclipse.wst.common_core.feature* > plugins/org.eclipse.wst.common_ui.feature* > plugins/org.apache.xerces.feature* > plugins/org.eclipse.xsd* > plugins/org.eclipse.jem* > plugins/org.eclipse.wst.xml_ui.feature* > plugins/org.eclipse.emf* > features/org.eclipse.gef* > features/org.eclipse.wst.xml_core.feature_* > features/org.eclipse.wst.common_core.feature_* > features/org.eclipse.wst.common_ui.feature_* > features/org.apache.xerces.feature_* > features/org.eclipse.xsd_* > features/org.eclipse.jem_* > features/org.eclipse.wst.xml_ui.feature_* > features/org.eclipse.emf_* > By removing the <plugin ..> declarations from the hibernate JAR it stops the JAR claiming it is the authorative source for that plugin to the update manager. By including the original features/ files from the original authorative source means that if a user installs pre-requisites (or has pre-requisites already installed) when they use JAR two, and restart Eclipse will automatically pickup and use the lastest installed version of WTP/XSD/EMF/GEF/JEM compatible with hibernate tools. > This has the effect is automatically upgrading the version of pre-requisites when multiple versions are found. But in the event the users version of pre-requisites is too old or non-existant then the ones in the JAR two will be picked up and used. > If the re-packaged version of freemarker is also being used inside other JBOSS plugins, then I would suggest a seperate feature/org.jboss.ide.eclipse.freemarker*/feature.xml be provided and all plugins built on top are then to pickup that with an <import ...> declaration. If hibernate tools is the only user of freemarker then leading it inside hibernate tools is fine. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |