continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <>
Subject [jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum = broken module-links on site
Date Thu, 09 Oct 2008 05:05:08 GMT


Emmanuel Venisse updated CONTINUUM-1163:

    Fix Version/s:     (was: 1.2.1)

The patch is already applied but it isn't relate to this issue.
I don't see a way to fix this issue for the moment until we remove the actual project directory
structure (CONTINUUM-1108)

> Flat SCM Structure + Continuum = broken module-links on site
> ------------------------------------------------------------
>                 Key: CONTINUUM-1163
>                 URL:
>             Project: Continuum
>          Issue Type: Wish
>          Components: Integration - Maven 2
>    Affects Versions: 1.0.2
>            Reporter: Patrick Huber
>             Fix For: 1.x
>         Attachments: continuum-api-patch.txt, continuum-core-patch.txt
> We have a flat project structure and we're gradually adding maven support. The layout
looks like this:
> /masterproject/trunk/pom.xml
> /component/trunk/pom.xml
> /component/trunk/subcomponent1/pom.xml
> /component/trunk/subcomponent2/pom.xml
> in out masterproject/trunk/pom.xml, the module is defined like this:
> <module>../../component/trunk</module>
> Building locally works fine, but when the build is run in continuum, it can't find the
module because continuum has its own layout.
> The annoying result is, that our <menu ref="module"/> will print a href and text
of "../../component/trunk" in the modules menu.
> The build output contains this: "[WARNING] No filesystem module-POM available"
> How do we get this to work locally as well as in continuum?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message