Is there a way to remove modules from a MavenLauncher config?
- Dominant language
- Java
- Stars
- 2k
- Forks
- 392
- Avg merge
- 11h 24m
- Merged PRs (30d)
- 36
Description
Hi, I'm using Spoon to help with the modernization of some legacy code. One of of the core projects is a nightmarish maven project, that has 3 subprojects, etc of which have their own subprojects. The overall project produces multiple war files, etc etc. In any case, after turning Spoon loose on it, I've discovered that there are some duplicate classes, that don't cause problems for normal builds as they are pulled into artifacts in non-conflicting ways.
Of course this is causing a problem for Spoon as it attempts to build a model for the entire project. I've identified modules that I can remove when focusing on the code for one of the generated artifacts, but there doesn't seem to be a way for me to 'edit' the `SpoonPom` i get from calling `.getPomFile` on the launcher.
Contributor guide
Research direction
Start with MavenLauncher and the SpoonPom returned by getPomFile, then trace how modules are read and used when building the model. Determine the supported way to exclude selected modules and document or test it so a caller can focus Spoon on one generated artifact without duplicate classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100