Hi,
ok, project.getProjectReferences() is exactly what I need. Thank you Thomas
for the hint and thank you Karl for answering, too. I will remember these
mechanisms.
Regards,
Christian
Am Fr., 24. Apr. 2020 um 15:41 Uhr schrieb Christian Domsch <
land...@gmail.com>:
> OK, something I missed
OK, something I missed to explain: this subtree of patched libraries per
patched webmodule would be serialized into a json string and embedded into
every patched library. This then could be read by the monitoring tool for
checking the installation. Why every patched library? Because I cannot
Hi,
ok, more detail. Our application is in the end defined by mainly three war
modules. These contain all the jars that we build ourselves (modules in the
reactor) plus all dependencies from outside (irrelevant for what I want to
do). We also have a patch building process that does not build the
Hi,
On 24.04.20 14:47, Christian Domsch wrote:
Hi,
I would like to be able to get access to the reactor module tree. I have a
specific plugin that is executed for each reactor module and it needs to
check, if for a predefined set of modules in the reactor (in our case war
archives that contain
IIUC you should be able to do that using Project#getReferencedProjects(),
you may have to first call Project#getExecutionProject().
Have a look at
https://github.com/tbroyer/gwt-maven-plugin/blob/master/src/main/java/net/ltgt/gwt/maven/AbstractDevModeMojo.java
and
see if it somehow fits your
