${maven.multiModuleProjectDirectory} is not resolved #1291
Comments
|
Thanks @laeubi answering about the unexpected executions:
|
|
@blacelle m2e now supports multi-module directory but it seems the property is not set, do you think you can provide a PR with a minimal reproducer in the |
|
And if possible open a new issue so that we have a Quick-Fix for failed executions! |
|
OK, It needed a bunch of additional seconds.
and again stuck quite some time after: (I hope it will get faster after the initial execution) |
|
The local build is encountering issues: |
|
https://github.com/eclipse-m2e/m2e-core/blob/master/CONTRIBUTING.md#prerequisites
|
|
m2e is an eclipse project, so you can not really edit is with only a single project as it depends on different other eclipse plugins (not part of m2e) so you need at least an IDE with PDE support, set the target platform and import the m2e.core and m2e.core.tests, but using the proposed dev IDE is maybe the fastest path to success. |
|
In the meantime of the unitTest, I still have mojo being unexpectly executed. I switch the flag to WARN (as I'm happy to see something is not optimal), but they mojo are still being executed:
If I switch to ignore: will it skip the execution, and will it just ignore the failures? |
|
With CLI:
Is there a minimal command to run tests, without re-compiling all previous modules? |
|
You can run single test from the IDE ... |
You can open the Maven Lifecycle Mapping view to see the source of a mojo execution. Beside that you might need to update the Project config to take the change into account. Also please test if maybe a restart helps (so we probably seeing a caching issue here). |
|
Even after an update of the project config, and a restart of eclipse, I still get unexpected Mojo executions (and failure):
|
|
I have something similar: `- Failed to execute mojo org.eclipse.tycho:tycho-packaging-plugin:1.7.0:package-plugin {execution: default-package-plugin} (org.eclipse.tycho:tycho-packaging-plugin:1.7.0:package-plugin:default-package-plugin:package) org.eclipse.core.runtime.CoreException: Failed to execute mojo org.eclipse.tycho:tycho-packaging-plugin:1.7.0:package-plugin {execution: default-package-plugin} And the lifecycle mapping says, that the tycho-plugins have an unknown source:
I tried it with the m2e-pde plugin, as well as with the m2e-tycho-connector. The result is the same. |
Tycho 1.7 is really old, can you try with the current 3.0.5 release? |
|
I could try, but this might take some time. Will come back with the results. |
I consider a multi-module project, with a maven-plugin configured with :${maven.multiModuleProjectDirectory}
Since
M2E - Maven Integration for Eclipse 2.2.0.20230228-2348 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e, some maven plugin executions are triggered (while previously not), and they are not as easy as before to be deactiveted: it used to be doable through the context menu:In addition of Eclipse getting slow seemingly due to these executions, I see
${maven.multiModuleProjectDirectory}is not resolved in Eclipse m2e.Full stack:
The text was updated successfully, but these errors were encountered: