[
https://issues.apache.org/jira/browse/MBUILDCACHE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956935#comment-17956935
]
Olivier Lamy commented on MBUILDCACHE-49:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-build-cache-extension#305|https://github.com/apache/maven-build-cache-extension/issues/305].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Allow caching for pom package projects
> --------------------------------------
>
> Key: MBUILDCACHE-49
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-49
> Project: Maven Build Cache Extension (Moved to GitHub Issues)
> Issue Type: New Feature
> Affects Versions: 1.0.0
> Reporter: Tomáš Mrázek
> Priority: Major
> Labels: pull-request-available
>
> In class `MavenProjectInput` and method `calculateChecksum()` at line `207`
> is check for pom project and if true, input files are skipped. What was the
> reason behind ignoring pom projects? I've seen plenty of pom projects with
> some build logic where caching does make a sense. For example some resource
> transformations or building external projects via exec-maven-plugin. In those
> cases both source and target files exist but different packaing other than
> pom does not make a lot of sense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
