You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Spencer White (JIRA)" <ji...@codehaus.org> on 2007/11/14 08:57:25 UTC
[jira] Created: (CONTINUUM-1565) continuum does not see update
files via scm plugin
continuum does not see update files via scm plugin
--------------------------------------------------
Key: CONTINUUM-1565
URL: http://jira.codehaus.org/browse/CONTINUUM-1565
Project: Continuum
Issue Type: Bug
Components: SCM
Affects Versions: 1.1-beta-4
Environment: linux 2.6.16.18, Perforce Server 2005.2.PATCH/100601, maven 2.0.7, jdk 1.6.0_03
Reporter: Spencer White
BuildController does not see changes and therefor does not do a build. Here is how I tested:
1. cd /project/dir
2. find ./ -type f -exec md5sum {} \; > 2.old
3. check in changes to perforce from another client
4. wait for Continuum to do run it's scheduled task to update code
5. Continuum:
346298228 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results
346298254 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - The project was not built because no changes were detected in sources since the last build.
346298255 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - No changes, not building
6. find ./ -type f -exec md5sum {} \; > 2.new
7. diff 2.old 2.new
28c27
< d408dc1aab6914b85e3bd2e1ae609368 ./src/main/java/com/visto/apps/client/IPhoneyClientProtocolHandler.java
---
> 79dfa098c212744ffec226a8126bb3f5 ./src/main/java/com/visto/apps/client/IPhoneyClientProtocolHandler.java
IPhoneyClientProtocolHandler.java was the file that I had changed and checked into perforce.
In Continuum 1.0.3 this project worked fine but it looks like maven-scm used p4 sync to update files. Then I had to add another project on the same perforce server and had to upgrade to 1.1-beta-4.
This may have something to do with the maven-scm plugin possibly?
Thanks.
--
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-1565) continuum does not see update
files via scm plugin
Posted by "Spencer White (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113844 ]
Spencer White commented on CONTINUUM-1565:
------------------------------------------
That is correct. The find statement is executed in the working directory for the project.
> continuum does not see update files via scm plugin
> --------------------------------------------------
>
> Key: CONTINUUM-1565
> URL: http://jira.codehaus.org/browse/CONTINUUM-1565
> Project: Continuum
> Issue Type: Bug
> Components: SCM
> Affects Versions: 1.1-beta-4
> Environment: linux 2.6.16.18, Perforce Server 2005.2.PATCH/100601, maven 2.0.7, jdk 1.6.0_03
> Reporter: Spencer White
>
> BuildController does not see changes and therefor does not do a build. Here is how I tested:
> 1. cd /project/dir
> 2. find ./ -type f -exec md5sum {} \; > 2.old
> 3. check in changes to perforce from another client
> 4. wait for Continuum to do run it's scheduled task to update code
> 5. Continuum:
> 346298228 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results
> 346298254 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - The project was not built because no changes were detected in sources since the last build.
> 346298255 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - No changes, not building
> 6. find ./ -type f -exec md5sum {} \; > 2.new
> 7. diff 2.old 2.new
> 28c27
> < d408dc1aab6914b85e3bd2e1ae609368 ./src/main/java/com/visto/apps/client/IPhoneyClientProtocolHandler.java
> ---
> > 79dfa098c212744ffec226a8126bb3f5 ./src/main/java/com/visto/apps/client/IPhoneyClientProtocolHandler.java
> IPhoneyClientProtocolHandler.java was the file that I had changed and checked into perforce.
> In Continuum 1.0.3 this project worked fine but it looks like maven-scm used p4 sync to update files. Then I had to add another project on the same perforce server and had to upgrade to 1.1-beta-4.
> This may have something to do with the maven-scm plugin possibly?
> Thanks.
--
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-1565) continuum does not see update
files via scm plugin
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113789 ]
Emmanuel Venisse commented on CONTINUUM-1565:
---------------------------------------------
files are updated in the continuum working directory?
> continuum does not see update files via scm plugin
> --------------------------------------------------
>
> Key: CONTINUUM-1565
> URL: http://jira.codehaus.org/browse/CONTINUUM-1565
> Project: Continuum
> Issue Type: Bug
> Components: SCM
> Affects Versions: 1.1-beta-4
> Environment: linux 2.6.16.18, Perforce Server 2005.2.PATCH/100601, maven 2.0.7, jdk 1.6.0_03
> Reporter: Spencer White
>
> BuildController does not see changes and therefor does not do a build. Here is how I tested:
> 1. cd /project/dir
> 2. find ./ -type f -exec md5sum {} \; > 2.old
> 3. check in changes to perforce from another client
> 4. wait for Continuum to do run it's scheduled task to update code
> 5. Continuum:
> 346298228 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results
> 346298254 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - The project was not built because no changes were detected in sources since the last build.
> 346298255 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - No changes, not building
> 6. find ./ -type f -exec md5sum {} \; > 2.new
> 7. diff 2.old 2.new
> 28c27
> < d408dc1aab6914b85e3bd2e1ae609368 ./src/main/java/com/visto/apps/client/IPhoneyClientProtocolHandler.java
> ---
> > 79dfa098c212744ffec226a8126bb3f5 ./src/main/java/com/visto/apps/client/IPhoneyClientProtocolHandler.java
> IPhoneyClientProtocolHandler.java was the file that I had changed and checked into perforce.
> In Continuum 1.0.3 this project worked fine but it looks like maven-scm used p4 sync to update files. Then I had to add another project on the same perforce server and had to upgrade to 1.1-beta-4.
> This may have something to do with the maven-scm plugin possibly?
> Thanks.
--
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