You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Tommaso Teofili (JIRA)" <de...@uima.apache.org> on 2010/06/01 09:42:37 UTC
[jira] Commented: (UIMA-1051) doc build not working on Linux
[ https://issues.apache.org/jira/browse/UIMA-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873914#action_12873914 ]
Tommaso Teofili commented on UIMA-1051:
---------------------------------------
I think that it's time to try to fix this, I am on a Mac and had to go to parent-pom-docbook POM.xml and remove every <embedFile> tag to be able to install PearPackagingMavenPlugin.
I think that it's definitely a bad practice to have absolute paths and even worse when this avoid non-Windows users/devs to build and install artifacts.
So requiring them to remove such tags or manually change the absolute paths is not an option in my opinion.
I will try to inspect if I can fix it another way (thinking about separating OS-based profiles for docbook at the moment).
> doc build not working on Linux
> ------------------------------
>
> Key: UIMA-1051
> URL: https://issues.apache.org/jira/browse/UIMA-1051
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout, Documentation
> Affects Versions: 2.2.2AS, 2.2.2, 2.3
> Reporter: Marshall Schor
> Priority: Minor
>
> The document build on Linux for UIMA-AS (and for base UIMA too) fails to properly make the olink (cross document reference database system) work, because of differing file naming conventions between linux and windows.
> The document build also fails to handle the font selection - that code was built just for Windows.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.