No I consider it a "namespace collision" that hibernate is distributing
org.eclipse.* stuff. I'm only allowing org.eclipse.* to come from the eclipse
website. Depending upon which base version of WTP I use files may or may not be
overwritten but conceptually there is still an unclean namespace collision by the fact
your redistributing.
I was doing something like:
unzip "${BASEDIR}/HibernateTools-3.2.0.beta6a.zip" \
"features/org.hibernate.*" \
"plugins/org.hibernate.*" \
"plugins/org.jboss.*" || exit 1
To filter unwanted stuff out. If the plugin works afterwards great.
But I've had large periods of times over the past 6 months where the hibernate plugin
has not been working (for whatever reason).
But the feature.xml inside hibernate tools is just all wrong IMHO. You should not be
using <plugin ..> for any org.eclipse.* stuff. You should be using <import
...> and when you redistribute any org.eclipse.* stuff you should also be redistrubting
the features/org.eclipse.* files too.
There is also <include ...> which I'm not sure what it means but I have seen it
in other plugins. Maybe swapping <plugin ..> to <include ..> in the current
hibernate tools feature.xml for all org.eclipse.* namespace components is a step in the
right direction.
This request is back to my original hibernate tools query and the example features.xml in
JIRA.
In looking into matters a little more I am finding other possible problems with the plugin
versioning system (in general) which dont make sense to me yet.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962814#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...