What's new in the coming Gwt Maven Plugin 2.1.1

The coming Gwt Maven Plugin 2.1.1 will have new features.

This stuff is currently available as 2.1.1-SNAPSHOT in the codehaus repo : https://nexus.codehaus.org/content/groups/snapshots-group/

Running your application in debug mode with AppEngine Launcher

  <build>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>gwt-maven-plugin</artifactId>
        <version>2.1.1-SNAPSHOT</version>
        <configuration>
          <server>com.google.appengine.tools.development.gwt.AppEngineLauncher</server>
        </configuration>
      </plugin>
    </plugins>
  </build>

See appengine-launcher

Css Interface Generator

See Css Interface Generator

More Gwt compiler options
-compileReport, -optimize, -XsoycDetailed, -strict (see Documentation )

Compiler Report
To have link to the Gwt compiler report in your Maven generated web site
See Compiler Report

Full changelog

Do not hesitate to test and send feedback.
Thanks !

Release Maven Gwt Plugin 2.1.0 (gwt 2.1.0 compatible)

Hi Folks,

The gwt maven plugin version 2.1.0 has been released.

The major change is to be gwt 2.1.0 compatible.

Release Notes - Maven 2.x GWT Plugin - Version 2.1.0

New Feature

• [MGWT-181] -Add support for GWT compilers -workDir option
• [MGWT-190] - support GWT 2.1
• [MGWT-218] - Support for setting the -runStyle parameter for gwt:test

Sub-task

• [MGWT-191] - gwt:run runs Hosted Mode instead of Dev Mode for GWT 2.1.0.M1

Bug

• [MGWT-110] - Generated interface not identical to interface generated by GWT tooling
• [MGWT-111] - gwt:run - Multi-module projects with custom start page not well supported
• [MGWT-118] - GWT Compile fails with IBM JDK
• [MGWT-129] - Multi module projects doesn't work properly in HostedMode.
• [MGWT-142] - java.lang.NoClassDefFoundError: com/google/gwt/dev/Compiler when running plugin on Mac
• [MGWT-147] - GWT modules with inherited entry point are never compiled
• [MGWT-149] - generateAsync fails with ParseException (ignoring servicePattern?)
• [MGWT-151] - skip compile when model file not contain entry point.
• [MGWT-152] - Incorrect documenation on the Maven site
• [MGWT-155] - Documentation on GWTTesting is incorrect/Broken link
• [MGWT-161] - gwt-maven-plugin does not work with spaces in project location on Linux
• [MGWT-164] - Inheriting module does not inherit its <entry-point> or <servlet> definitions
• [MGWT-165] - scanning for .gwt.xml files doesn't take into account all source roots
• [MGWT-171] - ServicePattern is ignored
• [MGWT-183] - Cannot compile a module that inherits a module with entry points
• [MGWT-186] - Generic Interface is not generated correctly
• [MGWT-187] - "utility module" detection is incorrect
• [MGWT-189] - .class files get copied into WEB-INF/classes without package structure
• [MGWT-198] - AbstractGwtShellMojo hides failure information when executing the compiler process
• [MGWT-201] - Sources directories in inherited modules are ignored
• [MGWT-223] - i18n fails under Eclipse with m2eclipse
• [MGWT-228] - When running with GWT 2.1.0 the plugin require gwt-dev-<platform> jars

Improvement

• [MGWT-62] - Possibly bind gwt:compile to the 'prepare-package' phase by default in 'war' projects (maven 2.1)
• [MGWT-76] - Solution for multi module builds and hosted mode
• [MGWT-88] - Add mergedWebXml parameter to MergeWebXmlMojo
• [MGWT-128] - Allow specifying custom environment variables for run/debug goals
• [MGWT-146] - Explicit setup mode setting
• [MGWT-148] - Compile also when GWT module file has changed
• [MGWT-154] - GenerateAsync generate files with unused imports
• [MGWT-162] - Support for server=n
• [MGWT-169] - support devmode for multiple modules
• [MGWT-170] - Find source jars and add them to the classpath when executing the GWT compiler
• [MGWT-172] - generateAsync suporting "com.google.gwt.http.client.Request" return objects
• [MGWT-178] - No messages if a module doesn't contain entry points
• [MGWT-180] - Add Option for bindAddress
• [MGWT-194] - Update documentation for /war in GWT 2.0.x
• [MGWT-195] - create documentation for 'comfortable GWT debugging'
• [MGWT-225] - Update BCEL dependency to fix the broken pom.
  

