continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Schram (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-377) "No files changed" shouldn't be a build error
Date Fri, 28 Oct 2005 19:22:11 GMT
    [ http://jira.codehaus.org/browse/CONTINUUM-377?page=comments#action_49522 ] 

Scott Schram commented on CONTINUUM-377:
----------------------------------------

Ok, I see from looking at the wrapper.log that I had a brief network problem at the time that
I was testing the features.  Sorry I didn't realize it at the time.  One can see this network
failure by unplugging the ethernet. :)

It would be nice if the build ends up in an error state, if some of that information about
what caused the error showed up in the "Build Error" field on the Build result screen.

Thanks!



> "No files changed" shouldn't be a build error
> ---------------------------------------------
>
>          Key: CONTINUUM-377
>          URL: http://jira.codehaus.org/browse/CONTINUUM-377
>      Project: Continuum
>         Type: Bug
>     Versions: 1.0
>     Reporter: Scott Schram
>     Priority: Minor

>
>
> When you manually make an ant project build, "No files changed" causes a build error.
> It should go ahead and build (and maybe even from a fresh checkout) and not be an error.

-- 
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


Mime
View raw message