Hi Robert
On 17/03/2010 14:55, Robert M. Fuhrer wrote:
Sure, I have no objection.
Thanks.
But I'm curious: Is the purpose of this bundling simply to avoid
the need for additional p2 metadata on the IMP update site?
I hope not. It just needs some inspiration. I've noticed that the
contents.xml in contents.jar has an interesting references element.
Maybe someone at EclipseCon will give some inspiration.
Until IMP joins the train, we probably have to bundle IMP dependencies
to ensure that the Modeling package is self-contained.
I.e., if you do this, then I assume you won't need us to
"upgrade" the IMP update site to a full-blown p2 update site, right?
It would be great if you could; it eliminates one possible cause. But I
thoroughly sympathesize with a certain inertia witrh regards to
changing build procedures.
Regards
Ed Willink
On Mar 16, 2010, at 3:40 PM, Ed Willink wrote:
Hi
The M2M/QVTd OCL editor is being migrated for distribution as part of
the MDT/OCL Examples feature for Helios.
This introduces a dependency on IMP Runtime. To avoid problems with a
dangling reference from the Modeling package and transitive
installation from the IMP update site, is it ok to bundle the
unmodified IMP Runtime plugin as part of MDT/OCL Examples feature?
--
Cheers,
- Bob
-------------------------------------------------
Robert M. Fuhrer
Research Staff Member
Programming Technologies Dept.
IBM T.J. Watson Research Center
_______________________________________________
imp-dev mailing list
imp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/imp-dev
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.791 / Virus Database: 271.1.1/2752 - Release Date: 03/17/10 07:33:00
|
