Eran Chintaka wrote:

1. There are lot of non-eclipse users who are checking out/in code (FYI
: most of the axiom devs are *not* using eclipse). So why bother we
checking out eclipse junk :)

Are you telling me, it disturbs you to have two additional files and a
folder, which are most possibly even hidden because of the .foo
convention?


2. As Ajith also had already mentioned, maven helps you to generate the
relevant IDE specific stuff.

It does. However, the output of the plugins is far from acceptable. In
particular, the output folders will rarely match.

Besides, there's more to it: Compiler settings (which should obviously
match those from the pom), formatting guidelines, and the like. These
aren't controlled by any plugin.


3. Some one can declare a variable in Eclipse, pointing to his folder
and can accidentally commit that in to svn.

The files I have committed do not use any variables.


4. If some one is having a customized version of .project and .classpath
files, they always gets conflicts, which is un-necessary, IMO.

IMO, that's a question of discipline. And, if it actually happens:
What prevents you from revoking or overwriting a commit?


5. None or most of the WS project do not have IDE specific committed so
far. Eg : Axis2, axiom, neethi, etc.,

JaxMe, XML-RPC, and ws-commons-util do. :-)


The point I am trying to make is that IDE specific files can be good
for some people. If they proove to be disturbing the projects work,
then I'd be the first to remove it. But so far I can only see a "we
don't like it" and no "look at this example, it has really done harm".
Which matches my personal experience with other projects.


Jochen



--
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to