[
https://issues.apache.org/jira/browse/UIMA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798899#comment-13798899
]
Peter Klügl commented on UIMA-3352:
-----------------------------------
Has anyone an idea how to solve that? I spend some time on this a few years
ago, but found no good solution. The problem was that relative paths are
resolved against the Eclipse installation in the Ruta Workbench, not against
the workspace (with plain java). The situation that the user can now use a
separate vm or not does also not ease the problem. Is there a way to support
relative paths?
My first guess would be that we do not support relative paths in the workbench,
but completely support loading from class path. You could then ignore the
absolute paths set by the Workbench as long as the Ruta projects are in the
class path. However, this is not yet well-conceived.
> absolute vs. relative paths in auto generated engine.xml
> --------------------------------------------------------
>
> Key: UIMA-3352
> URL: https://issues.apache.org/jira/browse/UIMA-3352
> Project: UIMA
> Issue Type: Wish
> Components: ruta
> Affects Versions: 2.1.0ruta
> Reporter: Daniel Maeurer
> Priority: Trivial
>
> When building a ruta project the parameter settings in the generated
> xyzEngine.xml files are overwritten with absolute paths to "descriptor" and
> "script" folder. Before deploying my project to a server i always have to
> change the parameter settings back to "./script" by hand. Maybe relative
> paths in the generated files are more convenient.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
