Nontrivial aspects of hyphenation in technical texts

Here, I wondered how to correctly transfer such constructions as file names, full class names with namespaces, paths, urls, and similar things found in technical texts?

For example: "Database connection parameters must be specified in the file Testdatabase.Hibernate.cfg.xml". Where to put the hyphenation in the word "Testdatabase.Hibernate.cfg.xml"?

Options:
')
0) Do not transfer. Also, of course, an option. But when the text is stretched wide and giant spaces appear, it will become clear that only the assholes make up this way .

1) By syllables
Test¬da¬babase.Hi¬ber¬nate.cfg.xml
The disadvantage of this method seems to me that the hyphen at the end of the line may be mistaken as part of the file name.

2) After points
Testdatabase.¬Hibernate.¬cfg.¬xml
There is a danger that the dot will be perceived as the end of a sentence.

3) Before dots
Testdatabase¬.Hibernate¬.cfg¬.xml
The dot at the beginning of the line looks pretty dumb.

I also asked this question on a litera. Ru, we will see what they answer.

Thus, I have not yet decided for myself. Maybe someone from the surrounding complement this text with a new argument "for" or "against"?

UPD: After examining some of the books on Google Books, I came to the conclusion that the hyphenation mark is not used for hyphenation according to urls, paths and namespaces, but it is broken down into parts by points or slashes. At the same time, a dot or a slash always remains at the end of a line.

UPD 2: Answer literacy.ru:
“The rules of Russian spelling, of course, do not regulate such cases. It is unlikely that such chains are subject to transfer. ”