Skip to content
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

Strongly reference KNet jar #152

Closed
masesdevelopers opened this issue Nov 26, 2022 · 0 comments · Fixed by #153
Closed

Strongly reference KNet jar #152

masesdevelopers opened this issue Nov 26, 2022 · 0 comments · Fixed by #153
Assignees
Labels
enhancement New feature or request KNet KNet related issue

Comments

@masesdevelopers
Copy link
Contributor

Is your feature request related to a problem? Please describe.
If in the deployment folder there are multiple version of knet-*.jar the last version is not chosen because the operating system reports the versions in lexicographical order and the oldest one is the first and chosen.

Describe the solution you'd like
Strongly set the version during jars import clause in this line:

lst.Add(JarRootPath != null ? Path.Combine(JarRootPath, "*.jar") : JarRootPath);

using the version defined on the assembly executing the code. JAR and assembly is expected have the same version.

Describe alternatives you've considered
Set the version each time the version change.

Additional context
See masesgroup/JNet#100

@masesdevelopers masesdevelopers added enhancement New feature or request KNet KNet related issue labels Nov 26, 2022
@masesdevelopers masesdevelopers self-assigned this Nov 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request KNet KNet related issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant