]
George Gastaldi commented on FORGE-2408:
----------------------------------------
Yes, I agree that this sentence is ambiguous. How about:
{code}
This event is fired by the container to signal that a specific addon has started.
To listen for startup of the addon where the observer is contained, observe this event
with the {@link Local} qualifier
{code}
PostStartup bug, or should be documented better
-----------------------------------------------
Key: FORGE-2408
URL:
https://issues.jboss.org/browse/FORGE-2408
Project: Forge
Issue Type: Bug
Components: Dependencies, Furnace CDI
Affects Versions: 2.20.1.Final
Reporter: Ondrej Zizka
Assignee: George Gastaldi
STR:
Check out the 1a89b1c commit from
https://github.com/OndraZizka/windup/commit/1a89b1cac3f76e519571fd08c0cf3...
And run the WindupUpdateRulesetTest.
That will fail in RulesetUpdateChecker, because the PostStartup is fired for all (?)
addons, even those which do not depend on windup-exec, and therefore the @Inject fails
with "IllegalStateException: Addon service [...RulesetUpdater] is not
registered".
I am not quite sure if that's how it should behave. Shouldn't it be called for
the "current addon" as stated in the javadoc of PostStartup?
Or if not, then please specify better when this is called and what is the state of the
addons.