On Fri, Oct 6, 2017 at 10:23 AM, Ed Willink <[email protected]> wrote:
> A SimRel check requires David/Frederic to do a lot of chasing to get > complete compliance. > I'd like to remind that SimRel is a community project just like any other, and that contributions are most likely welcome from anyone. All work on SimRel isn't to be done by David or Frederic and we (SimRel users) also have the responsibility to contribute code to it from time to time instead of getting someone else's todo-list explode ;) That said, more technically, I imagine we could relatively easily copy and adapt one of the SimRel report for labels or version that already gets into MANIFEST.MF for all SimRel bundles, and replace the actual payload by a simple regexp comparison. However, before we spend some resources on that, I believe this mush be discussed and desired by the Planning Council? Or should it be the other way round (ie we -the community- create the report and add it to SimRel build) and then Planning Council decides how much to enforce this report? A Tycho check only works for Tycho users, so it does not help Tycho-1 > (Buckminster) or Tycho+1 (whatever) > That's right. However, the logic behind it is simple enough to be repeated in all tools. Adding some abstraction layer for it seems a bit overkill. The cool thing is that having it in Tycho delivers the value to much more users than SimRel, really helping this good practice to be adopted everywhere, and ultimately leading to more peace between JPMS and OSGi faster. All that said, I think there is no bad place where adding a warning, or report or whatever; and having it in too many places is better than having it nowhere. Let just see where actual work happens first ;)
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
