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 2020/11/13 21:30:00 UTC

[jira] [Commented] (UIMA-6254) Move API report post-analysis script into the build resources

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

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

There is a problem with putting the post-analysis script into a shared artifact: the japicmp maven plugin cannot load the analysis script from the plugin classpath - only from the filesystem. That means in order to move the script to a shared artifact, we'd have to use e.g. the Maven Dependency Plugin's {{dependency:unpack}} goal to extract the script as part of the build. Not sure if that is so great.

I have opened a feature request in the japicmp repo about loading the script form the classpath: https://github.com/siom79/japicmp/issues/274

> Move API report post-analysis script into the build resources
> -------------------------------------------------------------
>
>                 Key: UIMA-6254
>                 URL: https://issues.apache.org/jira/browse/UIMA-6254
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Build, Packaging and Test
>            Reporter: Richard Eckart de Castilho
>            Assignee: Richard Eckart de Castilho
>            Priority: Major
>             Fix For: parent-pom-14, build-resources-5
>
>
> Currently, several projects maintain the post-analysis groovy script in their own repos. But it can be shared in the build resources and the concern of the API report can be fully pushed into the overall UIMA parent POM.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)