-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-28070 Replace javax.servlet.jsp dependency with tomcat-jasper #5607
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
Changes from all commits
8378368
d43f8b9
f337f39
b32f263
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -87,6 +87,11 @@ | |
| <exclude>junit:junit</exclude> | ||
| <exclude>org.hamcrest:hamcrest-core</exclude> | ||
| <exclude>org.mockito:mockito-core</exclude> | ||
| <!-- Exclude transitive dependencies of tomcat-jasper, not needed at runtime --> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We do not need this for our release binaries? For client I think it is OK that we do not need to start a web server, but for hbase we do need to start master/rs webs? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I tested out master startup in local mode. Was able to start with just tomcat-jasper, tomcat-jasper-el and tomcat-el-api and hence removed others. Also these 3 jars bring in all those classes which are getting removed from classpath due to removal of javax.el and javax.servlet.jsp. Can keep these for safer side. Please let me know WDYT. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Then we could just exclude them in the dependencyManagement or dependencies section in our pom file? We need to them in tests? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes @Apache9, these are required at compile time to generate the jsp pages but i was able to load web pages w/o them during runtime. Hence excluding from assembly. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Gentle ping @Apache9. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @Apache9 seems someone is interested in this patch. Could you please have another look at the changes and the above discussion and see if we are good here. Please let me know if otherwise. |
||
| <exclude>org.apache.tomcat:tomcat-juli</exclude> | ||
| <exclude>org.apache.tomcat:tomcat-api</exclude> | ||
| <exclude>org.apache.tomcat:tomcat-util-scan</exclude> | ||
| <exclude>org.apache.tomcat:tomcat-util</exclude> | ||
| </excludes> | ||
| </dependencySet> | ||
| </dependencySets> | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.