Add metadata for eclipse-pde-build to manifest-file #1515
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When developing OSGi-bundles and using the eclipse-pde-build requires additional meta-data in the manifest-file at compile-time. Detailed explanations are described in http:https://blog.vogella.com/2016/02/09/osgi-bundles-fragments-dependencies/. The section "When are fragments the wrong agent of choice?" describes exactly the hapi-fhir-architecture, the problems, that I had and the solution. This change is completly safe because it is ignored at runtime. It is just needed at compile time in a special usa case within eclipse.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When developing OSGi-bundles and using the eclipse-pde-build requires
additional meta-data in the manifest-file at compile-time.
Detailed explanations are described in
http:https://blog.vogella.com/2016/02/09/osgi-bundles-fragments-dependencies/.
The section "When are fragments the wrong agent of choice?" describes
exactly the hapi-fhir-architecture, the problems that I had and the
solution.
To understand the example here the analog files in hapi-fhir:
org.fipro.host <=> hapi-fhir-base
org.fipro.host.fragment <=> hapi-fhir-structures-r4
This change is completly safe because it is ignored at runtime. It is
just needed at compile time in a special usa case within eclipse.