Fwiw, one possible suspect is the following code:

https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L1484-L1497
The access to the config properties are not synchronized.

2018-04-09 23:54 GMT+02:00 Guillaume Nodet <gno...@apache.org>:

>
>
> 2018-04-09 23:38 GMT+02:00 Greg Logan <gregorydlo...@gmail.com>:
>
>> Hi all,
>>
>> Building Opencast (https://github.com/opencast/opencast), our final step
>> is packaging into assemblies (assemblies/pom.xml).  Since I haven't seen
>> this elsewhere it's hard to really give you a small reproducible test case,
>> but at least it's part of the final steps rather than requiring a full
>> build.
>>
>> Which project should I file the bug against?  Karaf itself?  Or Maven
>> Assembly Plugin?
>>
>
> Karaf please.
>
> Is there a specific assembly failing ? When you say the config.properties
> file is corrupted, what does it look like ?
>
>
>>
>> Thanks,
>> G
>>
>> On Mon, Apr 9, 2018 at 1:20 PM, Guillaume Nodet <gno...@apache.org>
>> wrote:
>>
>>> It may be a thread issue while building the assembly.
>>> Please raise a JIRA and attach what you have, a way to reproduce the
>>> issue would be helpful.
>>>
>>> Guillaume
>>>
>>> 2018-04-09 19:15 GMT+02:00 Greg Logan <gregorydlo...@gmail.com>:
>>>
>>>> Hi all,
>>>>
>>>> We're running into an issue where rarely (1/20 or so) of our assembly
>>>> builds end up with a corrupted config.properties file - multiple libraries
>>>> are missing from the file and thus our code fails to start because the
>>>> dependencies are missing.  I took a quick look through JIRA and could not
>>>> find a related issue, but I could also be searching for the wrong things...
>>>>
>>>> Is this something that rings a bell with anyone?  I have a snapshot of
>>>> both a known good, and known bad build, but subsequent builds of the same
>>>> version of our codebase yield working builds.  There don't appear to be any
>>>> error messages in the final assembly packaging logs, so I'm not even really
>>>> sure where to start debugging.
>>>>
>>>> G
>>>>
>>>
>>>
>>>
>>> --
>>> ------------------------
>>> Guillaume Nodet
>>>
>>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
>
>


-- 
------------------------
Guillaume Nodet

Reply via email to