[MAGNOLIA-7202] ModuleBootstrapTask performance improvement Created: 22/Nov/17 Updated: 23/Nov/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 5.6 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Ronald Ten Berge | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Description |
|
During a debugging session regarding the ModuleBootstrapTask I saw that the ModuleBootstrapTask#acceptResource() method gets called for all classpath resources due to BootstrapResourcesTask#getResourcesToBootstrap(). I think it would be possible to override the BootstrapResourcesTask#getResourcesToBootstrap() method in ModuleBootstrapTask to only handle classpath resources from the current module. I guess this would also result in an additional method in the ClasspathResourcesUtil. |