[Building Sakai] Out of date Eclipse files

[Matthew Buckett]

2009/8/19 Matthew Buckett <matthew.buckett at oucs.ox.ac.uk>:
> 2009/8/19 Noah Botimer <botimer at umich.edu>:
>> Do we have any idea what the silent majority expects? That is, every
>> time I've tried to generate .project/.classpath, I've gotten
>> something wildly different from what is checked in. It may be
>> inertia, but it feels miserable to me to have everything up-ended in
>> your IDE with no sense of why it's "better" other than saving someone
>> else some maintenance headache. I specifically mean how the packages
>> are broken out and how the package explorer, etc., behave.
>
> If you regenerate them on a 2.5.x checkout then you will end up with
> projects named differently and the division of projects being
> different. On 2.6.x/trunk it should be pretty much the same.
>
> Changing between 2.5.x and 2.6.x does take a little getting used to
> (the different naming). I wouldn't suggest removing all the
> .project/.classpath files on the 2.5.x branches.

Just to give an example under 2.5.x the announcements tool has these
projects in the eclipse package explorer:

announcement-api
announcement-impl
announcement-tool

and the same tool in 2.6.x/trunk is:

sakai-announcement-api
sakai-announcement-help
sakai-announcement-impl
sakai-announcement-pack
sakai-announcement-tool

These are both with running any maven commands and are from a clean
svn checkout.

-- 
  Matthew Buckett