Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Use different class loaders for scanning annotations and classes required for plugin #76

Closed
gigaSproule opened this issue May 30, 2018 · 1 comment
Closed

Use different class loaders for scanning annotations and classes required for plugin #76

gigaSproule opened this issue May 30, 2018 · 1 comment
Labels
enhancement
Milestone
1.0.6

Comments

@gigaSproule
Copy link
Owner

Currently the same class loader is used for both scanning annotations and for custom classes required for the plugin. This doesn't really make much sense and could (in theory) cause version conflict issues. Instead, their should be a class loader for scanning annotations and using the current class loader for the plugin.
@gigaSproule gigaSproule added this to the 1.0.5 milestone May 30, 2018
@gigaSproule gigaSproule mentioned this issue May 30, 2018
Closed
@gigaSproule gigaSproule mentioned this issue May 31, 2018
Closed
@gigaSproule gigaSproule modified the milestones: 1.0.5, 1.0.6 Jun 6, 2018
gigaSproule added a commit that referenced this issue Nov 29, 2018
@gigaSproule
Bumped gradle to version 5, bumped swagger version to 1.5.21, bumped …
00f0b2a 
…other versions to latest, added new classloader to fix issue #76 and added support for Scala
@gigaSproule
Copy link
Owner Author

Should be fixed by PR #128

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
1.0.6
Development

No branches or pull requests
1 participant
@gigaSproule