[
http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Carter updated CONTINUUM-1163:
--------------------------------------
Attachment: continuum-core-patch.txt
Attached patches allow the url to be normalized to allow continuum to retrieve
pom files in a flat structure
> Flat SCM Structure + Continuum = broken module-links on site
> ------------------------------------------------------------
>
> Key: CONTINUUM-1163
> URL: http://jira.codehaus.org/browse/CONTINUUM-1163
> Project: Continuum
> Issue Type: Wish
> Components: Integration - Maven 2
> Affects Versions: 1.0.2
> Reporter: Patrick Huber
> Fix For: 1.1-alpha-2
>
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
