You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "apache maillist (JIRA)" <ji...@codehaus.org> on 2008/10/02 03:29:08 UTC
[jira] Created: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Continuum 1.2 does not build the project when it has changes in sub-modules
---------------------------------------------------------------------------
Key: CONTINUUM-1915
URL: http://jira.codehaus.org/browse/CONTINUUM-1915
Project: Continuum
Issue Type: Bug
Components: Integration - Maven 2
Affects Versions: 1.2
Environment: Linux
Reporter: apache maillist
Priority: Critical
Log shows:
2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
In continuum, the working copy looks like this
- parent-md
- mycommon
- myintegration
- mybusiness
- mydo
- pom.xml
the pom.xml is used for adding project into continuum
the pom.xml consist of those projects
<modules>
<module>parent-md</module>
<module>mycommon</module>
<module>myintegration</module>
<module>mybusiness</module>
<module>mydo</module>
</modules>
parent-md is the parentpom for all project listed
After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Commented: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Geert Pante (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150961#action_150961 ]
Geert Pante commented on CONTINUUM-1915:
----------------------------------------
So, just to be clear: you have a recursive build, so in Continuum you only see the 10 top projects?
Then it's logical that your sub-module will never be built separately.
But the change in CONTINUUM-1807 should not apply for you: you probably want to launch your recursive build.
Wendy, can you check if the change in CONTINUUM-1807 makes an exception for recursive builds?
The change in CONTINUUM-1807 may only affect non-recursive builds.
I don't know if there's an easy way to parse build definitions to detect if they're recursive or not. Maybe just looking for the absence of "--non-recursive" will do.
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Assigned: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy reassigned CONTINUUM-1915:
---------------------------------------
Assignee: Olivier Lamy
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 1.2.3
>
> Attachments: m2buildexecutor.java-fix-for-isRecursive.diff
>
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Commented: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Johan Larsson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153768#action_153768 ]
Johan Larsson commented on CONTINUUM-1915:
------------------------------------------
Thanks for the start! But that will just make it build all the time, because the isRecursive check is to early in the method and if the arguments is empty it will not think it can be recursive.
I have attachad a diff which at least on my side seems to work as expected.
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Commented: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151061#action_151061 ]
apache maillist commented on CONTINUUM-1915:
--------------------------------------------
Yes, I see 10 top projects; all sub modules are showing only on the "working copy" for each project. I have taken out "--non-recursive". The situation we have now is the developer changed code in sub module, nothing get built even for the sub module that was changed.
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Commented: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Larvell Jones (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152203#action_152203 ]
Larvell Jones commented on CONTINUUM-1915:
------------------------------------------
shouldBuild in MavenTwoBuildExecutor is using the incorrect logic to determine if build is recursive.
{code}
boolean isRecursive = StringUtils.isNotEmpty( buildDefinition.getArguments() ) && !(
buildDefinition.getArguments().indexOf( "-N" ) < 0 ||
buildDefinition.getArguments().indexOf( "--non-recursive" ) < 0 );
{code}
Should be:
{code}
boolean isRecursive = StringUtils.isNotEmpty( buildDefinition.getArguments() ) && (
buildDefinition.getArguments().indexOf( "-N" ) < 0 &&
buildDefinition.getArguments().indexOf( "--non-recursive" ) < 0 );
{code}
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules and the m2 build is recursive
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated CONTINUUM-1915:
------------------------------------
Summary: Continuum 1.2 does not build the project when it has changes in sub-modules and the m2 build is recursive (was: Continuum 1.2 does not build the project when it has changes in sub-modules)
> Continuum 1.2 does not build the project when it has changes in sub-modules and the m2 build is recursive
> ---------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 1.2.3
>
> Attachments: m2buildexecutor.java-fix-for-isRecursive.diff
>
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Closed: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules and the m2 build is recursive
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy closed CONTINUUM-1915.
-----------------------------------
Resolution: Fixed
fix in 1.2.x branch rev [723119|http://svn.apache.org/viewvc?rev=723119&view=rev]
merge in trunk rev [723121|http://svn.apache.org/viewvc?rev=723121&view=rev]
Attached patch not used
> Continuum 1.2 does not build the project when it has changes in sub-modules and the m2 build is recursive
> ---------------------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Assignee: Olivier Lamy
> Priority: Critical
> Fix For: 1.2.3
>
> Attachments: m2buildexecutor.java-fix-for-isRecursive.diff
>
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Issue Comment Edited: (CONTINUUM-1915) Continuum 1.2 does
not build the project when it has changes in sub-modules
Posted by "Larvell Jones (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152203#action_152203 ]
larvelljones edited comment on CONTINUUM-1915 at 10/28/08 5:11 PM:
--------------------------------------------------------------------
shouldBuild in MavenTwoBuildExecutor is using incorrect logic to determine if build is recursive.
{code}
boolean isRecursive = StringUtils.isNotEmpty( buildDefinition.getArguments() ) && !(
buildDefinition.getArguments().indexOf( "-N" ) < 0 ||
buildDefinition.getArguments().indexOf( "--non-recursive" ) < 0 );
{code}
Should be:
{code}
boolean isRecursive = StringUtils.isNotEmpty( buildDefinition.getArguments() ) && (
buildDefinition.getArguments().indexOf( "-N" ) < 0 &&
buildDefinition.getArguments().indexOf( "--non-recursive" ) < 0 );
{code}
was (Author: larvelljones):
shouldBuild in MavenTwoBuildExecutor is using the incorrect logic to determine if build is recursive.
{code}
boolean isRecursive = StringUtils.isNotEmpty( buildDefinition.getArguments() ) && !(
buildDefinition.getArguments().indexOf( "-N" ) < 0 ||
buildDefinition.getArguments().indexOf( "--non-recursive" ) < 0 );
{code}
Should be:
{code}
boolean isRecursive = StringUtils.isNotEmpty( buildDefinition.getArguments() ) && (
buildDefinition.getArguments().indexOf( "-N" ) < 0 &&
buildDefinition.getArguments().indexOf( "--non-recursive" ) < 0 );
{code}
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Johan Larsson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Johan Larsson updated CONTINUUM-1915:
-------------------------------------
Attachment: m2buildexecutor.java-fix-for-isRecursive.diff
Fix for isRecursive issue. Diff is against continuum-1.2.2.
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
> Attachments: m2buildexecutor.java-fix-for-isRecursive.diff
>
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Commented: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149589#action_149589 ]
apache maillist commented on CONTINUUM-1915:
--------------------------------------------
by the way, when I add the project, I checked "For multi modules project, load only root as recursive build", otherwise, continuum checks out all child projects as a flat structure.
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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] Commented: (CONTINUUM-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149595#action_149595 ]
Wendy Smoak commented on CONTINUUM-1915:
----------------------------------------
Linking to CONTINUUM-1807 - this was an intentional change in Continuum 1.2
... and the discussion thread http://www.nabble.com/Continuum-1.2-build-does-not-build-the-project-when-it-has-change-in-sub-modules-td19770898.html
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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-1915) Continuum 1.2 does not build the
project when it has changes in sub-modules
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivier Lamy updated CONTINUUM-1915:
------------------------------------
Fix Version/s: 1.2.3
Patch Submitted: [Yes]
> Continuum 1.2 does not build the project when it has changes in sub-modules
> ---------------------------------------------------------------------------
>
> Key: CONTINUUM-1915
> URL: http://jira.codehaus.org/browse/CONTINUUM-1915
> Project: Continuum
> Issue Type: Bug
> Components: Integration - Maven 2
> Affects Versions: 1.2
> Environment: Linux
> Reporter: apache maillist
> Priority: Critical
> Fix For: 1.2.3
>
> Attachments: m2buildexecutor.java-fix-for-isRecursive.diff
>
>
> Log shows:
> 2008-10-01 18:00:04,701 [pool-1-thread-1] INFO action#update-working-directory-from-scm - Updated 2 files.
> 2008-10-01 18:00:04,732 [pool-1-thread-1] INFO buildController - Merging SCM results
> 2008-10-01 18:00:05,011 [pool-1-thread-1] INFO continuumBuildExecutor#maven2 - Changes are only in sub-modules.
> 2008-10-01 18:00:05,019 [pool-1-thread-1] INFO buildController - No changes in the current project, not building
> In continuum, the working copy looks like this
> - parent-md
> - mycommon
> - myintegration
> - mybusiness
> - mydo
> - pom.xml
> the pom.xml is used for adding project into continuum
> the pom.xml consist of those projects
> <modules>
> <module>parent-md</module>
> <module>mycommon</module>
> <module>myintegration</module>
> <module>mybusiness</module>
> <module>mydo</module>
> </modules>
> parent-md is the parentpom for all project listed
> After developer making changes in sub-modules ex: myintegration in SVN, continuum detects the changes during schedule run but nothing gets built even myintegration itslef. This model works well in 1.1.
> Now all of our 10+ projects with 50+ sub-modules in total stop building by schedule.
--
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