You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2013/01/28 03:53:13 UTC

[jira] [Commented] (UIMA-2612) Mark enhanced files to avoid processing them multiple times

    [ https://issues.apache.org/jira/browse/UIMA-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564007#comment-13564007 ] 

Richard Eckart de Castilho commented on UIMA-2612:
--------------------------------------------------

Build times are faster, but when a change in the POM is made (e.g. componentVendor is configured in the uimafit-maven-plugin), Eclipse does not recompile the enhanced classes so the enhancement marker is not removed so the vendor is not added to the already enhanced classes.

I wonder if there is a way for a Maven plugin to detect if it is running within a normal incremental build or due to a change to the Maven model.
                
> Mark enhanced files to avoid processing them multiple times
> -----------------------------------------------------------
>
>                 Key: UIMA-2612
>                 URL: https://issues.apache.org/jira/browse/UIMA-2612
>             Project: UIMA
>          Issue Type: Improvement
>          Components: uimafit, uimafit-maven-plugin
>    Affects Versions: 2.0.0uimaFIT
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Minor
>
> Add a marker annotation (e.g. @Enhanced) to classes that have been processed using the "enhance" goal of the Maven plugin. When the plugin runs again, e.g. during an incremental build, this marker could be detected and the reprocessing could be skipped immediately. This should improve the build times in Eclipse.
> Since the annotation has to be in the class file, it has to be added to the uimafit module. If it was only in the uimafit-maven-plugin, the enhanced classes could not be loaded unless that module was on the classpath.
> ... well, actually I think they could be loaded, but we've had issues with findbugs annotations that Eclipse couldn't resolve when analyzing the class file, so probably better avoid such situations (cf. https://code.google.com/p/uimafit/issues/detail?id=78).

--
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