Re: Need help.. How to configure POM for multi-module checkout
Yeah, that's a good idea...
On 2019/03/24 14:38:25, Kyle Marek wrote:
> You can arbitrarily switch to other tags and branches with submodules.
> It is just a simple `git checkout X` from the submodule's directory.
>
> -Kyle
>
> On 3/24/19 9:51 AM, ga...@oedata.com wrote:
> > Hi Nick,
> >
> > Thank you for that suggestion. That was also suggested on stackoverflow by
> > Karl. That method is better suited for static-ish configurations. I need
> > a BOM type system where I can dynamically switch between tags and branches
> > for different modules, much like clear case. I'll be moving to a different
> > structure and tool chain in 6 months.
> >
> > cheer
> >
> > On 2019/03/24 01:45:50, Kyle Marek wrote:
> >> 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
> >>
> > -
> > 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 Karl, Thank you for the suggestion to use maven-shade/maven-assembly-plugin(s). I was planning to use them, but haven't gotten around to them yet. I was hung up on the checkout/build thing. :- Maybe on Tuesday. The libraries are in 7 modules to manage the development cycle, specifically functional and unit testing. The aggregate library.jar will not have test cases other than one per library to ensure each module was included in the library.jar. The BOM file is the way I'm going as per your suggestion. cheers, gary On 2019/03/24 21:45:37, Karl Heinz Marbaise wrote: > Hi Gary, > > On 24.03.19 17:55, ga...@oedata.com wrote: > > Hi Nick, > > > > Thanks for the questions, I'll try to explain. > > > > The parent pom aggregates a library (jar) from different and sometimes > > interdependent modules. The parent pom checks out the module sources with > > the poms and compiles them into a single jar. > > > Maybe I misunderstand a thing here. But it sounds as if you have a > resulting library which results in a single jar? Let us ignore at the > first place the checkout things etc. > > Basicly I would say if your result is a single jar you usually have a > single maven project? > > If your result is a single jar which is combined from different modules > I would reconsider the architecture cause usually it's better having > separated modules like *-api, *-core etc. and may be a supplemental > thing could be a shaded-jar which combines several of them... > > Having seperated modules make testing easier which means you can put > your unit tests into the appropriate module etc. > > Do you use maven-shade/maven-assembly-plugin? > > If you like to produce a BOM file. The usualy way is to make a separate > module which contains simply the dependencyManagement with mentioning > the modules it should contain. > > Kind regards > Karl Heinz Marbaise > > > - > 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 Gary, On 24.03.19 17:55, ga...@oedata.com wrote: Hi Nick, Thanks for the questions, I'll try to explain. The parent pom aggregates a library (jar) from different and sometimes interdependent modules. The parent pom checks out the module sources with the poms and compiles them into a single jar. Maybe I misunderstand a thing here. But it sounds as if you have a resulting library which results in a single jar? Let us ignore at the first place the checkout things etc. Basicly I would say if your result is a single jar you usually have a single maven project? If your result is a single jar which is combined from different modules I would reconsider the architecture cause usually it's better having separated modules like *-api, *-core etc. and may be a supplemental thing could be a shaded-jar which combines several of them... Having seperated modules make testing easier which means you can put your unit tests into the appropriate module etc. Do you use maven-shade/maven-assembly-plugin? If you like to produce a BOM file. The usualy way is to make a separate module which contains simply the dependencyManagement with mentioning the modules it should contain. Kind regards Karl Heinz Marbaise - 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 Nick,
Thanks for the questions, I'll try to explain.
The parent pom aggregates a library (jar) from different and sometimes
interdependent modules. The parent pom checks out the module sources with the
poms and compiles them into a single jar.
I was using the modules pattern in in the parent pom to make the BOM easier
(less confusing) to manage. I was also using scm plugin for multi-module
checkouts. Independently, multi-module builds and multi-module checkouts work
perfectly.
When I mix the SCM plugin with the multi-module build, reactor first checks if
the module's poms exist prior to checkout. I was wondering whether there was a
way to defer the pom check until after checkout. After reviewing reactor code,
I found that is not possible without changes.
It looks like the release plugin interacts with reactor in a complimentary
process.
On 2019/03/24 11:31:28, Nikki Novak wrote:
> Gary,
>
> Having modules residing in other repositories is not a problem...
>
> ...but why do they not have a pom.xml ?
>
> ...Is the POM on a different branch ?
> ...Are the modules using ANT or gradle instead ?
> ...Are you auto-generating POMs ?
>
> Like, I'm really scratching my head trying to figure out what is going on
> here ?
>
> If the only thing you need to do is checkout, then you could add a git
> submodule and add the folder to the maven aggregator ?
> The git submodule always points to a specific commit (until you update the
> reference).
>
> Would that be a viable option for your purpose(s) ?
>
> Nick
>
>
> From: garym@
> Sent: Sunday, March 24, 2019 1:26 AM
> To: users@maven.apache.org
> Subject: 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}
&g
Re: Need help.. How to configure POM for multi-module checkout
You can arbitrarily switch to other tags and branches with submodules.
It is just a simple `git checkout X` from the submodule's directory.
-Kyle
On 3/24/19 9:51 AM, ga...@oedata.com wrote:
> Hi Nick,
>
> Thank you for that suggestion. That was also suggested on stackoverflow by
> Karl. That method is better suited for static-ish configurations. I need a
> BOM type system where I can dynamically switch between tags and branches for
> different modules, much like clear case. I'll be moving to a different
> structure and tool chain in 6 months.
>
> cheer
>
> On 2019/03/24 01:45:50, Kyle Marek wrote:
>> 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
>>
> -
> 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 Nick,
Thank you for that suggestion. That was also suggested on stackoverflow by
Karl. That method is better suited for static-ish configurations. I need a
BOM type system where I can dynamically switch between tags and branches for
different modules, much like clear case. I'll be moving to a different
structure and tool chain in 6 months.
cheer
On 2019/03/24 01:45:50, Kyle Marek wrote:
> 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
>
>
-
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
Gary,
Having modules residing in other repositories is not a problem...
...but why do they not have a pom.xml ?
...Is the POM on a different branch ?
...Are the modules using ANT or gradle instead ?
...Are you auto-generating POMs ?
Like, I'm really scratching my head trying to figure out what is going on here ?
If the only thing you need to do is checkout, then you could add a git
submodule and add the folder to the maven aggregator ?
The git submodule always points to a specific commit (until you update the
reference).
Would that be a viable option for your purpose(s) ?
Nick
From: garym@
Sent: Sunday, March 24, 2019 1:26 AM
To: users@maven.apache.org
Subject: 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
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: multi module checkout
Hi fellow developers,
I have a web application that relies on several modules. So to build it, I
have a master pom.xml file. What I want this pom file to do is to checkout
out all the modules.
below is my pom file.
project
define
modelVersion4.0.0/modelVersion
groupIdnet.srirangan.packt.maven/groupId
artifactIdTestModularApp/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
nameMyLargeModularApp/name
/define
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.1/version
executions
execution
idcheck-out-project1/id
phasegenerate-sources/phase
goals
goalcheckout/goal
/goals
configuration
checkoutDirectory${project.build.directory}/module1/checkoutDirectory
connectionUrlscm:svn:svn://svnserver/svn/module1/trunk/connectionUrl
connectionTypeconnection/connectionType
developerConnectionscm:svn:svn://svnserver/svn/module1/trunk/developerConnection
usernameusername/username
passwordpassword/password
/configuration
/execution
execution
idcheck-out-project2/id
phasegenerate-sources/phase
goals
goalcheckout/goal
/goals
configuration
checkoutDirectory${project.build.directory}/module1/checkoutDirectory
connectionUrlscm:svn:svn://svnserver/svn/module1/trunk/connectionUrl
connectionTypeconnection/connectionType
usernameusername/username
passwordpassword/password
/configuration
/execution
/executions
/plugin
/plugins
/build
/project
I have tried **mvn scm:checkout** and **mvn scm:checkout
-check-out-project1** but it give me the error:
**Cannot run checkout command : Can't load the scm provider. You need to
define a connectionUrl parameter.**
I don't understand why this is happening since I have the connectionUrl
parameters defined inside the pom file already,the ideas point that I want
to get to is having the pom file configured to be able to checkout multiple
projects at the same time. Please let me know what I am doing wrong here,
Thanks in Advance.
Also, how would you set up a master pom.xml file so that you could checkout
all the modules all at once and istall them all? Please help a lost
developer!!! Thank you very much.
--
View this message in context:
http://maven.40175.n5.nabble.com/multi-module-checkout-tp396061p5538934.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
multi module checkout
Hi Everyone - I'm having a problem checking out the code from my multi
module project - it's very frustrating and I've been working on it for a
few days, so any help anyone can provide will be greatly appreciated.
Here's the background - I have a multi module project where the parent
project is just used for meta data- in other words there is no code
associated with the parent, it's just used to configure settings common
to all child projects. It builds nothing and its packaging is set to
POM.
I'm trying to check out my code from CVS
--
1. If I put the SCM element in the child pom's and remove it from the
parent then run mvn scm:checkout from the parent directory, I get the
error:
Cannot run checkout command :
Embedded error: Can't load the scm provider.
You need to define a connectionUrl parameter
I see no connectionUrl parameter within the SCM documentation.
--
2. If I put the SCM element in the parent pom and remove it from the
child pom's then run the mvn scm:checkout from the parent directory, I
get the error:
[ERROR] cvs server: cannot find module `reviewmanager' - ignored
cvs server: cannot find module `reviewmanager' - ignored
[ERROR] BUILD ERROR
Here it's trying to checkout the artifactId of reviewmanager, which is
the artifactId for the parent. However since the packaging is set to
POM, I'd think Maven would skip the parent knowing that it's a project
for meta data only
My scm configuration for the top 2 tries is structured like this:
scm
connectionscm:cvs:pserver:herestheuser:heresthepassw...@server.domain:
/ABC/DEF:${artifactId}/connection
developerConnectionscm:cvs:pserver:herestheuser:heresthepassw...@serve
r.domain:/ABC/DEF:${artifactId}/developerConnection
tagHEAD/tag
/scm
--
3. If I keep the configuration in the parent and remove the artifactId
from the connection / developerConnection and then run mvn scm:checkout
then I get the following error:
Cannot run checkout command
Embedded error: Exception while executing SCM command
Username isn't defined.
The scm config for this last attempt is like this:
scm
connectionscm:cvs:pserver:herestheuser:heresthepassw...@server.domain:
/ABC/DEF/connection
developerConnectionscm:cvs:pserver:herestheuser:heresthepassw...@serve
r.domain:/ABC/DEF/developerConnection
tagHEAD/tag
/scm
--
4. If I take the same configuration (as used in the top 2 examples With
the ${artifactId}) and put it in any of the child pom's and then run the
mvn scm:checkout from the Child Directory, then it works fine.
This seems like it would be a very common usecase so I'm surprised I
can't find more information about it on the web. Maybe I'm doing a bad
job searching.
Re: multi module checkout
On 6/14/10 11:58 AM, House, Thomas wrote: This seems like it would be a very common usecase so I'm surprised I can't find more information about it on the web. Maybe I'm doing a bad job searching. An observation - I get the impression scm:checkout isn't used very much and/or this is a CVS-specific problem, so it may just be that no one has run into this before. Justin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
