You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@uima.apache.org by Jens Grivolla <j+...@grivolla.net> on 2010/12/14 19:18:30 UTC

runPearMerger on already merged PEARs

It seems that runPearMerger.sh does not correctly adjust the paths when 
the input PEARs are already a merge.

On first run `runPearMerger.sh ae1.pear ae2.pear -n ae12` the paths to 
resources get adjusted from $main_root/X to $main_root/ae1/X or 
$main_root/ae2/X respectively.

However, on subsequent `runPearMerger.sh ae12.pear ae3.pear -n ae123` 
only the top level paths appear to get adjusted.

Should I file an issue, or is that a known and accepted limitation of 
PearMerger?

Thanks,
Jens

Re: runPearMerger on already merged PEARs

Posted by Thilo Götz <tw...@gmx.de>.

On 12/14/2010 19:18, Jens Grivolla wrote:
> It seems that runPearMerger.sh does not correctly adjust the paths when the
> input PEARs are already a merge.
> 
> On first run `runPearMerger.sh ae1.pear ae2.pear -n ae12` the paths to resources
> get adjusted from $main_root/X to $main_root/ae1/X or $main_root/ae2/X
> respectively.
> 
> However, on subsequent `runPearMerger.sh ae12.pear ae3.pear -n ae123` only the
> top level paths appear to get adjusted.
> 
> Should I file an issue, or is that a known and accepted limitation of PearMerger?
> 
> Thanks,
> Jens
> 

I think this is a known limitation of the pear merger.
Not sure how hard this would be to fix.  Feel free to
take a look at the code :-)

--Thilo