[Springframework-developer] Most build artifacts now produced under target. You need to kill build.properties file!

[Colin S. <col...@ex...>]

As per the previous discussion, I have changed the Ant and Eclipse 
builds to output most artifacts to somewhere under a base 'target' 
directory. The exception to this is the 'dist' and 'docs/api' contents, 
which remain unchanged.

You need to (one-time) manually remove the old top-level dirs produced 
by the build, such as
  .classes
  .testclasses
  junit-reports
etc.

PLEASE READ: The existing properties system, where build.properties was 
checked in, but people also commonly changed values to do something like 
turn off a test, was not really great, since it's never a good idea to 
modify CVS files with changes which shouldn't be checked it. The file 
will always show up as modified, and it's very easy to accidentally 
check it in. So I have made project.properties the source for all 
default properties, and build.properties only for _overriding_ these. 
This is also how Maven actually treats these files, as a bonus.

As such, if you didn't change any values in build.properties, just kill 
your existing build.properties file. If you changed one or more values, 
then only those changed values should be left in build.properties. Your 
build will almost certainly break if you just leave the existing 
build.properties there, since some properties were renamed!

For Eclipse: my Eclipse got massively confused with the move of the 
output folders. No amount of refresh or synchronization could get it to 
be happy and not think that there were conflicts in regards to the old 
output folder. The way I resolved things was to right click on the 
project, do a 'delete' (but do _not_ delete contents), then do a 
re-import of the project. And don't forget to share it again for CVS.

Regards,
Colin