You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marat Abrarov (Jira)" <ji...@apache.org> on 2020/12/20 10:41:00 UTC
[jira] [Updated] (MEAR-292) skipClassPathModification option should
prevent adding Class-Path entry into MANIFEST.mf
[ https://issues.apache.org/jira/browse/MEAR-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marat Abrarov updated MEAR-292:
-------------------------------
Description: It looks like there is a bug in implementation of {{skipClassPathModification}} option introduced in MEAR-182 - if {{skipClassPathModification}} is {{true}} and original MANIFEST.mf of EAR module artifact has no {{Class-Path}} entry, then empty {{Class-Path}} entry is added into EAR module. I believe that {{Class-Path}} entry should not be added in this case. (was: It looks like there is a bug in implementation of {{skipClassPathModification}} option introduced in MEAR-182 - if {{skipClassPathModification}} is {{true}} and original MANIFEST.mf of EAR module artifact has no {{Class-Path}} entry, then empty {{Class-Path}} entry is added into EAR module.)
> skipClassPathModification option should prevent adding Class-Path entry into MANIFEST.mf
> ----------------------------------------------------------------------------------------
>
> Key: MEAR-292
> URL: https://issues.apache.org/jira/browse/MEAR-292
> Project: Maven EAR Plugin
> Issue Type: Bug
> Affects Versions: 3.1.0
> Environment: Windows 10 x64
> Reporter: Marat Abrarov
> Priority: Major
>
> It looks like there is a bug in implementation of {{skipClassPathModification}} option introduced in MEAR-182 - if {{skipClassPathModification}} is {{true}} and original MANIFEST.mf of EAR module artifact has no {{Class-Path}} entry, then empty {{Class-Path}} entry is added into EAR module. I believe that {{Class-Path}} entry should not be added in this case.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)