For the record, the aggregation build is
now running "clean", with only LDT and BIRT (still) disabled
and a MAT feature disabled, since it depends on BIRT. I know BIRT being disabled will effect
EPP packages for M3, so I hope it can be fixed soon.
In addition, there are three other files
with disabled features or repositories -- I assume disabled by the project's
themselves, at least I don't recall doing it.
For all cases, please let us know why
disabled (no longer participating?) and when you expect to have "fixed".
As always, feel free to ask if questions
Greg Watson <g.watson@xxxxxxxxxxxx> To:
Cross project issues
10/21/2015 10:40 AM Subject:
Next turn of the crank ... runtime compatibility
bundle Sent by:
I thought I’d fixed PTP already, but I’ll check again.
Since no response from Birt, I have
disabled BIRT from the aggregation, for now (which required me to also
disable MAT chart feature, for now, since depends on BIRT) so that
we can see who else might still depend on compatibility bundle.
According to my local builds, I think PTP does?
If so, please correct soon, please ... I'd like to know if there's any
more, after that is fixed?
It appears some projects are not going to be able to react to the removal
of runtime.compatibility bundle, for M2, so I have re-enabled the LDT contribution.
478009 and Bug
478330). This will allow the aggregation build, at least, to complete, so that others
can make progress.
This won't help projects who have a direct dependancy on, say, DTP (which
in turn as a dependency on runtime compatibility bundle) since they depend
on it, but do not provide it. For those people, the only work around I know of is to "include"
only that bundle from our M1 repository, or something similar. Less that ideal, but I'd like to push forward and see if we can get out
some form of M2 that can be used to create a cleaner M3!
Let me know if suggestions or alternative approaches. (And, FYI, it does
not appear that extending the deadline a few days will help with the runtime
compatibility issue, but, if anyone has been blocked due to this issue,
and needs a few days to work around the problem, I think it reasonable
to consider an extension of a few days ... if you make such a request,
please be specific ... I'd hate to extend it to Monday instead of Friday
(let's say) and then that still not be enough time.)
I hope that is a temporary condition, since (in this case) do not think
the Platform would like others "extending the life" of something they are trying to end. But
... I am not sure. I think the next step is to hear from the LDT project. I have opened bug
478009 for this issue.
I did also use b3 aggregator editor to search for others who might be contributing
that bundle, and it appears there are no others. (And, appears that LDT contributes much more potentially problematic bundles,
than just that one, since they duplicate a great deal of other's projects, for their "Eclipse product").