I don't think I responded to this one? Alphabetizing in PB.project
would probably go a long way. I think the correct fix for this
might be to add all of these to .cvsignore -- that is assuming that
you only using the autogenerated forms? I'd be curious to see if you
do a clean build of your project with the newer builds if it gets rid
of those old subproject references now that the builder for
PB.project is change some. You can also just delete PB.project now
and have it regenerate.
On Sep 25, 2005, at 9:54 AM, Dov Rosenberg wrote:
> We are starting to have problems with conflicts in PB.project files
> and wot
> WOProject framework and classpath files in applications,
> frameworks, and
> subprojects now that we have multiple people checking things in on
> a regular
> basis.
>
> The PB.project problem might be resolved if the PB.project file is
> organized
> alphabetically when the rebuild is done. Also I am not sure how the
> PB.project files are generated. We kept getting a subproject listed
> in our
> PB.project that was no longer in the project. No amount of Eclipse
> refreshing could convince it otherwise. We finally manually edited our
> Subversion .svn/Entries file and Eclipse/WOLips built the files
> correctly.
>
>
> --
> Dov Rosenberg
> Conviveon/Inquira
> Knowledge Management Experts
> http://www.conviveon.com
> http://www.inquira.com
>
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Sep 27 2005 - 20:19:21 EDT