On 9/16/2013 12:38 PM, Peter Klügl wrote:
> On 16.09.2013 17:46, Marshall Schor wrote:
>> On 9/16/2013 11:26 AM, Peter Klügl wrote:
>>> On 16.09.2013 17:20, Marshall Schor wrote:
>>>> It looks like there's some perhaps unneeded dependencies in some of the jar
>>>> builds.  Example:
>>>>
>>>> The ruta-core jar: the META-INF/DEPENDENCIES (generated by Maven) includes
>>>>
>>>>   antlr
>>>>   aopalliance
>>>>   htmlparser
>>>>
>>>> All of which have non Apache licenses.  Were these actually included in 
>>>> the Jar
>>>> (they seem not to be), then the license/notice file for the Jar would need 
>>>> updating.
>>>>
>>>> If this is just a wrong pom dependency thing for this JAR, then I think it 
>>>> is
>>>> not a blocker, and can be fixed in the next release.
>>> They are not included in ruta-core.jar, but in the engine plugin. They
>>> have been added there, because ruta-core, e.g., provides the
>>> implementation of the html analysis engines, which require the htmlparser.
>>>
>>> I fear that aopalliance is not yet mentioned in the engine plugin.
>> It is listed in the public domain, so there is no license, and no notice, I 
>> think.
> So this means I do not have to change anything? Or should I add a note
> in the notice file of the engine plugin?
For the ruta-core project, I don't think you need any note in the notice file.

-Marshall

> Peter
>
>
>> -Marshall
>>>  Or,
>>> is it enough that the aopalliance is included and we have the agreement
>>> of the feature? On the other hand the aopalliance.jar provides no own
>>> license file.
>>>
>>> Peter
>>>
>>>
>>>
>>>> -Marshall
>>>>  
>>>> On 9/13/2013 8:07 AM, Peter Klügl wrote:
>>>>> Hi,
>>>>>
>>>>> the first release candidate of the sandbox project Apache UIMA Ruta
>>>>> v2.1.0 is ready for voting.
>>>>>
>>>>> I beg for a rapid review process because I need this release for the
>>>>> tutorial (September 24).
>>>>>
>>>>> Staging repository:
>>>>> https://repository.apache.org/content/repositories/orgapacheuima-038/
>>>>>
>>>>> SVN tag:
>>>>> https://svn.apache.org/repos/asf/uima/sandbox/ruta/tags/ruta-2.1.0-rc1
>>>>>
>>>>> Composite repository:
>>>>> https://dist.apache.org/repos/dist/dev/uima/eclipse-update-site/composite-update-site/2
>>>>>
>>>>> Archive with all sources:
>>>>> http://people.apache.org/~pkluegl/uima-releases/ruta-2.1.0-rc1/ruta-2.1.0-source-release.zip
>>>>>
>>>>> Overall 88 issues have been fixed for this release.
>>>>> They can be found in the RELEASE_NOTES.html and here:
>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%222.1.0ruta%22%20AND%20component%20%3D%20ruta%20AND%20status%20in%20(Resolved%2C%20Closed)%20ORDER%20BY%20priority%20DESC
>>>>>
>>>>> Major Changes in this Release
>>>>>
>>>>> UIMA Ruta Language and Analysis Engine:
>>>>>
>>>>> - Combinations of rule elements that specify no sequential constraint
>>>>> - Rule elements with inlined rules, which are interpreted as "actions"
>>>>> or "conditions"
>>>>> - Dot notation for accessing features, also available as matching 
>>>>> conditions
>>>>> - Implicit actions and conditions
>>>>> - New analysis engines for CAS manipulation
>>>>> - Direct import of uimaFIT analysis engines without descriptor
>>>>> - RutaEngine is now a uimaFIT component
>>>>> - Manual specification of the start anchor for a rule match
>>>>> - Many bug fixes
>>>>>
>>>>> UIMA Ruta Workbench:
>>>>>
>>>>> - Compatible with uimaj 2.4.2 and Eclipse Kepler
>>>>> - New framework for constraint-driven evaluation
>>>>> - Two new rule learning algorithms for the TextRuler framework
>>>>> - New views, e.g., Annotation Check and Html viewer
>>>>> - Combinations with java projects
>>>>> - Open CAS Editor at Eclipse startup causes less problems
>>>>> - Many bug fixes
>>>>>
>>>>>
>>>>> ONLY FOR REVIEWING:
>>>>>
>>>>> Documentation (pdf file):
>>>>> http://people.apache.org/~pkluegl/uima-releases/ruta-2.1.0-rc1/tools.ruta.book.pdf
>>>>>
>>>>>
>>>>> Please vote on release:
>>>>>
>>>>> [ ] +1 OK to release
>>>>> [ ]  0 Don't care
>>>>> [ ] -1 Not OK to release, because ...
>>>>>
>>>>> Thanks.
>>>>>
>>>>> Peter
>>>>>
>

Reply via email to