arturobernalg commented on issue #367: URL: https://github.com/apache/maven-install-plugin/issues/367#issuecomment-6516469300
Tried to reproduce this against both the reported 3.1.2/3.1.4 and current master, with a 3-module reactor matching what's described (an aggregator pom, `myproject-parent` packaging pom, `myproject-web` packaging war), using `-DinstallAtEnd=true` and a couple of structural variants (web depending on parent as its actual `<parent>`, and as a sibling with a plain pom dependency). All of them install cleanly. Added temporary trace logging around `InstallMojo.processProject`'s `ArtifactIdUtils.equalsId(pomArtifact, projectArtifact)` check to confirm it isn't just reading fine but silently not firing -- it does fire and nulls `projectArtifact` for both pom-packaged modules in every run, so the "did not assign a file" branch is never reached. Same guard is present back to at least 3.1.2, so I don't think this is version-specific either. One thing that stands out in the pasted log: the goal execution is attributed to `on project myproject` (the aggregator) while the actual missing-artifact complaint is about `myproject-parent` -- with `installAtEnd`, all installs run in one batch at the very end, so that attribution can point at whichever project happens to be current when the batch runs rather than the one the error is actually about. Might be worth double-checking that the error is really about `myproject-parent` and not, say, a third module or a custom packaging/extension not mentioned in the description. @wilx a minimal reproducer repo (or the full `-X` log around the install phase) would help a lot here -- I couldn't find a shape of this that fails on my end. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
