Most of the devs are using (I hope so) jbosstools/jbdevstudio multiple TP's in eclipse, but sometimes, when new features/bundles are added into TP, they still need to do builds using maven to verify it is still working for individual module or set of individual modules. To simplify the knowledge about how to build/test proposed changes I suggest to disable default multiple2repo profile for jbosstools/jbdevstudio multiple target platforms and activate it only for jenkins by testing ${env.WORKSPACE} property. That simple change would reduce maven build execution to default:

mvn clean install

and there would be no need to worry about -P-multiple2repo.

(see attached PR for details)