Skip to main content

Thanks jTrac, You're Doing a Fine Job

I just wanted to give a shout-out to the members of the jTrac project. jTrac is an issue-tracking system which can be installed out of the box as a stand-alone server using Jetty and HSQLDB, or can be installed as a war in an existing server.

jTrac was very easy to install in our existing JBoss instance and required only a few settings and a directory for storing attachments and the application's HSQLDB database files. Once you have it installed and configured, you can create spaces for each of your applications. Each of these spaces can have a set of custom fields as well as a custom set of states and transitions. Write access to each space is limited to only members of that space. In addition you can make transistions dependent on a particular user role within the space.

The application seems to be mature enough to be feature complete, but does still have some minor nice-to-haves (book-markable searches, Eclipse Mylyn integration) and missing ui polish.

Labels:

Comments

Post a Comment

Popular posts from this blog

Using MonoDevelop to Create an ASP.NET Web Service

NOTE : instructions below are for MonoDevelop 2.6 Beta 2 - built on 2011-04-06 03:37:58+0000 Getting Started Create a new ASP.NET Web Application in MonoDevelop: From the menu, select: File → New → Solution… Expand C# . Select ASP.NET → Web Application . Enter a name for the ASP.NET project that will be created in the solution in Name: . Change the root location for the solution in Location: , if desired. Change the name of the root solution in Solution Name: , if desired. The Results – I What you have after executing the new ASP.NET Web Application project wizard is a solution containing one ASP.NET Web Application project. In the default project view in MonoDevelop, you'll find the following items: Default.aspx – This is the default web form rendered and presented in the browser when http://<server>:<port>/ is accessed. Default.aspx.cs – This C# file contains the developer-created common code and event handlers which can be used to affect the process
5 comments
Read more

Testing Toolbelt: SpringJUnit4ClassRunner

The org.springframework.test.context.junit4.SpringJUnit4ClassRunner class is another implementation of the JUnit TestRunner class which is used to enable various features of Spring for every run of the test class and every test within it. To use the features provided by the SpringJUnit4ClassRunner class, you need to mark the class using the RunWith annotation using SpringJUnit4ClassRunner as its parameter. In addition to the custom test runner, you will want to mark the class with the ContextConfiguration annotation. The ContextConfiguration annotation is used to mark classes which will automatically read a Spring configuration file and use it to create an ApplicationContext . By default, this file located at <package path>/<test class name>-context.xml . Use the locations argument to over-ride. The ApplicationContext used by the Spring-integrated test will only be loaded once for the whole test class. This behavior can be over-ridden by annotating a test metho
2 comments
Read more