Hi Niclas, > > Correct. IMVSO, the entire Studio must be able to be created without > Eclipse
this is already possible. Eclipse itself generates an ant task for building and testing. > itself, and that versioning and dependency management is centralized to > the > index.xml. I had a conversation with Steven this morning - and I proposed to synchronize the index.xml and projects dependencies. This is because you will change alot of dependencies / versions while developing a project in Eclipse. My idea is to enable the sync feature with every change in a project. > > > You also removed all the .project files. You will not be able to load > > those projects into eclipse workspace then. > > I can't load it anyway, since these files keep getting absolute references > in > them, showing your local layout. This is only true for .classpath file. In .project there is no filePath at all. For the classpath it is a bit a silly problem: you can change the file paths to be relative by hand. But they are overwritten by eclipse if you change the classpath. I will figure out a solution and post this question to the usergroup. > Talking to friends who are using Eclipse in a distributed environment, > they > say that keep the .project and .classpath files non-committed to the > codebase > repository. They mean that will improve the collaboration problems, and I > think it makes sense, since Eclipse have chosen to make these files > filesystem hidden (Linux/Unix). Hm - not sure. See above All the best Andreas --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.762 / Virus Database: 510 - Release Date: 13.09.2004 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
