You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Patrick Huber (JIRA)" <ji...@codehaus.org> on 2007/02/13 14:13:21 UTC
[jira] Created: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
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
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
[jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
Posted by "Jesse McConnell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse McConnell updated CONTINUUM-1163:
---------------------------------------
Description:
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?
was:
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?
Fix Version/s: 1.1-alpha-2
> 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
>
>
> 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
[jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
Posted by "Gregory Carter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gregory Carter updated CONTINUUM-1163:
--------------------------------------
Attachment: continuum-api-patch.txt
> 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
[jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse updated CONTINUUM-1163:
----------------------------------------
Fix Version/s: (was: 1.1-beta-1)
To Sort
> 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: To Sort
>
> 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
[jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse updated CONTINUUM-1163:
----------------------------------------
Fix Version/s: (was: To Sort)
Future
> 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: Future
>
> 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
[jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated CONTINUUM-1163:
------------------------------------
Patch Submitted: [Yes]
> 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: Future
>
> 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
[jira] Updated: (CONTINUUM-1163) Flat SCM Structure + Continuum =
broken module-links on site
Posted by "Gregory Carter (JIRA)" <ji...@codehaus.org>.
[ 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