Skip to content

Conversation

@gosar
Copy link
Contributor

@gosar gosar commented Feb 16, 2023

Motivation and Context

As part of Smithy Reference Architecture, we are defining new Identity and Auth interfaces that will reside in new modules.

Modifications

This change adds new modules and makes existing modules will depend on these new modules for backwards-compatibility. The actual code changes will be done in separate PRs. This change preps the module changes only. To allow the build to succeed, Placeholder.java classes are added to make the module jar non-empty and also maven-dependency-plugin has been temporarily disabled.

Testing

./mvnw clean install

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 added tests to cover my changes
  • All new and existing tests passed
  • I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
  • My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

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

These modules are empty for now.
So there is a jar created for the module.
Currently have setup dependencies in maven but there is not
actual code dependencies across these modules. Once new
code is added to the modules this will be undone.
@gosar gosar requested a review from millems February 16, 2023 00:02
Comment on lines 34 to 35
<!-- TODO: this is not present in all pom.xml files. Is there a reason, or just a miss -->
<url>https://aws.amazon.com/sdkforjava</url>
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably just a miss.. Unless it's inherited from the parent?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

removed these TODOs and another one for HTTP v/s Http as we use HTTP in other modules already.

Copy link
Contributor

Choose a reason for hiding this comment

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

Must just be a miss, then!

@gosar gosar marked this pull request as ready for review February 16, 2023 00:50
@gosar gosar requested a review from a team as a code owner February 16, 2023 00:50
@gosar gosar changed the base branch from master to feature/master/sra-identity-auth February 16, 2023 01:36
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 7 Code Smells

85.7% 85.7% Coverage
0.0% 0.0% Duplication

@gosar gosar merged commit 5db07c8 into feature/master/sra-identity-auth Feb 17, 2023
@gosar gosar deleted the gosar/sra-ia-module-changes branch April 1, 2023 00:02
aws-sdk-java-automation pushed a commit that referenced this pull request Mar 24, 2025
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