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 27, 2009, 19:52 UTC
Message-ID
<200909272152.33224.robin.rosenberg.lists@dewire.com>
In-Reply-To
<892492.1652.qm@web27801.mail.ukl.yahoo.com>
lördag 26 september 2009 22:10:16 skrev Mark Struberg <struberg@yahoo.de>:
> 
> As you already pointed to: we have to clearly separate between settings stored in the project itself and settings stored in the workspace. The first are by far not all settings needed, the 2nd are not checked in to git anyway. Maybe I didn't  find it yet, but is there an ability to set formatter settings for XML (e.g. Tabs vs spaces policy)? I was only able to specify this for the whole workspace and not on a per project basis.

Those are workspace settings in the 3.4, not checked 3.,5 yet. You could add it to bugzilla as a feature request. All settings should be available as project settings I think.

> And there is a lot more which imho cannot be set for a project. So checking in the xml sounds like it is way more powerful isn't? And we would have this

For JGit, not really. Everything that is not project settings should be left as the default. The only reason is tool constraints. I'm not well versed enough to tell what neatbeans does here.

> feature for a lot non-Eclipse users too (e.g. for Jonas who hacks the nbgit NetBeans plugin based on JGit (again: EGit is a different story!)).

I'm not sure keeping netbeans settings would be a problem, but that is about how much we could do

Show 12 quoted lines
> 
> > 
> > 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.
> 
> And the profiler settings, and and and. It's sad, but the list is long :(
Yep...
> We can also let the eclipse settings files checked in currently if you like. But I'd be happy if we continue collecting information and then make a decision.

I definitely think we should keep them until we find an alternate solution. The projects settings are way too useful to be thrown out.

-- robin
Previous: Mark StrubergNext: Jonas Fonseca
Message 32 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.