JPF has moved - please update your browser bookmarks:
JPF has moved to its own server that is hosted at the NASA Ames Research Center. First and foremost - this does not change the licensing or public read access. JPF continues to be open source.
The reason for this move was twofold:
(1) extensions have become so numerous that we need to split them into their own projects (which can be hosted on the new server). JPF extensions do not necessarily coexist, and not many people work with more than one at a time, so they shouldn't convolute the JPF distribution and fight for classpath priorities. Since we still want to keep the jpf core and all our current extensions together, we needed more than one repository for JPF. Now we have Mercurial repositories for (eventually) each of them, all can be loaded as separate projects into your favorite IDE. You can follow the status of JPF projects (core and extensions) on http://babelfish.arc.nasa.gov/trac/jpf/wiki/projects/start
(2) With all these extensions from different authors, documentation becomes crucial. Even more so since the different JPF projects have vastly different levels of maturation, and some are cutting edge research that is very much work in progress. A wiki is much more suitable than the old static website to keep things up-to-date and facilitate collaborative development. The caveat is that we need strong hierarchical navigation for the JPF docu. So we wanted to have control over our wiki, and have chosen Trac so that we can integrate the docu with issue management and (eventually) the Mercurial repositories.
Splitting core and extensions also required a new JPF configuration/bootstrapping mechanism, which now uses site- and per-project configuration files, in addition to the old default.properties and the *.jpf application properties. Details on http://babelfish.arc.nasa.gov/trac/jpf/wiki/user/config
Speaking of *.jpf application properties - they are also the basis for the new jpf-shell infrastructure, which finally unifies the plugins, and uses standalone swing applications as graphical front ends of JPF (while still being able to communicate with the Eclipse/NetBeans IDEs).
The Sourceforge repository will stay, i.e. people can choose when to port their extensions. However, the JPF core in the Sourceforge Subversion repository will not be updated anymore - be aware of that code bases will diverge quickly, and our live site is now on http://babelfish.arc.nasa.gov/trac/jpf.
Check out http://babelfish.arc.nasa.gov/trac/jpf/blog and the rest of the (evolving) Wiki to find details about other technical and distribution changes.
If you are a maintainer of a current JPF extension and need write access for the new repositories or the Wiki, please go to http://babelfish.arc.nasa.gov/trac/jpf/wiki/about/account and register for an account on the new server.
The old mailing lists have been replaced by our JPF Google Group. We only have one group since traffic is low enough and we want to avoid redundant posts. You have to subscribe manually to this group.
Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. and its subsidiaries in the U.S. and other countries