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/10/28 16:18:21 UTC
[jira] Closed: (UIMA-1917) parent-pom use of dependency +
unpack-dependencies inadvertantly affecting children poms
[ https://issues.apache.org/jira/browse/UIMA-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1917.
--------------------------------
Resolution: Fixed
> parent-pom use of dependency + unpack-dependencies inadvertantly affecting children poms
> ----------------------------------------------------------------------------------------
>
> Key: UIMA-1917
> URL: https://issues.apache.org/jira/browse/UIMA-1917
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: build-parent-pom-1
>
>
> In an attempt to get the release plugin to automatically update the uima-build-resources version number, I had switched the inclusion of the uima-build-resources files from maven-dependency-plugin goal of unpack to unpack-dependencies.
> Although this worked for building the parent pom, when run on a ordinary child pom (e.g., the DictionaryAnnotator), the dependencies were the entire set of dependencies merged from the parent pom and the child pom, and the unpack-dependencies unpacked all of them.
> Since there were other issues with getting the release plugin to automaitcally manage the uima-build-resources version number see https://issues.apache.org/jira/browse/UIMA-1916 ), fix this by changing back to the unpack goal, specifying just the artifact and files wanted, and remove the <dependencies> spec from the parent-pom to avoid having it merged with all children.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.