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

Cleanup some things after removal of joda-time hack #18959

Closed
wants to merge 3 commits into from

Conversation

rmuir
Copy link
Contributor

@rmuir rmuir commented Jun 19, 2016

After removing this hack, we can cleanup a bit. Particularly important is to be able to treat codebases as a unique thing (since ES jar is no longer duplicated on the classpath to be "in front of" joda-time). This gives a lot of internal checks in case something goes wrong.

I know the other day i accidentally installed groovy as a plugin (its already a module), and the error was strange. So using Set and checking the return values is an easy improvement.

urlElements[i] = PathUtils.get(element).toUri().toURL();
URL url = PathUtils.get(element).toUri().toURL();
if (urlElements.add(url) == false) {
throw new IllegalStateException("jar hell!" + System.lineSeparator() +
Copy link
Contributor

Choose a reason for hiding this comment

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

indentation is off here?

@s1monw
Copy link
Contributor

s1monw commented Jun 20, 2016

LGTM left some minors

@clintongormley clintongormley added >enhancement :Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts v5.0.0-alpha5 and removed v5.0.0-alpha4 labels Jun 20, 2016
@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

1 similar comment
@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

rjernst added a commit to rjernst/elasticsearch that referenced this pull request Mar 15, 2017
After the removal of the joda time hack we used to have, we can cleanup
the codebase handling in security, jarhell and plugins to be more picky
about uniqueness. This was originally in elastic#18959 which was never merged.

closes elastic#18959
rjernst added a commit that referenced this pull request Mar 21, 2017
After the removal of the joda time hack we used to have, we can cleanup
the codebase handling in security, jarhell and plugins to be more picky
about uniqueness. This was originally in #18959 which was never merged.

closes #18959
rjernst added a commit that referenced this pull request Mar 21, 2017
After the removal of the joda time hack we used to have, we can cleanup
the codebase handling in security, jarhell and plugins to be more picky
about uniqueness. This was originally in #18959 which was never merged.

closes #18959
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Packaging RPM and deb packaging, tar and zip archives, shell and batch scripts >enhancement help wanted adoptme Team:Delivery Meta label for Delivery team v5.4.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants