[jbosstools-issues] [JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-16220:
------------------------------------

Last time I played with this approach to building everything in one place was December, apparently.

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-submodules_master/

> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
>                 Key: JBIDE-16220
>                 URL: https://issues.jboss.org/browse/JBIDE-16220
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.2.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>             Fix For: 4.2.x
>
>         Attachments: buildlog_maven311.txt
>
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
>  "git submodule" started learning a new mode to integrate with the
>    tip of the remote branch (as opposed to integrating with the commit
>    recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc.



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