[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ve-dev] Reorganization in CVS
|
Not sure I understand why it was needed then. I see a couple of optional
requirements listed at build-time, but they don't appear to be
preventing compilation.
Optional plug-in org.eclipse.perfmsr.core_1.0.0 is not available.
Optional plug-in com.ibm.etools.emf.event_[3.0.0,4.0.0) is not available.
How would including this feature help/hinder/change the output of the
build, if it's not to be included in the final SDK / update site?
Do you have any insights into why the build won't resolve the o.e.ve
plugin? I expect the real problem is that a requirement is missing (eg.,
xulrunner) from basebuilder so while I can compile in the Eclipse
workspace, I can't (yet) compile in a headless basebuilder build.
Any suggestions would be helpful. Please continue this thread in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=270849
Thx,
Nick
Rich Kulp wrote:
Hi Nick,
I was just looking at the defect you were talking about for the reorg
and noticed something:
Also created a o.e.ve.perfcore-feature, as it existed before as
"phony.perfcore".
That was there only for build purposes, it is not meant to be shipped.
That is because there is an actual performance plugin that is optionally
able to be installed (comes from IBM as I recall) and it not an actual
part of VE.
So just make sure this isn't actually packaged within the VE when the
build is finished.
Thanks,
Rich
------------------------------------------------------------------------
_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev
--
Nick Boldt :: http://wiki.eclipse.org/User:Nickb
Release Engineer :: Eclipse Modeling & Dash Athena
