JiriOndrusek opened a new pull request #3781: URL: https://github.com/apache/camel/pull/3781
Issue: https://issues.apache.org/jira/browse/CAMEL-14950 @davsclaus , @oscerd I've noticed small error with big impact. Test for scenario with servlet was testing scenario without servlet. This simple change it fixes, but there is a problem. By previous commit version of servlet-api was set to 3.1.0.Final to be consistent with camel - correct move. *But undertow is not able to start servlet without 4.0 api.* So with this fix, test will show an error *NoClassDefFoundError: javax/servlet/http/MappingMatch* (error will be solved in case of servlet-api org.jboss.spec.javax.servlet:jboss-servlet-api_4.0_spec) Which seems to be blocker for this change. What do you think? Only solution I see is to keep servlet-api required for undertow in pom. [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful subject line and body. [ ] If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. [ ] Run `mvn clean install -Psourcecheck` in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically. Below are the contribution guidelines: https://github.com/apache/camel/blob/master/CONTRIBUTING.md ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
