[jira] Created: (UIMA-1760) Fix AE Descriptors' names
Fix AE Descriptors' names -- Key: UIMA-1760 URL: https://issues.apache.org/jira/browse/UIMA-1760 Project: UIMA Issue Type: Bug Components: Sandbox-AlchemyAPI Annotator Reporter: Tommaso Teofili Assignee: Tommaso Teofili Name of AE Descriptors are wrong for: HtmlMicroformatsAEDescriptor.xml URLMicroformatsAEDescriptor.xml TextKeywordExtractionAEDescriptor.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1760) Fix AE Descriptors' names
[ https://issues.apache.org/jira/browse/UIMA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1760. --- Resolution: Fixed Fix AE Descriptors' names -- Key: UIMA-1760 URL: https://issues.apache.org/jira/browse/UIMA-1760 Project: UIMA Issue Type: Bug Components: Sandbox-AlchemyAPI Annotator Reporter: Tommaso Teofili Assignee: Tommaso Teofili Name of AE Descriptors are wrong for: HtmlMicroformatsAEDescriptor.xml URLMicroformatsAEDescriptor.xml TextKeywordExtractionAEDescriptor.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1760) Fix AE Descriptors' names
[ https://issues.apache.org/jira/browse/UIMA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili closed UIMA-1760. - Fix AE Descriptors' names -- Key: UIMA-1760 URL: https://issues.apache.org/jira/browse/UIMA-1760 Project: UIMA Issue Type: Bug Components: Sandbox-AlchemyAPI Annotator Reporter: Tommaso Teofili Assignee: Tommaso Teofili Name of AE Descriptors are wrong for: HtmlMicroformatsAEDescriptor.xml URLMicroformatsAEDescriptor.xml TextKeywordExtractionAEDescriptor.xml -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: purpose of properties scm.branch, scm.module.path, and scmBranchPropertyName
Marshall, as far as I know those properties are related to the Maven Release/SCM Plugin and used by Maven BuildNumber Plugin. Moreover it was part of the fix for https://issues.apache.org/jira/browse/UIMA-1694 , as far as I can remember it prevented some warnings to come up, but it was a bit hard to debug what that warning were really meaning so that tags stayed. Tommaso 2010/4/9 Marshall Schor m...@schor.com What is the purpose of these properties set in the uimaj pom? What components in the build make use of these settings? A quick google search didn't seem to show an obvious answer, and a search of our project poms didn't turn up any uses :-) -Marshall
Re: [Informal Vote] please express your opinion on using Nexus and Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Yes, it really sounds nice to me too (so +1 again). Tommaso 2010/4/6 Jörn Kottmann kottm...@gmail.com Marshall Schor wrote: Here's my vision of automation (achieved over time :-) ), and why CI could be important - it is building the potential releases from source checkout. We have CI going on Hudson; we decide at some point that things merit a release; so we push some button on the CI or Nexus interface and get a particular snapshot release tagged, checked out and built as a candidate. We do some additional integration testing, and then vote on the thing in the nexus repo, where it look like a release but is in some held state. After the vote succeeds, we log onto the Nexus web interface and push another button, and the release happens. +1 sounds nice Jörn
Re: Sandbox OSGi runtime
Nice one! It seems a nice effort from the Felix community and it looks like it's perfectly aligned with what we are trying to do (a POM with a dependency on the library to bundle and the Maven Felix plugin for the configuration of the bundle), so we may choose one of two ways: contribute such POMs to Felix Commons (but we'd need to change the group-id to org.apache.felix.commons) or have them deployed inside our SVN and linked (having UIMA listed as one of the supporting libraries) to the Felix Commons project. Since we already have OSGi versions of core framework inside our SVN to support Eclipse plugins we may go for the second option. So if we agree I could start a thread on Felix ML to let them know about this effort. What do you think? Have a nice day. Tommaso 2010/4/4 Marshall Schor m...@schor.com +1. I think there is a (slowly?) growing interest in OSGi - see, for instance, the latest info in the apache felix project [1] and in particular, the newer, possibly unreleased subprojects [2]. There are efforts there in the Apache Felix Commons subproject [3] to do more or less what you are trying to do here - it would be good to confirm these approaches are aligned :-). -Marshall [1] http://felix.apache.org/site/index.html [2] http://felix.apache.org/site/subprojects.html [3] http://felix.apache.org/site/apache-felix-commons.html
Re: Sandbox OSGi runtime
It seems I missed something with the previous configuration. Modifying POMs using your approach everything is still working and better looking. Thanks very much Marshall. What do you think of creating the sandbox-osgi-runtime (multi-module) project on the Sandbox so that everyone can use such generated bundles? Happy Easter to everyone. Tommaso
Re: Sandbox OSGi runtime
2010/3/25 Marshall Schor m...@schor.com
Seems like a reasonable approach (caveat: I'm not really up-to-date with
the use-cases).
Is it possible to factor out any (i.e., most) of the felix bundle plugin
configuration into the parent pom?
Good point Marshall.
I tried to do so but it seems the configuration tag cannot be defined
partially (something on the parent POM and something else inside the child
POM) so I thought using Maven properties could be a solution in order to
define some fixed values for configuration inside the parent POM.
Parent POM:
properties
import-packageorg.apache.uima,*/import-package
embed-dependency*;scope=compile;inline=true/embed-dependency
singletonsingleton:=true/singleton
jreJ2SE-1.5/jre
ext-apitrue/ext-api
buddy-policyregistered/buddy-policy
nousestrue/nouses
manifest-locationMETA-INF/manifest-location
/properties
Inside the child POM only Export-package and Bundle-SymbolicName are
defined:
...
configuration
manifestLocation${manifest-location}/manifestLocation
instructions
_nouses${nouses}/_nouses
Export-Packageorg.apache.uima.lucas.*/Export-Package
Import-Package${import-package}/Import-Package
Embed-Dependency${embed-dependency}/Embed-Dependency
Bundle-SymbolicNameorg.apache.uima.lucas;${singleton}/Bundle-SymbolicName
Bundle-RequiredExecutionEnvironment${jre}/Bundle-RequiredExecutionEnvironment
Eclipse-ExtensibleAPI${ext-api}/Eclipse-ExtensibleAPI
Eclipse-BuddyPolicy${buddy-policy}/Eclipse-BuddyPolicy
/instructions
/configuration
..
Waiting for your comments about it.
Tommaso
P.S.:
In Apache Clerezza the AlchemyAPI and OpenCalais annotators are used at this
moment to enable auto tagging of resources.
[jira] Resolved: (UIMA-1740) Mock integration tests on AlchemyAPI Annotator
[ https://issues.apache.org/jira/browse/UIMA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1740. --- Resolution: Fixed Mocked tests added, thanks to Simone Tripodi for suggestions on how to handle URLConnections for non-Http ones Mock integration tests on AlchemyAPI Annotator --- Key: UIMA-1740 URL: https://issues.apache.org/jira/browse/UIMA-1740 Project: UIMA Issue Type: Bug Reporter: Tommaso Teofili Assignee: Tommaso Teofili Since previously the API key was already put inside the AE descriptor and now it's been removed, the URL call should be mocked to avoid tests' failure due to HTTP 403 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1740) Mock integration tests on AlchemyAPI Annotator
[ https://issues.apache.org/jira/browse/UIMA-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili closed UIMA-1740. - Mock integration tests on AlchemyAPI Annotator --- Key: UIMA-1740 URL: https://issues.apache.org/jira/browse/UIMA-1740 Project: UIMA Issue Type: Bug Reporter: Tommaso Teofili Assignee: Tommaso Teofili Since previously the API key was already put inside the AE descriptor and now it's been removed, the URL call should be mocked to avoid tests' failure due to HTTP 403 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1747) TikaAnnotator: null pointer exception in MarkupHandler.populateCAS
[ https://issues.apache.org/jira/browse/UIMA-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12852309#action_12852309 ] Tommaso Teofili commented on UIMA-1747: --- Hi Greg, it seems to me you're right in regards of the Type string so the patch should be fixing the issue. I am wondering about the need of the line: Type markupType = cas.getTypeSystem().getType(org.apache.uima.tika.MarkupAnnotation) since it seems it is never used, so we may choose to remove it. In regards of Exception now that the package name is fixed, it's something it should happen only when that FS is not defined inside the TypeSystem. So for example we may choose to create an UnknownTypeException like the one inside the ConceptMapper https://svn.apache.org/repos/asf/incubator/uima/sandbox/trunk/ConceptMapper/src/main/java/org/apache/uima/conceptMapper/support/tokens/UnknownTypeException.java but extending RuntimeException so that we should not change method signature to declare throwing exception. What do you think? TikaAnnotator: null pointer exception in MarkupHandler.populateCAS -- Key: UIMA-1747 URL: https://issues.apache.org/jira/browse/UIMA-1747 Project: UIMA Issue Type: Bug Components: Sandbox-TikaAnnotator Affects Versions: 2.3 Reporter: Greg Holmberg Priority: Blocker Attachments: UIMA-1747-patch.txt I get the following NPE. java.lang.NullPointerException at org.apache.uima.cas.impl.CASImpl.createFS(CASImpl.java:474) at org.apache.uima.tika.MarkupHandler.populateCAS(MarkupHandler.java:168) at org.apache.uima.tika.TIKAWrapper.populateCASfromURL(TIKAWrapper.java:105) at org.apache.uima.tika.FileSystemCollectionReader.getNext(FileSystemCollectionReader.java:99) at org.apache.uima.collection.impl.cpm.engine.ArtifactProducer.readNext(ArtifactProducer.java:494) at org.apache.uima.collection.impl.cpm.engine.ArtifactProducer.run(ArtifactProducer.java:711) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Informal Vote] please express your opinion on using Nexus and Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
2010/3/27 Marshall Schor m...@schor.com I'm +1 for doing this, and offer to do some/most of the legwork to get this to happen. Other opinions? I'm +1 too. Tommaso
Re: Sandbox OSGi runtime
Back again, 2010/3/10 Tommaso Teofili tommaso.teof...@gmail.com I am doing some tests with this approach using some of these bundled annotators with Apache Clerezza. Tests seem to go well using OpenCalaisAnnotator and AlchemyAPIAnnotator bundles generated with Maven Felix plugin. I've temporarily put the POMs on a GC SVN [1] so that you can view and comment this approach. What do you think? Cheers, Tommaso [1] : http://code.google.com/p/osgi-uima-sandbox/source/browse/#svn/trunk/osgi-uima-sandbox
[jira] Created: (UIMA-1745) Wrong name in TextLanguageDetectionAEDescriptor
Wrong name in TextLanguageDetectionAEDescriptor --- Key: UIMA-1745 URL: https://issues.apache.org/jira/browse/UIMA-1745 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Priority: Minor name inside TextLanguageDetectionAEDescriptor.xml descriptor of AlchemyAPIAnnotator refers to TextCategorizationAEDescriptor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1745) Wrong name in TextLanguageDetectionAEDescriptor
[ https://issues.apache.org/jira/browse/UIMA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1745. --- Resolution: Fixed Wrong name in TextLanguageDetectionAEDescriptor --- Key: UIMA-1745 URL: https://issues.apache.org/jira/browse/UIMA-1745 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Priority: Minor name inside TextLanguageDetectionAEDescriptor.xml descriptor of AlchemyAPIAnnotator refers to TextCategorizationAEDescriptor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1745) Wrong name in TextLanguageDetectionAEDescriptor
[ https://issues.apache.org/jira/browse/UIMA-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili closed UIMA-1745. - Assignee: Tommaso Teofili Wrong name in TextLanguageDetectionAEDescriptor --- Key: UIMA-1745 URL: https://issues.apache.org/jira/browse/UIMA-1745 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Priority: Minor name inside TextLanguageDetectionAEDescriptor.xml descriptor of AlchemyAPIAnnotator refers to TextCategorizationAEDescriptor -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Sandbox OSGi runtime
2010/3/6 Marshall Schor m...@schor.com On 3/4/2010 3:00 AM, Tommaso Teofili wrote: Hi Marshall 2010/3/3 Marshall Schor m...@schor.com would it make sense to have individual osgi packaging of sandbox annotators? Do you mean you prefer not to have a single module aggregating all annotators in a single bundle and you'd prefer each annotator having its own individual OSGi bundle? Yes. Some of the annotators have very large (could be 100's of megabytes, for instance) statistical models. I just made myself a multi module Maven project containing one module for each of the Sandbox annotators so that one can select which annotators to install on an OSGi runtime but at the same time they are tied together inside a unique project. Each module contains only the POM which uses the Maven Felix plugin to produce the annotator bundle (more or less like in uimaj-ep-runtime). I am doing some tests with this approach using some of these bundled annotators with Apache Clerezza. Tommaso
Font error in generating PDF documentation
Hi all, doing documentation for AlchemyAPI Annotator I found problems generating the PDF version of the documentation since inside the uima-docbook-tool a Windows font is referenced inside the FOP configuration file (fop-config.xml). ... embed-url=file:///c:/WINDOWS/Fonts/palai.TTF ... This doesn't work for non Windows platforms. What do you think about it? Do you think we should keep it anyway or change it to make it machine independent (but I don't how at the moment) or just remove it? Cheers. Tommaso P.S.: To do AlchemyAPI Annotators documentation PDF I had to remove the above line from the fop-config.xml inside tools/fop-versions dir of uima-docbook-tool
[jira] Resolved: (UIMA-1741) Add AlchmeyAPI Annotator documentation
[ https://issues.apache.org/jira/browse/UIMA-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1741. --- Resolution: Fixed Add AlchmeyAPI Annotator documentation -- Key: UIMA-1741 URL: https://issues.apache.org/jira/browse/UIMA-1741 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Generated documentation on features and use of AlchemyAPI Annotator must be provided -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Sandbox OSGi runtime
Hi Marshall 2010/3/3 Marshall Schor m...@schor.com would it make sense to have individual osgi packaging of sandbox annotators? Do you mean you prefer not to have a single module aggregating all annotators in a single bundle and you'd prefer each annotator having its own individual OSGi bundle? (I'm assuming you're thinking about annotators, not about other things, right?) Yes, right. Cheers. Tommaso
Sandbox OSGi runtime
Hi all, what do you think of a uimaj module similar to uimaj-ep-runtime just for sandbox components (something like sanxbox-osgi-runtime)? This is useful when you want to use Sandbox components in an OSGi environment. Cheers. Tommaso
Re: Doing the IP-Clearance for the AlchmeyAPI Annotator
Ok, thanks for your kind help with this one :-) Cheers, Tommaso 2010/3/3 Jukka Zitting jukka.zitt...@gmail.com Hi, On Wed, Mar 3, 2010 at 3:08 PM, Tommaso Teofili tommaso.teof...@gmail.com wrote: it seems to me that the IP-Clearance on gene...@incubator got lazy consensus. Should we raise a RESULT email? Done. Thanks for the reminder. Any further steps needed I can help with? (According to Marshall's previous email it seems the answer is no) No, this was the last step of the process. BR, Jukka Zitting
Re: svn commit: r915877 - in /incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts: categorization/ entity/ keywords/ language/ microformats/
Hi Marshall 2010/2/24 Marshall Schor m...@schor.com The comments you removed are generated and serve to identify the source from which the generated classes were created. If JCasGen is re-run, these comments will be re-inserted I think. my idea was that having a cleaner committed code was a good idea even if when re-generated the paths will appear again. It sounded to me like some dirty lines, but indeed it's a trivial issue. At some point, we might want to set up JCasGen to align with the approaches used for other generated artifacts (like javacc), make a maven plugin to run it, etc. That would be nice! Thanks for your hints. Tommaso -Marshall Original Message Subject:svn commit: r915877 - in /incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts: categorization/ entity/ keywords/ language/ microformats/ Date: Wed, 24 Feb 2010 17:16:25 - From: tomm...@apache.org Reply-To: uima-dev@incubator.apache.org To: uima-comm...@incubator.apache.org Author: tommaso Date: Wed Feb 24 17:16:24 2010 New Revision: 915877 URL: http://svn.apache.org/viewvc?rev=915877view=rev Log: [UIMA-1744] - local path comments removed Modified: incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/categorization/Category.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/AlchemyAnnotation.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Anniversary.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/City.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Company.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Continent.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Country.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Drug.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/EntertainmentAward.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Facility.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/FieldTerminology.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/FinancialMarketIndex.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/GeographicFeature.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/HealthCondition.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Holiday.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Movie.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/MusicGroup.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/NaturalDisaster.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/OperatingSystem.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Organization.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Person.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/PrintMedia.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Product.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/RadioProgram.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Region.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Sport.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/SportingEvent.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/StateOrCounty.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/Technology.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/TelevisionShow.java incubator/uima/sandbox/trunk/AlchemyAPIAnnotator/src/main/java/org/apache/uima/alchemy/ts/entity/TelevisionStation.java
Re: Doing the IP-Clearance for the AlchmeyAPI Annotator
Hi Jukka, 2010/2/26 Jukka Zitting jukka.zitt...@gmail.com Hi On Fri, Feb 26, 2010 at 2:25 PM, Marshall Schor m...@schor.com wrote: Hi Jukka, Can you do these next steps to complete this? Sure, thanks for the reminder! I'll take care of this right away. The IP clearance record looks good, thanks Tommaso! Note that as it's usually better to wait until the IP clearance is complete before committing a new codebase to Apache svn, but it's no big problem that you already did so. Sorry, I had thought that I could commit it right after the SGA was recorded. Lesson learned. Thanks. Tommaso BR, Jukka Zitting
[jira] Created: (UIMA-1744) Remove generated local path commenti inside AlchemyAPI Annotator FeatureStructures
Remove generated local path commenti inside AlchemyAPI Annotator FeatureStructures -- Key: UIMA-1744 URL: https://issues.apache.org/jira/browse/UIMA-1744 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Priority: Trivial remove /** ... /Users/... */ comments inside FeatureStructures generated by JCasGen inside AlchemyAPI Annotator -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1744) Remove generated local path comments inside AlchemyAPI Annotator FeatureStructures
[ https://issues.apache.org/jira/browse/UIMA-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated UIMA-1744: -- Summary: Remove generated local path comments inside AlchemyAPI Annotator FeatureStructures (was: Remove generated local path commenti inside AlchemyAPI Annotator FeatureStructures) Remove generated local path comments inside AlchemyAPI Annotator FeatureStructures -- Key: UIMA-1744 URL: https://issues.apache.org/jira/browse/UIMA-1744 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Priority: Trivial remove /** ... /Users/... */ comments inside FeatureStructures generated by JCasGen inside AlchemyAPI Annotator -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Doing the IP-Clearance for the AlchmeyAPI Annotator
Ok, thanks again Jukka. Cheers. Tommaso 2010/2/21 Jukka Zitting jukka.zitt...@gmail.com Hi, On Sun, Feb 21, 2010 at 9:52 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: I've fixed the points you mentioned, only I haven't put down the 3) since I'll ask Jukka first (sorry for not asking you first). I'd be happy to take care of the parts where an ASF officer is needed. BR, Jukka Zitting
Re: Doing the IP-Clearance for the AlchmeyAPI Annotator
Hi Marshall, I've fixed the points you mentioned, only I haven't put down the 3) since I'll ask Jukka first (sorry for not asking you first). I fixed point 4) putting a mail-archives.com link since I could read the previous link but you couldn't, is it ok? Cheers, Tommaso 2010/2/21 Marshall Schor m...@schor.com Hi, Some changes: 1) In the description, you might include a link to the Alchemy website when you mention it first. 2) Under Project Info - because we're still incubating (until we get voted out, first by the IPMC and next by the board, which might take another month), the PMC responsible should read something like: Apache UIMA (currently an Incubator project, so officially, the Incubator PMC) 3) Officer or member managing donation: I would put down Jukka Zitting (would be nice to ask him first of course :-) ) 4) in the Related Votes section, the link to the vote thread is broken (message is: The requested URL /mod_mbox/incubator-uima-dev/201001.mbox/ b917db631001290112r3f4332aflc29bec1c88d7e...@mail.gmail.com was not found on this server.) When these are fixed, I think the thing to do is to talk with Jukka, and see if he would be willing to manage this clearance. -Marshall On 2/20/2010 12:03 PM, Tommaso Teofili wrote: Hi Marshall, Could you please review the IP clearance xml for AlchemyAPI Annotator? You can find it here: http://svn.apache.org/repos/asf/incubator/uima/site/trunk/uima-website/xdocs/ip-clearances/alchemyapi-annotator.xml Thanks Tommaso 2010/2/19 Tommaso Teofili tommaso.teof...@gmail.com Hi Marshall, Yes I can do it, no problem. Thanks, Tommaso 2010/2/19 Marshall Schor m...@schor.com See http://incubator.apache.org/ip-clearance/index.html Tommaso, can you take the lead in getting the IP form filled out? I volunteer to review :-) The unofficial place we've done this work in the past is in the uima-website project. There, under xdocs, is a folder, ip-clearances. You could copy in the current template (from the above referenced web page) and start there. To format this template so you can see what it looks like and if there are any errors, etc., you run the same kind of ant scripts we use to build our website - except it uses some different libraries; the ant script is called build-ip-clearances.xml. -Marshall
[jira] Updated: (UIMA-1733) Import AlchemyAPI Annotator code inside the Sandbox
[ https://issues.apache.org/jira/browse/UIMA-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated UIMA-1733: -- Attachment: alchemy-annotator.zip the code donated (in its pre import version) Import AlchemyAPI Annotator code inside the Sandbox --- Key: UIMA-1733 URL: https://issues.apache.org/jira/browse/UIMA-1733 Project: UIMA Issue Type: Task Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Attachments: alchemy-annotator.zip Once the SGA has been recorded we can start importing the code -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: I noticed that IntelliJ IDEA has a community edition that is now opensource (Apache license) and free
Hi Marshall, I also add that for Apache committers there is also the possibility to ask for a commercial license for free. I asked and got it. Cheers. Tommaso 2010/2/19 Marshall Schor m...@schor.com In case anyone wants to add IDEA support for UIMA... -Marshall
[jira] Closed: (UIMA-1733) Import AlchemyAPI Annotator code inside the Sandbox
[ https://issues.apache.org/jira/browse/UIMA-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili closed UIMA-1733. - Import AlchemyAPI Annotator code inside the Sandbox --- Key: UIMA-1733 URL: https://issues.apache.org/jira/browse/UIMA-1733 Project: UIMA Issue Type: Task Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Once the SGA has been recorded we can start importing the code -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Discuss] graduation
+1 Tommaso 2010/2/17 Jukka Zitting jukka.zitt...@gmail.com Hi, On Wed, Feb 17, 2010 at 3:01 AM, Marshall Schor m...@schor.com wrote: +1 from me, but I have recently received responses from our other 2 mentors, who both agree to help out occasionally, on the PMC - so I'd like to add them to our PMC list (Sam Ruby, and Ken Coar). Ken acknowledges that he hasn't been too helpful in the past (but he has done various things only an Apache Member can do, for us) and says that maybe he can be of better help in the future, and Sam was OK either way with us putting him on the PMC. Sounds good to me! BR, Jukka Zitting
[jira] Commented: (UIMA-1733) Import AlchemyAPI Annotator code inside the Sandbox
[ https://issues.apache.org/jira/browse/UIMA-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12834679#action_12834679 ] Tommaso Teofili commented on UIMA-1733: --- SGA has been recorded, so we can start importing the code Import AlchemyAPI Annotator code inside the Sandbox --- Key: UIMA-1733 URL: https://issues.apache.org/jira/browse/UIMA-1733 Project: UIMA Issue Type: Task Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Once the SGA has been recorded we can start importing the code -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1733) Import AlchemyAPI Annotator code inside the Sandbox
[ https://issues.apache.org/jira/browse/UIMA-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1733. --- Resolution: Fixed Code import completed Import AlchemyAPI Annotator code inside the Sandbox --- Key: UIMA-1733 URL: https://issues.apache.org/jira/browse/UIMA-1733 Project: UIMA Issue Type: Task Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Once the SGA has been recorded we can start importing the code -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1740) Mock integration tests on AlchemyAPI Annotator
Mock integration tests on AlchemyAPI Annotator --- Key: UIMA-1740 URL: https://issues.apache.org/jira/browse/UIMA-1740 Project: UIMA Issue Type: Bug Reporter: Tommaso Teofili Assignee: Tommaso Teofili Since previously the API key was already put inside the AE descriptor and now it's been removed, the URL call should be mocked to avoid tests' failure due to HTTP 403 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1741) Add AlchmeyAPI Annotator documentation
Add AlchmeyAPI Annotator documentation -- Key: UIMA-1741 URL: https://issues.apache.org/jira/browse/UIMA-1741 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Generated documentation on features and use of AlchemyAPI Annotator must be provided -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [PROPOSAL] AlchemyAPI Annotator
Hi all, Just for information purpose: I've sent the grant 6 days ago, but still got no reply. Cheers. Tommaso 2010/2/3 Tommaso Teofili tommaso.teof...@gmail.com Sure, Tommaso 2010/2/3 Jörn Kottmann kottm...@gmail.com Tommaso Teofili wrote: Thanks a lot, Marshall! We'll fill the grant and let you know once it's been sent. Maybe you want to open a jira issue, then we can track the import of the project there. Jörn
Re: [Discuss] graduation
Hi Jukka, the proposed resolution is in my opinion very good. +1 Cheers. Tommaso 2010/2/16 Jukka Zitting jukka.zitt...@gmail.com Hi, Let's push this forward... See below for a proposed board resolution with Marshall as the chairman, with all the current committers (and me as a former mentor) as PMC members, and with the scope I proposed in response to Marshall's version. WDYT? BR, Jukka Zitting X. Establish the Apache UIMA Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software related to the analysis of unstructured data, guided by the UIMA Oasis Standard, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache UIMA Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache UIMA Project be and hereby is responsible for the creation and maintenance of software related to the analysis of unstructured data, guided by the UIMA Oasis Standard, and be it further RESOLVED, that the office of Vice President, Apache UIMA be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache UIMA Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache UIMA Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache UIMA Project: * Adam Lallyala...@apache.org * Bhavani Iyer bhav...@apache.org * Burn Lewisb...@apache.org * Edward Epsteine...@apache.org * Jaroslaw Cwiklik cwik...@apache.org * Joern Kottmannjo...@apache.org * Jukka Zitting ju...@apache.org * Marshall Schorsc...@apache.org * Michael Baessler mbaess...@apache.org * Thilo Goetz twgo...@apache.org * Tommaso Teofili tomm...@apache.org * Tong Fin tong...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Marshall Schor be appointed to the office of Vice President, Apache UIMA, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache UIMA PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache UIMA Project; and be it further RESOLVED, that the Apache UIMA Project be and hereby is tasked with the migration and rationalization of the Apache Incubator UIMA podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator UIMA podling encumbered upon the Apache Incubator Project are hereafter discharged.
rename uimaj-ep-runtime ?
Hi all, following the UIMA and OSGI thread, do you think we can rename uimaj-ep-runtime as uimaj-osgi-untime ? I'm for a +1. I think it would be much clearer than binding it to Eclipse name but it's just my opinion. So what do you think? Cheers, Tommaso p.s.: the version in the parent is 2.3.0.incubating instead 2.3.0-incubating, maybe we'd better change it to make it consistent with the other projects' version
[jira] Commented: (UIMA-1733) Import AlchemyAPI Annotator code inside the Sandbox
[ https://issues.apache.org/jira/browse/UIMA-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12832088#action_12832088 ] Tommaso Teofili commented on UIMA-1733: --- SGA has been sent Import AlchemyAPI Annotator code inside the Sandbox --- Key: UIMA-1733 URL: https://issues.apache.org/jira/browse/UIMA-1733 Project: UIMA Issue Type: Task Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Once the SGA has been recorded we can start importing the code -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: going to Maven central
For the common practices to upload an artifact to Maven Central: http://maven.apache.org/guides/mini/guide-central-repository-upload.html I read that our Apache repo gets synchronized with Central so we hopefully only need to deploy it on our repo and it will automatically will get to Central. However I don't know if the http://people.apache.org/repo/m2-incubating-repository/ is considered external or not (it's said to be accepted as synced but if everything outside Central is considered external the answer is yes) though I wonder if that repo can stay inside the POM. Cheers. Tommaso 2010/2/7 Marshall Schor m...@schor.com Tommaso Teofili wrote: Hi all, since we are talking about graduation I think that another thing we need to leverage is the availability of UIMA packages on Maven central. As far as I know there some constraints we should respect to reach this, for example being independent from other external repos. What do you think? I am in favor of updating things to better follow Maven conventions and constraints. Can you say more specifically what needs changing? Do our POMs currently have dependencies to other external repos? -Marshall
going to Maven central
Hi all, since we are talking about graduation I think that another thing we need to leverage is the availability of UIMA packages on Maven central. As far as I know there some constraints we should respect to reach this, for example being independent from other external repos. What do you think? Cheers. Tommaso
Re: [PROPOSAL] AlchemyAPI Annotator
Thanks a lot, Marshall! We'll fill the grant and let you know once it's been sent. Cheers, Tommaso 2010/2/1 Marshall Schor m...@schor.com 30% * 19K lines = ~ 5.7Klocs, written by 2 people (mostly Tommaso). This seems to me to fit the criteria of needing a software grant (see http://apache.org/licenses/#grants), where it says: When an individual or corporation decides to donate a body of existing software or documentation to one of the Apache projects, they need to execute a formal Software Grant Agreement http://apache.org/licenses/software-grant.txt (SGA) with the ASF. I don't think it is very difficult to do - the main issue in the past has been getting confirmation that it was recorded. See bottom of page http://incubator.apache.org/ip-clearance/index.html for instructions re: having multiple people sign. See this page http://incubator.apache.org/ip-clearance/ip-clearance-template.html for instructions on where to send (under Process, step 3). -Marshall Tommaso Teofili wrote: 2010/1/29 Jörn Kottmann kottm...@gmail.com How many of these 19K lines are generated ? About 70%. Cheers, Tommaso
Re: [PROPOSAL] AlchemyAPI Annotator
Sure, Tommaso 2010/2/3 Jörn Kottmann kottm...@gmail.com Tommaso Teofili wrote: Thanks a lot, Marshall! We'll fill the grant and let you know once it's been sent. Maybe you want to open a jira issue, then we can track the import of the project there. Jörn
[jira] Created: (UIMA-1733) Import AlchemyAPI Annotator code inside the Sandbox
Import AlchemyAPI Annotator code inside the Sandbox --- Key: UIMA-1733 URL: https://issues.apache.org/jira/browse/UIMA-1733 Project: UIMA Issue Type: Task Components: Sandbox Reporter: Tommaso Teofili Assignee: Tommaso Teofili Once the SGA has been recorded we can start importing the code -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Discuss] graduation
After reading that page I also think UIMA is ready to graduate. Cheers, Tommaso 2010/1/30 Eddie Epstein eaepst...@gmail.com Reading through the main link (use .html not htm) there are a lot of things to do as part of the graduation process, and UIMA looks ready to start. I'm +1 for helping. Eddie On Fri, Jan 29, 2010 at 5:00 PM, Marshall Schor m...@schor.com wrote: After reading the parts of the ASF website related to graduation from the incubator to a top-level project (for instance I think this is the main link: http://incubator.apache.org/guides/graduation.htm), do you think we're ready for graduation? Is there more we need to do first? -Marshall
Re: OSGIing UIMA
Hi all, my initial need was to simply use UIMA as OSGI bundle so I looked at the uimaj-as-osgi-runtime and uimaj-eclipse-runtime that seem to me very near to what I deserve, they were fine except that (at the moment) I don't need the UIMA-AS packages and the 'eclipse' label puzzled me a bit and actually, as far as I can understand, the Eclipe plugin configurations in the uimaj-eclipse-plugins POM are not needed for an OSGI environment. So my first idea was only to do some crafting on uimaj-eclipse-runtime. What I realized after Thilo's reply was that instead of having a unique UIMA OSGI runtime artifact (bundle) with all the stuff inside we could make each UIMA module (uimaj-core, uimaj-tools, uimaj-cpe, etc) a single bundle with all its fine grain packages and resources. If this should be the case we should provide alternative packagings (jar/pear/bundle) to maintain compatibility with non-OSGI systems. More over (for annotators) if we enable the bundle packaging then we need to modify the tools that use pears i.e. the CVD to be able to load AEs also from a bundle. Thanks for your replies, Cheers. Tommaso 2010/1/28 Jörn Kottmann kottm...@gmail.com Marshall Schor wrote: I'm probably showing my ignorance here :-) but, leaving aside the question of making core uima support annotators as osgi bundles, can you say what the differences are between the uimaj-ep-runtime bundle we build for eclipse, having all the core UIMA capability, and your goal below of making uimaj available as an OSGI bundle? My understanding is that Eclipse plugins are osgi bundles, and we build these using the Felix maven plugin, which wraps the standard OSGI bundle making code. Thanks for the clarifications... Isn't the only thing we are missing the support for annotators in OSGi bundles ? Right now that can be hacked by using the Eclipse-RegisterBuddy header, which works for example with the spring OSGi server. Thilo, why do you think we cannot add OSGi annotator bundles without breaking backward compatibility ? Beside that, it might be a bit more tricky for uima as because it relies on ActiveMQ which did not work well with OSGi in my tests with the uima as client and the spring OSGi server. Jörn
Re: [PROPOSAL] AlchemyAPI Annotator
Hi all, we have 3 +1s and no 0s nor -1s. Can we consider it passed and go on with importing the code? Cheers, Tommaso
Re: [PROPOSAL] AlchemyAPI Annotator
Hi Thilo, I wrote all the code by myself except for some help from Simone Tripodi (Cocoon committer and PMC, Commons Digester Sandbox and Labs Amber committer) with the JsonDigester to parse Json files (made with javacc). In total it's 18.705 lines of code (you can see some metrics by Ohloh on http://code.google.com/p/alchemy-annotator/ ), many classes are JCASGen generated TypeSystem classes but the relevant part is more or less 50 classes. Do you think we need a software grant? Cheers, Tommaso 2010/1/29 Thilo Goetz twgo...@gmx.de On 1/29/2010 10:12, Tommaso Teofili wrote: Hi all, we have 3 +1s and no 0s nor -1s. Can we consider it passed and go on with importing the code? Cheers, Tommaso Tommaso, how much code is it? If it's not a lot of code, and you wrote all of it yourself, you can just commit it. If it's a significant amount of code, we may need a code grant (it would be easier if we didn't). --Thilo
Re: [PROPOSAL] AlchemyAPI Annotator
2010/1/29 Jörn Kottmann kottm...@gmail.com How many of these 19K lines are generated ? About 70%. Cheers, Tommaso
Re: OSGIing UIMA
2010/1/29 Jörn Kottmann kottm...@gmail.com Taking this approach does not has a real advantage over the approach we have right now, in my opinion. Maybe you save a few KB storage on the server, if you do not deploy all the classes. But what else do you think we get ? One thing that it would be useful is hot redeploying of only some of the components of the distribution (annotators or other modules) instead of the entire distribution. I personally like the idea of going towards something a bit more interoperable of our PEARs (that work pretty well indeed) but don't misunderstand me, I'm not for a we must fully convert to OSGI now, let's put some ideas down and see if they are good. So I think Marshall's point of putting a wiki page to collect all the pros and cons is nice. Cheers, Tommaso
OSGIing UIMA
Hi all, reading http://cwiki.apache.org/UIMA/uima-osgi-enablement.html I was wondering about how making uimaj available as an OSGI bundle. I've seen the uimaj-as-osgi-runtime so I think I could make something similar to it, and not using eclipse-plugin-supePom as parent, only for uimaj-core, tools component-test, etc. (excluding AS stuff). What do you think about it? Since this is something I'm going to dig inside to integrate UIMA with Clerezza do you have any suggestions/hints? Cheers, Tommaso
Re: OSGIing UIMA
Hi Thilo 2010/1/28 Thilo Goetz twgo...@gmx.de I've been thinking about this topic myself on and off for a while. I think it doesn't make much sense to create a UIMA core OSGi bundle without OSGi-enabling UIMA itself. If you go the OSGi route, you want your annotators to be bundles as well. So you need to add the ability to UIMA to load annotator OSGi bundles. I don't think that would be too hard to do, but I'm not sure it can be done in ways that are completely backward compatible. I would personally love to see OSGi bundles replace our pear format. Anyway, these are just my thoughts. If there is interest in really OSGiifying UIMA, that's something I'd be interested in contributing to. --Thilo I agree with your points indeed, in my opinion making all UIMA components OSGI bundles would be a real plus in the means of standards, distribution, interoperabilty and more. On the contrary it might be not so good to have this change for deploying stuff in a non-OSGI environment so we should think about having alternative packagings for (backward) compatibility (for example using maven profiles, but it's just the first thing that comes to my mind). More over it could perhaps bring one more dependency (Felix?) inside UIMA so it would be another drawback. An alternative would be having a UIMA OSGIfier for each of the UIMA base components but I don't like the idea very much and it could be a long way ... Thanks Thilo, I am interested in this OSGIfication, what do others think about it? Cheers, Tommaso
Re: [PROPOSAL] AlchemyAPI Annotator
2010/1/26 Eddie Epstein eaepst...@gmail.com Presumably you are finding this useful? Yes I do :-) If the answer is yes, +1! Eddie Cheers, Tommaso
[PROPOSAL] AlchemyAPI Annotator
Hi all, I've developed a set of UIMA components (analysis engines) wrapping AlchemyAPI [1] webservices provided by Orchestr8 [2] I'd like to donate and include in the Sandbox. These services are something similar to the OpenCalais ones and include: - Entity extraction - Text categorization - Language detection - Keyword extraction - Text extraction - Content scraping - Microformats extraction - RSS/Atom extraction You can find the code under Google Code at [3]. I hope it can be useful. Cheers, Tommaso P.S.: Note (just like OpenCalais) that to be able to use these webservices you need a subscription key. [1] : http://www.alchemyapi.com [2] : http://www.orch8.net/ [3] : http://code.google.com/p/alchemy-annotator/
January board report
Hi, fot the January 2010 report (today is the deadline) I collected the following items: * 2.3.0-RC9 is out for testing and being voted as 2.3.0-incubating * UIMA and Semantic Search presentation at IKS 2nd workshop (see [[ http://incubator.apache.org/uima/iks09.html|here]]) * new incubating project Clerezza planning to integrate with UIMA * New committer voted in (Bhavani Iyer) * Fixed switching between ResourceManagers loaded with different class loaders * Fixed script classpaths * Fixed UIMA-AS broker connection issues I got the last three items from our Jira sorting issues by priority. Any other suggestion is welcome :) Cheers. Tommaso
Re: January board report
2010/1/13 Thilo Goetz twgo...@gmx.de Hi Tommaso, it's a good thought, but I don't think the board is interested in our progress at that level of detail. I would leave out mentioning specific issues we fixed. My opinion, anyway. --Thilo Ok, thanks Thilo. I only wanted to point out our effort in putting together a clean stable release but you're probably right, too much detail. Other suggestions? Cheers. Tommaso
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Hi guys, we have to report by Wednesday, I can take care of it. We can share in this thread all the stuff we want to report. Cheers. Tommaso 2010/1/1 Marvin mar...@apache.org Dear UIMA Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798629#action_12798629 ] Tommaso Teofili commented on UIMA-1717: --- a big +1 for me Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
Hi, I'm going to add - 2.3.0-RC9 is out for testing - UIMA and Semantic Search presentation at IKS 2nd workshop (see http://wiki.iks-project.eu/index.php/2nd_Workshop) - new incubating project Clerezza planning to integrate with UIMA Tommaso 2010/1/11 Tommaso Teofili tommaso.teof...@gmail.com Hi guys, we have to report by Wednesday, I can take care of it. We can share in this thread all the stuff we want to report. Cheers. Tommaso 2010/1/1 Marvin mar...@apache.org Dear UIMA Developers, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 January 2010, 2 pm Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is one week prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/January2010 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Incubator PMC/Board report for January 2010 (UIMA Developers uima-dev@incubator.apache.org)
2010/1/11 Thilo Goetz twgo...@gmx.de Would it be appropriate to say something like getting ready for a graduation vote very soon so the Board knows we're getting there and doesn't worry about us too much? +1 Tommaso
Re: [VOTE] Release UIMA 2.3.0 RC9 as UIMA 2.3.0 incubating
+1 Tommaso 2010/1/11 Marshall Schor m...@schor.com Marshall Schor wrote: This build keeps the uimacpp and sandbox components from the previous release candidate (the download site on people.apache.org/~schorhttp://people.apache.org/%7Eschorhas hard links to the previous artifacts - so they are guaranteed to be identical). We've had a few sanity checks for the RC9 build, including installing the Eclipse plugins via the RC9 update site on both linux and windows, and running downloading installing the base uima and uima-as binary components and running the installation verification tests - and everything looks good. This build consists of 4 major components: the core UIMA framework (uimaj), the C++ enablement (uimacpp), the Asynchronous Scaleout component (uima-as) and a set of annotators and other add-ons (sandbox). These have been through more than 3 months of validation and testing (counting the previous release candidates). The build process was strengthened to include running RAT (the Release Audit tool) automatically and verifying no RAT issues are found (except for the uimacpp part, where it is still run and verified manually). The release artifacts are available on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC9/http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC9/ These artifacts include a partial version of the Eclipse Update Site for the Eclipse plugins, but is complete for the 2.3.0 release. The release is digitally signed by Marshall Schor for all the components except for the C++ component, which is signed by Edward Epstein. No new export control issues are needed for the components; only the uima-as component continues to be classified as 5D002 because it includes Apache ActiveMQ which is so classified (see http://www.apache.org/licenses/exports/ ) Please vote on approving this release. This vote is for all 4 components, together. After the UIMA committers vote, we will ask the IPMC to vote. [ ] +1 Release RC9, it's ready [ ] -1 Don't release yet because of these issues which need to be addressed first: ... --Marshall +1 -Marshall
[jira] Commented: (UIMA-1717) Use Apache Hudson and Nexus repository facilities
[ https://issues.apache.org/jira/browse/UIMA-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12798715#action_12798715 ] Tommaso Teofili commented on UIMA-1717: --- in my experience Nexus is good because you can control dependencies (selecting which are got from central and which are hosted), moreover I think is good for the release process (deploy-staging-release i.e.: no more private spaces for hosting RCs required) and finally for the fact that having a Nexus snapshot repo you can let users download for example a 2.3.0-incubating-SNAPSHOT without having to build it from sources. my 2 cents Use Apache Hudson and Nexus repository facilities - Key: UIMA-1717 URL: https://issues.apache.org/jira/browse/UIMA-1717 Project: UIMA Issue Type: Wish Components: Build, Packaging and Test Reporter: Richard Eckart de Castilho Original Estimate: 0h Remaining Estimate: 0h The ASF seems to provide a continuous integration facility (c.f. http://wiki.apache.org/general/Hudson), as well as a Nexus Maven artifact repository (c.f. http://wiki.apache.org/portals/FrontPage/HowtoUseNexusForRelease). It would be great if UIMA would make use of these facilities, allowing for better testing as well as access to fresh snapshot artifacts. It would hopefully also facilitate things for people compiling UIMA or the UIMA sandbox on their private Hudson instances. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: 2.3.0 release candidate 08 now on people.apache.org for review
Hi, I tested uimaj (on Mac) and everything went fine. Cheers, Tommaso 2009/12/16 Jörn Kottmann kottm...@gmail.com Marshall Schor wrote: This candidate is located at http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC8/http://people.apache.org/%7Eschor/uima-release-candidates/2.3.0-RC8/and includes uimaj uima-as sandbox (this is identical to RC7, it wasn't rebuilt) uimacpp (this is a rebuild by Eddie, hard-linked from p.a.o/~eae, rel 03) eclipse-update-site I'll start the vote in 2-3 days, after some sanity tests are done (to insure I didn't mess up the build process). I will install the new uima-as on our test servers tomorrow. Jörn
[jira] Closed: (UIMA-1694) Error 'scm url cannot be null' on uimaj POM
[ https://issues.apache.org/jira/browse/UIMA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili closed UIMA-1694. - Error 'scm url cannot be null' on uimaj POM --- Key: UIMA-1694 URL: https://issues.apache.org/jira/browse/UIMA-1694 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.3S Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: 2.3 When launching 'mvn -Dmaven.repo.local=/tmp/uimaj-rc5 clean install' for testing the new 2.3.0-rc5, an error 'scm url cannot be null' on uimaj POM comes out -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1694) Error 'scm url cannot be null' on uimaj POM
[ https://issues.apache.org/jira/browse/UIMA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12785945#action_12785945 ] Tommaso Teofili commented on UIMA-1694: --- I don't know if it'll be necessary to have specific versions of this tag in each project's pom, probably it would be better; it would not be a big issue, though a bit annoying to maintain. Maybe we could put https in place of http now, and once the release has been done we can point to the appropriate tag inside the url. What do you think? Error 'scm url cannot be null' on uimaj POM --- Key: UIMA-1694 URL: https://issues.apache.org/jira/browse/UIMA-1694 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.3S Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: 2.3 When launching 'mvn -Dmaven.repo.local=/tmp/uimaj-rc5 clean install' for testing the new 2.3.0-rc5, an error 'scm url cannot be null' on uimaj POM comes out -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: testing rc-2
added myself for testing base rc2 package on Mac. Tommaso 2009/11/17 Marshall Schor m...@schor.com We invite all who are following this list to download and test release candidate 2. Please visit the wiki page http://cwiki.apache.org/confluence/display/UIMA/TestPlan2.3.0 and edit it as needed. A good practice: if you decide to test something (say, for instance, the install on a MAC platform), edit the bottom part of the page and add a line describing what you plan to do, with an empty box for Status / comments. This will let others know you are planning to test this area, and may avoid some duplicate work :-). When the test is done, add that in the status, something like 100% done or whatever. I hope to get the essential testing and reviews done this week. -Marshall
Re: UIMA @ IKS-project
Hi all, back from 2nd IKS [1] Workshop last friday in Rome where I had a speech/demo about UIMA and Semantic Search. It's been a nice experience and I would like to share with you some good news. Firstly I had some good feedback about UIMA in general from the people at the workshop. Bertrand Delacretaz, who is part of IKS as Day employee and also member of ASF, had a good feeling about UIMA for semantic search to include inside IKS stack [2]. The Nuxeo open source ECM [3] is developing its semantic search module on the top of UIMA. You can see some photos here [4]. My introduction slides are available at [5]. My demos were about a real estate market analysis tool which uses UIMA for metadata extraction and an integration between UIMA and AlchemyAPI, I hope to be able to provide the screecasts soon. Let me know if you have any questions. Cheers, Tommaso [1] : http://www.iks-project.eu [2] : http://dev.day.com/microsling/content/blogs/main/iks-pragmatic-view-update.html [3] : http://www.nuxeo.com/en [4] : http://homepages.uni-paderborn.de/fabianc/iks-gam-rome09/ [5] : http://www.slideshare.net/teofili/apache-uima-and-semantic-search [6] : 2009/10/16 Tommaso Teofili tommaso.teof...@gmail.com Hi all, I've been contacted from the guys of IKS European Project (see http://www.iks-project.eu ) and they asked me to give a demo talk about UIMA applied to semantic search. The workshop is going to be held on November 12 and 13 in Rome, Italy (see http://www.iks-project.eu/every-cms-needs-semantic-search-and-iks-can-help-you-build-it). Cheers, Tommaso
Re: UIMA @ IKS-project
Sure :) Tommaso 2009/11/18 Marshall Schor m...@schor.com Nice report, Tommaso. Maybe we can also add this to our website in the events and conferences area? -Marshall Tommaso Teofili wrote: Hi all, back from 2nd IKS [1] Workshop last friday in Rome where I had a speech/demo about UIMA and Semantic Search. It's been a nice experience and I would like to share with you some good news. Firstly I had some good feedback about UIMA in general from the people at the workshop. Bertrand Delacretaz, who is part of IKS as Day employee and also member of ASF, had a good feeling about UIMA for semantic search to include inside IKS stack [2]. The Nuxeo open source ECM [3] is developing its semantic search module on the top of UIMA. You can see some photos here [4]. My introduction slides are available at [5]. My demos were about a real estate market analysis tool which uses UIMA for metadata extraction and an integration between UIMA and AlchemyAPI, I hope to be able to provide the screecasts soon. Let me know if you have any questions. Cheers, Tommaso [1] : http://www.iks-project.eu [2] : http://dev.day.com/microsling/content/blogs/main/iks-pragmatic-view-update.html [3] : http://www.nuxeo.com/en [4] : http://homepages.uni-paderborn.de/fabianc/iks-gam-rome09/ [5] : http://www.slideshare.net/teofili/apache-uima-and-semantic-search [6] : 2009/10/16 Tommaso Teofili tommaso.teof...@gmail.com Hi all, I've been contacted from the guys of IKS European Project (see http://www.iks-project.eu ) and they asked me to give a demo talk about UIMA applied to semantic search. The workshop is going to be held on November 12 and 13 in Rome, Italy (see http://www.iks-project.eu/every-cms-needs-semantic-search-and-iks-can-help-you-build-it ). Cheers, Tommaso
[jira] Commented: (UIMA-1647) Scripts fail to call runUimaClass.sh
[ https://issues.apache.org/jira/browse/UIMA-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12773495#action_12773495 ] Tommaso Teofili commented on UIMA-1647: --- I'm trying to reproduce it on my Mac Scripts fail to call runUimaClass.sh - Key: UIMA-1647 URL: https://issues.apache.org/jira/browse/UIMA-1647 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Environment: Ubuntu Server 8.10, Java 1.6 Reporter: Jörn Kottmann Assignee: Jörn Kottmann Priority: Blocker Fix For: 2.3, 2.3AS Executing deployAsyncService.sh fails with the following error message: .: 28: runUimaClass.sh: not found deployAsyncService.sh calls runUimaClass.sh with . runUimaClass.sh ..., in an older version this script called setUimaClassPath.sh, but that was done with the absolute path: . $UIMA_HOME/bin/setUimaClassPath.sh I suggest that we change all our .sh scripts to use the absolute path like it was done before for at least the deployAsyncService.sh script. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
UIMA @ IKS-project
Hi all,I've been contacted from the guys of IKS European Project (see http://www.iks-project.eu ) and they asked me to give a demo talk about UIMA applied to semantic search. The workshop is going to be held on November 12 and 13 in Rome, Italy (see http://www.iks-project.eu/every-cms-needs-semantic-search-and-iks-can-help-you-build-it). Cheers, Tommaso
Re: UIMA report is due
I never wrote that report before, but if nobody else comes out I volunteer (maybe I'll ask some help here and there to gather all the informations). +1 for begin the graduation process after the 2.3.0 release. Tommaso 2009/10/13 Jukka Zitting jukka.zitt...@gmail.com Hi, We're again due for our quarterly report, see [1]. Anyone willing to draft the report? As for the top priorities before graduation, I think UIMA is now ready to graduate and only needs to follow the graduation process [2] to become an Apache TLP. [1] http://wiki.apache.org/incubator/October2009 [2] http://incubator.apache.org/guides/graduation.html#process BR, Jukka Zitting
Re: Change to build process for assemblies
I also get the same behavior Jorn reports (inspecting).
Tommaso
2009/10/13 Jörn Kottmann kottm...@gmail.com
Despite these warnings the distribution gets created, but it has the wrong
name uima-as-2.3.0-incubating-SNAPSHOT-xxx but should be
uima-2.3.0-incubating-SNAPSHOT-xxx.
Jörn
Jörn Kottmann wrote:
When building (mvn install in uimaj-distr) on Unix I get lots of warnings
towards the
end maybe, there is something incorrect:
[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: src/main/assembly/bin.xml
[INFO] Reading assembly descriptor: src/main/assembly/src.xml
[INFO] Building tar :
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-bin.tar.gz
[WARNING] Assembly file:
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-bin.tar.gz
is not a regular file (it may be a directory). It cannot be attached to the
project build for installation or deployment.
[INFO] Building zip:
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-bin.zip
[WARNING] Assembly file:
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-bin.zip
is not a regular file (it may be a directory). It cannot be attached to the
project build for installation or deployment.
[INFO] uima-as-2.3.0-incubating-SNAPSHOT/ already added, skipping
[INFO] Building tar :
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-src.tar.gz
[INFO] uima-as-2.3.0-incubating-SNAPSHOT/ already added, skipping
[WARNING] Assembly file:
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-src.tar.gz
is not a regular file (it may be a directory). It cannot be attached to the
project build for installation or deployment.
[INFO] uima-as-2.3.0-incubating-SNAPSHOT/ already added, skipping
[INFO] Building zip:
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-src.zip
[INFO] uima-as-2.3.0-incubating-SNAPSHOT/ already added, skipping
[WARNING] Assembly file:
/home/joern/uima-dev3/uimaj-distr/target/uima-as-2.3.0-incubating-SNAPSHOT-src.zip
is not a regular file (it may be a directory). It cannot be attached to the
project build for installation or deployment.
Jörn
Re: UIMA report is due
2009/10/13 Marshall Schor m...@schor.com Tommaso Teofili wrote: I never wrote that report before, but if nobody else comes out I volunteer (maybe I'll ask some help here and there to gather all the informations). +1 for begin the graduation process after the 2.3.0 release. Tommaso Great, Thanks Tommaso! Please start by cutting/pasting a copy of our last report, and deleting the specific items - this will guarantee that the first boiler plate part of the report is there :-). Here is the April report: *UIMA is a component framework for the analysis of unstructured content such as text, audio and video. UIMA entered incubation on October 3, 2006. * *Some recent activity: * - *OASIS (http://www.oasis-open.org) members approved the Unstructured Information Management Architecture (UIMA) version 1.0 as an OASIS Standard. * - *A new contributor, Rico Landefeld, contributed a component to enable indexing annotations as fields using Lucene. * - *Many bug fixes and improvements continue to be focused on UIMA-AS (the asynchronous scaleout add-on to base UIMA) driven by experience with users doing extensive scaleout. The fixes address error handling and performance. * - *IBM and MAYO Clinic announced a new consortium around making available open-source UIMA annotators for use by the Medical / Health area; see http://ohnlp.org* *Items to complete before graduation: * *We still need to attract more new committers with diverse affiliations. * As far as I understand this final line can be removed too. Some items to include: New committers added (Burn Lewis and you :-) ), work almost complete on 2.3.0 release, new integration with other Apache projects (such as Lucas - integration with Apache Lucene search). Another point item: The Configurable Feature Editor, including documentation, was refreshed, and will be included in the next release. Another point item: the next sandbox release is more than doubling the number of pre-done UIMA components that are available with the framework. Another point is that IBM announced a grand challenge effort to have a computer compete live against humans on the popular (in the USA) TV game, Jeopardy! in answering open-domain questions, (not connected to the internet), in real time - and that this system is being built upon UIMA and UIMA-AS (see http://www.research.ibm.com/deepqa/faq.shtml#24 ). I'd also add that building (Maven use optimized using parent POMs, RAT, etc...) and code quality (generics, deprecation of stale code) have been improved, UIMA-AS has been graduated out of the Sandbox as an add-on package. And you can change the items to complete before graduation to saying it's ready to graduate, and plans to start that process after the current release activity is finished. Finally, if you have time, the project page ( http://incubator.apache.org/projects/uima.html ) needs updating, especially to add the new committers. Keep us posted throughout the day your progress on these - to give others a chance to review / update the report (as it's due tomorrow! ). Do I have to incrementally update the wiki while we discuss or only when we reach a satisfiable verion of the report? Thanks, Tommaso -Marshall 2009/10/13 Jukka Zitting jukka.zitt...@gmail.com Hi, We're again due for our quarterly report, see [1]. Anyone willing to draft the report? As for the top priorities before graduation, I think UIMA is now ready to graduate and only needs to follow the graduation process [2] to become an Apache TLP. [1] http://wiki.apache.org/incubator/October2009 [2] http://incubator.apache.org/guides/graduation.html#process BR, Jukka Zitting
Re: UIMA report is due
I've just updated the wiki. Let me know if there is something else to mention that comes in your mind. Tommaso 2009/10/13 Marshall Schor m...@schor.com Tommaso Teofili wrote: 2009/10/13 Marshall Schor m...@schor.com Tommaso Teofili wrote: I never wrote that report before, but if nobody else comes out I volunteer (maybe I'll ask some help here and there to gather all the informations). +1 for begin the graduation process after the 2.3.0 release. Tommaso Great, Thanks Tommaso! Please start by cutting/pasting a copy of our last report, and deleting the specific items - this will guarantee that the first boiler plate part of the report is there :-). Here is the April report: Probably best to use the July 2009 report :-) as the template, (but it probably doesn't really matter...) *UIMA is a component framework for the analysis of unstructured content such as text, audio and video. UIMA entered incubation on October 3, 2006. * *Some recent activity: * - *OASIS (http://www.oasis-open.org) members approved the Unstructured Information Management Architecture (UIMA) version 1.0 as an OASIS Standard. * - *A new contributor, Rico Landefeld, contributed a component to enable indexing annotations as fields using Lucene. * - *Many bug fixes and improvements continue to be focused on UIMA-AS (the asynchronous scaleout add-on to base UIMA) driven by experience with users doing extensive scaleout. The fixes address error handling and performance. * - *IBM and MAYO Clinic announced a new consortium around making available open-source UIMA annotators for use by the Medical / Health area; see http://ohnlp.org* *Items to complete before graduation: * *We still need to attract more new committers with diverse affiliations. * As far as I understand this final line can be removed too. Right. Some items to include: New committers added (Burn Lewis and you :-) ), work almost complete on 2.3.0 release, new integration with other Apache projects (such as Lucas - integration with Apache Lucene search). Another point item: The Configurable Feature Editor, including documentation, was refreshed, and will be included in the next release. Another point item: the next sandbox release is more than doubling the number of pre-done UIMA components that are available with the framework. Another point is that IBM announced a grand challenge effort to have a computer compete live against humans on the popular (in the USA) TV game, Jeopardy! in answering open-domain questions, (not connected to the internet), in real time - and that this system is being built upon UIMA and UIMA-AS (see http://www.research.ibm.com/deepqa/faq.shtml#24). I'd also add that building (Maven use optimized using parent POMs, RAT, etc...) and code quality (generics, deprecation of stale code) have been improved, UIMA-AS has been graduated out of the Sandbox as an add-on package. Great. Also mention the Cas Editor has been graduated out of the Sandbox and is now part of base UIMA. And you can change the items to complete before graduation to saying it's ready to graduate, and plans to start that process after the current release activity is finished. Finally, if you have time, the project page ( http://incubator.apache.org/projects/uima.html ) needs updating, especially to add the new committers. Keep us posted throughout the day your progress on these - to give others a chance to review / update the report (as it's due tomorrow! ). Do I have to incrementally update the wiki while we discuss or only when we reach a satisfiable verion of the report? To reduce work, just update the wiki, and then post here that's it's updated; we'll take a look on the wiki and do any updates there, I think. -Marshall Thanks, Tommaso -Marshall 2009/10/13 Jukka Zitting jukka.zitt...@gmail.com Hi, We're again due for our quarterly report, see [1]. Anyone willing to draft the report? As for the top priorities before graduation, I think UIMA is now ready to graduate and only needs to follow the graduation process [2] to become an Apache TLP. [1] http://wiki.apache.org/incubator/October2009 [2] http://incubator.apache.org/guides/graduation.html#process BR, Jukka Zitting
Re: UIMA report is due
I've added also Tika to the projects UIMA is now integrated with. Tommaso 2009/10/13 Tommaso Teofili tommaso.teof...@gmail.com I've just updated the wiki. Let me know if there is something else to mention that comes in your mind. Tommaso 2009/10/13 Marshall Schor m...@schor.com Tommaso Teofili wrote: 2009/10/13 Marshall Schor m...@schor.com Tommaso Teofili wrote: I never wrote that report before, but if nobody else comes out I volunteer (maybe I'll ask some help here and there to gather all the informations). +1 for begin the graduation process after the 2.3.0 release. Tommaso Great, Thanks Tommaso! Please start by cutting/pasting a copy of our last report, and deleting the specific items - this will guarantee that the first boiler plate part of the report is there :-). Here is the April report: Probably best to use the July 2009 report :-) as the template, (but it probably doesn't really matter...) *UIMA is a component framework for the analysis of unstructured content such as text, audio and video. UIMA entered incubation on October 3, 2006. * *Some recent activity: * - *OASIS (http://www.oasis-open.org) members approved the Unstructured Information Management Architecture (UIMA) version 1.0 as an OASIS Standard. * - *A new contributor, Rico Landefeld, contributed a component to enable indexing annotations as fields using Lucene. * - *Many bug fixes and improvements continue to be focused on UIMA-AS (the asynchronous scaleout add-on to base UIMA) driven by experience with users doing extensive scaleout. The fixes address error handling and performance. * - *IBM and MAYO Clinic announced a new consortium around making available open-source UIMA annotators for use by the Medical / Health area; see http://ohnlp.org* *Items to complete before graduation: * *We still need to attract more new committers with diverse affiliations. * As far as I understand this final line can be removed too. Right. Some items to include: New committers added (Burn Lewis and you :-) ), work almost complete on 2.3.0 release, new integration with other Apache projects (such as Lucas - integration with Apache Lucene search). Another point item: The Configurable Feature Editor, including documentation, was refreshed, and will be included in the next release. Another point item: the next sandbox release is more than doubling the number of pre-done UIMA components that are available with the framework. Another point is that IBM announced a grand challenge effort to have a computer compete live against humans on the popular (in the USA) TV game, Jeopardy! in answering open-domain questions, (not connected to the internet), in real time - and that this system is being built upon UIMA and UIMA-AS (see http://www.research.ibm.com/deepqa/faq.shtml#24). I'd also add that building (Maven use optimized using parent POMs, RAT, etc...) and code quality (generics, deprecation of stale code) have been improved, UIMA-AS has been graduated out of the Sandbox as an add-on package. Great. Also mention the Cas Editor has been graduated out of the Sandbox and is now part of base UIMA. And you can change the items to complete before graduation to saying it's ready to graduate, and plans to start that process after the current release activity is finished. Finally, if you have time, the project page ( http://incubator.apache.org/projects/uima.html ) needs updating, especially to add the new committers. Keep us posted throughout the day your progress on these - to give others a chance to review / update the report (as it's due tomorrow! ). Do I have to incrementally update the wiki while we discuss or only when we reach a satisfiable verion of the report? To reduce work, just update the wiki, and then post here that's it's updated; we'll take a look on the wiki and do any updates there, I think. -Marshall Thanks, Tommaso -Marshall 2009/10/13 Jukka Zitting jukka.zitt...@gmail.com Hi, We're again due for our quarterly report, see [1]. Anyone willing to draft the report? As for the top priorities before graduation, I think UIMA is now ready to graduate and only needs to follow the graduation process [2] to become an Apache TLP. [1] http://wiki.apache.org/incubator/October2009 [2] http://incubator.apache.org/guides/graduation.html#process BR, Jukka Zitting
Re: UIMA report is due
And also Apache Camel to drive UIMA AS processing. Got it. 2009/10/13 Jörn Kottmann kottm...@gmail.com Tommaso Teofili wrote: I've just updated the wiki. Let me know if there is something else to mention that comes in your mind. The Configurable Feature Editor, including documentation, was refreshed, and will be included in the next release. Isn't it called Configurable Feature Extractor ? Right, it's now fixed. Tommaso
Re: UIMA report is due
2009/10/13 Thilo Goetz twgo...@gmx.de Tommaso, thanks for taking care of the report. I tried to add a line, but can't seem to log in to the wiki right now. Since we don't have much time, could you add a bullet on the recent UIMA workshop at a comp. ling. conference (Joern and I were there): - academic UIMA a ref=http://docs.google.com/View?id=dft23bqs_3c7qnzg6x;workshop/a with strong participation from UIMA's users list community Thanks, Thilo Just done! Tommaso Tommaso Teofili wrote: I never wrote that report before, but if nobody else comes out I volunteer (maybe I'll ask some help here and there to gather all the informations). +1 for begin the graduation process after the 2.3.0 release. Tommaso 2009/10/13 Jukka Zitting jukka.zitt...@gmail.com Hi, We're again due for our quarterly report, see [1]. Anyone willing to draft the report? As for the top priorities before graduation, I think UIMA is now ready to graduate and only needs to follow the graduation process [2] to become an Apache TLP. [1] http://wiki.apache.org/incubator/October2009 [2] http://incubator.apache.org/guides/graduation.html#process BR, Jukka Zitting
Re: [jira] Reopened: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
Hi, I set the SandboxDistr parent to SimpleUimaAsService POM too and set uimaj-as-activemq dependency scope to provided to avoid importing unnecessary transitive dependencies. Tommaso Il giorno 03/ott/2009, alle ore 00.08, Tommaso Teofili ha scritto: Il giorno 02/ott/2009, alle ore 19.21, Marshall Schor ha scritto: hmmm. I had left out the SimpleUimaAsService from the modules section originally in the mistaken belief that I needed to do that to avoid including it in the sandbox release. (That's not required, because the sandbox release content is set just by the assembly descriptors). But, in any case, you can set the parent of this to be the SandboxDistr, independently of whether or not the SimpleUimaAsService is in the module aggregation. Ok, it's right. I was in doubt so I did not add the parent. Then, you can delete all of the plugins in the build section :-) , and it will still build, nicely. There's some issue we'll need to dig through, though, because it pulls in a large number of jars related to activemq (I think), not all of which would need to be distributed. Yes, the large amount of jars is related to activemq; to avoid this we could set activemq scope to 'provided' or use the exclusion tag to import only wanted transitive dependencies. Note: this is not being released with our 2.3.0 release per previous discussions which indicated it needed to be documented first. -Marshall Tommaso
Re: [jira] Reopened: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
Hi Marshall, Lookin in the SandboxDistr POM I see SimpleUimaAsService is commented because SimpleUimaAsService needs uima-as for building and uima-as is not in the lifecycle of Sandbox, so finally SimpleUimaAsService was left out to avoid the Sandbox building failure. For this reason I did not put the parent SandboxDistr POM inside SimpleUimaAsService. Tommaso 2009/10/2 Marshall Schor m...@schor.com Tommaso Teofili (JIRA) wrote: [ https://issues.apache.org/jira/browse/UIMA-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] Tommaso Teofili reopened UIMA-1462: --- some plugins useful for licensing purposes were wrongly removed from pom Hi Tommaso - This POM appears to be missing the parent link. The POM parents add a lot of common build / dependency behavior; can you add that link, and then the much simpler POM will maybe work :-) -Marshall SimpleUimaAsService has checked in SimpleServer libraries as binaries - Key: UIMA-1462 URL: https://issues.apache.org/jira/browse/UIMA-1462 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleUimaAsService Affects Versions: 2.2.2S, 2.3S Reporter: Thilo Goetz Assignee: Tommaso Teofili Fix For: 2.3S Attachments: patch1462.txt, patch1462b1.txt, patch1462b2.txt, patch1462c1.txt, patch1462c2.txt, simpleServerDistributionPatch.txt, simpleUimaAsServicePatch.txt For the upcoming release, this should be changed so it depends on the SimpleServer project directly.
Re: [jira] Reopened: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
Il giorno 02/ott/2009, alle ore 19.21, Marshall Schor ha scritto: hmmm. I had left out the SimpleUimaAsService from the modules section originally in the mistaken belief that I needed to do that to avoid including it in the sandbox release. (That's not required, because the sandbox release content is set just by the assembly descriptors). But, in any case, you can set the parent of this to be the SandboxDistr, independently of whether or not the SimpleUimaAsService is in the module aggregation. Ok, it's right. I was in doubt so I did not add the parent. Then, you can delete all of the plugins in the build section :-) , and it will still build, nicely. There's some issue we'll need to dig through, though, because it pulls in a large number of jars related to activemq (I think), not all of which would need to be distributed. Yes, the large amount of jars is related to activemq; to avoid this we could set activemq scope to 'provided' or use the exclusion tag to import only wanted transitive dependencies. Note: this is not being released with our 2.3.0 release per previous discussions which indicated it needed to be documented first. -Marshall Tommaso
[jira] Resolved: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
[ https://issues.apache.org/jira/browse/UIMA-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1462. --- Resolution: Fixed tests pass, pom is simpler SimpleUimaAsService has checked in SimpleServer libraries as binaries - Key: UIMA-1462 URL: https://issues.apache.org/jira/browse/UIMA-1462 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleUimaAsService Affects Versions: 2.2.2S, 2.3S Reporter: Thilo Goetz Assignee: Tommaso Teofili Fix For: 2.3S Attachments: patch1462.txt, patch1462b1.txt, patch1462b2.txt, patch1462c1.txt, patch1462c2.txt, simpleServerDistributionPatch.txt, simpleUimaAsServicePatch.txt For the upcoming release, this should be changed so it depends on the SimpleServer project directly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
[ https://issues.apache.org/jira/browse/UIMA-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili reopened UIMA-1462: --- some plugins useful for licensing purposes were wrongly removed from pom SimpleUimaAsService has checked in SimpleServer libraries as binaries - Key: UIMA-1462 URL: https://issues.apache.org/jira/browse/UIMA-1462 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleUimaAsService Affects Versions: 2.2.2S, 2.3S Reporter: Thilo Goetz Assignee: Tommaso Teofili Fix For: 2.3S Attachments: patch1462.txt, patch1462b1.txt, patch1462b2.txt, patch1462c1.txt, patch1462c2.txt, simpleServerDistributionPatch.txt, simpleUimaAsServicePatch.txt For the upcoming release, this should be changed so it depends on the SimpleServer project directly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1462) SimpleUimaAsService has checked in SimpleServer libraries as binaries
[ https://issues.apache.org/jira/browse/UIMA-1462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1462. --- Resolution: Fixed Plugins section in POM is now correct. Can we now delete the /lib directory (with its binary jars) in the project root? SimpleUimaAsService has checked in SimpleServer libraries as binaries - Key: UIMA-1462 URL: https://issues.apache.org/jira/browse/UIMA-1462 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleUimaAsService Affects Versions: 2.2.2S, 2.3S Reporter: Thilo Goetz Assignee: Tommaso Teofili Fix For: 2.3S Attachments: patch1462.txt, patch1462b1.txt, patch1462b2.txt, patch1462c1.txt, patch1462c2.txt, simpleServerDistributionPatch.txt, simpleUimaAsServicePatch.txt For the upcoming release, this should be changed so it depends on the SimpleServer project directly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1581) RegularExpressionAnnotator tests fail
[ https://issues.apache.org/jira/browse/UIMA-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12760420#action_12760420 ] Tommaso Teofili commented on UIMA-1581: --- The files generated in tests differ in two fields: * testFeature6 expected testFeature6=2343.34 but found actual 234334.0 * testFeature7 expected testFeature7=2.4 but found actual 24.0 So far I could not manage to find the reason for such a strange behaviour RegularExpressionAnnotator tests fail - Key: UIMA-1581 URL: https://issues.apache.org/jira/browse/UIMA-1581 Project: UIMA Issue Type: Bug Components: Sandbox-RegexAnnotator Affects Versions: 2.3S Environment: MacOS X Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: 2.3 the following TestSetFeatureValues tests fail: * testSetFeatureValues1 * testSetFeatureValues2 * testSetFeatureValues3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Maybe unneeded file in Snowball Annotator?
I'm for deleting both (partially) void install.xml in SnowballAnnotator and Tagger and add PearPackaging dependency to Snowball.Tommaso 2009/9/24 Marshall Schor m...@schor.com I found in the Tagger project, another one of these. This one is partially filled out, but it doesn't seem to be used by the maven pear packaging plugin. That plugin generated a different install.xml - the generated one had the following differences (other is the partially filled out one, not the generated one): * The OS Name was Windows XP, not Windows * The JDK_VERSION was 1.6.0_16 (yes, I know, I need to go back to 1.5 ...), the other was 1.4.0 * The classpath just had the uima-an-tagger.jar; the resources were put on the datapath. The other had both the jar and the resources on the classpath, and didn't have the datapath set. It seems to me that this partially filled out install.xml file can be deleted - what do you think? -Marshall Marshall Schor wrote: There's a file in metadata/install.xml - looks like a default/empty PEAR Install file: ?xml version=1.0 encoding=UTF-8? COMPONENT_INSTALLATION_DESCRIPTOR OS /OS TOOLKITS /TOOLKITS UIMA_FRAMEWORK /UIMA_FRAMEWORK SUBMITTED_COMPONENT /SUBMITTED_COMPONENT INSTALLATION /INSTALLATION /COMPONENT_INSTALLATION_DESCRIPTOR Can I delete it? or should this annotator include pear packaging (it currently doesn't..., but I could easily add it)? -Marshall
Re: SimpleServer special assembly
the specific assembly for SimpleServer was added to make a distribution jar when you run 'mvn package', containg /lib jars too (actually only uima-simple-server-xbean-1.0.jar). Tommaso 2009/9/22 Marshall Schor m...@schor.com The SimpleServer project is the only sandbox project with its own assembly, which is done in addition to the Sandbox assembly. It produces one bin-style assembly, and packages it as a Jar. This Jar has * the class files * a lib directory containing embedded Jars - one for the simple server, and one for the special generated uima-simple-server-xbean-1.0 jar. * META-INF dir having the LIC/NOT/DIS files plus the MANIFEST. * a samples dir (in the Jar because it's in src/resources) * a SimpleServerConfig.xsd file (in the Jar because it's in src/resources) Should we keep this additional assembly? I guess it seems a bit confusing to have one of the projects have an additional assembly, but perhaps it's being used by others, and should therefore be kept. I would lean toward removing this, if it won't break users... -Marshall
Re: SimpleServer dependencies on 3rd party jars
It's ok for me. Did your tests work using the patch supplied in http://issues.apache.org/jira/browse/UIMA-1582 ? On my environment (MacOsX with Maven 2.2.1) SimpleServer tests work only with that patch. Cheers, Tommaso 2009/9/22 Marshall Schor m...@schor.com I went through these, and change the dependencies as follows: 1) org.apache.xmlbeans:xmlbeans changed to 2.4.0 (was 2.3.0) - several other projects are using 2.4.0, and I thought it best to stay consistent :-) 2)javax.xml.bind:jsr173_api commented out. Instead, the xmlbeans transitively pulls in stax:stax-api 1.0.1. This is the same as several other sandbox projects using xmlbeans. 3) changed the other dependencies for things which were not included in the lib/ previously, to scopeprovided/scope - this puts these in the compile-time classpath, but they are excluded from the jars that the dependency plugin pulls into the lib/ that will be distributed. Is this OK? (it does build, run the tests, etc.). -Marshall
Re: xmlbeans use of either stax or jsr173_api jars
Hi Marshall,I tried to remove jsr173 dependency from SimpleServer and DictionaryAnnotator and used Xmlbeans 2.4.0 version. Tests and packaging behave properly (/lib directory had not been removed in SimpleServer since I was waiting for the issue to be closed, but it should be deleted as soon as Maven way is definitely chosen). StAX ( http://stax.codehaus.org/Home ) is under Apache License 2.0 so it's ok from the licensing point of view, we should only investigate if we like this JSR173 specification implementation or we would like to choose another one. In my opinion it is ok (no more dependencies needed). Tommaso 2009/9/21 Marshall Schor m...@schor.com Several sandbox projects have dependencies on xmlbeans (e.g. RegularExpressionAnnotator, SimpleServer, and ConfigurableFeatureExtractor). The first 2 have obtained xmlbeans from http://xmlbeans.apache.org (as evidenced by their NOTICE). They have copied (some of) the Jar files that come from this into their lib/ directories (xbean.jar, jsr173_1.0_api.jar). The maven repo entry http://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/2.4.0/xmlbeans-2.4.0.pom lists a dependency dependency groupIdstax/groupId artifactIdstax-api/artifactId version1.0.1/version /dependency In the maven repository, this is listed as an Apache-licensed Jar, and I have read on the web (must be right :-) ) that this is a substitute which could be used instead of the jsr173_1.0_api. If I switch things in the Sandbox to obtain jar parts that are dependencies from the Maven repo system, instead of taking them from our lib/ directories, this change will result in having the above 2 projects get the xbean jar (as before) at version 2.4.0 and the stax_api jar version 1.0.1 instead of the jsr173_1.0_api. Is this OK? -Marshall (who is quite confused by the existence of all these alternative ways of putting parts together...)
[jira] Created: (UIMA-1581) RegularExpressionAnnotator tests fail
RegularExpressionAnnotator tests fail - Key: UIMA-1581 URL: https://issues.apache.org/jira/browse/UIMA-1581 Project: UIMA Issue Type: Bug Components: Sandbox-RegexAnnotator Affects Versions: 2.3S Environment: MacOS X Reporter: Tommaso Teofili Assignee: Tommaso Teofili Fix For: 2.3 the following TestSetFeatureValues tests fail: * testSetFeatureValues1 * testSetFeatureValues2 * testSetFeatureValues3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1582) SimpleServer ConfigTest fails
[ https://issues.apache.org/jira/browse/UIMA-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated UIMA-1582: -- Attachment: 1582patch.txt cutting off the starting carriage return from expected make tests pass, as it should (files differ only of that /r). SimpleServer ConfigTest fails - Key: UIMA-1582 URL: https://issues.apache.org/jira/browse/UIMA-1582 Project: UIMA Issue Type: Bug Components: Sandbox-SimpleServer Affects Versions: 2.3S Environment: MacOS X Reporter: Tommaso Teofili Fix For: 2.3 Attachments: 1582patch.txt testResultGeneration1 to testResultGeneration10 fail due to a wrong starting carriage return in the expected String used to compare against the actual result; actual.equals(expected) fails for standoff (not inlined configuration XML). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: xmlbeans use of either stax or jsr173_api jars
for SimpleServer the patch supplied in https://issues.apache.org/jira/browse/UIMA-1582 fix the tests (if you can give it a try, in order to make sure this is not an environment dependent issue).for RegexAnnotator I opened https://issues.apache.org/jira/browse/UIMA-1581 Changing the discussed dependencies does not affect tests. Tommaso 2009/9/22 Thilo Goetz twgo...@gmx.de Tommaso Teofili wrote: Hi Marshall,I tried to remove jsr173 dependency from SimpleServer and DictionaryAnnotator and used Xmlbeans 2.4.0 version. Tests and packaging behave properly (/lib directory had not been removed in SimpleServer since I was waiting for the issue to be closed, but it should be deleted as soon as Maven way is definitely chosen). StAX ( http://stax.codehaus.org/Home ) is under Apache License 2.0 so it's ok from the licensing point of view, we should only investigate if we like this JSR173 specification implementation or we would like to choose another one. In my opinion it is ok (no more dependencies needed). If the test cases go through, it's safe to switch and I'm all for it (speaking for SimpleServer and RegexAnnotator). --Thilo Tommaso 2009/9/21 Marshall Schor m...@schor.com Several sandbox projects have dependencies on xmlbeans (e.g. RegularExpressionAnnotator, SimpleServer, and ConfigurableFeatureExtractor). The first 2 have obtained xmlbeans from http://xmlbeans.apache.org (as evidenced by their NOTICE). They have copied (some of) the Jar files that come from this into their lib/ directories (xbean.jar, jsr173_1.0_api.jar). The maven repo entry http://repo1.maven.org/maven2/org/apache/xmlbeans/xmlbeans/2.4.0/xmlbeans-2.4.0.pom lists a dependency dependency groupIdstax/groupId artifactIdstax-api/artifactId version1.0.1/version /dependency In the maven repository, this is listed as an Apache-licensed Jar, and I have read on the web (must be right :-) ) that this is a substitute which could be used instead of the jsr173_1.0_api. If I switch things in the Sandbox to obtain jar parts that are dependencies from the Maven repo system, instead of taking them from our lib/ directories, this change will result in having the above 2 projects get the xbean jar (as before) at version 2.4.0 and the stax_api jar version 1.0.1 instead of the jsr173_1.0_api. Is this OK? -Marshall (who is quite confused by the existence of all these alternative ways of putting parts together...)
Re: A common approach to sandbox projects distribution of 3rd party jars
Hi Marshall,
I mostly agree with you for putting binaries into lib dir from SVN for the
release because we would like the checkout/compile phase to be as easy and
quick as possible.
Though it could be somehow annoying I think it would be nice in the near
future (after the release) to leave those binaries out and use long time
stable artifact versions from the central Maven repository where possible.
Tommaso
2009/9/20 Marshall Schor m...@schor.com
I'm going through our build process for the Sandbox Distribution, and
consolidating/unifying many aspects of it (not yet checked in - still a
work in progress).
One area I've examined: Many sandbox projects rely on and redistribute
3rd party Jars (that are Apache licensed, or are otherwise OK to
distribute).
All (I think) of these Jars are dependencies (in the Maven system) that
maven can automatically download from its repositories, to the .m2 local
repo.
Many sandbox projects put these Jars into the project's lib/ directory.
Some sandbox projects check in these Jars into SVN, and build their
distributions by copying their lib/ dir to the distribution; others use
the maven dependency plugin to get these jars into the local repository
(if not already there) and then copy that into the distribution.
After thinking about this for a while, and considering both methods, I
think the most reliable way to handle 3rd party Jars is to manually put
them into the lib/ directory, once, and then check the lib/ directory
into SVN. This avoids build issues in the future which could occur if
the Jar obtained from the maven dependency plugin is somehow corrupted,
or changes level, etc. Also, having the Jars in SVN insures that
whatever work we do to update the LICENSE/NOTICE files for those Jars
remains valid (because the Jar doesn't (potentially) change).
Examples of project copying Jars into its lib/ dir manually:
BSFAnnotator
DictionaryAnnotator
RegularExpressionAnnotator
SimpleServer
Examples of project using the maven dependency plugin:
ConfigurableFeatureExtractor (work in progress, pom doing this not yet
checked in)
Lucas
So, unless there are strong objections, I'm going to be changing the
sandbox build to consistently do the following:
- for 3rd party dependencies - expect the Jars to be manually put in
the lib/ dir and checked into SVN
- put the lib/ into the bin distribution
- if a pear is being built, put the lib/ into the pear
- not automatically populate the lib/ using the maven dependency
plugin mechanism
- change the maven descriptors for these dependencies, where needed,
to scopesystem/scope indicating these jars are in the lib/, and add
the systemPaht element.
This places a small burden on the developers when creating a new project
to obtain the needed 3rd party Jars once and put them in the lib/ dir.
One way to do this is to initially code the maven 3rd party Jar
dependencies with no scope (defaulting thereby to compile) and let
maven get these Jars from searching its repositories. Then, copy them
from the .m2 local repository to the lib/ dir, and change the scope to
system, and set systemPath${basedir}/lib/.jar/systemPath.
-Marshall
Re: Making sandbox documentation available on our website
I think that's a very nice idea. +1 2009/9/21 Marshall Schor m...@schor.com I plan to make a modification to the web-site to host all the sandbox documentation, similar to how we host the base UIMA documentation. Any objections? In preparation for this I'll be updating the builds for the sandbox documentation to update a directory in the uima-website project. I plan to add a directory named uima-website/docs/downloads/next-release/sandbox/artifactId. After the release is approved, we can move the stuff in next-release to the current place: uima-website/docs/downloads/sandbox/artifactId. The website will only host the current release. People wanting older ones, can always download the distribution. -Marshall
[jira] Updated: (UIMA-1500) Deprecate UIMA 1.x classes in org.apache.uima.analysis_engine.annotator
[ https://issues.apache.org/jira/browse/UIMA-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated UIMA-1500: -- Attachment: uima1500_1patch.txt Based on Marshall advice I modified the comments to suggest which class to use. i.e.: @deprecated As of release 2.3.0, use UimaContext instead Deprecate UIMA 1.x classes in org.apache.uima.analysis_engine.annotator --- Key: UIMA-1500 URL: https://issues.apache.org/jira/browse/UIMA-1500 Project: UIMA Issue Type: Improvement Components: Core Java Framework Reporter: Jörn Kottmann Fix For: 2.3 Attachments: uima1500_1patch.txt, uima1500patch.txt The mentioned package contains 1.x classes and interfaces, which have a comment which suggest using 2.0 API. These classes and interfaces should be deprecated, namely these are: Annotator_ImplBase.java AnnotatorContext.java AnnotatorContext.java GenericAnnotator_ImplBase.java GenericAnnotator.java JTextAnnotator_ImplBase.java JTextAnnotator.java TextAnnotator.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1500) Deprecate UIMA 1.x classes in org.apache.uima.analysis_engine.annotator
[ https://issues.apache.org/jira/browse/UIMA-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved UIMA-1500. --- Resolution: Fixed Assignee: Tommaso Teofili patch applied Deprecate UIMA 1.x classes in org.apache.uima.analysis_engine.annotator --- Key: UIMA-1500 URL: https://issues.apache.org/jira/browse/UIMA-1500 Project: UIMA Issue Type: Improvement Components: Core Java Framework Reporter: Jörn Kottmann Assignee: Tommaso Teofili Fix For: 2.3 Attachments: uima1500_1patch.txt, uima1500patch.txt The mentioned package contains 1.x classes and interfaces, which have a comment which suggest using 2.0 API. These classes and interfaces should be deprecated, namely these are: Annotator_ImplBase.java AnnotatorContext.java AnnotatorContext.java GenericAnnotator_ImplBase.java GenericAnnotator.java JTextAnnotator_ImplBase.java JTextAnnotator.java TextAnnotator.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-961) Cleanup - remove unused things
[ https://issues.apache.org/jira/browse/UIMA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754553#action_12754553 ] Tommaso Teofili commented on UIMA-961: -- As I can't find CapabilityContainer and assemblies have been refactored, can we close this one? Cleanup - remove unused things -- Key: UIMA-961 URL: https://issues.apache.org/jira/browse/UIMA-961 Project: UIMA Issue Type: Improvement Components: Build, Packaging and Test, Core Java Framework Reporter: Marshall Schor Priority: Trivial Clean up by removing: CapabilityContainer class - no longer used, Assemblies for producing Eclipse plugins - no longer used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-39) superiterator (an iterator that returns all annotations that span a specified annotation)
[ https://issues.apache.org/jira/browse/UIMA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12754554#action_12754554 ] Tommaso Teofili commented on UIMA-39: - maybe we can dever this past 2.3.0? superiterator (an iterator that returns all annotations that span a specified annotation) - Key: UIMA-39 URL: https://issues.apache.org/jira/browse/UIMA-39 Project: UIMA Issue Type: New Feature Components: Core Java Framework Reporter: Adam Lally Priority: Minor We've had this feature request from internal users and from an external user on the alphaWorks forum: http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13880014cat=28thread=138315treeDisplayType=threadmode1forum=444#13880014 The basic requirement is to find all annotations of a particular type whose span encompasses a specified annotation. For example: find the paragraph that spans this sentence. Or, find all NamedEntities that span this Token. We've discussed with users the idea of an AnnotationIndex.superiterator() method, and they seem to like that idea. This would be a complement to subiterator(). superiterator(xyz) would return annotations that covered annotation xyz. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1500) Deprecate UIMA 1.x classes in org.apache.uima.analysis_engine.annotator
[ https://issues.apache.org/jira/browse/UIMA-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated UIMA-1500: -- Attachment: uima1500patch.txt I made a patch to fix this: I added @deprecated As of release 2.3.0, please use UIMA 2.x classes to the javadoc comment and the @Deprecated annotation for the classes you listed before Deprecate UIMA 1.x classes in org.apache.uima.analysis_engine.annotator --- Key: UIMA-1500 URL: https://issues.apache.org/jira/browse/UIMA-1500 Project: UIMA Issue Type: Improvement Components: Core Java Framework Reporter: Jörn Kottmann Fix For: 2.3 Attachments: uima1500patch.txt The mentioned package contains 1.x classes and interfaces, which have a comment which suggest using 2.0 API. These classes and interfaces should be deprecated, namely these are: Annotator_ImplBase.java AnnotatorContext.java AnnotatorContext.java GenericAnnotator_ImplBase.java GenericAnnotator.java JTextAnnotator_ImplBase.java JTextAnnotator.java TextAnnotator.java -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-510) JCasGen uses an older Java model for merging hand-coded code with generated code, which doesn't support Java beyond the 1.4 level.
[ https://issues.apache.org/jira/browse/UIMA-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12753126#action_12753126 ] Tommaso Teofili commented on UIMA-510: -- +1 JCasGen uses an older Java model for merging hand-coded code with generated code, which doesn't support Java beyond the 1.4 level. Key: UIMA-510 URL: https://issues.apache.org/jira/browse/UIMA-510 Project: UIMA Issue Type: Bug Components: Tools Affects Versions: 2.1, 2.2, 2.3 Reporter: Marshall Schor JCasGen has a merge functionality to merge user-written code in previous versions of the generated JCas cover classes, with regenerated versions of these cover classes, so as to preserve the user-written code (new code or modifications). The functionality is provided by EMF. EMF started issuing warning messages that the Java modelling package it uses, JDOM, was not updated for Java versions beyond Java 1.4. Because of this, running JCasGen gives the following message in the Eclipse Error Log: Using the JDOM API when the source compatibility is not set to '1.4' or lower can cause unpredictable results. The fix is to see if our use of EMF for this can be modified to use JDT's AST APIs instead. For EMF itself, there is a property for the Facade Helper Class in the GenModel that can be switched to org.eclipse.emf.codegen.merge.java.facade.ast.ASTFacadeHelper - this might be where to start looking. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