Task

• [MGWT-188] - Update FAQ re: "NoSuchMethodError"
  

Have Fun !
--
Olivier Lamy on behalf of the The Maven Team

PS : pushing open source release is fun The famous song :-)

Open Source song :-)

The famous french singer jcfrog has made a nice song on Open Source :-)

Have a look here : http://www.youtube.com/watch?v=CBHFnTlAJ4s

Check out the other one on twitter : http://www.youtube.com/watch?v=oetmdgPRyqw

I hope we will have one for ASF

Have Fun !

-Olivier

Apache Maven Site Plugin 3.0-beta-3 for maven 3

The Maven team is pleased to announce the release of the Maven Site Plugin, version 3.0-beta-3 for Maven 3.

This version is intended to be the version of the Maven Site Plugin for Maven 3.

The Site Plugin is used to generate a site for the project.

You should specify the version in the section of your project's POM:

<plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-site-plugin</artifactId>

<version>3.0-beta-3</version>

</plugin>

Release Notes - Maven 3.x Site Plugin - Version 3.0-beta-3

Bug

• [MSITE-500] - Warning message about missing report plugin version shows null instead of plugin groupId:aritfactId
• [MSITE-504] - Maven site fails to run due to non-report goals
• [MSITE-505] - Unable to use SVN SCM wagon to upload a site
• [MSITE-506] - Maven3 conflict with plexus-archiver
• [MSITE-507] - report plugin doesn't have dependencies section coming from build section configuration
• [MSITE-508] - attach-descriptor goals leaks file handlers, causing sporadic build failures when gpg tries to sign descriptor during release
• [MSITE-512] - [Regression] Configuration of m-javadoc-p at reportSet level is not taken into account

Task

• [MSITE-513] - use release final maven 3.0 artifacts

Have Fun !

--

Olivier Lamy on behalf of the The Maven Team

Maven Selenium Plugin 1.1 (Maven 3 compatible)

Hi,

The Maven Selenium Plugin 1.1 version has been released.

The most important fix is the Maven 3 compatibility !

Improvement

• [MSELENIUM-66] - Support Maven 3 (upgrade to GMaven 1.3)
• [MSELENIUM-67] - Reuse Xvfb for multi-module project

Don't miss to update the version in your pom

<plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>selenium-maven-plugin</artifactId>

<version>1.1</version>

</plugin>

Have Fun !

Tomcat Maven Plugin 1.1 Released

Tomcat Maven Plugin 1.1 has been released.
Site documentation : http://mojo.codehaus.org/tomcat-maven-plugin/.

Here the release notes :

Bug

• [MTOMCAT-55] - Can't shutdown tomcat started with tomcat:run with fork=true
• [MTOMCAT-57] - Secondary war files deployed with incorrect context path

Improvement

• [MTOMCAT-63] - Make isWar() check consistent with MTOMCAT-23
• [MTOMCAT-64] - Document how to change the Embedded Tomcat Version
• [MTOMCAT-65] - Upgrade Tomcat to 6.0.29

Have Fun !

Hudson Maven Dependency Update Trigger : First Hudson plugin with maven 3 apis

I have made the first release of the Maven Dependency Update Trigger hudson plugin.
Wiki page here : http://wiki.hudson-ci.org//x/jgfDAg
This plugin will check according to the cron expression if your SNAPSHOT dependencies has been updated and (optionnaly) check if your plugins SNAPSHOT has been updated too. And trigger a build if necessary.
This is usefull if you have project dependencies not in the same hudson instance or using an other continuous integration tool.
Note this plugin use maven 3 apis to build maven projects and check dependencies.
Hudson 1.379 is required to use this plugin.



So have fun and give me feedbacks.