-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
chore: merge branch dev
to main
#232
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Annotations required reflection and working with them turned out to be rather cumbersome. The annotations have been replaced with properties for the most part. BREAKING CHANGE: Patch annotations have been removed. PatcherException is now thrown in various places. PatchBundleLoader is now a map of patches associated by their name. Patches are now instances.
This allows other sub-projects to exist.
This commit introduces an annotation processor for patches. Patches can use the `@Patch` instead of super constructor parameters. BREAKING CHANGE: The manifest for patches has been removed, and the properties have been added to patches. Patches are now `OptionsContainer`. The `@Patch` annotation has been removed in favour of the `@Patch` annotation from the annotation processor.
# [15.0.0-dev.1](v14.2.2...v15.0.0-dev.1) (2023-09-04) * feat!: Add patch annotation processor ([3fc6a13](3fc6a13)) * feat!: Remove patch annotations ([3b4db3d](3b4db3d)) ### Features * Add patch annotation processor ([#231](#231)) ([a29931f](a29931f)) ### BREAKING CHANGES * The manifest for patches has been removed, and the properties have been added to patches. Patches are now `OptionsContainer`. The `@Patch` annotation has been removed in favour of the `@Patch` annotation from the annotation processor. * Patch annotations have been removed. PatcherException is now thrown in various places. PatchBundleLoader is now a map of patches associated by their name. Patches are now instances.
# [15.0.0-dev.2](v15.0.0-dev.1...v15.0.0-dev.2) (2023-09-06)
BREAKING CHANGE: This renames packages and the Maven package.
BREAKING CHANGE: `PatchBundleLoader` is not a map anymore
# [15.0.0-dev.3](v15.0.0-dev.2...v15.0.0-dev.3) (2023-09-06) ### Bug Fixes * Make `CompatiblePackage.versions` a property ([67b7dff](67b7dff)) * Use correct module name ([080fbe9](080fbe9)) * feat Use `Set` as super type for `PatchBundleLoader` ([4b76d19](4b76d19)) ### BREAKING CHANGES * `PatchBundleLoader` is not a map anymore * This renames packages and the Maven package.
…ersions` is empty
…list If a patch is used as a dependency, it would be present in `dependencyResolutionMap`. If that patch would also be annotated, then the generated patch would depend on itself.
Otherwise the log will not include what originally raised the exception.
BREAKING CHANGE: This gets rid of the public constructor.
# [15.0.0-dev.4](v15.0.0-dev.3...v15.0.0-dev.4) (2023-09-13) ### Bug Fixes * Account for source patch dependency for tests ([6918418](6918418)) * Always make the generated patch depend on the source patch ([8de3063](8de3063)) * Catch correct exception ([637d487](637d487)) * Delegate `PatchBundleLoader` by mutable set of patches ([9a109c1](9a109c1)) * Do not resolve the proxied patch to the proxy in the dependency list ([e112837](e112837)) * Do not set `CompatiblePackage.versions` if `@CompatiblePackage.versions` is empty ([6b1e0a1](6b1e0a1)) * Filter for patches correctly ([4bc4b0d](4bc4b0d)) * Find dependency in `context.allPatches` ([670f015](670f015)) * Log the correct patch names ([9fdb8f0](9fdb8f0)) * Print patch name instead of class name ([4e7811e](4e7811e)) * Print stack trace of exception ([aa71146](aa71146)) * Run code-block if `executablePatches` does not yet contain `patch` ([1d7aeca](1d7aeca)) * Suppress logger when loading patches in `PatchBundleLoader` ([72c9eb2](72c9eb2)) ### Code Refactoring * Internalize processor constructor ([a802d0d](a802d0d)) ### BREAKING CHANGES * This gets rid of the public constructor.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request will merge branch
dev
tomain
.