- to report some news about the new maven-ooo-plugin-it project
- to give a short introduction how to start a project with a local GIT repository and push it later to github
Local GIT Repository Created
Yesterday I decided to start my own integration test project for the maven-ooo-plugin. Here are the steps to create a GIT repository for this project (GIT must be installed):- create the project directory (mkdir maven-ooo-plugin-it)
- change to this directory (cd maven-ooo-plugin-it)
- create local GIT repository (git init)
Pushed to GITHUB
Today I wanted to push this project to github. If you log and follow the Dashboard link you find a New Repository button which I used to create the maven-ooo-plugin-it repository on github. Now I got a list of steps which I followed:- cd cd maven-ooo-plugin-it
- git remote add origin git@github.com:oboehm/maven-ooo-plugin-it.git
- git push origin master
... link (0 Kommentare) ... comment
As I learned today one reason for an com.sun.star.deployment.DeploymentException can be:
- an incomplete classpath entry in the generated manifest file,
- a missing __writeRegistryServiceInfo or
- a missing __getComponentFactory method in a Java component
... link (0 Kommentare) ... comment

Na ja, jetzt sind es halt zwei Monate später. Aber wer Interesse daran hat, die Zeitschrift gibt es noch im gut sortierten Zeitschriftenladen...
... link (0 Kommentare) ... comment

Two objects which are equals should return the same hash code (and not the other way around, as some developers think).
...Note that it is generally necessary to override the hashCode method whenever this method is overridden, so as to maintain the general contract for the hashCode method, which states that equal objects must have equal hash codes.This is corresponding Javadoc about the equals method. For those who forget this PatternTesting offers now an ObjectTester which checks classes with overwitten equals methods:
ObjectTester.assertEquals(my.little.Dummy.class);The ObjectTester will create with this call two Dummy objects to check the implementation. If it is not ok an Assertion Error will be thrown.
You can also add a package to check if all classes in the package have a correct equals/hashCode implementation:
ObjectTester.assertEquals(Dummy.class.getPackage()); ObjectTester.assertEqualsOfPackage("my.little");Both calls are identical. You can also exclude classes from this check. This is sometimes necessary for classes where the constructor produces different objects (as is the case for the Date class, for example).
In a similar way you can check classes with the SerializableTester and CloneableTester if they are really serializable or clonable.
... link (0 Kommentare) ... comment
<build> ... <sourceDirectory>${basedir}/src</sourceDirectory> <testSourceDirectory>${basedir}/test</testSourceDirectory> <resources> <resource> <directory>src</directory> </resource> </resources> <testResources> <testResource> <directory>test</directory> </testResource> </testResources> ... </build>In diesem Beispiel liegen die Sourcen unter src und die Test-Sourcen unter test (inkl. der jeweiligen Resource- und Property-Dateien).
... link (0 Kommentare) ... comment
At github I found an enhancement of this Maven plugin. But the only stuff which was working on my MacBook was 'mvn archetype:create...'. Because I needed the plugin I forked it to my maven-ooo-plugin clone and tried to continue the work of Cédric and Frédéric.
What's working:
- mvn archetype:create (more or less, no changes from my side)
- mvn generate-sources (call of idlc, regmerge and javamaker, see OOo Java Eclipse Tutorial)
- mvn package (creation of OXT, the OpenOffice extension)
... link (0 Kommentare) ... comment
validator.validate(new StreamSource(reader))Marc Guillemot macht mich darauf aufmerksam, dass in den Javadocs zum StreamSource-Konstruktor der folgende Hinweis enthalten ist:
...Normally, a stream should be used rather than a reader, so that the XML parser can resolve character encoding specified by the XML declaration...Und tatsächlich - nachdem ich den Reader durch einen InputStream ersetzt hatte, lief mein Testfall ohne Fehler durch.
... link (0 Kommentare) ... comment

If you use Maven PatternTesting is not yet sync'd to the Central Maven Repository (the ticket for upload is still "reopened"). So add labs.agentes.de/repository to your POM as described in Build with Maven.
The next event where you can watch PatternTesting live will be probably the gearconf in Düsseldorf. I plan to present a little drama with Christian Heise about a normal day in a developers life.
Stay tuned...
... link (0 Kommentare) ... comment

Daneben gab es viele erstklassige Vorträge auf dem Java Forum Stuttgart. Als Mitorganisator war es nicht immer einfach, sich für die richtigen Vorträge zu entscheiden, aber ich denke, es ist uns ganz gut gelungen. Etwas blöd war die Lage des Mozart-Saals, bei dem man erst mal raus in die gleißende Sonne musste, ehe man dann in ein dunkles Loch hinabstieg. Aber von dieser "Umleitung" haben wir leider auch erst kurz vorher von der Messeleitung erfahren. Auf Heise Developer steht ein sehr schöner Artikel über das Java Forum, dem ich mich nur anschließen kann.
... link (0 Kommentare) ... comment

What's new with 1.0.0? For Maven user the group id has changed to "org.patterntesting". While it is not yet sync'd to Maven's default repository you can find it in labs.agentes.de/repository/.
For Non-Maven user the download was now simplified. You need only to download patterntesting-libs-1.0.0-bin.zip from Sourceforge which contains all PatternTesting libraries and the libraries where PatternTesting depends on.
Some of the samples are now documented in the PatternTesting Wiki under Getting Started but are not yet available for download. This will come with PatternTesting 1.0.1. But you can find the sources in CVS below the patterntesting-samples module (the intro and jfs2010 directory).

With PatternTesting 1.0.0 also the home page has moved to patterntesting.org. If you are interested in PatternTesting you can see it also at the Java Forum Stuttgart at 1st July.
Happy PatternTesting...... link (0 Kommentare) ... comment

... link (0 Kommentare) ... comment

... link (0 Kommentare) ... comment

Mit dem zweiten Vortrag, "Pleiten, Pech und PatternTesting", bin ich noch nicht ganz fertig, aber da habe ich ja noch bis Samstag, 12. Juni Zeit...
... link (0 Kommentare) ... comment
... link (0 Kommentare) ... comment