uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: new testcase for running Pear inside CPE - question on how to package
Date Mon, 05 Nov 2007 23:17:31 GMT
Good idea to package the source in the Pear.

I take it that you "install" the pear everytime you run the test?  I'm
trying to avoid doing that, by having an "installed" pear, and using
relative paths.  I got it to work on Windows, but Joern reports a
problem which looks like it doesn't work on Linux due to some difference
here.  I'm working on getting my Linux platform up to date, so I can
look into this.  Let me know if you have any insight on how to do this,
better, please :-)


Michael Baessler wrote:
> Marshall Schor wrote:
>> There will be a new testcase for the CPE to test running Pears inside a
>> CPE.  The test needs a Pear.  So I made one by setting up another
>> eclipse project "uimaj-pear-forTesting" which is a pear which does
>> nothing, but references a JCas cover class.
>> In the uimaj-cpe project, I added a new resource under
>> src/test/resources to be where I "installed" the pear, and then I
>> installed the uimaj-pear-forTesting pear, there.  I changed the two
>> parts of the install which hard-coded the absolute path, to relative
>> paths, and tested for Maven builds, - looks like it works fine.
>> So - my question - I think I should check in the uimaj-pear-forTesting"
>> project - so we have the source in case we want to alter/improve/fix
>> this test pear someday.  It's not needed to be built as part of the
>> maven build.  I'm thinking of just leaving it as a plain Eclipse
>> project, and checking in the .project and .classpath files - that way,
>> the "pear packager" tool will work (the project has the "UIMA nature").
>> Anyone have alternate / better suggestion?
>> Cheers. -Marshall
> I have also written some tests for the PEAR stuff where I need PEAR
> files for testing.
> I created the PEARs and packaged them together with source code,
> .project and .classpath files.
> I only committed the packaged PEAR to the SVN. If changes are
> necessary, the PEAR can be extracted and the source code can be changed.
> The disadvantage of this approach is the binary format of the PEAR
> file, so the RAT tool cannot detect issues within the PEAR source! But
> we only talk about
> test cases that are not shipped with the binary UIMA distribution.
> -- Michael

View raw message