Skip to content

Add OSGi Bundle metadata #725

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

Merged
merged 1 commit into from
Sep 24, 2018
Merged

Add OSGi Bundle metadata #725

merged 1 commit into from
Sep 24, 2018

Conversation

dagnir
Copy link
Contributor

@dagnir dagnir commented Sep 24, 2018

Description

Add OSGi metadata to MANIFEST.MF

Note: This does not completely enable the SDK to be loaded in an OSGi container because of some currently blockers. See #719 and #726.

Motivation and Context

Step towards allowing SDK to be used in OSGi.

Testing

  • mvn clean install and check JAR MANIFEST.MF files.

Tested a modified version of this PR that exports all packages (including .internal. packages) by loading the required bundles for ACM in Apache Felix and made a service call.

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Checklist

  • I have read the CONTRIBUTING document
  • Local run of mvn install succeeds
  • My code follows the code style of this project
  • My change requires a change to the Javadoc documentation
  • I have updated the Javadoc documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed
  • A short description of the change has been added to the CHANGELOG

License

  • I confirm that this pull request can be released under the Apache 2 license

Apache Aries SPI Fly is used to provide runtime loading of HTTP clients.

Fixes aws#607

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this plugin required in modules like flow, services. Isn't just http-clients and core enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what you mean. All of the dependencies pulled in by a service client need to be OSGi compatible, which includes flow.

@dagnir dagnir merged commit 2614631 into aws:master Sep 24, 2018
aws-sdk-java-automation added a commit that referenced this pull request Feb 4, 2020
…29d6e7ea

Pull request: release <- staging/8bb6144f-3114-42ce-83b0-12b229d6e7ea
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