From: Douglas Campos <douglas@theros.info>
To: Mark Struberg <struberg@yahoo.de>
Cc: MatthiasSohn <matthias.sohn@sap.com>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"spearce@spearce.org" <spearce@spearce.org>
Subject: Re: [JGIT PATCH 7/9] removing eclipse project files
Date: Fri, 25 Sep 2009 10:25:24 -0300 [thread overview]
Message-ID: <ed88cb980909250625g7ae4685dh96aae6174c8d90d1@mail.gmail.com> (raw)
In-Reply-To: <212350.78171.qm@web27802.mail.ukl.yahoo.com>
Forwarding to list, as I always forgot to add all recipients (my bad :( )
> and no: currently the very file you mentioned contains a lot more stuff. In fact most of this are only editor settings, preferred formattings etc which has nothing to do with the build per se. Eclipse has the ability to import/export all those settings in a XML file which is version independent. We should go this way and also supply similar setting-files for Idea and NetBeans. But forcing those settings via an internal Eclipse plugin config file is imho bad practice.
The problem lies here. JGit, AFAIK, has very _strict_ rules, this is
the corner case that makes sense to enforce via IDE. It spares time
from everyone here.
I like the maven-generated eclipse projects, but I think that we need
the same level of service provided by the eclipse settings.
IMHO, as always.
--
Douglas Campos (qmx)
+55 11 7626 5959
next prev parent reply other threads:[~2009-09-25 13:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 21:16 [JGIT PATCH 1/9] mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de> Mark Struberg
[not found] ` <1253740570-10718-2-git-send-email-struberg@yahoo.de>
2009-09-23 21:16 ` [JGIT PATCH 3/9] moving some license files and META-INF Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 4/9] checkin all eclipse project file changes Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 5/9] mavenized org.spearce.jgit.pgm Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 6/9] enable missing test cases and fix jgit executable creation Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 7/9] removing eclipse project files Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 8/9] renamed the PathSuffixFilter test to JUnit conventions, so it gets executed via maven test Mark Struberg
2009-09-23 21:16 ` [JGIT PATCH 9/9] Add the <scm> section to the parent pom Mark Struberg
2009-09-24 6:29 ` [JGIT PATCH 7/9] removing eclipse project files Ferry Huberts
2009-09-24 6:55 ` Mark Struberg
2009-09-24 7:57 ` Ferry Huberts
2009-09-24 8:24 ` Mark Struberg
2009-09-24 8:57 ` Ferry Huberts
2009-09-24 8:57 ` Ferry Huberts
2009-09-25 21:40 ` Robin Rosenberg
2009-09-24 11:24 ` Sohn, Matthias
2009-09-24 11:50 ` Mark Struberg
2009-09-25 13:25 ` Douglas Campos [this message]
2009-09-25 21:17 ` Robin Rosenberg
2009-09-26 20:10 ` Mark Struberg
2009-09-27 19:52 ` Robin Rosenberg
2009-09-28 2:21 ` Jonas Fonseca
2009-09-28 6:34 ` Robin Rosenberg
2009-09-28 6:42 ` Robin Rosenberg
2009-09-25 21:33 ` [JGIT PATCH 1/9] mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de> Robin Rosenberg
2009-09-26 19:50 ` Mark Struberg
2009-09-28 12:46 ` Jonas Fonseca
2009-09-30 19:51 ` Mark Struberg
2009-09-30 21:16 ` Shawn O. Pearce
2009-09-30 23:13 ` Mark Struberg
2009-09-30 23:16 ` Jason van Zyl
2009-10-01 11:15 ` Mark Struberg
2009-10-01 13:55 ` Jason van Zyl
2009-10-01 1:33 ` Jonas Fonseca
2009-10-01 2:05 ` Douglas Campos
[not found] <891180.68852.qm@web27805.mail.ukl.yahoo.com>
2009-09-25 15:48 ` [JGIT PATCH 7/9] removing eclipse project files Michael Gaffney
2009-09-25 21:21 ` Robin Rosenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed88cb980909250625g7ae4685dh96aae6174c8d90d1@mail.gmail.com \
--to=douglas@theros.info \
--cc=git@vger.kernel.org \
--cc=matthias.sohn@sap.com \
--cc=spearce@spearce.org \
--cc=struberg@yahoo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).