The lucene link looks like it is doc for a java package of classes, not a separate file in the release artifact.
IMO, we can link to link AOO or offer downloads in the ant scripts/installer. I think the second key question is, does the code that calls/uses the category X code/data need to be in a separate file or not. Remember that the Flex SDK already has a category X dependency for the optional embedded font jars. The code that calls the category X jars is bundled in the one and only release artifact, but the code is set up such that those category X jars can be missing. The mentors ruled that was sufficient because nobody "must" download the category X jars to successfully use the Flex SDK. I would expect we would do the same for Squiggly. Just bundling the code should be ok because you can still use the rest of the Flex SDK. But if you want, we can ask on the legal-discuss thread. -Alex On 8/31/14 12:21 AM, "Justin Mclean" <jus...@classsoftware.com> wrote: >Hi, > >Or even better this link: >https://lucene.apache.org/core/4_0_0/analyzers-common/org/apache/lucene/an >alysis/hunspell/package-summary.html > >Justin
