We actually do that all the time, it works perfectly. Some archive
managers even let you edit the file without unpacking it. You may need
to rename it from .pear to .zip and back to .pear when you're done.
Jens
On 04/26/2012 06:10 PM, Marshall Schor wrote:
Thanks Thilo.
Could you unzip the pear with an unzipper, and do the change to fix the
file path and then zip it back up again? That way the variable
replacement stuff wouldn't run.
-Marshall
On 4/26/2012 5:07 AM, Thilo Goetz wrote:
On 25/04/12 23:20, Marshall Schor wrote:
I hope its trivial :-) (But I haven't tried it...).
It's not trivial, because the pear installer desctructively
replaces variables with local paths on installation. If
you don't know what you're doing, it will be much easier to
ask the other team to get you the original pear file.
There is no supported way to repackage an installed pear
file.
--Thilo
-Marshall
On 4/25/2012 1:15 PM, Mike O'Leary wrote:
I received a copy of an application that works with UIMA a few weeks
ago from
some colleagues at another location. When I followed the
instructions to
install it, I got an error message while unpacking a pear file, and it
looks
like an XML file within it contains some hard-coded pathnames to a
machine at
the organization that sent our colleagues the application originally.
I could
ask them to get in touch with the organization and ask them to
recreate the
pear file with relative pathnames so it can be installed on machines
on other
networks, and I probably will do that. But I was wondering how hard it
would be
just to correct the pathnames, re-package the pear file, and reinstall
that
one. I have never worked with UIMA before, so I am learning the basics
as I go.
How complicated would it be to create an Eclipse project using the
directory
structure that the pear file expanded to, or to run a command line
application
that creates a pear file from that directory structure?
Thanks,
Mike
