apache / apache/maven-build-cache-extension
[MBUILDCACHE-125] Separate configuration/outputs per module
- Dominant language
- Java
- Stars
- 163
- Forks
- 77
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 4
Description
**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** opened **[MBUILDCACHE-125](https://issues.apache.org/jira/browse/MBUILDCACHE-125?redirect=false)** and commented
I'd like to provide a separate \ configuration per module in a multi-module project.
The only workaround that comes to mind is to add entries that capture the module name like this:
\../../database/target/classes\
This has me wondering if there are other settings that make sense to configure on a per-module basis instead of globally.
---
No further details from [MBUILDCACHE-125](https://issues.apache.org/jira/browse/MBUILDCACHE-125?redirect=false)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing global configuration and how settings are applied across modules; the issue does not identify repository files, tests, or entry points. Define the per-module configuration scope and determine which other settings, if any, should follow the same model. Done means multi-module projects can configure outputs independently without the workaround described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100