Jakub Narloch created ARQ-1834: ---------------------------------- Summary: Spring extension - Optional/Conditional feature loading Key: ARQ-1834 URL: https://issues.jboss.org/browse/ARQ-1834 Project: Arquillian Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Jakub Narloch Spring Boot gives my the idea on how to workaround the problem that Arquillian is versioned completly seperatly from the Spring Framework. Causing problems when trying to target functionality from specific Spring version. At the moment this has been handled by providing many artifacts each with support for different Spring version. But I wonder whether this could not be done a bit smarter with a form of dynamic recognition what is actually avaible on the classpath and in the same time enabling proper extension and or version for which this is targeted. Either way this would be rather a task for next major Spring extension version, becouse most likely this would break the backward compatibility and would probably will mean that we may change the organization of the extension artifacts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)