Skip to content

Thk v1.15.6 #77

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 5 commits into from
Nov 1, 2023
Merged

Thk v1.15.6 #77

merged 5 commits into from
Nov 1, 2023

Conversation

TomKimsey
Copy link
Collaborator

No description provided.

@TomKimsey TomKimsey requested a review from alexjhawk November 1, 2023 14:29
@TomKimsey TomKimsey self-assigned this Nov 1, 2023
# Version: 2.1
#
# This action is configured to automatically run when a push
# is made or pull request is merged to the `main` or `master`
# branch.

name: Compile Test
name: Package Test
Copy link
Collaborator

Choose a reason for hiding this comment

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

What do you think about Package Build Test or Packaging Test? I don't think it's a huge concern, but Package Test just seems off to me.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This is still in draft. not sure why i added a reviewer yet.

Im fine with "Package Test" or "Build Test", "Package Test" doesnt bother me at all.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Do you want "Build Test"

Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm okay with either, although Build Test may be a bit more descriptive as it covers the Javadoc checking too.

@TomKimsey TomKimsey force-pushed the THK_v1.15.6 branch 2 times, most recently from 98f9f52 to 476e1c3 Compare November 1, 2023 14:46
@TomKimsey TomKimsey requested a review from alexjhawk November 1, 2023 14:50
@TomKimsey TomKimsey marked this pull request as ready for review November 1, 2023 14:50
alexjhawk
alexjhawk previously approved these changes Nov 1, 2023
@@ -171,6 +171,7 @@
<dependencySourceExcludes>
<dependencySourceExclude>com.hms_networks.americas.sc.mvnlibs:ewon-etk:*</dependencySourceExclude>
</dependencySourceExcludes>
<failOnWarnings>true</failOnWarnings>
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should be carried upstream to the starter project.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yeah I agree

# Version: 2.1
#
# This action is configured to automatically run when a push
# is made or pull request is merged to the `main` or `master`
# branch.

name: Compile Test
name: Package Test
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm okay with either, although Build Test may be a bit more descriptive as it covers the Javadoc checking too.

This test now uses the package command to test both compilation and
javadoc creation. This ensures both the code is able to be built and the
javadocs are valid.
@TomKimsey TomKimsey requested a review from alexjhawk November 1, 2023 14:59
Javadoc warnings now trigger build to fail to ensure that the
documentation is complete and accurate.
@TomKimsey TomKimsey merged commit 5837478 into main Nov 1, 2023
@TomKimsey TomKimsey deleted the THK_v1.15.6 branch November 1, 2023 15:59
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