Migrated from https://bugs.eclipse.org/bugs/show_bug.cgi?id=561777
Have a lokk at the API revision work done in 561380 regarding licensing requirements resolution. Here ResolvedRequirements service is invited to encapsulate a way a developer can declare a licensing requirement (Requirement).
Eclipse product developer can use either BundleRequirements or ComponentRequirements implementations, which are both equinox-dependent.
And there are no universal, flatform-agnostic implementation (can appear though).
For a Spring-app developer employing Passage Spring framework definitely can provide it's own way(s) to register licensing requirement.
In the scope of this task this/these should be designed and implemented, add subtasks if necessary.