While this is true, there is a "deployment artifact" repository which is
separate from the local repo (~/.m2/repository) of the user running
continuum. This can be configured within Continuum. It is a proper repo,
not a local repo, and continuum deploys artifacts into this repo, even if
you don't
On 7/5/06, Mark Reynolds <[EMAIL PROTECTED]> wrote:
I have changed my multi-project build so it only builds the parent pom
without --non-recursive.
There are some double negatives here.
Do you mean you have deleted your other projects from the continuum
build and that there is now only one pro
On 6/15/06, Mark Reynolds <[EMAIL PROTECTED]> wrote:
I should have mentioned that I am not talking about the local repository
used by maven (in .m2). Artifacts created with the assembly plugin get
installed in there just fine.
Rather, I can't see how to get them to install into the local reposit
I have changed my multi-project build so it only builds the parent pom
without --non-recursive. My parent pom is pom and
the only thing that gets copied to the internal "Deployment
Repository" is the parent pom. Is this the expected behavior? I would
like to have all my module artifacts as wel
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
no, you don't need to restart it for all changes done throught the web
interface, only for
modification in application.xml.
For google talk, you need to define the jabber domain like described in faqs :
http://maven.apache.org/continuum/faq
We have Continuum checking SVN once per minute so our build will begin
very quickly after someone does a commit.
Occasionally there is some problem, for instance, where something
happens with Continuum's SVN working copy requiring "cleanup" to be run.
In this case, Continuum will send out appr
My experience is that with a multi-module project, you should do as
advised here by Emmanuel delete all but the parent project builds, and
remove --non-recursive from the parent project.
Under the default scenario, where continuum tries to build each module
separately, it doesn't seem like th
Hi,
Question 1
=
Does continuum actually work with Maven 2?
Yes, it does. We've got it up and running here with several multi-module
projects. And they even work with the "--non-recursive" option. All
modules share a common structure:
Toolbox/
|-- pom.xml
|-- toolbox-ant
| |-- p
Question 1
=
Does continuum actually work with Maven 2?I'm trying to build my m2
project.My top level pom.xml defines the
modules that need to be built.The modules are defined as follows:
eportal-services
eportal-messaging
eportal-messaging-support
eportal-webservices
eportal
E
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Do you have a pom.xml at the root of the working directory?
Emmanuel
No.Isn't continuum suppose to use the pom.xml I supplied when adding
projects as the top level pom?My project structure looks like as
follows:
/MyCompanyEportal/pom.xml
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Actually, continuum create one project by module and it checkout each module in
its own directory.
If you don't want one project by module, you can delete all modules in
continuum interface and
remove --non-recursive from the build definit
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
what do you have in the project working directory that failed?
Emmanuel
I have all the modules checked out of CVS
Jeff Mutonho
GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042
Actually, continuum create one project by module and it checkout each module in
its own directory.
If you don't want one project by module, you can delete all modules in continuum interface and
remove --non-recursive from the build definition of your parent project.
Emmanuel
Jeff Mutonho a é
what do you have in the project working directory that failed?
Emmanuel
Jeff Mutonho a écrit :
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I think part is missing in your pom or it's wrong.
Emmanuel
This is my in my pom
scm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/lib/cv
On 7/4/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
I think part is missing in your pom or it's wrong.
Emmanuel
This is my in my pom
scm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/lib/cvsroot:dev
scm:cvs:pserver:mutonj:[EMAIL PROTECTED]:/var/lib/cvsroot:dev
The modules are ch
My top level pom defines the following modules :
eportal-services
eportal-messaging
eportal-messaging-support
eportal-webservices
eportal
Besides the failed build i mentioned in my previous post ,Continuum is
checking these out of CVS into a one directory , eg 50 , then it
cre
I think part is missing in your pom or it's wrong.
Emmanuel
Jeff Mutonho a écrit :
I'm trying to build my m2 project.My top level pom.xml defines the
modules that need to be built.The modules are defined as follows:
eportal-services
eportal-messaging
eportal-messaging-support
epor
I'm trying to build my m2 project.My top level pom.xml defines the
modules that need to be built.The modules are defined as follows:
eportal-services
eportal-messaging
eportal-messaging-support
eportal-webservices
eportal
Each module has its own pom.xml .When I point continuum to
Tatiana Escovedo a écrit :
Hi,
I've analysed the code and found out that the notifiers implementation can
be done extending the class AbstractContinuumNotifier, right?
Yes
When your notifier will be implemented, you need to declare it in
apps/continuum/conf/application.xml (like other noti
19 matches
Mail list logo
