How to configure maven to checkout multiple modules before module reactor fails
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
target/mod-1
target/mod-2
org.apache.maven.plugins
maven-scm-plugin
1.9.4
mod-1
generate-sources
${mod-1.url}
${mod-1.versionType}
${mod-1.version}
${mod-1.directory}
checkout
mod-2
generate-sources
${mod-2.url}
${mod-2.versionType}
${mod-2.version}
${mod-2.directory}
checkout
.
--
Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Need help.. How to configure POM for multi-module checkout
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 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 repositories.
>
> I elected to use the scm plugin because it allows me to select branches and
> tags, based on the project and development requirements. I didn't suspect
> reactor would check for poms before executing the life cycle.
>
> I'm sure this has been solved by someone in the past. I just don't know how
> to solve it using maven. I can solve it with a bunch of execute blocks, but
> that is very ugly. I'm going to look at the release plugin and a few others
>
> It's likely I'm using the wrong plugin or I'm missing a plugin.
>
> BTW, I like your iterator plugin
>
> cheers
> gary
>
>
>
>
> On 2019/03/23 23:56:48, Karl Heinz Marbaise wrote:
>> 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.
>>
>>
>> mvn clean package
>>
>> from the root location..
>>
>> https://github.com/khmarbaise/javaee
>> https://github.com/khmarbaise/supose
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> On 24.03.19 00:35, Gary M wrote:
>>> 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.
>>>
>>>
>>>org.apache.maven.plugins
>>>maven-scm-plugin
>>>1.9.4
>>>
>>>
>>>mod-1
>>>generate-sources
>>>
>>> ${mod-1.url}
>>> ${mod-1.versionType}
>>> ${mod-1.version}
>>> ${mod-1.directory}
>>>
>>>
>>> checkout
>>>
>>>
>>>
>>>mod-2
>>>generate-sources
>>>
>>> ${mod-2.url}
>>> ${mod-2.versionType}
>>> ${mod-2.version}
>>> ${mod-2.directory}
>>>
>>>
>>> checkout
>>>
>>>
>>>
>>>
>>> .
>>>
>>>
>>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
signature.asc
Description: OpenPGP digital signature
Re: Need help.. How to configure POM for multi-module checkout
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
repositories.
I elected to use the scm plugin because it allows me to select branches and
tags, based on the project and development requirements. I didn't suspect
reactor would check for poms before executing the life cycle.
I'm sure this has been solved by someone in the past. I just don't know how to
solve it using maven. I can solve it with a bunch of execute blocks, but that
is very ugly. I'm going to look at the release plugin and a few others
It's likely I'm using the wrong plugin or I'm missing a plugin.
BTW, I like your iterator plugin
cheers
gary
On 2019/03/23 23:56:48, Karl Heinz Marbaise wrote:
> 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.
>
>
> mvn clean package
>
> from the root location..
>
> https://github.com/khmarbaise/javaee
> https://github.com/khmarbaise/supose
>
> Kind regards
> Karl Heinz Marbaise
>
> On 24.03.19 00:35, Gary M wrote:
> > 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.
> >
> >
> >org.apache.maven.plugins
> >maven-scm-plugin
> >1.9.4
> >
> >
> >mod-1
> >generate-sources
> >
> > ${mod-1.url}
> > ${mod-1.versionType}
> > ${mod-1.version}
> > ${mod-1.directory}
> >
> >
> > checkout
> >
> >
> >
> >mod-2
> >generate-sources
> >
> > ${mod-2.url}
> > ${mod-2.versionType}
> > ${mod-2.version}
> > ${mod-2.directory}
> >
> >
> > checkout
> >
> >
> >
> >
> > .
> >
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Need help.. How to configure POM for multi-module checkout
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.
mvn clean package
from the root location..
https://github.com/khmarbaise/javaee
https://github.com/khmarbaise/supose
Kind regards
Karl Heinz Marbaise
On 24.03.19 00:35, Gary M wrote:
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.
org.apache.maven.plugins
maven-scm-plugin
1.9.4
mod-1
generate-sources
${mod-1.url}
${mod-1.versionType}
${mod-1.version}
${mod-1.directory}
checkout
mod-2
generate-sources
${mod-2.url}
${mod-2.versionType}
${mod-2.version}
${mod-2.directory}
checkout
.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Need help.. How to configure POM for multi-module checkout
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.
org.apache.maven.plugins
maven-scm-plugin
1.9.4
mod-1
generate-sources
${mod-1.url}
${mod-1.versionType}
${mod-1.version}
${mod-1.directory}
checkout
mod-2
generate-sources
${mod-2.url}
${mod-2.versionType}
${mod-2.version}
${mod-2.directory}
checkout
.
Re: Failsafe: Killing self fork JVM. PING timeout elapsed.
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 not used if PpidChecker#canUse() returns true, and the PPID is checked every second whether Maven process is alive. The reason why it returned false is that "/bin/ps -o etime -p " failed? (see the dump file in directory /target/surefire-reports, what logged in there?) Maybe caught an exception in [1] due to "ps" is not installed. If this is happens then the ForkedBooter falls back to the old mechanism listening to the PING events. The method PpidChecker#canUse() is called in ForkedBooter in the method: processCheckerJob( final PingScheduler pingMechanism ) If the faster mechanism in PpidChecker objectively fails due to the OS or system, we have to concentrate on the older mechanism using the PING as you have described in the previous email. If there's no such OS nor system issue and "ps" works in native console in your Docker container, then we have to concentrate on PpidChecker as well. [1]: https://github.com/apache/maven-surefire/blob/master/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java#L363 On Fri, Mar 22, 2019 at 9:47 PM Jason Young wrote: > Thanks Tibor. I'll use `encodeAndWriteToOutput` later. For now, I hacked > together some temporary changes to ForkedBooter so that it "logs" (just > `System.out.println`) the current time every time: > >- the command reader thread reads a NOOP via stdin, >- it starts the ping job, >- it checks for NOOP (`canUseNewPingMechanism(..)` returns `false`), and >- it would have exited because there is no NOOP (`!pingDone`). > > I also commented out the code to exit in that case so it keeps running and > logging. > > The resulting output starts out showing that it's receiving ping every 10s > and checking for NOOP every 30s, as expected. But then one large test > begins, and: > > DEBUG 2019/03/22 19:14:40.223 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:02.723 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.139 GMT ForkedBooter: Running ping job (i.e. > checking if we read a ping earlier). > DEBUG 2019/03/22 19:18:03.172 GMT ForkedBooter: Checking for NOOP from > Maven process. > DEBUG 2019/03/22 19:18:03.186 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.187 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.187 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.187 GMT ForkedBooter: Running ping job (i.e. > checking if we read a ping earlier). > DEBUG 2019/03/22 19:18:03.188 GMT ForkedBooter: Checking for NOOP from > Maven process. > DEBUG 2019/03/22 19:18:03.187 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.243 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.307 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.308 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.202 GMT ForkedBooter: Running ping job (i.e. > checking if we read a ping earlier). > DEBUG 2019/03/22 19:18:03.323 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.337 GMT ForkedBooter: Checking for NOOP from > Maven process. > DEBUG 2019/03/22 19:18:03.351 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.351 GMT ForkedBooter: Running ping job (i.e. > checking if we read a ping earlier). > DEBUG 2019/03/22 19:18:03.351 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.352 GMT ForkedBooter: Checking for NOOP from > Maven process. > DEBUG 2019/03/22 19:18:03.366 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.393 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.380 GMT ForkedBooter: Running ping job (i.e. > checking if we read a ping earlier). > DEBUG 2019/03/22 19:18:03.409 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.424 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.423 GMT ForkedBooter: Checking for NOOP from > Maven process. > DEBUG 2019/03/22 19:18:03.424 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.438 GMT ForkedBooter: Running ping job (i.e. > checking if we read a ping earlier). > DEBUG 2019/03/22 19:18:03.438 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.453 GMT ForkedBooter: Checking for NOOP from > Maven process. > DEBUG 2019/03/22 19:18:03.454 GMT ForkedBooter: Received ping from Maven > process. > DEBUG 2019/03/22 19:18:03.476 GMT ForkedBooter: R
