Hi All,
I had a customized versions of .classpath and it seems te be giving a
conflict to me. I also belive that IDE specific files should not be included
in the SVN repo.
So +1 for removing those.
Chamikara
On 8/23/06, Afkham Azeez <[EMAIL PROTECTED]> wrote:
Me too. +1 to NOT havi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If the project would have IDE specific files, that would lead to
uncontrollable filtering, when building src and bin distributions and so
on. Besides mvn/maven ability to build the correct project files
(single/multiproject) would cover the (+90
Me too. +1 to NOT having any IDE specific files in the code repository.
On 8/23/06, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
Eran Chinthaka wrote:
>Any action item on this? I can still see .project files in the svn.
>
>Do we wanna move that to a separate folder as Denn
eez wrote:
>
>
>>IMHO the codebase is going to get cluttered with so may IDE specific files
>>of different IDEs if users who use several IDEs (IDEA, JBuilder, JDeveloper
>>etc, etc.) all start committing their IDE specific files. So as a general
>>practice, it is better
Any action item on this? I can still see .project files in the svn.
Do we wanna move that to a separate folder as Dennis suggested or wanna
completely remove them?
-- Chinthaka
Afkham Azeez wrote:
> IMHO the codebase is going to get cluttered with so may IDE specific files
> of differen
ributor"
which might lead to "alright lets make it really hard to set up a
development environment so we only get clever contributors". We're
talking about inclusivity and community development (which I'm sure
none of us disagree with) ... So perhaps to draw this to a conc
If there is going to be a vote, I'm +1 for *not* including any IDE specific
files in th SVN repo, since having those in the repo unneccesarilly
complicate things.
Azeez
On 8/18/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Jochen Wiedmann wrote:
> Eran Chintaka wrote:
>
>&
. 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?
Again, y
IMHO the codebase is going to get cluttered with so may IDE specific files
of different IDEs if users who use several IDEs (IDEA, JBuilder, JDeveloper
etc, etc.) all start committing their IDE specific files. So as a general
practice, it is better not to commit IDE specific files.
Azeez
On 8/18
?
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,
10 matches
Mail list logo
