Re: UIMA JMS
Eddie Epstein wrote: To support some advanced users of UIMA, we have been working on an alternative general scalability mechanism for UIMA analytics. Our goals were to provide a standards-based, much more flexible and powerful capability than that offered by the UIMA collection processing manager, with less software complexity. To this end we have developed an architecture based on asynchronous messaging technology conforming to the JMS standard, and from that built a small scalability extension for Apache UIMA, which we call UIMA JMS. The extension uses JMS and allows incorporating alternative JMS middleware implementations. The primary end-user interface to UIMA JMS is a new descriptor, the UIMA deployment descriptor. This descriptor references standard UIMA component descriptors, and adds the configuration information necessary to specify which annotators are to be replicated, where they will be deployed, how many threads to run concurrently, how error conditions are to be handled and several other details. Our initial implementation uses Apache's ActiveMQ for the JMS messaging middleware. We would like to explore donating this extension to the UIMA project, if this is acceptable to the community, and would appreciate any comments or feedback Sounds interesting, but do you have some more detailed information UIMA JMS? Maybe some user documentation or stuff like that? Is this only an addition to the current Apache UIMA implementation (only additional components) or do we have to modify the UIMA core projects to run UIMA JMS? -- Michael
[jira] Created: (UIMA-528) Add information on RASP4UIMA to external resources page
Add information on RASP4UIMA to external resources page --- Key: UIMA-528 URL: https://issues.apache.org/jira/browse/UIMA-528 Project: UIMA Issue Type: New Feature Components: Website Reporter: Thilo Goetz Assignee: Thilo Goetz Priority: Minor Also add a general sentence about updates to this part of our website. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-528) Add information on RASP4UIMA to external resources page
[ https://issues.apache.org/jira/browse/UIMA-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilo Goetz closed UIMA-528. Resolution: Fixed Add information on RASP4UIMA to external resources page --- Key: UIMA-528 URL: https://issues.apache.org/jira/browse/UIMA-528 Project: UIMA Issue Type: New Feature Components: Website Reporter: Thilo Goetz Assignee: Thilo Goetz Priority: Minor Also add a general sentence about updates to this part of our website. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-371) XMI serialization to UIMA C++
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: UIMA-371.patch The patch fixes the handling of FSList type features to be compatible with the Java XMI output and to support multiple references allowed attribute. XMI serialization to UIMA C++ - Key: UIMA-371 URL: https://issues.apache.org/jira/browse/UIMA-371 Project: UIMA Issue Type: New Feature Components: C++ Framework Reporter: Eddie Epstein Assignee: Eddie Epstein Fix For: 2.2C Attachments: UIMA-371.patch, uimacpp-xmi.patch, uimacpp_xmi.patch, uimacpp_xmi.zip, xmi_bytearray.patch In order to comply to the UIMA standard for CAS data, Bhavani Iyer has been working on XMI serialization support for UIMA C++. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: feature path evaluation
Michael Baessler wrote: Hi, does the UIMA framework has a method to evaluate a feature path as String value? -- Michael No response... does this mean, there is no such method or nobody have read this? -- Michael
Re: What is the expected behavior of type system merge for these cases?
OK. Am implementing tests and then the fixes :-) 2 more cases have come up: 1) One descriptor specifies multipleReferencesAllowed as false, the other omits this. The spec says omitting is the same as false. So this will be OK. 2) One descriptor specifies an element Range Type restriction, the other doesn't specify. I'm making this throw an exception, per the logic for #2 below in Thilo's note. -Marshall Adam Lally wrote: On 8/13/07, Marshall Schor [EMAIL PROTECTED] wrote: 1) Type Foo, feature Bar - range type FSArray whose element type is Baz Type Foo, feature Bar - range type FSArray whose element type is NotBaz (Should throw an exception?) 2) Type Foo, feature Bar - range type FSArray, whose element type is Baz Type Foo, feature Bar - range type FSArray whose element type is Subtype_of_Baz (Should be element Type = Subtype_of_Baz?) 3) Type Foo, feature Bar - range type FSArray with multipleReferencesAllowed = false Type Foo, feature Bar - range type FSArray with multipleReferencesAllowed = true (Should throw an exception?) I would vote for exceptions in all three cases (agreeing with Thilo's logic about #2). -Adam
Re: What is the expected behavior of type system merge for these cases?
Hi Marshall, Marshall Schor wrote: OK. Am implementing tests and then the fixes :-) please don't commit anything to trunk until we're done with this release. Else we might have to branch now, and I'd like to avoid that if we can. 2 more cases have come up: 1) One descriptor specifies multipleReferencesAllowed as false, the other omits this. The spec says omitting is the same as false. So this will be OK. 2) One descriptor specifies an element Range Type restriction, the other doesn't specify. I'm making this throw an exception, per the logic for #2 below in Thilo's note. Not specifying a component type restriction is the same as specifying uima.cas.TOP. -Marshall Adam Lally wrote: On 8/13/07, Marshall Schor [EMAIL PROTECTED] wrote: 1) Type Foo, feature Bar - range type FSArray whose element type is Baz Type Foo, feature Bar - range type FSArray whose element type is NotBaz (Should throw an exception?) 2) Type Foo, feature Bar - range type FSArray, whose element type is Baz Type Foo, feature Bar - range type FSArray whose element type is Subtype_of_Baz (Should be element Type = Subtype_of_Baz?) 3) Type Foo, feature Bar - range type FSArray with multipleReferencesAllowed = false Type Foo, feature Bar - range type FSArray with multipleReferencesAllowed = true (Should throw an exception?) I would vote for exceptions in all three cases (agreeing with Thilo's logic about #2). -Adam
[jira] Updated: (UIMA-526) Cas Editor: Add a new Edit View for editing of FS
[ https://issues.apache.org/jira/browse/UIMA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörn Kottmann updated UIMA-526: --- Attachment: UIMA-526.patch Please apply the patch. Cas Editor: Add a new Edit View for editing of FS - Key: UIMA-526 URL: https://issues.apache.org/jira/browse/UIMA-526 Project: UIMA Issue Type: Improvement Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann Attachments: UIMA-526.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-526) Cas Editor: Add a new Edit View for editing of FS
[
https://issues.apache.org/jira/browse/UIMA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520032
]
Thilo Goetz commented on UIMA-526:
--
Applying this patch gives rise to the following compiler errors. Am I doing
something wrong at my end?
This is from mvn clean install
[INFO] Scanning for projects...
[INFO]
[INFO] Building UIMA CAS Editor
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory C:\code\ApacheUIMA\CasEditor\target
[INFO] Deleting directory C:\code\ApacheUIMA\CasEditor\target\classes
[INFO] Deleting directory C:\code\ApacheUIMA\CasEditor\target\test-classes
[INFO] [antrun:run {execution: CleanLicenseNoticeDisclaimer}]
[INFO] Executing tasks
[delete] Deleting directory
C:\code\ApacheUIMA\CasEditor\src\main\resources\META-INF
[delete] C:\code\ApacheUIMA\CasEditor\src\main\resources\META-INF not found.
[INFO] Executed tasks
[INFO] [antrun:run {execution: CopyLicenseNoticeDisclaimer}]
[INFO] Executing tasks
[copy] Copying 3 files to
C:\code\ApacheUIMA\CasEditor\src\main\resources\META-INF
[INFO] Executed tasks
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 155 source files to C:\code\ApacheUIMA\CasEditor\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\ValueColumnLabelProvider.java:[25,33]
cannot find symbol
symbol : class CellLabelProvider
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\ValueColumnLabelProvider.java:[26,33]
cannot find symbol
symbol : class ViewerCell
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\ValueColumnLabelProvider.java:[28,45]
cannot find symbol
symbol: class CellLabelProvider
final class ValueColumnLabelProvider extends CellLabelProvider {
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\ValueColumnLabelProvider.java:[30,21]
cannot find symbol
symbol : class ViewerCell
location: class
org.apache.uima.caseditor.editor.editview.ValueColumnLabelProvider
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\FeatureColumnLabelProvider.java:[25,33]
cannot find symbol
symbol : class CellLabelProvider
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\FeatureColumnLabelProvider.java:[26,33]
cannot find symbol
symbol : class ViewerCell
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\FeatureColumnLabelProvider.java:[28,47]
cannot find symbol
symbol: class CellLabelProvider
final class FeatureColumnLabelProvider extends CellLabelProvider {
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\FeatureColumnLabelProvider.java:[30,21]
cannot find symbol
symbol : class ViewerCell
location: class
org.apache.uima.caseditor.editor.editview.FeatureColumnLabelProvider
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\EditViewPage.java:[50,33]
cannot find symbol
symbol : class ColumnViewer
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\EditViewPage.java:[51,33]
cannot find symbol
symbol : class EditingSupport
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\EditViewPage.java:[56,33]
cannot find symbol
symbol : class TreeViewerColumn
location: package org.eclipse.jface.viewers
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\EditViewPage.java:[93,50]
cannot find symbol
symbol : class EditingSupport
location: class org.apache.uima.caseditor.editor.editview.EditViewPage
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\EditViewPage.java:[94,32]
cannot find symbol
symbol : class ColumnViewer
location: class
org.apache.uima.caseditor.editor.editview.EditViewPage.ValueEditingSupport
C:\code\ApacheUIMA\CasEditor\src\main\java\org\apache\uima\caseditor\editor\editview\ValueColumnLabelProvider.java:[29,3]
method does not override a method from its superclass
Re: feature path evaluation
On 8/15/07, Michael Baessler [EMAIL PROTECTED] wrote: Michael Baessler wrote: Hi, does the UIMA framework has a method to evaluate a feature path as String value? -- Michael No response... does this mean, there is no such method or nobody have read this? I didn't respond because I do not know the answer. -Adam
[jira] Created: (UIMA-529) Type System Merging not checking for compatible element types, nor compatible multipleReferencesAllowed settings
Type System Merging not checking for compatible element types, nor compatible multipleReferencesAllowed settings Key: UIMA-529 URL: https://issues.apache.org/jira/browse/UIMA-529 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.1, 2.2 Reporter: Marshall Schor Assignee: Marshall Schor Priority: Trivial Fix For: 2.3 When merging two identically named types, the feature merge for identically named features needs to check that the element type (for arrays and lists) is specified the same, and the setting of the multipleReferencesAllowed is the same. See thread in uima-dev: http://thread.gmane.org/gmane.comp.apache.uima.devel/1260 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-526) Cas Editor: Add a new Edit View for editing of FS
[ https://issues.apache.org/jira/browse/UIMA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520045 ] Jörn Kottmann commented on UIMA-526: Hi Thilo, the edit view uses eclipse 3.3 api. I did forget to update the pom.xml for eclipse 3.3 dependencies. I think its less work if you change to dependencies from eclipse 3.2.0 to eclipse 3.3.0 by yourself, but I can also attach another patch for it. Jörn Cas Editor: Add a new Edit View for editing of FS - Key: UIMA-526 URL: https://issues.apache.org/jira/browse/UIMA-526 Project: UIMA Issue Type: Improvement Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann Attachments: UIMA-526.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: feature path evaluation
Michael Baessler wrote: Michael Baessler wrote: Hi, does the UIMA framework has a method to evaluate a feature path as String value? -- Michael No response... does this mean, there is no such method or nobody have read this? I missed reading this message... By feature path - do you mean instances of the type org.apache.uima.cas.FeaturePath? If so, I think there is no toString method for this. Since it's just a string a feature names, a toString method would need to concatenate these with some separator character, I guess. -Marshall
[jira] Resolved: (UIMA-529) Type System Merging not checking for compatible element types, nor compatible multipleReferencesAllowed settings
[ https://issues.apache.org/jira/browse/UIMA-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-529. - Resolution: Fixed Type System Merging not checking for compatible element types, nor compatible multipleReferencesAllowed settings Key: UIMA-529 URL: https://issues.apache.org/jira/browse/UIMA-529 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.1, 2.2 Reporter: Marshall Schor Assignee: Marshall Schor Priority: Trivial Fix For: 2.3 When merging two identically named types, the feature merge for identically named features needs to check that the element type (for arrays and lists) is specified the same, and the setting of the multipleReferencesAllowed is the same. See thread in uima-dev: http://thread.gmane.org/gmane.comp.apache.uima.devel/1260 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: What is the expected behavior of type system merge for these cases?
Thilo Goetz wrote: Hi Marshall, Marshall Schor wrote: OK. Am implementing tests and then the fixes :-) please don't commit anything to trunk until we're done with this release. Else we might have to branch now, and I'd like to avoid that if we can. oops - sorry - didn't see this note, until after I had committed. For these kinds of things, best to send an instant message :-)... 2 more cases have come up: 1) One descriptor specifies multipleReferencesAllowed as false, the other omits this. The spec says omitting is the same as false. So this will be OK. 2) One descriptor specifies an element Range Type restriction, the other doesn't specify. I'm making this throw an exception, per the logic for #2 below in Thilo's note. Not specifying a component type restriction is the same as specifying uima.cas.TOP. OK - I guess this will need to be added to the test - to allow no type restriction to match one which specifies explicitly uima.cas.TOP. I'll re-open the Jira issue. -Marshall
Re: [VOTE] Release uimaj-2.2.0-RC8 as uimaj-2.2.0-incubating
I think all the committers have voted +1... Can we declare the vote closed and go to the incubator at this point? -Marshall Thilo Goetz wrote: We've had a few days to do regression testing on this level, and nothing new has come up. The release artifacts are available on people.a.o at /home/twgoetz/uima-distributions/2.2/RC8 So please cast your vote: [ ] +1 Release RC8 as uimaj-2.2.0-incubating, it's ready [ ] -1 Don't release yet, I found issues --Thilo
Re: What is the expected behavior of type system merge for these cases?
Marshall Schor wrote: Thilo Goetz wrote: Hi Marshall, Marshall Schor wrote: OK. Am implementing tests and then the fixes :-) please don't commit anything to trunk until we're done with this release. Else we might have to branch now, and I'd like to avoid that if we can. oops - sorry - didn't see this note, until after I had committed. For these kinds of things, best to send an instant message :-)... Oh well, we'll have to figure out how to proceed then. I'll have to catch up on some SVN docs to see about branching. It seems highly unlikely that our release candidate will just pass the incubator PMC ;-) --Thilo
Re: [jira] Commented: (UIMA-526) Cas Editor: Add a new Edit View for editing of FS
Jörn Kottmann (JIRA) wrote: [ https://issues.apache.org/jira/browse/UIMA-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520045 ] Jörn Kottmann commented on UIMA-526: Hi Thilo, the edit view uses eclipse 3.3 api. I did forget to update the pom.xml for eclipse 3.3 dependencies. I think its less work if you change to dependencies from eclipse 3.2.0 to eclipse 3.3.0 by yourself, but I can also attach another patch for it. No, don't worry, I hoped it would be something simple like that but couldn't figure it out ;-) I'll take care of it tomorrow morning. --Thilo Jörn Cas Editor: Add a new Edit View for editing of FS - Key: UIMA-526 URL: https://issues.apache.org/jira/browse/UIMA-526 Project: UIMA Issue Type: Improvement Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann Attachments: UIMA-526.patch
[jira] Reopened: (UIMA-529) Type System Merging not checking for compatible element types, nor compatible multipleReferencesAllowed settings
[ https://issues.apache.org/jira/browse/UIMA-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor reopened UIMA-529: - For merging element types, no specification and a specification of uima.cas.TOP should be allowed as equal Type System Merging not checking for compatible element types, nor compatible multipleReferencesAllowed settings Key: UIMA-529 URL: https://issues.apache.org/jira/browse/UIMA-529 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects Versions: 2.1, 2.2 Reporter: Marshall Schor Assignee: Marshall Schor Priority: Trivial Fix For: 2.3 When merging two identically named types, the feature merge for identically named features needs to check that the element type (for arrays and lists) is specified the same, and the setting of the multipleReferencesAllowed is the same. See thread in uima-dev: http://thread.gmane.org/gmane.comp.apache.uima.devel/1260 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release uimaj-2.2.0-RC8 as uimaj-2.2.0-incubating
Marshall Schor wrote: I think all the committers have voted +1... Can we declare the vote closed and go to the incubator at this point? -Marshall Thilo Goetz wrote: We've had a few days to do regression testing on this level, and nothing new has come up. The release artifacts are available on people.a.o at /home/twgoetz/uima-distributions/2.2/RC8 So please cast your vote: [ ] +1 Release RC8 as uimaj-2.2.0-incubating, it's ready [ ] -1 Don't release yet, I found issues --Thilo Let's give it the usual 72 hours. --Thilo
Re: continuous integration
Saw another post (may be outdated) that said Continuum didn't handle flat Maven structures, only the nested ones - and we're using the flat approach I think. -Marshall (hoping to get to continuous integration at some point :-) Marshall Schor wrote: More info: Several posts on maven-user on the topic is continuum dead suggest another alternative, https://hudson.dev.java.net/ and another says here's a matrix of various tools: http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matrix -Marshall (hoping that at some point, we'll get to continuous integration... ) Marshall Schor wrote: If and when we decide that continuous integration is the way to go, Atlassian, the folks who did Jira and Confluence Wiki (which we're using) also have a continuous integration product, called Bamboo. Several Apache projects are using it, here: http://opensource.bamboo.atlassian.com/ -Marshall
Re: continuous integration
Hi Marshall, a few weeks ago I tested cruisecontrol with the uima project and it worked with our maven project structure. Maybe you would like to take a look at it. Jörn On Aug 15, 2007, at 9:01 PM, Marshall Schor wrote: Saw another post (may be outdated) that said Continuum didn't handle flat Maven structures, only the nested ones - and we're using the flat approach I think. -Marshall (hoping to get to continuous integration at some point :-) Marshall Schor wrote: More info: Several posts on maven-user on the topic is continuum dead suggest another alternative, https://hudson.dev.java.net/ and another says here's a matrix of various tools: http://docs.codehaus.org/display/DAMAGECONTROL/Continuous +Integration+Server+Feature+Matrix -Marshall (hoping that at some point, we'll get to continuous integration... ) Marshall Schor wrote: If and when we decide that continuous integration is the way to go, Atlassian, the folks who did Jira and Confluence Wiki (which we're using) also have a continuous integration product, called Bamboo. Several Apache projects are using it, here: http:// opensource.bamboo.atlassian.com/ -Marshall
Re: UIMA JMS
The documentation for this has been posted to the Apache UIMA wiki. You can navigate there by clicking on the wiki link of http://incubator.apache.org/uima and then on the Documentation link, and then on the Documentation for Asynchronous Scaleout enablement of Apache UIMA http://cwiki.apache.org/UIMA/uimaasdoc.html link (if you don't see it, please hit refresh in your browser). -Marshall Marshall Schor wrote: Michael Baessler wrote: Eddie Epstein wrote: To support some advanced users of UIMA, we have been working on an alternative general scalability mechanism for UIMA analytics. Our goals were to provide a standards-based, much more flexible and powerful capability than that offered by the UIMA collection processing manager, with less software complexity. To this end we have developed an architecture based on asynchronous messaging technology conforming to the JMS standard, and from that built a small scalability extension for Apache UIMA, which we call UIMA JMS. The extension uses JMS and allows incorporating alternative JMS middleware implementations. The primary end-user interface to UIMA JMS is a new descriptor, the UIMA deployment descriptor. This descriptor references standard UIMA component descriptors, and adds the configuration information necessary to specify which annotators are to be replicated, where they will be deployed, how many threads to run concurrently, how error conditions are to be handled and several other details. Our initial implementation uses Apache's ActiveMQ for the JMS messaging middleware. We would like to explore donating this extension to the UIMA project, if this is acceptable to the community, and would appreciate any comments or feedback Sounds interesting, but do you have some more detailed information UIMA JMS? Maybe some user documentation or stuff like that? Good idea. We're working through how to make this available - we have have a PDF doc which is a start; we might be able to post, perhaps as an attachment to the UIMA wiki. We're working on more documentation, including more tutorial information. Is this only an addition to the current Apache UIMA implementation (only additional components) or do we have to modify the UIMA core projects to run UIMA JMS? It is only an addition - no modification needed to the UIMA core. -- Michael
Re: What is the expected behavior of type system merge for these cases?
Thilo Goetz wrote: Marshall Schor wrote: Thilo Goetz wrote: Hi Marshall, Marshall Schor wrote: OK. Am implementing tests and then the fixes :-) please don't commit anything to trunk until we're done with this release. Else we might have to branch now, and I'd like to avoid that if we can. oops - sorry - didn't see this note, until after I had committed. For these kinds of things, best to send an instant message :-)... Oh well, we'll have to figure out how to proceed then. I'll have to catch up on some SVN docs to see about branching. It seems highly unlikely that our release candidate will just pass the incubator PMC ;-) --Thilo I think there also were other (previous) SVN updates done prior to my last one - for instance, updating the Docs re: threadsafe issues for shared resource impls. I did branching when I did my hot fix for 2.1, as I recall. So it can't be too hard ;-) -Marshall
Re: continuous integration
Jörn Kottmann wrote: Hi Marshall, a few weeks ago I tested cruisecontrol with the uima project and it worked with our maven project structure. Maybe you would like to take a look at it. Great, thanks. I'm still trying to get a sense of the communities. I found this: http://www.chris-read.net/?p=13 comparing CruiseControl version 2.6 (now at 2.7), bamboo 1.0 (it's now at 1.2.2), and teamCity 1.2 (now at 2.1). See also http://xooctory.xoocode.org/ - it's another CI open source project whose team works on other Apache projects. It has a section on comparison about 1/2 down the page. A quick look at Apache projects - I could only find one that was using CI (Harmony). Still don't have any definite opinions, myself... -Marshall Jörn On Aug 15, 2007, at 9:01 PM, Marshall Schor wrote: Saw another post (may be outdated) that said Continuum didn't handle flat Maven structures, only the nested ones - and we're using the flat approach I think. -Marshall (hoping to get to continuous integration at some point :-) Marshall Schor wrote: More info: Several posts on maven-user on the topic is continuum dead suggest another alternative, https://hudson.dev.java.net/ and another says here's a matrix of various tools: http://docs.codehaus.org/display/DAMAGECONTROL/Continuous+Integration+Server+Feature+Matrix -Marshall (hoping that at some point, we'll get to continuous integration... ) Marshall Schor wrote: If and when we decide that continuous integration is the way to go, Atlassian, the folks who did Jira and Confluence Wiki (which we're using) also have a continuous integration product, called Bamboo. Several Apache projects are using it, here: http://opensource.bamboo.atlassian.com/ -Marshall
[jira] Created: (UIMA-530) Cas Editor: The Annotation Editor throws sometimes exceptions if used as FS drag source
Cas Editor: The Annotation Editor throws sometimes exceptions if used as FS drag source --- Key: UIMA-530 URL: https://issues.apache.org/jira/browse/UIMA-530 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-531) Cas Editor: Delete button of the FSView does not work correctly
Cas Editor: Delete button of the FSView does not work correctly --- Key: UIMA-531 URL: https://issues.apache.org/jira/browse/UIMA-531 Project: UIMA Issue Type: Bug Components: Sandbox Reporter: Jörn Kottmann Assignee: Jörn Kottmann The button only works for Annotation but not for FeatureStructures. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
