How to create a maven multi-module build with scm (cvs)

Hello,
we are evaluating a CI-Server.

We have a Maven multi-module project; the source code of all modules is stored in cvs.

I didn't found out how to configure a multi-module maven project which consists of about 15 modules.
When I run the build only the multi-module project is checked out from cvs. Therefore the build fails (Could not find the model file ...).
Is it possible to configure one project so that all containing modules are checked out automatically?

Thanks!
Best regards, Ulrike

5 comments
Comment actions Permalink

Hello Ulrike,

Sorry, I don't quite understand the problem.

TeamCity doesn't distinguish single- and multi-module Maven projects.
It just run Maven with the pom you provide in the same way you do it from
the command line.

All you have to is to configure the VCS Root so that it points to the project
root.

Are the pom files and the sources of your project stored in the same directory
tree and the same repository?

Hello,
we are evaluating a CI-Server.
We have a Maven multi-module project; the source code of all modules
is stored in cvs.

I didn't found out how to configure a multi-module maven project which
consists of about 15 modules.

When I run the build only the multi-module project is checked out from
cvs. Therefore the build fails (Could not find the model file ...).

Is it possible to configure one project so that all containing modules
are checked out automatically?

Thanks!
Best regards, Ulrike
---
Original message URL:
http://www.jetbrains.net/devnet/message/5240212#5240212

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hi Sergey

every module is stored in a separate cvs module (but in the same repository).
The multimodule project pom.xml is also stored in a separate cvs module.

The feature I'm looking for is that I have just to configure the multimodule pom.xml instead of configuring all modules separately (Maven knows this concept).

0
Comment actions Permalink

Hello Ulrike,

If I get it right, combining all the project modules into a single directory
tree with the main pom.xml on the top would help.
This could be done by utilizing checkout rules.

If you describe the structure of all the project modules in the CVS repository,
I'll be able to suggest the suitable rules.

Hi Sergey

every module is stored in a separate cvs module (but in the same
repository). The multimodule project pom.xml is also stored in a
separate cvs module.

The feature I'm looking for is that I have just to configure the
multimodule pom.xml instead of configuring all modules separately
(Maven knows this concept).

---
Original message URL:
http://www.jetbrains.net/devnet/message/5240220#5240220

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0
Comment actions Permalink

Hi Sergey

we work with eclipse and therefore it's not possible to work with a hierarchical project layout (we have a flat project layout).
Every J2EE module is a separate cvs module.

Our main pom.xml looks like that:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.axatech.esa.seam</groupId>
    <artifactId>esa-build</artifactId>
    <packaging>pom</packaging>
    <version>2.0.0-SNAPSHOT</version>
    <description>Multimodule container project -- contains all relevant maven projects for esa-seam-jsf.
        Just invoke mvn install on this project for installing and testing the whole project
    </description>
    <name>Overall POM for whole esa application</name>
   
    <parent>
        <artifactId>j2ee-parent</artifactId>
        <groupId>com.axatech.eplatform.j2ee</groupId>
        <version>1.1</version>
    </parent>
 
    <modules>
        <module>dependencyManagement</module>
        <module>parents/business</module>
        <module>parents/presentation</module>
       
        <module>../esa-common</module>
        <module>../esa-business-ear</module>
        <module>../esa-business-transient</module>
        <module>../esa-business-transient-client-view</module>
        <module>../esa-presentation-components</module>
        <module>../esa-presentation-misc-components</module>
        <module>../esa-presentation-ear</module>
        <module>../esa-web</module>
    </modules>

</project>

0
Comment actions Permalink

Hello Ulrike,

Flat layout is not a problem.
How your modules are organized within your CVS repository?

Also could you please describe you runner and VCS root configuration and
attach the build log with the failure message.

Thank you.

Hi Sergey

we work with eclipse and therefore it's not possible to work with a
hierarchical project layout (we have a flat project layout).

Every J2EE module is a separate cvs module.


---
Original message URL:
http://www.jetbrains.net/devnet/message/5240226#5240226

--
Sergey Anchipolevsky
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


0

Please sign in to leave a comment.