[jbosstools-issues] [JBoss JIRA] (JBIDE-17280) Disable mirroring of multiple target platforms to simplify local builds

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968282#comment-12968282 ] 

Mickael Istria commented on JBIDE-17280:
----------------------------------------

Updated CI job to add the "-Pmultiple2repo" profile when it is necessary: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1290554e47b3750069643f7076d61de7c50f0e39
I also updated the user documentation: https://github.com/jbosstools/jbosstools-devdoc/commit/3f3e86f753edfcafcffd6320ab4c6d3fa8c5641b

I commented the PR.

> Disable mirroring of multiple target platforms to simplify local builds
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-17280
>                 URL: https://issues.jboss.org/browse/JBIDE-17280
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Denis Golovin
>            Assignee: Mickael Istria
>             Fix For: 4.2.0.Beta2
>
>
> 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: 
> {code}mvn clean install{code}
> and there would be no need to worry about -P-multiple2repo.
> (see attached PR for details)



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)