Nicolas Richeton

I’m having a Talend Open studio training today on the brand new 2.2.0 GA release. This release includes some nice new features such as advanced XML generation, export jobs as webservices, LDAP connectors, easy logging, automatic deployement on SpagoBI, etc.

One funny thing (hum) is that they are also hit by the update site issue of RCP 3.3 I have with ShareMedia (no update site listed in the update manager)

I spent less time on Sharemedia last week, because I was studying Maven usage in a real project context. But there are still some news :

Linux Build
ShareMedia is currently only tested on Windows and OSX platforms. The Linux build is sometime tested on some linux boxes to ensure it runs.

The latest tests I made this week were not good : UI was reaaally slow and MediaFlow did not worked. This is really strange, as both win and osx builds work great.

I always believed that I’ll have more issues on the OSX platform as this is the least represented among commiters and users. I was wrong, Linux seems worse.

So be warned, trying ShareMedia on a linux box will give you a really bad opinion of it. However, feedback is welcome, especially on the MediaFlow / OpenGL part. If you manage to get it work, please send me a comment/mail.

Picasa Web
In the latest nightly build, we have write support for Picasa Web libraries. Simply enter you google credentials, and you will be able to upload photos coming from your computer, other picasa albums or Jabber shares simply by Drag and Drop. You can also edit metadata (date, description) as you would do for local files.

There is still room for improvement : support for more metadata, image resizing before upload, …. this will come soon.

Nothing new, but this may help maven newbies.

• Using Jetty to run maven webapps with automatic context reloading :
  Add the folowing plugin to your project
  
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<scanIntervalSeconds>10</scanIntervalSeconds>
<webAppConfig>
<contextPath>/test</contextPath>
<tempDirectory>
${project.build.directory}/work</tempDirectory>
</webAppConfig>
</configuration>
</plugin>

  Then run :
  
mvn jetty:run

  See the maven-jetty-plugin page for more information
• Debugging webapps with maven : this can also be used to debug any remote java application
• Unit testing with Hibernate and HSQLDB
• Beware of “Q for Eclipse” : it seems that this maven plugin for eclipse changed my pom.xml and broke my jetty configuration (some attributes were removed). You should rather use m2eclipse for now