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

Automatically discover dependencies from a published product #3499

Merged
merged 1 commit into from
Feb 10, 2024

Conversation

laeubi
Copy link
Member

@laeubi laeubi commented Feb 10, 2024

Currently the publis-products mojo is only fully usable in the eclipse-repository packaging type but there are other use-cases where it becomes interesting to publish the product metadata and further use it, for example in an p2 installed runtime. Even though it works to use the mojos it is quite inconvenient as one has to specify all its requirements manually as extra dependencies.

This adds a new PublishProduct P2 unit providers that collect the dependencies from a product and supply them automatically as requirements to the project so the mojo can be used without having missed dependencies from the target.

@laeubi laeubi enabled auto-merge (rebase) February 10, 2024 18:37
Currently the publis-products mojo is only fully usable in the
eclipse-repository packaging type but there are other use-cases where it
becomes interesting to publish the product metadata and further use it,
for example in an p2 installed runtime. Even though it works to use the
mojos it is quite inconvenient as one has to specify all its
requirements manually as extra dependencies.

This adds a new PublishProduct P2 unit providers that collect the
dependencies from a product and supply them automatically as
requirements to the project so the mojo can be used without having
missed dependencies from the target.
@laeubi laeubi merged commit 8edc7b4 into eclipse-tycho:tycho-4.0.x Feb 10, 2024
8 of 9 checks passed
@akurtakov
Copy link
Member

Do you have some exampleto show what becomes possible/easier with this change that wasn't before?

@laeubi
Copy link
Member Author

laeubi commented Feb 11, 2024

This is used here:

@laeubi
Copy link
Member Author

laeubi commented Feb 12, 2024

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

Successfully merging this pull request may close these issues.

2 participants