[jbosstools-issues] [JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-20168 at 7/7/15 2:42 PM:
------------------------------------------------------------

OK, so instead of rebuilding xulrunner, I've done three things:

a) support the usecase where there's an buildinfo.json file for the build, but the Eclipse-SourceReferences SHA is null / missing
b) enable the source fetcher to fetch from the buildinfo.json's SHA, rather than just the SHA in the upstream project's MANIFEST.MF
c) create a buildinfo.json file for Xulrunner, which the JBT agg site can use to fetch sources and aggregate into its combined buildinfo.json file.

Commits: 

https://github.com/jbosstools/jbosstools-maven-plugins/commit/bfee320d5f5e5b83551e99649e228969cef95fb5
https://github.com/jbosstools/jbosstools-build-sites/commit/9491c23b80c3e4c01bc8b4e8127b4f9c4aaad7cd



was (Author: nickboldt):
OK, so instead of rebuilding xulrunner, I've done three things:

a) support the usecase where there's an buildinfo.json file for the build, but the Eclipse-SourceReferences SHA is null / missing
b) enable the source fetcher to fetch from the buildinfo.json's SHA, rather than just the SHA in the upstream project's MANIFEST.MF
b) create a buildinfo.json file for Xulrunner, which the JBT agg site can use to fetch sources and aggregate into its combined buildinfo.json file.

Commits: 

https://github.com/jbosstools/jbosstools-maven-plugins/commit/bfee320d5f5e5b83551e99649e228969cef95fb5
https://github.com/jbosstools/jbosstools-build-sites/commit/9491c23b80c3e4c01bc8b4e8127b4f9c4aaad7cd


> create buildinfo.json files for old project builds which predate buildinfo.json generator
> -----------------------------------------------------------------------------------------
>
>                 Key: JBIDE-20168
>                 URL: https://issues.jboss.org/browse/JBIDE-20168
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.Beta2
>
>
> Max asked:
> {quote}
> i'm asking what shah's was used in the build for these components.
> No sure if you are trolling me by us keeping having these conversations everytime we need to tag :)
> Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right.
> and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ?
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)