This PR "fixes" this behavior because each entry will be represented in its own line.
However, there is the possibility that this causes an invalid MANIFEST.MF file if the complete value of one entry exceeds the 72 bytes per line limit, e.g., org.emoflon.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.
IMO, this is more desirable compared to the previous implementation that broke multiple (existing) files repeatedly.
Before merging this PR, the manifest mechanism in
emoflon-core
produced invalidMANIFEST.MF
files in some of the test cases.,
-> This broke the files in some situations.Example:
This PR "fixes" this behavior because each entry will be represented in its own line. However, there is the possibility that this causes an invalid
MANIFEST.MF
file if the complete value of one entry exceeds the 72 bytes per line limit, e.g.,org.emoflon.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
. IMO, this is more desirable compared to the previous implementation that broke multiple (existing) files repeatedly.Tested with: