[jbosstools-dev] ACTION REQUIRED: Project leads, please tag your projects [ branch jbosstools-4.3.0.Beta1x -> tag jbosstools-4.3.0.Beta1 ]

[Max Rydahl Andersen]

On 26 Jun 2015, at 16:04, Nick Boldt wrote:

> Those were built BEFORE we had buildinfo.json files as part of the 
> builds. So, therefore "Build info file not accessible".
>
> Would you prefer a null or "" to a useful error message?

I would prefer two things:

1) That the format of the file is consistent so it is easy to parse.
    In this case it could be okey, just a bit weird having to say "if v 
is not type dict then read string as error".

2) That if we have missing pieces in our build to have consistent info 
about which builds are used we should
    get that fixed ASAP. i.e. in this case either get those built or 
still use old way to get this info for those two builds
    to at least have the info recorded so we can get them properly 
tagged.

Can you tell which tags to use for the tag ?

/max

>
> On 06/25/2015 09:13 AM, Max Rydahl Andersen wrote:
>> On 23 Jun 2015, at 21:32, Max Rydahl Andersen wrote:
>>
>>> On 23 Jun 2015, at 21:13, Nick Boldt wrote:
>>>
>>>> Do you mean this?
>>>>
>>>> http://download.jboss.org/jbosstools/static/mars/development/updates/core/4.3.0.Beta1/buildinfo.json
>>>>
>>>
>>
>> This file has the following segment:
>>
>> "http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/":
>> "Build info file not accessible:
>> http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/buildinfo.json",
>>
>> "http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/": 
>> "Build
>> info file not accessible:
>> http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/buildinfo.json"
>>
>>  }
>>
>> how come ?
>>
>> shouldn't this contain the actual used content ?
>>
>> /max
>> http://about.me/maxandersen
>
> -- 
> Nick Boldt :: JBoss by Red Hat
> Productization Lead :: JBoss Tools & Dev Studio
> http://nick.divbyzero.com


/max
http://about.me/maxandersen