You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we know, sisu is "flat", while plexus is filtering components based on visibility (is configurable to be "flat"/"global" as well, but am unaware of any usage relying on that). Maven uses Plexus with default "realm" visibility as well. Basically, Maven would be very fine with Sisu only EXCEPT for component visibility.
Would be great if Sisu would accept (on construction) some "filter" that would be applied to components, to achieve same "realm" visibility as Plexus does.
Maven while constructs Sisu (and Plexus) does use and will use ClassWorlds to create realm hierarchy, so something like RealmManager could be implemented in Maven, while Sisu could be created with some filter like RealmFilteredBeans is.
The text was updated successfully, but these errors were encountered:
As we know, sisu is "flat", while plexus is filtering components based on visibility (is configurable to be "flat"/"global" as well, but am unaware of any usage relying on that). Maven uses Plexus with default "realm" visibility as well. Basically, Maven would be very fine with Sisu only EXCEPT for component visibility.
Would be great if Sisu would accept (on construction) some "filter" that would be applied to components, to achieve same "realm" visibility as Plexus does.
Maven while constructs Sisu (and Plexus) does use and will use ClassWorlds to create realm hierarchy, so something like RealmManager could be implemented in Maven, while Sisu could be created with some filter like RealmFilteredBeans is.
The text was updated successfully, but these errors were encountered: