You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2013/07/11 16:49:48 UTC

[jira] [Created] (UIMA-3072) Add workaround for maven plugin-plugin bug

Marshall Schor created UIMA-3072:
------------------------------------

             Summary: Add workaround for maven plugin-plugin bug
                 Key: UIMA-3072
                 URL: https://issues.apache.org/jira/browse/UIMA-3072
             Project: UIMA
          Issue Type: Bug
          Components: Build, Packaging and Test
    Affects Versions: parent-pom-5
            Reporter: Marshall Schor
            Assignee: Marshall Schor
             Fix For: parent-pom-6


The maven-plugin-plugin is used in several projects to help build maven plugins.  Two of its goals, helpmojo and descriptor, extract info about the plugin from annotations.  A recent change deprecated the use of javadoc-style annotations, in favor of Java 5 annotations, and we've changed our maven plugin projects to Java 5 annotation style. 

Unfortunately, this style is broken for these two goals in the maven-plugin-plugin, because the goals end up in many cases (including during release:prepare) being run *before* the compiler runs.  The scan for these Java annotations scans the compiled code (which is not there yet, after, for instance, a clean has been run but before the compiler has run), and doesn't find any.

Two Jira issues (currently unresolved) address this:
  * http://jira.codehaus.org/browse/MNG-5346 and
  * http://jira.codehaus.org/browse/MPLUGIN-238

The workaround proposed by MNG-5346 for the helpmojo doesn't really work because the annotations are not extracted, and the helpmojo will generate without those.

Workaround this here by setting the phase for the maven-plugin-plugin to run after compile.  With this change, the mojohelp goal, if used, will fail, but that's appropriate for now.  If someone really needs this goal to work, it's best to run it, just once, after a compile step has build the classes (run without doing a "clean" so the compile classes are there), and then manually copy the generated classes to the real source, and then drop this goal. (or something equivalent - or wait till this gets fixed properly).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira