Sorry was too fast with my send button...
Hi,
at the moment i trying to dive into handling of MANIFEST.MF file [1], [2]...
If i create a MANIFEST.MF my own and let maven-jar-plugin take that file
via useDefaultManifest (target/classes/META-INF/MANIFEST.MF) it will be
extended by several entries:
My own file:
Manifest-Version: 1.0
Test: This is my MANUALLY CREATED MANIFEST FILE
Second: This is the second line.
After running through maven-jar-plugin you will get the following:
Manifest-Version: 1.0
Second: This is the second line.
Test: This is my MANUALLY CREATED MANIFEST FILE
Built-By: kama
Build-Jdk: 1.7.0_21
Created-By: Apache Maven 3.1.1
Archiver-Version: Plexus Archiver
There are comming up two questions:
1. Does it make sense to add only Manifest-Version
and Build-Jdk entries. But nothing else if i use
my own MANIFEST.MF file.
Based on what i have read on [3] it would make sense.
2. Currently the handling internally does not kepp the order
of the original entries which is based on the used implementation
(HashMap, Hashtable etc. which makes sense.
Wouldn't it be better to keep the original order of elements?
So based on what i can see we have handling of
manifest in maven-archiver component and in plexus-archiver ?
[1] https://issues.apache.org/jira/browse/MJAR-195
[2] https://issues.apache.org/jira/browse/MJAR-193
[3] https://docs.oracle.com/javase/tutorial/deployment/jar/defman.html
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
