Description of problem: The jbpm-designer-client is defined as test scope in jbpm-designer/jbpm-designer-backend/pom.xml(See below). Might I suggest that we remove the test scope? In product build, we will remove the test scope, but jbpm-designer-client shouldn't be removed in this case. So I am asking if we could remove the "test" scope for jbpm-designer/jbpm-designer-backend/pom.xml. <dependency> <groupId>org.jbpm</groupId> <artifactId>jbpm-designer-client</artifactId> <scope>test</scope> </dependency> Version-Release number of selected component (if applicable): How reproducible: jbpm-designer CR2 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Unclear why this would be necessary, we added test scope on purpose (and it seems to work for community build), unclear why it would need to be removed?
After discussed with Tiho, I think the concern for using "test" scope is to exclude them in war. I think "provided" is the preferable "<scope>" for dependencies in this case rather than "test" if you don't want to include it in war. The reason I am asking to remove it is that: We need to remove "test scope" depenencies in product build since it cause much more extra efforts to build them , importing them etc. But in this case, we hit error after remove a jbpm-designer artifact.
Ryan, I guess it makes sense to exclude artefacts that are only used in test-scope if you're not interested in those. But I don't think that you should exclude an artefact from the entire build when it's used as a test scope in one component (as it might just as well be used in compile-scope in another). I guess you should only exclude an artefact if it's only used in test-scope in all components, right?
Why is this dev - ? Looks like the work is still pending on Ryan..