eHour is a Web-based time registration tool for project-based businesses. The primary objective is to keep time tracking as simple as needed while still being very effective at measuring and reporting the amount of time your team spends on a project. eHour is available as a standalone version or a WAR file, which you can deploy in your existing environment. eHour is JVM (Java & Scala) based.
ProjectForge is a Web-based solution for project management including time sheet booking, Gantt charts, financial administration and controlling, issue management, and managing work-break-down structures. First-party and third-party plugins are supported. Ready-to-run packages of the ProjectForge server are available for Windows, Mac OS X, and all Java6-capable platforms (database and Web server are included). ProjectForge is also available as a web-archive file (war) for usage within your own Web server and for your own database installation.
QuickBuild is a continuous integration and release management server, acting as the central place to produce, test, deploy, and release software builds. It is designed to guard the health of your project by preventing broken builds, and to improve your build delivery process by pushing builds through a customizable pipeline (for example, dev->QA->release) with related information connected such as resolved issues and relevant SCM changes.
WebMon is a Java VM monitoring tool. It can be deployed to any servlet container or embedded in your EAR, or in JavaSE applications. RSS, e-mail, and Jabber notifications of potential problems are sent. It is useful if you aren't able to use traditional tools such as JConsole or VisualVM.
GWiki is an embeddable Wiki engine. It allows users to edit rich text fragments in an application you develop. It supports I18N files and mulitimedia content. Gwiki can be extended with macros written in Java or Groovy. It has a powerful right and role system, which can be fed from external sources such as LDAP, and allows access to business entitiels from wiki pages. It comes with Wicket integration out-of-the-box. Wicket-HTML-Fragments can be held within GWiki, so these pages can be managed by the Wiki System, while Wicket handles the application logic. GWiki can be deployed as a servlet on every servlet container. GWiki can use a filesystem, a Zip archive, or a database for its content storage.