Thanks ! I knew that the lines could be broken, but I did not know that
they could be broken in the middle of a jar name! So I thought this was
one cause of my problem. In fact, it is not. The problem is with the
assembly descriptors. But I think I will eventually find a solution know
I "know" where to look for;-)
Pierre-Yves
Thorsten Heit a écrit :
Hi,
- Even worst if possible, the plugin creates broken manifest. The lines
are cut after 70 characters, in the middle of a jar name. This makes the
<addClasspath>true</addClasspath> option completely useless. I though I
could use
<manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
instead, using my own manifest. This would be an inconvenient, because I
would have to update this file each time a dependency is added to the
application, but at least it would work. Not at all. the plugin still
breaks the line after 70 characters.
>From the Jar file specification:
(...)
Notes on Manifest and Signature Files
(...)
* Line length:
No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should be continued on extra lines (each starting with a single SPACE).
HTH
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
