In your contribution file,
soa-bpmn2-modeler.b3aggrcon - org.eclipse.simrel.build
Which means it is not being contributed
to the "simrel" repository ... (ending up in .../releases/staging,
and ultimately .../releases/mars).
From looking at Git history, it appears
I disabled it 3 months ago (presumably because it was causing the whole
build to fail),
and then 6 week ago, you updated the
URL, but you "forgot" (or, didn't know) to remove enabled="false".
Hope that clarifies it.
Bob Brodt <bbrodt@xxxxxxxxxx>
Cross project issues
11/12/2014 10:50 AM
Status and outlook for Mars M3 -
disabled items, and Mac executable signing.
I just checked soa-bpmn2-modeler and it seems to be
enabled for mars on the project website  and the repository references
by soa-bpmn2-modeler.b3aggrcon is also in place . What else am I missing?
Today's the last day to contribute to Mars
M3 (unless there are exceptional circumstances).
Wanted to call attention to those contributions with some part "disabled".
It is not the end of the world if they can not be re-enabled for M3, but
I wanted to be sure none were simply "oversights" in changing
Second, I should have announced this earlier, but if you haven't heard,
there have been changes imposed by an outside Operating System maker. Apple
changed it's "signing rules" recently, primarily for Yosemite,
(10.10) but actually went in to effect in latest release of Maverick (10.9.5).
There are two critical bugs where the work on our end is being tracked:
446390 - Change location of
eclipse.ini (for Max OS X signing)
445050 - Need to update "Mac
Both of them "tough bugs". The "bottom line" for Mac
executable signing is that it is not going to be possible, for M3. Users
can still use the various "run
anyway" work-arounds for unsigned
executables, and with lots of luck (and effort from many skilled people)
I hope we can get signing re-enabled for M4.