Marshall Schor wrote:
This is the October report.
Hmmm. seems I may have been wrong about this. The October report
predates this. So I'm not really sure what time period this report is
to cover.
Thilo - did you get any further info on what we're supposed to do about
these "reports"? Can
On 11/7/06, Adam Lally <[EMAIL PROTECTED]> wrote:
I think the GMail web client may have inserted newlines. Here's a try
via SMTP instead.
Well, that didn't appear to work either. You can tell that this has
extra newlines, for example here:
+++
uimaj-core/src/test/java/org/apache/uima/util/i
I think the GMail web client may have inserted newlines. Here's a try
via SMTP instead.
-Adam
Index: uimaj-core/pom.xml
===
--- uimaj-core/pom.xml(revision 470933)
+++ uimaj-core/pom.xml(working copy)
@@ -41,5 +41,14 @@
We have to get patches working in any case. Do attachments work?
That was the first thing I tried, but attachments don't seem to be
allowed on the list. Next I tried just pasting the patchfile contents
into an email, but Thilo reported getting errors when trying to apply
the patch. (When I th
We have to get patches working in any case. Do attachments work?
-Marshall
Thilo Goetz wrote:
Let's wait another day for your SVN accounts. uuencode really takes
me way back to the early 90s. I had no idea it still existed ;-) If
for some reason your SVN accounts fail to be set up tomorro
Adam Lally wrote:
One failure is a test that uses xi:include, which doesn't work in Java
1.5. I removed most of those from our tests but a couple are left.
Is it time to just remove this feature entirely? In addition to not
working in Java 1.5 (unless you separately install xalan.jar), it's
als
On 11/7/06, Michael Baessler <[EMAIL PROTECTED]> wrote:
+1 from my side, I also think that we can drop xi:include.
- Michael
I should probably clarify that my patch doesn't remove xi:include
support for UIMA; it only modifies the testcase to use import instead.
The actual removal can be done l
+1 from my side, I also think that we can drop xi:include.
- Michael
Thilo Goetz wrote:
+1
We have had for a long time now as our standard include
mechanism, let's just drop xi:include.
We also have one more test case failing with the IBM JDK 1.5 that I'm
working on, somehow other stuff k
One failure is a test that uses xi:include, which doesn't work in Java
1.5. I removed most of those from our tests but a couple are left.
Is it time to just remove this feature entirely? In addition to not
working in Java 1.5 (unless you separately install xalan.jar), it's
also not supported in
