aloys.oberthuer@gmx.net wrote on 02/25/2005 11:18:33 AM:
>> Still for it to work I need to open up the properties and add a JAR,
change
>> the Jdk, etc. to
>> trigger a rebuild. Otherwise the project shows a fault. Manually
rebuilding it
>> does not help.
>> And what might be a small bug: When I choose a non-default Jdk in the
Check out as...
>> Wizard I still get the default Jdk in my project properties and need to
choose
>> it again. Or is
>> this because I checked out the .project file?
>You really shouldn't use Checkout As ... if there is a .project file in
>the repository. This is because the file created by the wizard will be
>overlayed when the Checkout process happens. Also, what Checkout As ...
>can do is fairly limited. You can setup all sorts of fancy stuff in that
>Wizard, but in the end, the point of the Wizard was just to "register" the
>project and create the .project file. The stuff that gets checked out
>from the repository is just going to be placed where it exists relative to
>what you checked out in the repository. So if you have a folder named
>"src" in the repository you will get one in the WC. If you do not, it
>won't.
>Mark
But this means, all the developer's machines need to be setup the same way,
otherwise you'll get conflicting .project and .classpath files and adapting
these on one machine will make them incorrect on correcting them on another
machine??
Aloys
Received on Sun Feb 27 01:57:50 2005