[ https://issues.apache.org/jira/browse/WSS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alessio Soldano updated WSS-496: -------------------------------- Summary: "tests" classifier artifacts dependencies should not have compile scope (was: "tests" classifier artifacts should not have compile scope) > "tests" classifier artifacts dependencies should not have compile scope > ----------------------------------------------------------------------- > > Key: WSS-496 > URL: https://issues.apache.org/jira/browse/WSS-496 > Project: WSS4J > Issue Type: Bug > Components: WSS4J Core > Reporter: Alessio Soldano > Assignee: Colm O hEigeartaigh > Fix For: 2.0.0 > > > On trunk (2.0.0-SNAPSHOT), there're some maven artifacts which are built with > "tests" classifier and look to be used for tests. > Unfortunately, the ws-security-stax/pom.xml is not setting the scope for one > of them (org.apache.wss4j:wss4j-ws-security-dom:tests), resulting in polluted > transitive dependencies trees in any project that consumes Apache WSS4J. > This is a problem for example because the CryptoFactory uses the classloader > for resolving crypto properties and can hence end up reading from the test > artifact while that has nothing to do with the final user application. -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ws.apache.org For additional commands, e-mail: dev-h...@ws.apache.org