[
https://issues.apache.org/jira/browse/MARTIFACT-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922157#comment-17922157
]
Christopher Ng commented on MARTIFACT-80:
-----------------------------------------
i've come back to this again, actually it doesn't matter whether you place the
config at the top-level of the reactor or in an individual module, you can't
ignore the 'main' artifact of a module because it doesn't do the ignore check
for those. so in my case we're building an RPM as the main module artifact, and
the plugin can't be configured to ignore it.
> `ignore` doesn't work on the main module artifact
> -------------------------------------------------
>
> Key: MARTIFACT-80
> URL: https://issues.apache.org/jira/browse/MARTIFACT-80
> Project: Maven Artifact Plugin
> Issue Type: Bug
> Components: artifact:compare
> Affects Versions: 3.5.3
> Reporter: Christopher Ng
> Priority: Major
> Labels: pull-request-available
>
> The `ignore` configuration option doesn't work on the main artifact of the
> module, only on additional attached artifacts.
> Use case I have is that we're building RPMs on a (very) old CentOS version
> and they have attributes that aren't easily 'fixable' to be cleanly rebuilt.
> I ignore 'failures' in those individual modules, but when the plugin tries to
> do the aggregated `buildInfo` on the last module those RPMs aren't ignored,
> and I don't want to ignore failures for every module in the aggregator.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
