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

Provide manifest headers to load apm-agent-api in an OSGi environment #3345

Closed
royteeuwen opened this issue Oct 3, 2023 · 3 comments
Closed
Labels
agent-java community Issues and PRs created by the community triage

Comments

@royteeuwen
Copy link

It is currently not feasible to use the apm-agent-api in an OSGi environment, because there are no manifest headers generated that specify the required bundle headers to load the jar into an OSGi container

@github-actions github-actions bot added agent-java community Issues and PRs created by the community triage labels Oct 3, 2023
royteeuwen pushed a commit to royteeuwen/apm-agent-java that referenced this issue Oct 3, 2023
@SylvainJuge
Copy link
Member

Closing this as this is not something that will be relevant long term as a direct contribution to the agent repo.

The main reasons have been listed in the related PR: #3346 (comment), working around this by re-packaging or modifying the agent artifacts within the application packaging seems a simpler approach here.

@royteeuwen
Copy link
Author

OK, thanks for the update Sylvian. I understand the reasoning and in this specific case it is pretty easily fixed at my side

@SylvainJuge
Copy link
Member

Thanks to you too, this is quite rare that people understand why it can create too much burden long term on our side and accept this as "the best option" !!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agent-java community Issues and PRs created by the community triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants