Closed jonahgraham closed 4 months ago
I've confirmed in my local build using the re-built staging that the logged warnings are gone.
This usually happens if something is in the target that has (possibly) missing dependencies. The Planner might not choose that so its probably not a problem but I haven't found yet a good way to silence the slicer....
My Oomph build has many such warnings too, but it doesn't cause any problems there...
Thanks for resolving the warnings by fixing simrel - it is nice the RC2 is back to 0 warnings!
(Weird thing about 0 warnings is it means I don't trust my Ctrl-F for warning
as I assume I must have made a typo - this is a good problem to have!)
We have a regression in terms of warnings in the build:
and
appear multiple times.
These appear in the RC1 build - they started in the nightly builds on 23 May - https://ci.eclipse.org/packaging/job/epp/job/master/61/.
These are the simrel changes on that day: Commits on May 23, 2024 DLTK 6.4.1 for 2024-06 Contribute Acceleo 3.7.16 to Eclipse 2024-06 Wild Web Developer 1.3.5
I'll need to investigate more fully to understand the effect - but @merks if this seems familiar to you please let me know.
Originally posted by @jonahgraham in https://github.com/eclipse-packaging/packages/issues/166#issuecomment-2139895397