This week's book giveaway is in the Java 9 forum.
We're giving away four copies of Java 9 Modularity: Patterns and Practices for Developing Maintainable Applications and have Sander Mak & Paul Bakker on-line!
See this thread for details.
Win a copy of Java 9 Modularity: Patterns and Practices for Developing Maintainable Applications this week in the Java 9 forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Eclipse workspace and projects  RSS feed

 
Pat Farrell
Rancher
Posts: 4686
7
Linux Mac OS X VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Eclipse seems to want to force me to have a redundant layer of directories for my projects. I can't tell if I am doing something wrong, or if this is inevitable.

If I have a project in my sandbox, say "foobaz" then I have a directory structure that yields:


Its easy to tie the foobaz directory to a git repository, etc. When I used NetBeans, the sources, libs etc. would go directly under this, i.e.


Eclipse insists on adding a layer, also named foobaz, so I have



What am I doing wrong?

I don't to set "sandbox" as my workspace, since that directory is not under git/svn control, and I don't want to lose any .metadata and other magic files.
 
Jeanne Boyarsky
author & internet detective
Sheriff
Posts: 37384
531
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Pat Farrell wrote:Eclipse insists on adding a layer, also named foobaz, so I have

I have /src at the top level of my projects. Try creating a brand new Java project in Eclipse making sure "create separate folders for sources and class files" is selected. This creates:
foobaz/src
foobaz/bin

The manually create the /lib and /dist folders in it.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!