[jbosstools-issues] [JBoss JIRA] (JBIDE-12608) Replace local.* properties and profiles by Maven mirroring

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-12608:
----------------------------------------

This job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk.component--openshift-sandbox/3 shows that using the hudson-settings.xml works fine (it remove usage of local.composite profile in favor of mirroring of jbosstools-nightly-staging-composite, and then resolves against local mirror)
                
> Replace local.* properties and profiles by Maven mirroring
> ----------------------------------------------------------
>
>                 Key: JBIDE-12608
>                 URL: https://issues.jboss.org/browse/JBIDE-12608
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: Build/Releng
>    Affects Versions: 4.0.0.Alpha2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.0.0.Beta1
>
>         Attachments: hudson-settings.xml, hudson-settings.xml
>
>
> Currently, we deal with optimization for Jenkins by multiple local.* properties and local.* profiles.
> Those properties and profiles are just used in order to replace repository URL.
> Maven has the concept of mirroring for that, and without adding a profile, we can tell Maven to consume another URL for a given repo. Moreover, Tycho will support mirrors for repo in .target files starting from 0.16.0.
> WE should move to the mirror approach since it keeps things clear and separate issues: pom describe build, mirror allow to override repo without any change.
> Seems like Maven supports having 2 settings.xml files as input (one with -gs and one with -s), so no big difficulty here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira