How should I configure maven parent pom to checkout code before Module list
fails because the pom cannot be found.
It seems the maven's reactor test for a module's pom occurs before the
generate-sources phase when scm checkouts the projects with the projects'
pom.
How can I fix this ?
thanks
Not sure that it will help with version number matches, but you could
also use Git submodules to bring multiple repositories together in a
single tree.
See: https://git-scm.com/book/en/v2/Git-Tools-Submodules
On 3/23/19 9:26 PM, ga...@oedata.com wrote:
> Hi Karl,
>
> Thank you for replying on
Hi Karl,
Thank you for replying on mail server. and thanks for sending me the links to
you project poms. They look awesome.
The is a difference between your projects and my situation. Your projects all
the modules reside in the same repository. In my case, they reside in different
Hi,
I will give you the same answer as on StackOverflow.
The way you are going sounds wrong...
As I already suggested is the way to go creating a multi module build
which comprises of several modules which is located within a single Git
repository. this can be build by using a single command.
Hi,
I need some help with scm checking out multiple modules and building them.
I have several projects I'm consolidating into a single jar. Reactor
checks for module poms before generate-sources executes.
How do I fix this issue ?
thanks..
g
POM sample to give you an idea of what I've done.
Hi Jason,
I will get back to your last two emails, but currently your results remind
me to mention the following:
There are actually two mechanisms checking Maven process (parent process).
The new one is faster but with native support. And the older is pure Java
using ping events.
The ping is
