[
https://issues.apache.org/jira/browse/MJAR-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MJAR-279:
--------------------------------
Comment: was deleted
(was: Hi Rob, I will stall the next release until we have come to an agreement.
Here is my proposal I'd like you to try:
1. Make those assemblies not attach through the plugin configuration.
2. Disable the code in the detach MOJO
3. Run the new code and see how it works
>From my understanding and knowledge this should work just like you need, but
>without the pain and following the conventions.)
> maven-jar-plugin after upgrade of Maven to 3.8.3 doesn't include classpath to
> MANIFEST
> ---------------------------------------------------------------------------------------
>
> Key: MJAR-279
> URL: https://issues.apache.org/jira/browse/MJAR-279
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 3.2.0
> Environment: JDK 1.8.0_271
> Reporter: Jakub Moravec
> Priority: Blocker
> Fix For: waiting-for-feedback
>
> Attachments: debug_3_5_4_OK.log, debug_3_6_3_OK.log,
> debug_3_8_1_OK.log, debug_3_8_2_OK.log, debug_3_8_3_NOK.log,
> image-20211025-122928.png
>
>
> {noformat}
> Plugin configuration:{noformat}
> {noformat}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <configuration>
> <archive>
> <index>false</index>
> <manifest>
> <addClasspath>true</addClasspath>
> <useUniqueVersions>false</useUniqueVersions>
> <mainClass>eu.profinit.manta.platform.cli.Main</mainClass>
>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> </manifest>
> </archive>
> </configuration>
> </plugin>{noformat}
> Diff of MANIFEST.MF before ({{mvn clean install}} executed with Maven 3.5.4)
> and after ({{mvn clean install}} executed with Maven 3.8.3) is attached.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
