Task namespace usage should not require concurrent backport JARs [SPR-6161]

[spring-projects-issues]

Mark Fisher opened SPR-6161 and commented

This should not happen:

java.lang.IllegalStateException: Failed to load ApplicationContext
...
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class path resource [...];
nested exception is org.springframework.beans.FatalBeanException: Invalid NamespaceHandler class [org.springframework.scheduling.config.TaskNamespaceHandler] for namespace http://www.springframework.org/schema/task: problem with handler class file or dependent class; nested exception is java.lang.NoClassDefFoundError: edu/emory/mathcs/backport/java/util/concurrent/ThreadPoolExecutor$AbortPolicy

---

Affects: 3.0 RC1

Issue Links:

• INT-810 Remove the 'thread-pool-task-executor' element now that Spring 3 provides a "task" namespace ("is depended on by")
• ExecutorBeanDefinitionParser must not directly depends on backport concurrent [SPR-6250] #10918 ExecutorBeanDefinitionParser must not directly depends on backport concurrent ("is duplicated by")

Referenced from: commits e2af25b