[jira] Commented: (UIMA-387) XMI Serializer can write invalid control characters

2007-05-04 Thread Adam Lally (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493672 ] Adam Lally commented on UIMA-387: - >We should make sure we don't generate XMI that we can't read back in. It's >better

Re: UIMA pear runtime

2007-05-04 Thread Michael Baessler
Adam Lally wrote: On 5/2/07, Michael Baessler <[EMAIL PROTECTED]> wrote: After doing most of the UIMA pear runtime work... I would like to suggest something else that came to my mind when implementing the pear runtime. Currently we work with a customResourceSpecifier. I would like to change tha

Re: UIMA pear runtime

2007-05-04 Thread Adam Lally
On 5/4/07, Michael Baessler <[EMAIL PROTECTED]> wrote: OK I implemented the following pearSpecifier resource: http://uima.apache.org/resourceSpecifier";> InstalledPear /home/test/WhitespaceTokenizer The resourceType is the type of the pear archive we use. So maybe in the future we can

[jira] Reopened: (UIMA-371) XMI serialization to UIMA C++

2007-05-04 Thread Eddie Epstein (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eddie Epstein reopened UIMA-371: Further testing by Bhavani has found an incompatibilty with Java: byte arrays should be base64 encoded.

Re: UIMA pear runtime

2007-05-04 Thread Michael Baessler
Adam Lally wrote: On 5/4/07, Michael Baessler <[EMAIL PROTECTED]> wrote: OK I implemented the following pearSpecifier resource: http://uima.apache.org/resourceSpecifier";> InstalledPear /home/test/WhitespaceTokenizer The resourceType is the type of the pear archive we use. So maybe i

[jira] Updated: (UIMA-371) XMI serialization to UIMA C++

2007-05-04 Thread Bhavani Iyer (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-371: -- Attachment: xmi_bytearray.patch Fixed xmi serialization of byte array to handle signed values. Added som

[jira] Commented: (UIMA-387) XMI Serializer can write invalid control characters

2007-05-04 Thread Adam Lally (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493732 ] Adam Lally commented on UIMA-387: - > If the type is Byte Array, then it is serialized as Base64 Sorry, that was wrong.

[jira] Commented: (UIMA-371) XMI serialization to UIMA C++

2007-05-04 Thread Adam Lally (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493733 ] Adam Lally commented on UIMA-371: - >Further testing by Bhavani has found an incompatibilty with Java: byte arrays >sho

[jira] Updated: (UIMA-392) Eclipse Plugin packaging not working correctly

2007-05-04 Thread Adam Lally (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Lally updated UIMA-392: Environment: Maven 2.0.6 The build works in Maven v2.0.4, but fails in Maven v2.0.6. It looks like the prob

[jira] Created: (UIMA-395) TypeSystemMgr.addFeature should default multipleReferencesAllowed argument to false.

2007-05-04 Thread Adam Lally (JIRA)
TypeSystemMgr.addFeature should default multipleReferencesAllowed argument to false. Key: UIMA-395 URL: https://issues.apache.org/jira/browse/UIMA-395 Project: UIMA

[jira] Created: (UIMA-396) Javadoc for Feature.isMultipleReferencesAllowed is incorrect

2007-05-04 Thread Adam Lally (JIRA)
Javadoc for Feature.isMultipleReferencesAllowed is incorrect Key: UIMA-396 URL: https://issues.apache.org/jira/browse/UIMA-396 Project: UIMA Issue Type: Bug Components: C

[jira] Resolved: (UIMA-396) Javadoc for Feature.isMultipleReferencesAllowed is incorrect

2007-05-04 Thread Adam Lally (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Lally resolved UIMA-396. - Resolution: Fixed > Javadoc for Feature.isMultipleReferencesAllowed is incorrect >

[jira] Created: (UIMA-397) JSR47Logger_implTest failing with Sun Java 6

2007-05-04 Thread Marshall Schor (JIRA)
JSR47Logger_implTest failing with Sun Java 6 Key: UIMA-397 URL: https://issues.apache.org/jira/browse/UIMA-397 Project: UIMA Issue Type: Bug Components: Core Java Framework Affects V

collecting download statistics

2007-05-04 Thread Marshall Schor
It is apparently quite easy to collect download statistics, indirectly, setting up our download page to count clicks on the download link. There is a currently "free" service from google which will do the work for you, and also measure paths from search engines (not just theirs) to your site,

Re: [jira] Updated: (UIMA-371) XMI serialization to UIMA C++

2007-05-04 Thread Thilo Goetz
Two of the five patches attached to this issue do not have the "ASF Granted License" flag set. Could you please change that before we apply the patch? I'm not sure this can be done after the fact, maybe you'll need to re-attach the patch (delete and create again). --Thilo Bhavani Iyer (JIRA

Re: [jira] Updated: (UIMA-392) Eclipse Plugin packaging not working correctly

2007-05-04 Thread Thilo Goetz
I don't know about everybody else, but I'm really sorry I voted for the adoption of Maven when we moved to Apache. It seemed like the thing to do at the time, but I have come to regret it. I have no good understanding of how our build works, and the Maven documentation is terrible. If I had

[jira] Commented: (UIMA-395) TypeSystemMgr.addFeature should default multipleReferencesAllowed argument to false.

2007-05-04 Thread Thilo Goetz (JIRA)
[ https://issues.apache.org/jira/browse/UIMA-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493806 ] Thilo Goetz commented on UIMA-395: -- I find the fact that such XMI weirdnesses are intruding into our Java APIs distur