Menu
▾
▴
hibernate-issues
|
From: Darryl M. (JIRA) <no...@at...> - 2006-07-24 18:53:01
|
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
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
|
|
From: Darryl M. (JIRA) <no...@at...> - 2006-07-24 19:00:49
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=all ] Darryl Miles updated HBX-709: ----------------------------- Attachment: feature.xml Damn, Sorry JIRA wont let me edit the Priority to something more suitable once I've posted the issue. Please find attached a working new feature.xml file for 3.2.0.beta6a. > 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 |
|
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 |
|
From: Darryl M. (JIRA) <no...@at...> - 2006-07-27 22:57:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=comments#action_23764 ] Darryl Miles commented on HBX-709: ---------------------------------- I'm no guru but believe I have some limited understanding, so dont shoot me. No it does not. Your update site has a site.xml descriptor file which catalogues everything that is available from that update site, each downloadable item may contain one or more features. This way you can bundle prerequisites as now and provide a runtime only JAR from the same site at the same time, even multiple versions of things at the same time. The update manage will work out the best fit archive to download (and if it doesn't that a bug). This means someone with a suitable base version of WTP installed that uses the update site, the UI should automatically pick the runtime only JAR to install. But someone with just Eclipse Platform and no WTP, the UI should automaticially pick the runtime+prerequsites JAR to install. I dont think its worth the headache of exploding all all the features. Ideally each version of a unique feature would be in its own JAR. This way fine grained downloading and installing can be performed by the update manager and extra versions of pre-requisites are not installed on the system at all. This is only a problem say if you are 1 prerequisite missing you can end up downloading JAR two and installing everything in it just to get access to that one feature. But I dont believe anything gets broken when that happens so maybe we should not worry about it at all. Hibernate tools users there are 3 groups (as I see it): * Those with no Eclipse runtime installed [all in one jar] * Those with Eclipse runtime installed (but without WTP and its prerequisites) [HBX runtime + prerequisites, JAR two] * Those with Eclipse runtime + WTP installed [HBX runtime only, JAR one] Obviously the first group does not apply to the update manager and I'm not even sure if there is an all-in-one for download even on sourceforge. The other two can be distrubuted from the same update site (when packaged appropiately for update site deployment) and an equivalent JAR can be created in each two forms to put up on sourceforge. I would like to see a change of name take place so the current filename is used for the HBX runtime only and a new named archive (maybe with "-incdeps" in the filename). Or if thats a headache a new naming scheme for both to make everyone pick. (maybe "-runtime" in the name). Maybe you can point me in the direction of the ANT tasks and procedure that is used to create a distribution and the update site artifacts ? > 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 |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-07-28 12:22:20
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-709?page=comments#action_23795 ] Max Rydahl Andersen commented on HBX-709: ----------------------------------------- it is in releng module of jbosside. I recommend try and talk about this on the jboss ide maling list or dev forum since it is actually there the packaging occurs. It will be much appreciated. > 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 |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X