William,
thank you for pointing this out. I haven't been aware of that.
I also CC'd Miro Spoenemann who is one of the developers and the
contact person for the KIELER library.
Kind regards,
Henrik
Am 06.02.2013 20:46, schrieb David M
Williams:
Henrik,
Sorry to be the bearer of bad
news,
but ...
Seeing the Orbit build fail, and
looking
for the reason, I see that messages such as those below.
These give me pause, and pretty
much
change my mind about if this is appropriate for Orbit.
I am currently thinking not.
Orbit bundles, besides being from
"third
parties" are normally low level function that does not depend on
other
Eclipse projects.
This large set of bundles has so
many
dependencies on "Modeling" projects, and sounds like it is a
"complete system", that I think it better belongs in Modeling.
Perhaps proposed as
as a sub-project of gmf or
something,
if it doesn't fit in to any existing projects.
Missing required plug-in
org.eclipse.buckminster.sax_0.0.0.
Missing required plug-in
org.eclipse.acceleo.engine_0.0.0.
Missing required plug-in
org.eclipse.amalgam.discovery.ui_0.0.0.
Missing required plug-in
org.eclipse.gmf.runtime.diagram.ui_0.0.0.
Missing required plug-in
org.eclipse.gmf.runtime.diagram.ui.render_0.0.0.
Missing required plug-in
org.eclipse.buckminster.sax_0.0.0.
Missing required plug-in
org.eclipse.acceleo.engine_0.0.0.
Sorry this wasn't clearer,
sooner. I
think we've made one or two exceptions, but its been for "small"
things that were "low level" in Eclipse, such as
org.eclipse.osgi.resolver
(or something ... I forget what exactly).
Thus, I'll comment out your
contributions
from the Orbit feature, for now, and ask you to discuss the
"Modeling
project" approach with the Modeling PMC. (Ed Merks CC'd on this
note).
Thanks,
_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
|