[ http://jira.codehaus.org/browse/CONTINUUM-786?page=all ]
Jesse McConnell updated CONTINUUM-786:
--------------------------------------
Fix Version/s: 1.1
> Failing to build project in right order or failing to recognize a svn change
> in the right order
> -----------------------------------------------------------------------------------------------
>
> Key: CONTINUUM-786
> URL: http://jira.codehaus.org/browse/CONTINUUM-786
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Affects Versions: 1.0.3
> Reporter: Vincent Massol
> Priority: Critical
> Fix For: 1.1
>
> Attachments: Continuum after Cargo commit rev1152.jpg, This is what
> happened after a build all.jpg
>
>
> Here's what happened.
> * Today (26th of July) around 15:35GMT+1, I made a big commit in Cargo
> touching several modules.
> * At 16:04GMT+1 I received 2 emails from C (C = Continuum) showing
> compilation errors in the following 2 modules (see
> http://ci.codehaus.org:8001/continuum/servlet/continuum/target/Summary.vm/fid/continuumProject):
> ** "Cargo Core Geronimo Container"
> ** "Cargo Core Jetty Container"
> * Note that the build is working fine locally here
> The
> [error|http://ci.codehaus.org:8001/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuild&buildId=47541&id=151]
> is because it's finding a class that's been renamed in the "Cargo Core
> Container API" module. Note that this module is defined to be built before
> the two modules in error above.
> What's also strange is that C shows a lot of modules in error (the red
> crosses) but if you look in the build results these modules are building
> fine. I'm attaching a screenshot to this issue.
> What can I do more to help debu this? This makes C unusable for me as I
> consider these 2 emails as false positives. Is there something I don't
> understand?
> 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
