Xavier - we should definitely check if the jax-rs really is the culprit (or just the last job that updated the label) AND then look if we really need to scan the full classpath at this time of the build.
About putting in background it probably would not help since your job is dependent on the project build to finish anyway (if I understand the job purpose correctly). Worth to check though.
Is there any rules we can apply to the scanning to reduce it looking everywhere?
jar names is a real bad thing to base logic on![](https://issues.jboss.org/images/icons/emoticons/wink.gif)
Xavier - we should definitely check if the jax-rs really is the culprit (or just the last job that updated the label) AND then look if we really need to scan the full classpath at this time of the build.
About putting in background it probably would not help since your job is dependent on the project build to finish anyway (if I understand the job purpose correctly). Worth to check though.
Is there any rules we can apply to the scanning to reduce it looking everywhere?