Maven GWT Plugin

GWT modules with inherited entry point are never compiled

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2
  • Fix Version/s: 2.1.0
  • Labels:
    None
  • Number of attachments :
    1

Description

The plugin incorrectly considers all modules without an entry point specified directly in the module to be secondary modules (CompileMojo.compilationRequired() returns false). GWT supports inherited entry points, which are often useful e.g. in combination with GWT generators.

Such modules are never compiled but a message saying they are up-to-date is printed. Also the force setting is ignored.

In gwt-maven-plugin 1.1, modules with inherited entry point are compiled correctly.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Timo Boll added a comment -

A possible solution is to check for entry points only when modules were collected using auto-discovery or when $

{gwt.compiler.force}

is true.
This solution does not include validation of inherited entry points.

Show
Timo Boll added a comment - A possible solution is to check for entry points only when modules were collected using auto-discovery or when $ {gwt.compiler.force} is true. This solution does not include validation of inherited entry points.
Hide
Permalink
nicolas de loof added a comment -

fixed, thanks to <inherits> support in GwtModule

Show
nicolas de loof added a comment - fixed, thanks to <inherits> support in GwtModule

People

  • Assignee:
    nicolas de loof
    Reporter:
    Henri Sara
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: