You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Sanjay Choudhary <ch...@gmail.com> on 2006/02/24 21:24:56 UTC
Not building EAR for an application
Hi All,
We hv. and application building thru continuum
Our application is a normal J2EE application
pom.xml
EAR Project
EJB1 Project
EJB2 Project
Jar Project
Jar Project
War Project
Each of them has pom.xml. Now if we have change in Jar Project and EJB1
project, continuum builds the projects fine but doesn't rebuild the EAR.
Now we don't have a latest EAR and deploy. Is there a workaround to this?
Or this is a normal behavior of Continuum.
If it is the normal behavior, then how we we get the latest EAR?
Thanks,
Sanjay
Re: Not building EAR for an application
Posted by Mang Jun Lau <Ma...@otpp.com>.
I will add these workarounds to the Contiuum FAQ page.
_Mang
Emmanuel Venisse <em...@venisse.net>
02/27/2006 03:58 AM
Please respond to
continuum-users@maven.apache.org
To
continuum-users@maven.apache.org
cc
Subject
Re: Not building EAR for an application
Ah, you have one cvs modules by project module.
It's really strange to use this structure in CVS, generally a CVS module
is used for a complete
project with some subdirectories for project modules.
In your case, you can't use a parent pom without some work. I have 2 work
around:
- Refactor your CVS structure to a more standard
- Keep your actual structure and create a new module that will contains a
parent pom and a list of
symbolic link to your actual CVS modules. An other user use this solution
and it's works fine.
Emmanuel
Sanjay Choudhary a écrit :
> Hi Emmanuel,
>
> We use CVS (I wish it was svn). Each project of application corresponds
to a
> module in CVS.
>
> at root level pom.xml (Not in cvs) failed as it doesn't exist in CVS. I
> copied it manually to folder 1. In working directory I was able to see
> pom.xml
>
> parentPOM ( in cvs) in continuum folder name 2
>
> common (in cvs) in continuum folder name 3
>
> ejb1 (in cvs) folder name 4
>
> ejb2 (in cvs) folder name 5
>
> war (in cvs) folder name 6
>
> Java (in cvs) folder name 7
>
> ear (in cvs) folder name 8
>
> All the projects in CVS has pom.xml
>
> Now when I run mvn compile (or anyother phase) it doesn't work. It looks
for
> the directory common , java, war etc. which are not present. (Which I
> expected)
>
> ( I don't know the design reason, but it would have been great if we had
> real folder names instead of numeric numbers.)
>
> Let me know if I am doing something wrong here!!
>
> -Sanjay
>
>
> On 2/26/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
>>ok you don't use the standard maven layout.
>>
>>If you want to build all in one time, you should add a new pom in the
root
>>directory of your parent
>>pom and add one module in it (the parent pom), so all your modules will
be
>>checkout in the correct
>>directory structure
>>
>>Emmanuel
>>
>>Sanjay Choudhary a écrit :
>>
>>>Hi Emmanuel
>>>
>>>I like option 2 and I tried it too but it doesn't work
>>>
>>>My Parent pom has module definition as below:
>>>
>>><modules>
>>> <modules>
>>> <module>../common</module>
>>> <module>../ejb1</module>
>>> <module>../ejb2</module>
>>> <module>../war1</module>
>>> <module>../java1</module>
>>> <module>../ear</module>
>>> </modules>
>>></modules>
>>>
>>>But since Continuum uses number instead of folder name -N option
doesn't
>>>work. Is there a work around to this issue?
>>>
>>>-Sanjay
>>>
>>>On 2/25/06, Emmanuel Venisse <em...@venisse.net> wrote:
>>>
>>>
>>>>Actually a build start only if you have some changes in scm for your
>>>>project. In future, we'll can
>>>>start a build if a dependecies is new.
>>>>
>>>>If you want the latest EAR, without changes in your EAR project, you
>>
>>must
>>
>>>>build it manually from
>>>>Continuum. or you can build all from parent project if you remove -N
>>>>parameter in the build definition
>>>>
>>>>Emmanuel
>>>>
>>>>Sanjay Choudhary a écrit :
>>>>
>>>>
>>>>>Hi All,
>>>>>
>>>>>We hv. and application building thru continuum
>>>>>
>>>>>Our application is a normal J2EE application
>>>>>
>>>>>pom.xml
>>>>>
>>>>>EAR Project
>>>>>
>>>>>EJB1 Project
>>>>>
>>>>>EJB2 Project
>>>>>
>>>>>Jar Project
>>>>>
>>>>>Jar Project
>>>>>
>>>>>War Project
>>>>>
>>>>>Each of them has pom.xml. Now if we have change in Jar Project and
>>
>>EJB1
>>
>>>>>project, continuum builds the projects fine but doesn't rebuild the
>>
>>EAR.
>>
>>>>>Now we don't have a latest EAR and deploy. Is there a workaround to
>>>>
>>>>this?
>>>>
>>>>
>>>>>Or this is a normal behavior of Continuum.
>>>>>
>>>>>If it is the normal behavior, then how we we get the latest EAR?
>>>>>
>>>>>Thanks,
>>>>>Sanjay
>>>>>
>>>>
>>>>
>>
>
Re: Not building EAR for an application
Posted by Emmanuel Venisse <em...@venisse.net>.
Ah, you have one cvs modules by project module.
It's really strange to use this structure in CVS, generally a CVS module is used for a complete
project with some subdirectories for project modules.
In your case, you can't use a parent pom without some work. I have 2 work around:
- Refactor your CVS structure to a more standard
- Keep your actual structure and create a new module that will contains a parent pom and a list of
symbolic link to your actual CVS modules. An other user use this solution and it's works fine.
Emmanuel
Sanjay Choudhary a écrit :
> Hi Emmanuel,
>
> We use CVS (I wish it was svn). Each project of application corresponds to a
> module in CVS.
>
> at root level pom.xml (Not in cvs) failed as it doesn't exist in CVS. I
> copied it manually to folder 1. In working directory I was able to see
> pom.xml
>
> parentPOM ( in cvs) in continuum folder name 2
>
> common (in cvs) in continuum folder name 3
>
> ejb1 (in cvs) folder name 4
>
> ejb2 (in cvs) folder name 5
>
> war (in cvs) folder name 6
>
> Java (in cvs) folder name 7
>
> ear (in cvs) folder name 8
>
> All the projects in CVS has pom.xml
>
> Now when I run mvn compile (or anyother phase) it doesn't work. It looks for
> the directory common , java, war etc. which are not present. (Which I
> expected)
>
> ( I don't know the design reason, but it would have been great if we had
> real folder names instead of numeric numbers.)
>
> Let me know if I am doing something wrong here!!
>
> -Sanjay
>
>
> On 2/26/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
>>ok you don't use the standard maven layout.
>>
>>If you want to build all in one time, you should add a new pom in the root
>>directory of your parent
>>pom and add one module in it (the parent pom), so all your modules will be
>>checkout in the correct
>>directory structure
>>
>>Emmanuel
>>
>>Sanjay Choudhary a écrit :
>>
>>>Hi Emmanuel
>>>
>>>I like option 2 and I tried it too but it doesn't work
>>>
>>>My Parent pom has module definition as below:
>>>
>>><modules>
>>> <modules>
>>> <module>../common</module>
>>> <module>../ejb1</module>
>>> <module>../ejb2</module>
>>> <module>../war1</module>
>>> <module>../java1</module>
>>> <module>../ear</module>
>>> </modules>
>>></modules>
>>>
>>>But since Continuum uses number instead of folder name -N option doesn't
>>>work. Is there a work around to this issue?
>>>
>>>-Sanjay
>>>
>>>On 2/25/06, Emmanuel Venisse <em...@venisse.net> wrote:
>>>
>>>
>>>>Actually a build start only if you have some changes in scm for your
>>>>project. In future, we'll can
>>>>start a build if a dependecies is new.
>>>>
>>>>If you want the latest EAR, without changes in your EAR project, you
>>
>>must
>>
>>>>build it manually from
>>>>Continuum. or you can build all from parent project if you remove -N
>>>>parameter in the build definition
>>>>
>>>>Emmanuel
>>>>
>>>>Sanjay Choudhary a écrit :
>>>>
>>>>
>>>>>Hi All,
>>>>>
>>>>>We hv. and application building thru continuum
>>>>>
>>>>>Our application is a normal J2EE application
>>>>>
>>>>>pom.xml
>>>>>
>>>>>EAR Project
>>>>>
>>>>>EJB1 Project
>>>>>
>>>>>EJB2 Project
>>>>>
>>>>>Jar Project
>>>>>
>>>>>Jar Project
>>>>>
>>>>>War Project
>>>>>
>>>>>Each of them has pom.xml. Now if we have change in Jar Project and
>>
>>EJB1
>>
>>>>>project, continuum builds the projects fine but doesn't rebuild the
>>
>>EAR.
>>
>>>>>Now we don't have a latest EAR and deploy. Is there a workaround to
>>>>
>>>>this?
>>>>
>>>>
>>>>>Or this is a normal behavior of Continuum.
>>>>>
>>>>>If it is the normal behavior, then how we we get the latest EAR?
>>>>>
>>>>>Thanks,
>>>>>Sanjay
>>>>>
>>>>
>>>>
>>
>
Re: Not building EAR for an application
Posted by Sanjay Choudhary <ch...@gmail.com>.
Hi Emmanuel,
We use CVS (I wish it was svn). Each project of application corresponds to a
module in CVS.
at root level pom.xml (Not in cvs) failed as it doesn't exist in CVS. I
copied it manually to folder 1. In working directory I was able to see
pom.xml
parentPOM ( in cvs) in continuum folder name 2
common (in cvs) in continuum folder name 3
ejb1 (in cvs) folder name 4
ejb2 (in cvs) folder name 5
war (in cvs) folder name 6
Java (in cvs) folder name 7
ear (in cvs) folder name 8
All the projects in CVS has pom.xml
Now when I run mvn compile (or anyother phase) it doesn't work. It looks for
the directory common , java, war etc. which are not present. (Which I
expected)
( I don't know the design reason, but it would have been great if we had
real folder names instead of numeric numbers.)
Let me know if I am doing something wrong here!!
-Sanjay
On 2/26/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
> ok you don't use the standard maven layout.
>
> If you want to build all in one time, you should add a new pom in the root
> directory of your parent
> pom and add one module in it (the parent pom), so all your modules will be
> checkout in the correct
> directory structure
>
> Emmanuel
>
> Sanjay Choudhary a écrit :
> > Hi Emmanuel
> >
> > I like option 2 and I tried it too but it doesn't work
> >
> > My Parent pom has module definition as below:
> >
> > <modules>
> > <modules>
> > <module>../common</module>
> > <module>../ejb1</module>
> > <module>../ejb2</module>
> > <module>../war1</module>
> > <module>../java1</module>
> > <module>../ear</module>
> > </modules>
> > </modules>
> >
> > But since Continuum uses number instead of folder name -N option doesn't
> > work. Is there a work around to this issue?
> >
> > -Sanjay
> >
> > On 2/25/06, Emmanuel Venisse <em...@venisse.net> wrote:
> >
> >>Actually a build start only if you have some changes in scm for your
> >>project. In future, we'll can
> >>start a build if a dependecies is new.
> >>
> >>If you want the latest EAR, without changes in your EAR project, you
> must
> >>build it manually from
> >>Continuum. or you can build all from parent project if you remove -N
> >>parameter in the build definition
> >>
> >>Emmanuel
> >>
> >>Sanjay Choudhary a écrit :
> >>
> >>>Hi All,
> >>>
> >>>We hv. and application building thru continuum
> >>>
> >>>Our application is a normal J2EE application
> >>>
> >>>pom.xml
> >>>
> >>>EAR Project
> >>>
> >>>EJB1 Project
> >>>
> >>>EJB2 Project
> >>>
> >>>Jar Project
> >>>
> >>>Jar Project
> >>>
> >>>War Project
> >>>
> >>>Each of them has pom.xml. Now if we have change in Jar Project and
> EJB1
> >>>project, continuum builds the projects fine but doesn't rebuild the
> EAR.
> >>>Now we don't have a latest EAR and deploy. Is there a workaround to
> >>
> >>this?
> >>
> >>>Or this is a normal behavior of Continuum.
> >>>
> >>>If it is the normal behavior, then how we we get the latest EAR?
> >>>
> >>>Thanks,
> >>>Sanjay
> >>>
> >>
> >>
> >
>
>
Re: Not building EAR for an application
Posted by Emmanuel Venisse <em...@venisse.net>.
ok you don't use the standard maven layout.
If you want to build all in one time, you should add a new pom in the root directory of your parent
pom and add one module in it (the parent pom), so all your modules will be checkout in the correct
directory structure
Emmanuel
Sanjay Choudhary a écrit :
> Hi Emmanuel
>
> I like option 2 and I tried it too but it doesn't work
>
> My Parent pom has module definition as below:
>
> <modules>
> <modules>
> <module>../common</module>
> <module>../ejb1</module>
> <module>../ejb2</module>
> <module>../war1</module>
> <module>../java1</module>
> <module>../ear</module>
> </modules>
> </modules>
>
> But since Continuum uses number instead of folder name -N option doesn't
> work. Is there a work around to this issue?
>
> -Sanjay
>
> On 2/25/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
>>Actually a build start only if you have some changes in scm for your
>>project. In future, we'll can
>>start a build if a dependecies is new.
>>
>>If you want the latest EAR, without changes in your EAR project, you must
>>build it manually from
>>Continuum. or you can build all from parent project if you remove -N
>>parameter in the build definition
>>
>>Emmanuel
>>
>>Sanjay Choudhary a écrit :
>>
>>>Hi All,
>>>
>>>We hv. and application building thru continuum
>>>
>>>Our application is a normal J2EE application
>>>
>>>pom.xml
>>>
>>>EAR Project
>>>
>>>EJB1 Project
>>>
>>>EJB2 Project
>>>
>>>Jar Project
>>>
>>>Jar Project
>>>
>>>War Project
>>>
>>>Each of them has pom.xml. Now if we have change in Jar Project and EJB1
>>>project, continuum builds the projects fine but doesn't rebuild the EAR.
>>>Now we don't have a latest EAR and deploy. Is there a workaround to
>>
>>this?
>>
>>>Or this is a normal behavior of Continuum.
>>>
>>>If it is the normal behavior, then how we we get the latest EAR?
>>>
>>>Thanks,
>>>Sanjay
>>>
>>
>>
>
Re: Not building EAR for an application
Posted by Sanjay Choudhary <ch...@gmail.com>.
Hi Emmanuel
I like option 2 and I tried it too but it doesn't work
My Parent pom has module definition as below:
<modules>
<modules>
<module>../common</module>
<module>../ejb1</module>
<module>../ejb2</module>
<module>../war1</module>
<module>../java1</module>
<module>../ear</module>
</modules>
</modules>
But since Continuum uses number instead of folder name -N option doesn't
work. Is there a work around to this issue?
-Sanjay
On 2/25/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
> Actually a build start only if you have some changes in scm for your
> project. In future, we'll can
> start a build if a dependecies is new.
>
> If you want the latest EAR, without changes in your EAR project, you must
> build it manually from
> Continuum. or you can build all from parent project if you remove -N
> parameter in the build definition
>
> Emmanuel
>
> Sanjay Choudhary a écrit :
> > Hi All,
> >
> > We hv. and application building thru continuum
> >
> > Our application is a normal J2EE application
> >
> > pom.xml
> >
> > EAR Project
> >
> > EJB1 Project
> >
> > EJB2 Project
> >
> > Jar Project
> >
> > Jar Project
> >
> > War Project
> >
> > Each of them has pom.xml. Now if we have change in Jar Project and EJB1
> > project, continuum builds the projects fine but doesn't rebuild the EAR.
> > Now we don't have a latest EAR and deploy. Is there a workaround to
> this?
> > Or this is a normal behavior of Continuum.
> >
> > If it is the normal behavior, then how we we get the latest EAR?
> >
> > Thanks,
> > Sanjay
> >
>
>
Re: Not building EAR for an application
Posted by Emmanuel Venisse <em...@venisse.net>.
Actually a build start only if you have some changes in scm for your project. In future, we'll can
start a build if a dependecies is new.
If you want the latest EAR, without changes in your EAR project, you must build it manually from
Continuum. or you can build all from parent project if you remove -N parameter in the build definition
Emmanuel
Sanjay Choudhary a écrit :
> Hi All,
>
> We hv. and application building thru continuum
>
> Our application is a normal J2EE application
>
> pom.xml
>
> EAR Project
>
> EJB1 Project
>
> EJB2 Project
>
> Jar Project
>
> Jar Project
>
> War Project
>
> Each of them has pom.xml. Now if we have change in Jar Project and EJB1
> project, continuum builds the projects fine but doesn't rebuild the EAR.
> Now we don't have a latest EAR and deploy. Is there a workaround to this?
> Or this is a normal behavior of Continuum.
>
> If it is the normal behavior, then how we we get the latest EAR?
>
> Thanks,
> Sanjay
>