Appologies for not getting back to you on this yet.
I can confirm there is a problem with the build process, I have found
what should be the solution in the IVY docs, but it isn't working for me
yet.
Now my baby daughter has arrived so I am not sure when I will fix this
properly.
I suggest adding a temporary fix that deletes the cache data for the two
modules before they are built. If I recall correctly there is an ivy
property for getting at the cache directory.
I'll come back to this when I can.
Ross
On 05/03/2010 17:00, Scott Wilson wrote:
On 5 Mar 2010, at 16:01, Ross Gardler wrote:
On 05/03/2010 14:29, Scott Wilson wrote:
I made some changes to the parser sub-project code, however whenever I
run Wookie with "ant clean-db run" the updated parser code isn't used -
is there anything I should do to ensure that Wookie runs with the latest
snapshot of sub-project jars rather than an earlier cached version?
What is your current workflow?
If you:
- edit a subproject
- "ant publish-local" in the subproject
- "ant clean-db run" (see NOTE 1)
You will (should?) be running with the latest snapshot.
OK, I've tried this but I still get the cached subproject build. The
subproject clearly has recompiled, but the main Wookie run command
doesn't pick it up.
The only way I've managed to get it to refresh is to manually delete the
jar from ~/.ant/cache (or I could clean the whole cache but I really
don't want to do that)
We could force the publish-local step from the core build script, but
forcing a compilation of all sub-projects just to run Wookie adds an
unnecessary step to the process. If we do add it then I would want it
to be configurable from local.build.properties
In most IDEs you can add the publish-local step to the standard build
process of the IDE and thus remove the need to manually publish.
Ross
NOTE did you notice that clean-db is no longer necessary if you set
"initDB=false" in the local.build.properties. Now you only need to do
clean-db if you want to start from a fresh install.
D'oh no I hadn't!
