Versions Compared

Old Version 22

changes.mady.by.user Marshall Schor

Saved on

compared with

New Version Current

changes.mady.by.user Marshall Schor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

uimaj - (RC7) diffs: using $ diff -b -r uimaj-2.3.0-07 ../rc7/uimaj-orig/uimaj-2.3.0-incubating/

Expected diffs:

  • Some files copied to top level, not in SVN. Eg. packageAllJavaScourcesIntoJar.bat etc.
  • A bunch of empty dirs in SVN (e.g., src/main/resources, fop-versions/.../fonts) are omitted in the src zip by the assembly maven plugin
  • The PearPackagingMavenPlugin has its own set of files, not used in the distr packaging, because it was merged into the main uimaj build, and its docs were combined. However SVN still has the older approach - individual Lic/Not/Discl, and its own docbook. Leaving these in SVN because I think we'll be wanting to make the pear maven builder a separate project
  • 2 projects in SVN not in the release because they're not used in building from sources
    • uimaj-internal-tools
    • uimaj-jet-expander

uima-as - RC7 diffs:

  • Some files copied to top level, not in SVN. Eg. README, RELEASE_NOTES, addSourceToJars etc.
  • 2 empty dirs in SVN, not in src distr src/main/resources

sandbox - RC7 diffs:

  • The generated html/pdf docs for the sandbox projects are kept in the source- for use by the website (to display them), but since they're big and generated, they're not in the source distribution.
  • empty dirs in SVN, not in src distr e.g, src/main/resources, src/test, lib, etc.
  • there is in SVN a file NoticeFileResearchLog.txt not shipped - not needed to rebuild. This file is for maintainers, and documents research into crafting the proper Notice file.

The focus areas for testing include:

  • Installation from the binary distributions, on various platforms
  • Installing the Eclipse plugins from the temporary update site (on people.apache.org/
  • Running of the core (e.g. document analyzer, CPE GUI etc., on sample/examples or on your project)
  • Running of UIMA-AS in various deployments
  • Running of the Sandbox components

Misc Running

Burn:

  • Large aggregate uima-as, ran with older remote components, aggregate ran using auto-deployment (runRemoteAsyncAE) (RC3).
  • New error handling - timeouts reset when cas comes back (prevents CASes timing out if stuck behind preceeding long-running ones) works.

Eddie:

  • Tested uima/uima-as on very large complex system - verified whole system worked and timings were as expected.
  • Tested compatibility with C++ - run co-located C++ annotators, ran core UIMA with C++ annotators, using UIMA-AS to deploy C++ annotators. These are just basic tests...

Jerry:

  • Ran the uima-as "extended" JUnit tests (these test take a long time because they have loops looking for intermittent issues).