Multi-module projects

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Multi-module projects

Valeri Felberg
Hello,

I'm trying to solve following problem:

We have a project with multiple (around 30) modules in different languages (mostly Java and C++) built with Ant and Make. All of them are under the same SVN root/branch:

- svn://<host>/<repository>/<project>/trunk/<module>
- svn://<host>/<repository>/<project>/branches/<branch>/<module>
- svn://<host>/<repository>/<project>/tags/<tag>/<module>

and so on.

The build for the modules written in the same language is unified using the same targets and directory structure. So, in order to simplify configuration and improve maintainability, we would like to manage the modules in a hierarchical structure corresponding to the SVN layout:

project p
- branch trunk
-- module m1
-- module m2
- branch b1
-- module m1
-- module m2
- revision r1
-- module m1
-- module m2

and so on.

The modules of the same type (e.g . Java) should share the same build configuration.

I'm considering to write a plugin to solve the problem but that appears to be not that simple since it is not quite clear where this hierarchical structure should be placed in the Hudson architecture and how the views are to be extended.

If anybody has already solved a similar problem or has any idea how to solve it, please share it.

Cheers,
Valeri

Reply | Threaded
Open this post in threaded view
|

Re: Multi-module projects

Jean-Baptiste Quenot
* Valeri Felberg:

> Hello,
>
> I'm trying to solve following problem:
>
> We have a project with multiple (around 30) modules in different languages
> (mostly Java and C++) built with Ant and Make. All of them are under the
> same SVN root/branch:
>
> - svn://<host>/<repository>/<project>/trunk/<module>
> - svn://<host>/<repository>/<project>/branches/<branch>/<module>
> - svn://<host>/<repository>/<project>/tags/<tag>/<module>
>
> and so on.
>
> The build for the modules written in the same language is unified using the
> same targets and directory structure. So, in order to simplify configuration
> and improve maintainability, we would like to manage the modules in a
> hierarchical structure corresponding to the SVN layout:

I'd recommend to generate the Hudson project files automatically,
and use symbolic links for the workspace directory of each
project.  I did that for my project and it works pretty well.
--
     Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]