Re: [castor-dev] Mvn build and Eclipse
Werner Guttmann <[email protected]> Tue, 04 May 2010 09:13:00 +0200
| Newsgroups | gmane.comp.java.castor.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Andras, On 03.05.2010 08:23, Andras Hatvani wrote: > Hello, > > Although I'm not an official committer, but within the scope of a > university course I'm involved in the development and am affected, too > I'd like to share my thoughts. > I completely agree that IDE-specific files shouldn't be part of any > project's source tree, but I also don't like, if one project's modules > fill half of my workspace. Same here, but I learned to accept that I might have more than one workspace. And indeed, I do have in average three to four workspaces, depending on the number of projects I am working on in parallel. > Whether one decides for the single- or for > the multi-project method, both require trade-offs: > - clean and compact workspace vs manual classpath maintenance and > - automated classpath maintenance vs "polluted" workspace. > These two factors are which I can think of at first, but I'd be glad to > see a more complete list of benefits and drawbacks. > Btw, did anyone already contact the maven mailing list for further > information? > > Andras > > On 1 May 2010, at 16:20, Werner Guttmann <[email protected]> wrote: > >> Hi everybody, >> >> I'd really like to see .classpath and .project being removed from our >> SVN repository. I know there's some resistance, so let's use this >> thread to get an complete overview on any objections. >> >> Cheers >> Werner >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email