Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 561777 - [Passage] [Spring] design a way to declare licensing requirements #23

Open
ruspl-afed opened this issue Nov 17, 2021 · 0 comments

Comments

@ruspl-afed
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant