- This topic has 5 replies, 2 voices, and was last updated 19 years, 1 month ago by
.
-
Posts
-
Hi,
I am using eclipse at work, and sometimes bring my work home to stay caught up. The source is checked into a subversion repository, so I just maintain a working copy on a usb thumbdrive, and update it when I want to work on it at home. For the most part, this works well. The issues I’ve stubbed my toes on are having different project settings on my home machine. Things like pathing/lib dependancies, etc keep biting me. Case in point, is that on my work system at sometime I remember configuring it to copy library jar files into the PROJECT_HOME/lib dir, but can’t remember how to do this on my home machine (so it does not work at home). Is there a recomended workflow/pattern to make concurrent developemnt easier? How about project capabilites ,etc.TIA!
RandyRandy,
Preferences and settings are stored under the workspace in the .metadata subdirectory. However, if your thumbdrive has your entire workspace there should be no difference in settings at all. However, if you’re just carrying a single project around on it, that would account for some of the behavioral differences. If you’d like to keep doing that, then I’d recommend keeping the .metadata folder on it as well and updating it as needed. Please note that this may be quite large, however.
Of course, another way to operate, which is what we do here, is to update our projects from a shared version control system that we can access from anywhere. However, given the security policies at your place of employment, this might or might not be possible.
Hi Scott,
The source/webapp is checked into subversion, and I use subclipse to keep things in sync, so that will be the preferred way. Currently when I am done at work, I check it into svn, and then do a svn update on my usb thumbdrive, which I then copy over my src dir at home (I don’t have remote access at home to the svn repo). Project stuff is not included (ie it is just the source, and part of the webapp (web.xml, faces-config.xml, etc).What I would like to be able to do is share the project settings (ie the project capabilties (spring/jsf/hibernate), libs, etc in subversion, along with the source code. this way I (or others) can check out the project and have it work without having to jump through hoops to recreate the project dependancies. What stuff would I need to check into subversion in addtion to the source code to make this happen? Is this the stuff in the .metadata dir?
As an afterthought, I have a workspace/Lib dir that I keep external libs, and I create userlibs that point to this. Works pretty well as long as I name the userlib the same name.
Tx for your help!
randy
edit: clarification on my current workflow.
What I would like to be able to do is share the project settings (ie the project capabilties (spring/jsf/hibernate), libs, etc in subversion, along with the source code.
That’s what I’d recommend. You’ll need to check in all the dot files (.project, .classpath, .mymetadata, etc) along with all your code artifacts. To see *all* the files, you can use the Navigator view and turn of the filtering of ‘dot’ files in it’s preferences. Checking in everything but the compilation output directory (bin, etc) is really what’s needed to have it work the way you’d like.
good news, this seems to work, and so far pretty well.
I checked in all dirs (all dot files/dot dirs, my PROJHOME/lib dir, etc). Only MINOR stuff was things like user defined libs, which is easy to fix (I keep all libs in my workspace ie workspace/Libs, and it is easy to replicate that).
I can now maintain a project working copy on my usbdrive, keep it updated. At home I copy it to my HOME/workspace dir, and start eclipse. works great.
tx for your help!
Randy
