Open missedone opened 8 years ago
if we build with gradle (build.gradle
), the generate manifest is correctly, but I know the 6.9.13.x were released with kobalt which use an out of date version of MANIFEST.MF, since looks like kobalt can't dynamically generate it.
Correct Nick, that's exactly what happened.
Cédric
On Fri, Oct 7, 2016 at 5:35 PM, Nick Tan notifications@github.com wrote:
if we build with gradle (build.gradle), the generate manifest is correctly, but I know the 6.9.13.x were released with kobalt which use an out of date version of MANIFEST.MF https://github.com/cbeust/testng/blob/master/src/main/resources/META-INF/MANIFEST.MF, since looks like kobalt can't dynamically generate it.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cbeust/testng/issues/1190#issuecomment-252390348, or mute the thread https://github.com/notifications/unsubscribe-auth/AAFoopH9q9oAleA6QLF1GB-mClHxFxmAks5qxuU2gaJpZM4KRkQZ .
TestNG Version
6.9.13.x
Expected behavior
Actual behavior
'META-INF/MANIFEST.MF' of 6.9.13.8
Is the issue reproductible on runner?
Test case sample