[jbosstools-issues] [JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator
[
https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-20168 at 6/30/15 3:51 PM:
-------------------------------------------------------------
Seems that buildinfo.json reader isn't happy with my manually created json, and builds
are failing as a result. I've removed the xulrunner buildinfo.json file because
it's trying to compare the SHA in that file to the one in the MANIFEST.MF (and there
is none because this was built >2 years ago).
So... maybe we need to rebuild xulrunner to use the latest parent pom & generate it:
https://github.com/jbosstools/jbosstools-xulrunner/pull/15
was (Author: nickboldt):
Seems that buildinfo.json reader isn't happy with my manually created json.
So... maybe we need to rebuild xulrunner to use the latest parent pom & generate it:
https://github.com/jbosstools/jbosstools-xulrunner/pull/15
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)