Oli's Blog

Last week PatternTesting 0.8.0 was delivered. The main difference to PatternTesting 0.6.x is a split into several subprojects.

For the Hello-World-Example described in October you have to add now two jar files:

• patterntesting-check-0.8.0.jar
• patterntesting-rt-0.8.0.jar (for @SystemOutNeeded)

You can download the files from sourceforge. If you use Maven add the following lines into your pom.xml:

---

<dependency>
  <groupId>net.sf.patterntesting</groupId>
  <artifactId>patterntesting-check</artifactId>
  <version>0.8.0</version>
</dependency>

---

Happy Patterntesting...

If you want to use Patterntesting with Eclipse you must install the AspectJ plugin AJDT. If you haven't done it add the site http://download.eclipse.org/tools/ajdt/34/update for Eclipse 3.4 and install it.

Now we are ready to create a simple Java project with a hello.World class inside:

---

package hello;
public class World {
    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

---

Before we can add the PatternTesting library we must convert the project into a AspectJ project. Select "AspectJ Tools > Convert to AspectJ Project" from the project's context menu (right mouse key).

Next we will integrate the PatternTesting library. Download it from the download page and call the project properties. Select the entry "AspectJ Build" and then the tab "Aspect Path". Add the patterntesting.0.6.0.jar you have downloaded and press ok.


You should see now the warning No logging should be done using System.out! in the problems view. I don't know any program which needs to use System.out for printing so this warning is normally ok. One exception from this rule is this Hello-World program so you can suppress it using the anntoation @SystemOutNeeded:

---

package hello;
import patterntesting.java.annotation.*;
public class World {
    @SystemOutNeeded
    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

---

happy patterntesting...

This weekend a new version of PatternTesting was released. There is now some aspects for thread support available. Other aspects are now made concrete and can be (de)activated by annotations (e.g. @NullArgsAllowed or @SystemOutNeeded). For the other changes see Changes Report on PatternTesting homepage.

What is still missing are some samples how to use PatternTesting. This will be a task for the next weeks.

Stay tuned...

In the last week I improved Patterntesting and coupled some aspects with annotation for easier handling. But at the moment the SSH service of sourceforge is closed so that 'mvn site-deploy' does not work (see sourceforge tracker).

Also the patterntesting-devel mailing list is not alive at the moment. Sourceforge has moved to a new data center which was announced some days ago. I'm not the only one with this problem so I will wait...

Stay tuned...

This weekend a new version of PatternTesting with some ideas from the BOF session on the JAX conference was released on Sourceforge. It is also available via Maven repository on ibiblio.org.

Since last week patterntesting is available on ibiblio. If you use Maven for your builds you can use now the default repository.

Today release 0.5.0 of PatternTesting is released on Sourceforge. There is also a maven repository available under http://patterntesting.sf.net/m2/. There is an upload request on codehaus.org so I hope the patterntesting repository is synced the next days or weeks so that you can find it also on ibiblio.org.

This is my first release since I reanimated patterntesting (see PatternTesting Reloaded). One goal of this release was to become familiarized with the release process for Maven and Sourceforge.net. If you plan to do it for your project here 2 links which helps me:

• Guide to uploading artifacts to the Central Repository
• SourceForge.net: Offering Files for Download

The changes report and other project reports you can find on the PatternTesting home page.

Happy (Pattern)Testing!

PatternTesting is back! In the last months I changed the build process to Maven 2 (from Maven 1) and adapted the structure. Also the JUnit tests are reworked and the structure was adapted for Maven 2. There is still a lot of work left but a 'mvn site:deploy' is now possible.