BeanKeeper

How to join development

It is our experience, that a community of enthusiastic developers is more agile, and can beat a concentrated effort by a company almost any time. So we are always searching for developers who are interested in this project, and are willing to contribute something to help it. If you are a Java developer, you used BeanKeeper and think it is a great tool, have the enthusiasm to try contributing, then we invite you to try!

You can find all information about project structure, development cycle and other things on the Wiki.

Current state of project

This software is currently developed at the lowest priority inside the company as we have other responsibilities (like projects that pay). There is only a little community currently outside the company, but we really hope this will change in time.

There are also currently no known public projects that use this library. That said, the project is currently is in a usable state, and there are a few hobby level projects that use the library as far as we know. If you want a stable, zero risk solution, we recommend Hibernate for example. Use this library only, if you have time to evaluate it properly, and are willing to take a little risk for the benefit of reduced complexity.

Project Command Center

• Mailing Lists: You can subscribe to any of the mailing lists to become part of the discussions about user experiences, bugs, or the development.
• Wiki: This is the place for getting/contributing knowledge about BeanKeeper.
• Bug Tracking: Add or browse the current bug database.
• Feature Requests: Here you can add wishes, and track which features are scheduled for which release.

• Web access to source: You can browse the source of the library.
• svn://svn.netmind.hu/beankeeper/dev/trunk: You can check out the whole project with history. Repository is public, that means it can be read by all. Write is restricted to registered developers (read the wiki to find out how to become one).

• beankeeper-2.6.4-SNAPSHOT.jar (Revision: 691 ): Download the lastest build of BeanKeeper. Warning: these are mostly unstable latest builds. Below are some metrics of this build.
• Test output: The TestNG output of running the tests.
• Code coverage: The output of Emma, which gives a metric about how well the above tests cover the whole software.
• Findbugs output: This is the output of the automatic run of findbugs on the latest nightly build.
• JDepend graph: A dependency graph of BeanKeeper's internal packages provided by JDepend.