so you have 3 workspaces now? -igor
On 12/13/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
i am against removing those files If i had to checkout something and it doesn't work right out of the box compile time then i would already look for something else. Especially that we use maven. We have no idea what dependencies there are. So everybody has to know mvn eclipse:eclipse or something like that ? (i never used that) to generate the classpath. For me they are core project things. And why you have everything in one workspace is just igor doing stupid things ;) (but i agree eclipse should have "solution" support for this) johan On 12/13/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > IMO .classpath files should be removed from the repository as > > every developer has different usage: one wants JAR dependencies, > > one wants to reference other projects in the workspace. And > > apparently Igor has multiple versions of Wicket in his workspace > > thus needs different project names, whereas Eelco has not. > > Just for the record, I have 1.2, 1.3 and 2.0 in the same workspace. > Just differently named, and the deal was to leave the dependencies > without any version info in the projects. > > Eelco >
