compilation and packaging automation in How Do I? Posted January 20, 2009 · Report reply >> There is a non-documented option that can be used for this goal. The suggested approach works perfectly! Now, my .prj file no longer contains any references to the jars, which is exactly what I want. >> May I ask you, do you plan to change the content of this directory or do you need to create it once? The contents of the dir changes over time, though not very frequently. Just a collection of tens of third party dependencies that are updated and extended now and then. Right now it is a collection of jar files that have been statically checked into our source code repository, but once we integrate the JET compilation with the rest of our Maven-based build system, the dir with dependencies is determined by that system at compile time. So the less I have to meddle with JET project files, the better. >> If you create a JetPackII project with all the paths relative to the root directory, then you will be able to build this project on any machine with the same folder structure. What modifications do you mean? I have been able to turn all paths into relative paths. "Without modifications" means that I can relocate my source code without breaking the project files. This is important as we frequently create branches of our code. Still, I make a temporary copy of the .jpn file that I remove afterwards, as xpack does alter its contents slightly (some last modification dates if I recall correctly). Also, the file contains a lot of references to the jar files that I use, so I probably have to regenerate it once my dependencies change. I see no way to update the file automatically.