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 <khmarba...@gmx.de> 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. >>> <plugins> >>> <plugin> >>> <groupId>org.apache.maven.plugins</groupId> >>> <artifactId>maven-scm-plugin</artifactId> >>> <version>1.9.4</version> >>> <executions> >>> <execution> >>> <id>mod-1</id> >>> <phase>generate-sources</phase> >>> <configuration> >>> <connectionUrl>${mod-1.url}</connectionUrl> >>> <scmVersionType>${mod-1.versionType}</scmVersionType> >>> <scmVersion>${mod-1.version}</scmVersion> >>> <checkoutDirectory>${mod-1.directory}</checkoutDirectory> >>> </configuration> >>> <goals> >>> <goal>checkout</goal> >>> </goals> >>> </execution> >>> <execution> >>> <id>mod-2</id> >>> <phase>generate-sources</phase> >>> <configuration> >>> <connectionUrl>${mod-2.url}</connectionUrl> >>> <scmVersionType>${mod-2.versionType}</scmVersionType> >>> <scmVersion>${mod-2.version}</scmVersion> >>> <checkoutDirectory>${mod-2.directory}</checkoutDirectory> >>> </configuration> >>> <goals> >>> <goal>checkout</goal> >>> </goals> >>> </execution> >>> </executions> >>> >>> ..... >>> >>> </build> >>> >> --------------------------------------------------------------------- >> 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
