-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Child modules never built #13
Comments
Hi @ava1ar, I would expect Could you include the output of the command with
Thanks, -Ivan |
Maven allows such mixed hierarchies and it works well for my use case: module1 is independent (i.e. "core"), while module2 is part of the larger group (i.e. it is named as "codec-a", there are also "codec-b", "codec-c", etc - all under "codecs" pom project). |
Output of all modules (slightly altered):
So, the artifact structure is flat (except the ui part, which I would also want to make flat), while modules layout is tree-like. |
Thanks for trying this out, I hope we can get you going. The structure Is fine. And yes, Currently, the algorithm starts at each of the changed files and walks up the directory tree looking for a |
Thanks! Let me know if I can help troubleshooting this further. I really like the project, so would definitely try to contribute to it in future! |
Hi!
Thanks for implementing such nice thing - I was thinking about making something like this to manage out complex structure maven project and speed up the build. However somehow it never builds any child modules except the parent project.
Here is the debug output:
Basically,
xxx-module1
is a jar module under the parent,xxx-parent1
is a pom module, withxxx-module2
jar module under it. If I understand correctly, mvnmin supposed to selectxxx-module1
andxxx-module2
, but it picked only parent pom projectcom.org:xxx
and nothing else. Am I doing something wrong here?The text was updated successfully, but these errors were encountered: