Building not all subprojects

[Roberto de Castro <ro...@gmail.com>]

Hi there! I'll configure my project to be built by Maven2. There are 5
subprojects in my main project, but, sometimes there is modifications in
only one module, so It is not necessary to build all subprojects again.
What can I do NOT to build all subprojects of my main projects?
Best regards,
Roberto.

Re: Building not all subprojects

[dan tran <da...@gmail.com>]

configure maven profile to do that

http://maven.apache.org/guides/introduction/introduction-to-profiles.html


-D

On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
>
> How can I do this dinamycally? I mean, sometimes I need to build different
> modules. That is, suppose there are modules A, B and C in my project.
> Sometimes, I need to build modules A and B, and in another day I need to
> build module A only. In fact, I need to build the modules that have, at
> least, one of its programs modified.
> I'm planning to use Maven2 in a 24x7 application. A big system in fact,
> so,
> when programs of only one module have to be changed, I'd like to build and
> deploy this module only, instead of, buildind and deploying the whole
> application. I'm afraid I can not use Maven 2 because of this limitation,
> if
> I don't find a work around.
> Thanks a lot.
> Regards,
> Roberto
>
> On 9/15/06, dan tran <da...@gmail.com> wrote:
> >
> > Remove unwanted modules out of pom temporarily?
> >
> > -D
> >
> >
> >
> >
> >
> > On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
> > >
> > > Hi, Dan, but I don't want to use continuos integration in my project.
> I
> > > would like to control when to build the subprojects. Maven1 is able to
> > > build
> > > whatever project exits in a directory below the main project. i. e.,
> > main
> > > project triggers subprojects only if they were download to local
> > directory
> > > previously.
> > > I'd like a work around to do this in M2.
> > > Regards,
> > > Roberto.
> > >
> > > On 9/15/06, dan tran <da...@gmail.com> wrote:
> > > >
> > > > Maven itself is not smart enought to do that yet. But Continuum can
> do
> > > > that
> > > > for
> > > > you automatically.  If a source of a sub project change, Continuum
> > will
> > > > build all projects that depend
> > > > on the change project as well.
> > > >
> > > > -D
> > > >
> > > >
> > > > On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
> > > > >
> > > > > Hi there! I'll configure my project to be built by Maven2. There
> are
> > 5
> > > > > subprojects in my main project, but, sometimes there is
> > modifications
> > > in
> > > > > only one module, so It is not necessary to build all subprojects
> > > again.
> > > > > What can I do NOT to build all subprojects of my main projects?
> > > > > Best regards,
> > > > > Roberto.
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Re: Building not all subprojects

[Roberto de Castro <ro...@gmail.com>]

How can I do this dinamycally? I mean, sometimes I need to build different
modules. That is, suppose there are modules A, B and C in my project.
Sometimes, I need to build modules A and B, and in another day I need to
build module A only. In fact, I need to build the modules that have, at
least, one of its programs modified.
I'm planning to use Maven2 in a 24x7 application. A big system in fact, so,
when programs of only one module have to be changed, I'd like to build and
deploy this module only, instead of, buildind and deploying the whole
application. I'm afraid I can not use Maven 2 because of this limitation, if
I don't find a work around.
Thanks a lot.
Regards,
Roberto

On 9/15/06, dan tran <da...@gmail.com> wrote:
>
> Remove unwanted modules out of pom temporarily?
>
> -D
>
>
>
>
>
> On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
> >
> > Hi, Dan, but I don't want to use continuos integration in my project. I
> > would like to control when to build the subprojects. Maven1 is able to
> > build
> > whatever project exits in a directory below the main project. i. e.,
> main
> > project triggers subprojects only if they were download to local
> directory
> > previously.
> > I'd like a work around to do this in M2.
> > Regards,
> > Roberto.
> >
> > On 9/15/06, dan tran <da...@gmail.com> wrote:
> > >
> > > Maven itself is not smart enought to do that yet. But Continuum can do
> > > that
> > > for
> > > you automatically.  If a source of a sub project change, Continuum
> will
> > > build all projects that depend
> > > on the change project as well.
> > >
> > > -D
> > >
> > >
> > > On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
> > > >
> > > > Hi there! I'll configure my project to be built by Maven2. There are
> 5
> > > > subprojects in my main project, but, sometimes there is
> modifications
> > in
> > > > only one module, so It is not necessary to build all subprojects
> > again.
> > > > What can I do NOT to build all subprojects of my main projects?
> > > > Best regards,
> > > > Roberto.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Re: Building not all subprojects

[dan tran <da...@gmail.com>]

Remove unwanted modules out of pom temporarily?

-D





On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
>
> Hi, Dan, but I don't want to use continuos integration in my project. I
> would like to control when to build the subprojects. Maven1 is able to
> build
> whatever project exits in a directory below the main project. i. e., main
> project triggers subprojects only if they were download to local directory
> previously.
> I'd like a work around to do this in M2.
> Regards,
> Roberto.
>
> On 9/15/06, dan tran <da...@gmail.com> wrote:
> >
> > Maven itself is not smart enought to do that yet. But Continuum can do
> > that
> > for
> > you automatically.  If a source of a sub project change, Continuum will
> > build all projects that depend
> > on the change project as well.
> >
> > -D
> >
> >
> > On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
> > >
> > > Hi there! I'll configure my project to be built by Maven2. There are 5
> > > subprojects in my main project, but, sometimes there is modifications
> in
> > > only one module, so It is not necessary to build all subprojects
> again.
> > > What can I do NOT to build all subprojects of my main projects?
> > > Best regards,
> > > Roberto.
> > >
> > >
> >
> >
>
>

Re: Building not all subprojects

[Roberto de Castro <ro...@gmail.com>]

Hi, Dan, but I don't want to use continuos integration in my project. I
would like to control when to build the subprojects. Maven1 is able to build
whatever project exits in a directory below the main project. i. e., main
project triggers subprojects only if they were download to local directory
previously.
I'd like a work around to do this in M2.
Regards,
Roberto.

On 9/15/06, dan tran <da...@gmail.com> wrote:
>
> Maven itself is not smart enought to do that yet. But Continuum can do
> that
> for
> you automatically.  If a source of a sub project change, Continuum will
> build all projects that depend
> on the change project as well.
>
> -D
>
>
> On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
> >
> > Hi there! I'll configure my project to be built by Maven2. There are 5
> > subprojects in my main project, but, sometimes there is modifications in
> > only one module, so It is not necessary to build all subprojects again.
> > What can I do NOT to build all subprojects of my main projects?
> > Best regards,
> > Roberto.
> >
> >
>
>

Re: Building not all subprojects

[dan tran <da...@gmail.com>]

Maven itself is not smart enought to do that yet. But Continuum can do that
for
you automatically.  If a source of a sub project change, Continuum will
build all projects that depend
on the change project as well.

-D


On 9/15/06, Roberto de Castro <ro...@gmail.com> wrote:
>
> Hi there! I'll configure my project to be built by Maven2. There are 5
> subprojects in my main project, but, sometimes there is modifications in
> only one module, so It is not necessary to build all subprojects again.
> What can I do NOT to build all subprojects of my main projects?
> Best regards,
> Roberto.
>
>