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 2010/11/05 19:54:44 UTC
[jira] Closed: (UIMA-1923) add DEPENDENCIES to the list of RAT
exclusions
[ https://issues.apache.org/jira/browse/UIMA-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1923.
--------------------------------
Resolution: Fixed
Fix Version/s: build-parent-pom-1
> add DEPENDENCIES to the list of RAT exclusions
> ----------------------------------------------
>
> Key: UIMA-1923
> URL: https://issues.apache.org/jira/browse/UIMA-1923
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: build-parent-pom-1
>
>
> For projects which produce JARs and are released by running mvn release... on them directly (that is, "cd" to that project, and run mvn release...), a top level DEPENDENCIES file is generated, which need to have a RAT exclusion.
> I hadn't noticed this before, because I've only run mvn release on pom (not jar) projects. But now, I've run it on the uima-build-resources which is a Jar project, and this issues appeared. It would also be an issue when releasing individual sandbox (jar) projects.
> Add DEPENDENCIES to the RAT exclusion list, in the common UIMA parent pom.
> For the uima-build-resources project (which doesn't (can't) depend on our common parent-pom, because the parent pom "depends" on it), find another way to make this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.