I got a java.lang.NoClassDefFoundError: sun/awt/X11GraphicsEnvironment
running our test cases on a linux box. Turns out this is simply an
issue with the graphics libraries not being able to connect to the X
server. I have documented this issue on the wiki, for future reference:
http://cwiki.
Thilo Goetz wrote:
Marshall Schor wrote:
Running Findbugs, etc., will report on throws / catches that are
never used because the code in the try doesn't throw what is being
caught or propagated up.
It might be good to clean these up. Typically, they are not changed,
because that kind of a c
On 1/16/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Lev Kozakov wrote:
> So, should we just consider the XML encoding test not supported
> and return
> w/o a failure, if the returned 'encoding' string is 'null' ? The
> problem is
> that in the real case the PEAR installation may fail.
>
I s
Adam Lally wrote:
On 1/12/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Running Findbugs, etc., will report on throws / catches that are never
used because the code in the try doesn't throw what is being caught or
propagated up.
I'm not sure what you mean exactly - did you mean "because the c
Ok, I can reproduce the problem and found another one. For me it is not
possible to remove delegates in an aggregate. It is also not possible to
move one of these delegates to the Component Engine Flow section of the
window. .
-- Mirko
On 1/15/07, Mirko Jahn <[EMAIL PROTECTED] > wrote:
Ok, I w
On 1/17/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
I don't think you need to remove catch blocks from user code. If the
try/catch
is left in, then the user would get the warning that we're getting.
No, this is a different situation.
void someMethod() throw SomeException {
//Not a compile e
Marshall Schor wrote:
Thilo Goetz wrote:
Marshall Schor wrote:
Running Findbugs, etc., will report on throws / catches that are
never used because the code in the try doesn't throw what is being
caught or propagated up.
It might be good to clean these up. Typically, they are not changed,
b
On 1/17/07, Lev Kozakov <[EMAIL PROTECTED]> wrote:
Actually, we need to check both the Java version (java.version) and its
vendor (java.vendor), since IBM Java 1.4.x works fine with XML BOM. There is
no problem to skip the test, but real PEAR installation may fail, if one of
the descriptors conta
What testing beyond the unit tests will we do for this release?
Here are some items to consider:
1) "test" that all the Jira changes that would affect the documentation
have had the documentation updated
2) "Functional" testing, Installation verification testing (I think we
need a detailed lis
[
https://issues.apache.org/jira/browse/UIMA-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-10.
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
Refactoring complete. Assigning to Marsha
[
https://issues.apache.org/jira/browse/UIMA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally reopened UIMA-84:
Assignee: Marshall Schor
Mirko was able to reproduce the issue.
> CDE's "Find AE" Dialog does not work o
JMX Support has problems with AE names containing special characters (e.g.
commas)
--
Key: UIMA-199
URL: https://issues.apache.org/jira/browse/UIMA-199
Project: UIMA
[
https://issues.apache.org/jira/browse/UIMA-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-199.
---
Resolution: Fixed
> JMX Support has problems with AE names containing special characters (e.g.
> commas)
> ---
The UIMA technical committee over on OASIS had its first technical
meeting last week. Adam and I both attended. There was some
interesting discussion, things are getting off to a good start. If
you're interested, check out the meeting minutes in the documents area
of the UIMA TC page:
http:
On 1/16/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
I see this API was added to the CAS, but was not added to the JCas. Is
there a reason we would update the CAS API, and not do the corresponding
update in the JCas API?
What is JCas again?
(Other than, of course, that my suggested "refactor
On 1/17/07, Adam Lally <[EMAIL PROTECTED]> wrote:
On 1/17/07, Lev Kozakov <[EMAIL PROTECTED]> wrote:
> Actually, we need to check both the Java version (java.version) and its
> vendor (java.vendor), since IBM Java 1.4.x works fine with XML BOM.
There is
> no problem to skip the test, but real PE
Excessive releases of CAS on error in Aggregate CasMultiplier
-
Key: UIMA-200
URL: https://issues.apache.org/jira/browse/UIMA-200
Project: UIMA
Issue Type: Bug
Components:
On 1/17/07, Lev Kozakov <[EMAIL PROTECTED]> wrote:
I agree - documenting the limitation and workaround (using Xerces) is a good
idea.
I'll open a JIRA issue to update the documentation.
The 'isValidXmlFile' is used in PEAR installation to make sure the XML file
that requires 'adjustment/loca
[
https://issues.apache.org/jira/browse/UIMA-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-177.
---
Resolution: Fixed
JCas gen will issue warning messages when type merging that extends features
happens
[
https://issues.apache.org/jira/browse/UIMA-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-200.
---
Resolution: Fixed
> Excessive releases of CAS on error in Aggregate CasMultiplier
> ---
Document limitations of XML parser packaged with Sun Java 1.4
-
Key: UIMA-201
URL: https://issues.apache.org/jira/browse/UIMA-201
Project: UIMA
Issue Type: Task
Components
Somethings is likely amiss - any ideas?
Other data points:
When running this as part of mvn install - the test on the mac takes 57
seconds (pretty consistent)
When running this from eclipse, as a single test, on the mac, this takes
21 seconds( pretty consistent)
When running this from eclip
On 1/17/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
Somethings is likely amiss - any ideas?
Other data points:
When running this as part of mvn install - the test on the mac takes 57
seconds (pretty consistent)
When running this from eclipse, as a single test, on the mac, this takes
21 second
Maven does not allow resource (non-java) files under src/test/java (or
src/main/java for that matter). They must be under src/test/resources
(src/main/resources, respectively). Eclipse does not enforce this
restriction.
If you violate this restriction, unit tests may run in Eclipse but not Mave
I will test that on my intel mac as soon as I come home. Maybe there is a
difference between the PowerPC and the Intel architecture versions. As far
as I can remember, the mvn install took about 1:20 and mvn test something
less than a minute for all tests and projects (if that helps).
-- Mirko
O
[
https://issues.apache.org/jira/browse/UIMA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465586
]
Adam Lally commented on UIMA-198:
-
This is due to Maven bug http://jira.codehaus.org/browse/MSUREFIRE-148, which
has b
AnalysisEngineDescription.getDelegateAnalysisEngineSpecifiers() should only
resolve delegate imports, not other imports
---
Key: UIMA-202
URL: http
[
https://issues.apache.org/jira/browse/UIMA-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-202.
-
Resolution: Fixed
Assignee: Marshall Schor (was: Adam Lally)
> AnalysisEngineDescription.getDelegate
[
https://issues.apache.org/jira/browse/UIMA-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-45.
--
Resolution: Fixed
Significant cleanup has been done. Further items can be opened under separate
JIRA issues.
>
[
https://issues.apache.org/jira/browse/UIMA-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465605
]
Mirko Jahn commented on UIMA-198:
-
Make sense to me. The only problem in my case is that I tested this on a Mac
and th
Here are my results:
mvn test (dumping output in a logfile):
Running org.apache.uima.cas.test.SerializationReinitTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.863 sec
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.057 sec
Tests run: 3, Failures: 0, Err
31 matches
Mail list logo
