Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <464827222.1112227096665.JavaMail.jira@ajax.apache.org>
Date: Thu, 31 Mar 2005 01:58:16 +0200 (CEST)
From: "Jeremy Boynes (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-190) Derby build should be incremental
In-Reply-To: <1106499423.1112223149617.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-190?page=comments#action_61853 ]
     
Jeremy Boynes commented on DERBY-190:
-------------------------------------

The ant task the build uses to compile is incremental but does not check dependencies. Thus a second build will recompile files that have changed but not files that depend on them that have not been touched. This works most of the time.

The clobber (and clean which removes the object code but not generated source code) targets would typically be run after an update, before a testrun (and hence before commit), or when you see strange AbstractMethodErrors and the like.

> Derby build should be incremental
> ---------------------------------
>
>          Key: DERBY-190
>          URL: http://issues.apache.org/jira/browse/DERBY-190
>      Project: Derby
>         Type: Improvement
>   Components: Build tools
>     Versions: 10.0.2.2
>     Reporter: David Van Couvering

>
> You should not have to clobber and rebuild from scratch each time you update or modify your source.  This is time-consuming and affects overall productivity.    

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira