git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [JGIT PATCH 7/9] removing eclipse project files

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Sep 25, 2009, 21:17 UTC
Message-ID
<200909252317.02296.robin.rosenberg.lists@dewire.com>
In-Reply-To
<212350.78171.qm@web27802.mail.ukl.yahoo.com>
torsdag 24 september 2009 13:50:11 skrev Mark Struberg <struberg@yahoo.de>:
Show 7 quoted lines
> Hi Matthias!
> 
> the answer is a clear yes and no  - a 'jein' for german speaking people like you ;)
> 
> yes: we have the same settings for the compiler as used before: jdk 1.5 for source and target. This is exactly what has been taken in the ant build which was used prior to maven. 
>
> Please note that the settings in org.eclipse.jdt.core.prefs never had (and must not have) any impact on the created jar!
Not sure what ant files you are referring to here and which jars. The plugins downloadable from jgit.org has been built using PDE build. so some of the .settings should affect the compiler and thus the generated jars.
> 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.

That way is awkward and people to import the settings and screw them up in their workspaces. I've made the projects I'm involved use .settings and make different settings mostly a non-issue because everyone gets new settings automatically as they change. Prior to eclipse 3.3 sharing settings was a big problem, but It's not a big deal nowadays. The most annoying thing is that some settings are not available as project specific settings. 

We use 3.3 (well I think the last user dropped it recently), 3.4 and 3.5. I often have to fix up new projects but that is typically a one-time per eclipse project problem. (typically the JRE gets bound to a specific install location).
The .launch files is another story since they change format all the time.
-- robin
Previous: Douglas CamposNext: Mark Struberg
Message 30 of 35 in “mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de>”
  1. 1/9 mavenizing step 1: moved over the initial poms from Jasons branch Signed-off-by: Mark Struberg <struberg@yahoo.de>Mark Struberg, Sep 23, 2009
  2. Robin RosenbergSep 25, 2009
  3. Mark StrubergSep 26, 2009
  4. Jonas FonsecaSep 28, 2009
  5. Mark StrubergSep 30, 2009
  6. Shawn O. PearceSep 30, 2009
  7. Mark StrubergSep 30, 2009
  8. Jason van ZylSep 30, 2009
  9. Mark StrubergOct 1, 2009
  10. Jason van ZylOct 1, 2009
  11. Jonas FonsecaOct 1, 2009
  12. Douglas CamposOct 1, 2009
  13. 3/9 moving some license files and META-INFMark Struberg, Sep 23, 2009
  14. 4/9 checkin all eclipse project file changesMark Struberg, Sep 23, 2009
  15. 5/9 mavenized org.spearce.jgit.pgmMark Struberg, Sep 23, 2009
  16. 6/9 enable missing test cases and fix jgit executable creationMark Struberg, Sep 23, 2009
  17. 7/9 removing eclipse project filesMark Struberg, Sep 23, 2009
  18. 8/9 renamed the PathSuffixFilter test to JUnit conventions, so it gets executed via maven test.Mark Struberg, Sep 23, 2009
  19. 9/9 Add the <scm> section to the parent pomMark Struberg, Sep 23, 2009
  20. Ferry HubertsSep 24, 2009
  21. Mark StrubergSep 24, 2009
  22. Ferry HubertsSep 24, 2009
  23. Mark StrubergSep 24, 2009
  24. Ferry HubertsSep 24, 2009
  25. Ferry HubertsSep 24, 2009
  26. Robin RosenbergSep 25, 2009
  27. Sohn, MatthiasSep 24, 2009
  28. Mark StrubergSep 24, 2009
  29. Douglas CamposSep 25, 2009
  30. Robin RosenbergSep 25, 2009
  31. Mark StrubergSep 26, 2009
  32. Robin RosenbergSep 27, 2009
  33. Jonas FonsecaSep 28, 2009
  34. Robin RosenbergSep 28, 2009
  35. Robin RosenbergSep 28, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.