Skip to content

Add LICENSE and NOTICE files to generated client packages #542

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

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

jonathan343
Copy link
Contributor

The LICENSE and NOTICE files are currently added manually added to the client packages (see example PR).

This PR updates the code generator to generate an Apache-2.0 LICENSE file and NOTICE file with Copyright <currentYear> Amazon.com, Inc. or its affiliates. All Rights Reserved. at the top-level of the package.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jonathan343 jonathan343 requested a review from a team as a code owner August 14, 2025 19:24
/**
* This section controls the entire generated NOTICE
*
* <p>An integration may want to use this if they want to programmatically
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason we have the

tag here?

private static void writeLicense(
GenerationContext context
) {
context.writerDelegator().useFileWriter("LICENSE", writer -> {
Copy link
Contributor

Choose a reason for hiding this comment

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

How is this code AWS specific. I haven't tested it, so I could be wrong, but I think this will get generated for all SDKs, even non-AWS ones.

Does Smithy force a license that a customer must use? I would expect this to be a generic license that was smithy's default, then have that be overwritten by an AWS specific interceptor.

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