Re: [che-dev] Purpose of misc.xml in project metadata

[Vladislav Zhukovskii <vzhukovskii@xxxxxxxxxxx>]

This file can contains temporary system meta data related to project which shouldn't be in project.json. But unfortunately, to store such data you need to modify the model in source code. There is historically.

2015-11-01 13:08 GMT+02:00 Sharafy, Tareq <tareq.sharafy@xxxxxxx>:

Hi,

Right now Che has a special file in project metadata folder called "misc.xml". As I see in the source code, all the properties in .codenvy/misc.xml (updated, created, contentroot) are also available in the standard project.json. I'm not figuring out the purpose of actually having misc.xml, especially that it is never really used – every function that saves misc.xml in che-core-api-project does that together with modifying the standard project configuration accordingly. I could not find any usage outside che-core-api-project.

The existence of this file is causing many hacks in VFS and Git extensions of Che, which all seem to have the goal of simply ignoring the file. In the case of VFS, the situation is worse since VFS implementations are not aware of the project API and have the ".codenvy" folder name hard-coded dirtily.

My question is – what is the purpose of having the misc.xml file and the relevant ProjectMisc class in the source code?

thank you
Tareq Sharafy
Cloud Development Experience | SAP Labs Israel | 15 Hatidhar st, Raanana 43665, Israel
T +972-(0)7-4732-1647 | F +972-(0)9-777-5618

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev

--

 | Vladyslav Zhukovskyi | Java Developer | +38063-435-53-19 | Codenvy.com