Yes you are right but even member of our documentation team didn't know that the file is not empty.
I have just shown the content of the file to one of the developers and he was shocked to see his name in the path.
catapult.log.zip\C:\Users\username.surname\AppData\Local\Temp
Users should be able ...
Search found 3 matches
- Mon Sep 24, 2012 9:08 am
- Forum: Flare's General Discussion
- Topic: Catapult log when publishing
- Replies: 25
- Views: 25479
- Mon Sep 24, 2012 8:41 am
- Forum: Flare's General Discussion
- Topic: Catapult log when publishing
- Replies: 25
- Views: 25479
Re: Catapult log when publishing
I have only ever seen empty catapult.log.zip files in our published documentation. The documentation team have a batch file that attempts to delete the files but that process often fails.
I can see your point that the file may be useful but from my point of view, it is not right to provide a ...
I can see your point that the file may be useful but from my point of view, it is not right to provide a ...
- Mon Sep 24, 2012 7:49 am
- Forum: Flare's General Discussion
- Topic: Catapult log when publishing
- Replies: 25
- Views: 25479
Re: Catapult log when publishing
As an outsider who doesn't use the tool but rather uses the published output to include in installation packages, I really find it hard that developers find it acceptable to add such file (catapult.log.zip) to the published folder. A file which has nothing to do with what we want to publish.
What ...
What ...