The resolution was submitted, following the Apache change PMC Chair process;
it's on the agenda for the next Board meeting scheduled for November 18th.
Cheers. -Marshall
On 10/29/2020 2:47 PM, Marshall Schor wrote:
> Thank you all for your wonderful comments (blush!).
>
> I feel with t
Thank you all for your wonderful comments (blush!).
I feel with the recent activity picking up under Richard's initiative that UIMA
is in good hands.
Based on this consensus, I'll draft the appropriate resolution for the next
board meeting.
-Marshall
On 10/18/2020 10:19 AM, Marshall Schor
Hi everyone,
After a decade of serving as the UIMA Project's PMC Chairperson, I've decided to
step down as the UIMA PMC chair, as soon as we can reach a consensus on a new
chairperson.
I have found being the chairperson of this project and working with the
community on it, to be extremely
Nice! -Marshall
On 10/1/2020 4:17 AM, Richard Eckart de Castilho (Jira) wrote:
>
> [
> https://issues.apache.org/jira/browse/UIMA-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Richard Eckart de Castilho mentioned you on UIMA-6267
>
I think you're quite possibly right, as the original design didn't contemplate
the use case of lots of classloaders being dynamically created.
Do you have an example of that kind of use case?
-Marshall
On 9/30/2020 4:18 AM, Richard Eckart de Castilho wrote:
> Hi,
>
> while looking into
The UIMA framework is intended to support this kind of analysis.
The Apache UIMA project doesn't have any video analytics, itself, but you may
find some by googling uima and video analysis.
One such reference I found was this:
I believe that one or both of these was the default for the predecessor of
uima-as, Collection Processing Engine (CPE / CPM). See for example,
http://uima.apache.org/d/uimaj-current/references.html#ugr.ref.xml.cpe_descriptor.descriptor.operational_parameters
and notice the cpeConfig param
deprecation is fine. dropping with some kind of feature toggle, where it could
be restored if it turns out some people are using it, would be best...
-Marshall
On 9/15/2020 1:42 PM, Richard Eckart de Castilho (Jira) wrote:
> Richard Eckart de Castilho created UIMA-6265:
>
Here's the board report, a few hours past the deadline (got busy doing
other things)
Board report for Apache UIMA, for September 2020.
## Description:
Apache UIMA's mission: the creation and maintenance of open-source software
related to the analysis of unstructured data, guided by the UIMA
Hi,
Please reply with any items that should get into this report.
My sense is that with the Covid and Summer, things slowed down somewhat this
quarter.
* There was activity related to moving builds to a new infrastructure control,
mostly led by Richard (thank you again!).
* uima-as finally
Hi Peter,
In case you didn't see this, there's a deadline coming up in 1 week to have
Jenkins jobs migrated.
Are you working on this for Ruta?
-Marshall
On 7/22/2020 3:42 AM, Richard Eckart de Castilho wrote:
> Hi all,
>
> infra is setting up a new Jenkins infrastructure at
>
>
Jerry and Eddie - if you're not aware, there's a deadline in 1 week to get your
Jenkins builds migrated.
Can you focus on this?
-Marshall
On 7/22/2020 3:42 AM, Richard Eckart de Castilho wrote:
> Hi all,
>
> infra is setting up a new Jenkins infrastructure at
>
> https://ci-builds.apache.org
For those that missed it (like myself), the original note about this change is
on the bui...@apache.org mailing list,
which you can see here:
http://mail-archives.apache.org/mod_mbox/www-builds/202007.mbox/%3CCAN0Gg1dyFnWtD0sbmMJRvhQtZt1yXByv%3DgWW4d7N%2BZ5qvEEhdg%40mail.gmail.com%3E
(or just
nice, thanks! Any pointers to the big picture of what this change is about?
-Marshall
On 7/22/2020 3:42 AM, Richard Eckart de Castilho wrote:
> Hi all,
>
> infra is setting up a new Jenkins infrastructure at
>
> https://ci-builds.apache.org
>
> I have requested the creation of a folder for
[
https://issues.apache.org/jira/browse/UIMA-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17157800#comment-17157800
]
Marshall Schor commented on UIMA-6235:
--
I agree it's not a great approach, better approaches welcome
well, sorry, best intentions ... I haven't gotten around to doing this; may not
be able to get to it soon...
-Marshall
On 5/22/2020 10:40 AM, Marshall Schor wrote:
> ok, I'll do this... -M
>
> On 5/22/2020 11:08 AM, Richard Eckart de Castilho wrote:
>> On 20. May 2020, at 16:28,
[
https://issues.apache.org/jira/browse/UIMA-6235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156021#comment-17156021
]
Marshall Schor commented on UIMA-6235:
--
The background for this is described on our website here
good point.
Is there a Jira for doing this (yet)? Seems like we should do this first;
otherwise all projects inheriting from the new parent-pom will need to have
their own version of this script.
-Marshall
On 7/5/2020 11:55 AM, Richard Eckart de Castilho wrote:
> Do you want to release the
Looking at the history of the uima-wide parent-pom (it's at version
14-SNAPSHOT), it has 2 Jiras and an improvement to the rat configuration (to
print names of files with license issues).
The 2 Jiras (thanks to Richard :-) ) :
[UIMA-6184] Move code quality profiles to parent POM
* Formatting
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17148157#comment-17148157
]
Marshall Schor commented on UIMA-6243:
--
It may be possible to extend the way PEARs work to cover some
Marshall Schor created UIMA-6249:
Summary: remove sync contention in getJCasRegisteredType
Key: UIMA-6249
URL: https://issues.apache.org/jira/browse/UIMA-6249
Project: UIMA
Issue Type
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147731#comment-17147731
]
Marshall Schor commented on UIMA-6243:
--
Hi, getting the pear class path isolation to work in UIMA v3
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145773#comment-17145773
]
Marshall Schor commented on UIMA-6243:
--
I may have been using the wrong "version" of the 6
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145764#comment-17145764
]
Marshall Schor commented on UIMA-6243:
--
I see the same issue
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145763#comment-17145763
]
Marshall Schor commented on UIMA-6243:
--
It looks like the test case
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145735#comment-17145735
]
Marshall Schor commented on UIMA-6243:
--
on v3, failure happens
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17145727#comment-17145727
]
Marshall Schor commented on UIMA-6243:
--
Found the issue I think. I'm going to see how this works
[
https://issues.apache.org/jira/browse/UIMA-6248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144203#comment-17144203
]
Marshall Schor commented on UIMA-6248:
--
I also think this is not helpful / useful. It's also way
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141557#comment-17141557
]
Marshall Schor edited comment on UIMA-6243 at 6/24/20, 1:23 PM:
[~schor
[
https://issues.apache.org/jira/browse/UIMA-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141557#comment-17141557
]
Marshall Schor edited comment on UIMA-6243 at 6/24/20, 1:24 PM:
[~schor
yep, wrong ticket... sorry.
On 6/22/2020 2:36 AM, Peter Klügl (Jira) wrote:
> [
> https://issues.apache.org/jira/browse/UIMA-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141768#comment-17141768
> ]
>
> Peter Klügl commented on UIMA-6247:
>
[
https://issues.apache.org/jira/browse/UIMA-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17141501#comment-17141501
]
Marshall Schor commented on UIMA-6247:
--
Running this gave errors on all 3 test cases:
Caused
[
https://issues.apache.org/jira/browse/UIMA-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-6245.
--
Assignee: Marshall Schor
Resolution: Fixed
> CVD - Index out of bounds when expand
[
https://issues.apache.org/jira/browse/UIMA-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-6245:
-
Fix Version/s: 3.2.0SDK
> CVD - Index out of bounds when expanding Annotation in AnnotationIn
[
https://issues.apache.org/jira/browse/UIMA-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17140574#comment-17140574
]
Marshall Schor commented on UIMA-6245:
--
cleaned up with pull req #48, for general case. Discarding
[
https://issues.apache.org/jira/browse/UIMA-6245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17136568#comment-17136568
]
Marshall Schor commented on UIMA-6245:
--
thanks, will take a look.
> CVD - Index out of bounds w
Marshall Schor created UIMA-6244:
Summary: test case bug, running in windows
Key: UIMA-6244
URL: https://issues.apache.org/jira/browse/UIMA-6244
Project: UIMA
Issue Type: Bug
to be moderately active.
## Issues: No Board level issues at this time.
-Marshall Schor
Hard to believe, but another quarter has flown by...
Please reply with anything that should be included in the report.
I'll include 4 releases (2 for uimaFIT, 2 for Ruta), plus some updates on svn->
git:
uima-as (still underway) and ruta (done)
-Marshall
ok, I'll do this... -M
On 5/22/2020 11:08 AM, Richard Eckart de Castilho wrote:
> On 20. May 2020, at 16:28, Marshall Schor wrote:
>> If you have time, please redo this with this idea; if you don't have time, I
>> could probably get something done soonish... :-)
> I don't k
nice! and good to document the process :-) -Marshall
On 5/20/2020 4:51 AM, Richard Eckart de Castilho wrote:
> Hi,
>
>> On 20. May 2020, at 02:33, Marshall Schor wrote:
>>
>> How was this figured out? I had thought from reading the docs here
>> https://infr
Great idea!
I agree that configuring the location of the little groovy script needs fixing,
to work with multiple project layouts, and also think your idea of moving this
to a spot where other build artifacts exist, is a great idea!
That way, we can refer to it via a maven artifact reference.
I see from
https://github.com/apache/infrastructure-puppet/pull/1773/commits/6fcb902f7fc8ebf6d28c5bf68917244e77b29764
that it looks like Richard did a pull request for apache infrastructure-puppet
to add some redirects for the uima website's d/uimafit-2.* and d/uimafit-3.* and
d/ruta-2.* and
[
https://issues.apache.org/jira/browse/UIMA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17111398#comment-17111398
]
Marshall Schor commented on UIMA-6168:
--
There must be some use case I'm missing. This fix might
K with you to put this back?
-Marshall
On 5/19/2020 9:56 AM, Richard Eckart de Castilho wrote:
> On 19. May 2020, at 15:54, Marshall Schor wrote:
>> I see that the setting for the postAnalysisScript for japicmp was taken out
>> of
>> the uima-wide parent pom, and required to
having their own settings.
Am I missing something?
-Marshall
On 5/19/2020 9:56 AM, Richard Eckart de Castilho wrote:
> On 19. May 2020, at 15:54, Marshall Schor wrote:
>> I see that the setting for the postAnalysisScript for japicmp was taken out
>> of
>> the uima-wide par
I see that the setting for the postAnalysisScript for japicmp was taken out of
the uima-wide parent pom, and required to be in individual project parent poms.
What was the reason for this change?
-Marshall
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17109523#comment-17109523
]
Marshall Schor commented on UIMA-6228:
--
I think the idea is to have the redirect go from an older
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108297#comment-17108297
]
Marshall Schor commented on UIMA-6228:
--
redirects are possible. See:
[https://infra.apache.org
hopefully, we mostly use the -current form of urls (e.g. uimafit-current) rather
than specific versions...
I think it might be possible to set up http redirects for these, as well. Ideal
might be a redirect to a universal redirect page which lets the user know how to
get the older version of
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106671#comment-17106671
]
Marshall Schor commented on UIMA-6228:
--
uimaj 2.10.3 - keeping (don't remove) because it is a prereq
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106668#comment-17106668
]
Marshall Schor commented on UIMA-6228:
--
We ought to also look at the uima website, especially
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17106660#comment-17106660
]
Marshall Schor commented on UIMA-6228:
--
Poking the uima-as and ducc guys (mainly Jerry Cwiklik
ter for
aopalliance:aopalliance
some instances of "No NOTICE file was found - content not loaded into
property [postNoticeText]" e.g. uimafit-cpe
API Change Report: OK
asked about semantic version
IssuesFixed OK
README OK
spot check licenses OK
[x] +1 OK to release
- -M
perfect...
On 5/4/2020 1:07 PM, Richard Eckart de Castilho wrote:
> On 4. May 2020, at 19:00, Marshall Schor wrote:
>> It's marked unresolved / open. Is the version number wrong for 3.1.0?
> I was considering to cancel the vote and add this fix to 3.1.0, but then
> decided agains
issue UIMA-6226 https://issues.apache.org/jira/browse/UIMA-6226
is marked as belonging to 2.6.0 uima fit and ** uima 3.1.0 **.
It's marked unresolved / open. Is the version number wrong for 3.1.0?
-Marshall
I agree, makes sense :-) -Marshall
On 5/4/2020 12:41 PM, Richard Eckart de Castilho wrote:
> Hi,
>
>> On 4. May 2020, at 18:30, Marshall Schor wrote:
>>
>> API Change Report shows some "bindResource" methods were removed.
>>
>> Sometimes, rem
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17099113#comment-17099113
]
Marshall Schor commented on UIMA-6228:
--
You didn't miss anything :). That sounds fine. At next
API Change Report shows some "bindResource" methods were removed.
Sometimes, removing public methods users (may have) depended on implies
incrementing
the major component of the version.
I know there have been some iterations around fixing these methods, so it may be
fine to not increment the
while testing (with Java14) noticed these in the build-from-source (non are
blockers):
JCasUtilv3Test: some tests returning NaN or Infinity as speed-up-factor
JCasUtilv3Test: some test report < 1 speedup factor
groovy-maven-plugin: reports sometimes that
Javadoc warnings : missing
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17098966#comment-17098966
]
Marshall Schor commented on UIMA-6228:
--
Yes, the subsite needs to be rebuilt, with just the versions
good to ping, as I've been swamped with work... I'll try to get to this soon :-)
On 4/29/2020 6:39 AM, Richard Eckart de Castilho wrote:
>> On 19. Apr 2020, at 17:56, Richard Eckart de Castilho
>> wrote:
>>
>> I've posted the uimaFIT 3.1.0 release candidate 2.
> Ping? ;)
>
> -- Richard
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094543#comment-17094543
]
Marshall Schor commented on UIMA-6228:
--
No need to rebuild the composite site, unless you're changing
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093700#comment-17093700
]
Marshall Schor commented on UIMA-6228:
--
done for uimaj
> Please delete old releases from mirror
[
https://issues.apache.org/jira/browse/UIMA-6228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17093684#comment-17093684
]
Marshall Schor commented on UIMA-6228:
--
I'll do the uimaj maintenance. Can a main person for ducc
no, you are correct, I am mistaken (about the license). A (hopefully) temporary
confusion :-).
At some point, it might make sense to converge on just a single xmlunit
provider.
-Marshall
On 4/25/2020 3:19 PM, Richard Eckart de Castilho wrote:
> On 25. Apr 2020, at 21:16, Marshall Sc
While reviewing the changes, I see "xmlunit" dependency was added to
uimaj-parent pom.
This is used to compare xml outputs, I believe.
It looks like it has a license (a BSD form) which I think might require updating
all the licenses / (maybe notices) for both source and binary distr.
There are
on how to contribute using GIT PULL etc.,
and pointer to github repo in the readme :-)
[x] +1 OK to release
Marshall Schor
On 4/19/2020 11:53 AM, Richard Eckart de Castilho wrote:
> Hi,
>
> I've posted the uimaFIT 2.5.0 release candidate 2.
>
>
> uimaFIT 2.5.0 is a minor feature
[
https://issues.apache.org/jira/browse/UIMA-6225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090787#comment-17090787
]
Marshall Schor commented on UIMA-6225:
--
Hi, I'm guessing that the pear installer isn't designed
The current info on this is mainly in the Jira issue:
https://issues.apache.org/jira/browse/INFRA-19750
Some comments:
The existing git repo is incorrectly named (IMHO), because it doesn't follow the
conventions for all the others.
So, I think we can go ahead with creating a new git
The README has a section on "Modules".
It might be missing the entry for uimafit-benchmarks?
-Marshall
I see that uimafit-spring in the README is described as
experimental, and intentionally excluded from the binary.
-M
On 4/20/2020 1:43 PM, Marshall Schor wrote:
> along these same lines, I see the sources include
>
> uimafit-spring
> uimafit-legacy-support
> u
not a blocker, I think:
README says:
uimaFIT requires Java 1.8 or higher, UIMA 2.10.4 or higher,
but might want to say
uimaFIT requires Java 1.8 or higher, UIMA 2.10.4 or higher but less that UIMA
3.0.0,
(or figure out some better wording...) :-)
-Marshall
along these same lines, I see the sources include
uimafit-spring
uimafit-legacy-support
uimafit-examples
uimafit-benchmark
that are not in the binary distribution.
Should any of these be part of the binary?
-Marshall
On 4/20/2020 1:24 PM, Marshall Schor wrote:
> The REAME s
The REAME says:
For your convenience, the binary
distribution package of uimaFIT includes
all libraries necessary to use uimaFIT.
But the next sentence implies this isn't quite true:
In particular for novice users, it is strongly
advised to obtain a copy of the full UIMA
not a blocker:
[WARNING] Javadoc Warnings
[WARNING]
C:\au\t\uimaFIT\2.5.0\rc2\uimafit-2.5.0-bfs\uimafit-core\src\main\java\org\apache\uima\fit\internal\ResourceManagerFactory.java:55:
warning: no @param for resourceManagerCreator
[WARNING] public static synchronized void
This is probably ignorable:
When building for the 1st time from sources, my maven system downloaded from
central
both:
Downloaded from mirror-central: ...
org/codehaus/groovy/groovy-all/2.4.9/groovy-all-2.4.9.jar (7.0 MB at 482 kB/s)
Downloaded from mirror-central: ...
of getting out the
changes fixed so far, versus waiting to include even more fixes...
The announcement might include a note that the build works on Java 8, and has
some minor issues with Java 9+
-Marshall
On 4/18/2020 2:11 PM, Richard Eckart de Castilho wrote:
> On 18. Apr 2020, at 16:11, Marsh
This "fix" makes the test work:
1) add an import: import org.custommonkey.xmlunit.XMLUnit;
2) in front of the failing line ( XMLAssert.assertXMLEqual(expected, actual); )
add this line:
XMLUnit.setIgnoreWhitespace(true);
Cheers. -M
On 4/17/2020 5:18 PM, Marshall Schor wrot
Javadoc errors, when building with Oracle Java 14 in uimafit-core:
[ERROR] Exit code: 1 -
C:\au\t\uimaFIT\2.5.0\rc1\uimafit-2.5.0-bfs\uimafit-core\src\main\java\org\apache\uima\fit\internal\ResourceManagerFactory.java:55:
warning: no @param for resourceManagerCreator
[ERROR] public static
found the problem.
I was doing the build with Java 13.
Switched back to Java 8 and it worked.
In Java 13, the serialization has extra blank lines in the output.
Maybe there's a way to configure the XML compare utility to ignore this?
-Marshall
On 4/17/2020 4:24 PM, Marshall Schor wrote
this problem too went away when switching back to Java 8 from Java 13.
-Marshall
On 4/17/2020 4:18 PM, Marshall Schor wrote:
> Running the build-from-source, at an early phase it issued the messages:
>
> [INFO] --- gmaven-plugin:1.5:execute (read-notice) @ uimafit-parent ---
When doing build from sources, during the testing of the uimafit-core,
it got
[INFO] Running org.apache.uima.fit.factory.AnalysisEngineFactoryTest
Apr 17, 2020 4:13:04 PM PackageInstaller installPackage
INFO: Package installer message: [InstallationController]: extracting
Running the build-from-source, at an early phase it issued the messages:
[INFO] --- gmaven-plugin:1.5:execute (read-notice) @ uimafit-parent ---
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.codehaus.groovy.reflection.CachedClass$3$1
Hi, I'm working on this...
I noticed that the git checkout of the uimafit-2.5.0 tag has
Eclipse .settings files for the Java projects.
I think these are normally not checked into git?
Is this intentional?
-Marshall
2 to UIMA v3 user's guide refers to
the 3.0.0 version,
it should refer to
https://uima.apache.org/d/uimaj-current/version_3_users_guide.html
(and you could make it an kind of thing)
spot check maven artifacts: ok
spot check licenses/ notice: ok
[X] +1 OK to release
- - Marshall Schor
I'm willing to classify this as not a blocker.
UIMA V3 changed the logging setup - v2 used the built-into-java logger, v3 uses
slf4j, which adds
an indirection, which can use the built-in java logger, or integrate with
others.
The normal mechanism to control this is to include some jar that
The latest on moving to GIT is that you have to do most of this yourself.
See https://infra.apache.org/svn-to-git-migration.html
referenced from https://issues.apache.org/jira/browse/INFRA-19750 (scroll to
the last comment)
-Marshall
On 3/19/2020 12:16 PM, Richard Eckart de Castilho wrote:
>
[
https://issues.apache.org/jira/browse/UIMA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-6199.
--
Resolution: Fixed
> Unindexed document annotation added back to index during deserializat
[
https://issues.apache.org/jira/browse/UIMA-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084306#comment-17084306
]
Marshall Schor commented on UIMA-6215:
--
My guess is that the classpath for this project is set up
[
https://issues.apache.org/jira/browse/UIMA-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082556#comment-17082556
]
Marshall Schor commented on UIMA-6215:
--
OK, for now, the best thing is to un-install / remove UIMA
ls:all-tabpanel
> ]
>
> Richard Eckart de Castilho reassigned UIMA-6199:
>
>
> Assignee: Marshall Schor
>
>> Unindexed document annotation added bac
[
https://issues.apache.org/jira/browse/UIMA-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079967#comment-17079967
]
Marshall Schor commented on UIMA-6213:
--
I did the same. And I also did a plain Java project, just
[
https://issues.apache.org/jira/browse/UIMA-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079966#comment-17079966
]
Marshall Schor commented on UIMA-6215:
--
The tutorials are written for uima version 2. I suspect you
[
https://issues.apache.org/jira/browse/UIMA-6215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078849#comment-17078849
]
Marshall Schor commented on UIMA-6215:
--
Are you following the steps outlined here:
[http
...
-Marshall
On 4/8/2020 9:53 AM, Peter Klügl wrote:
> Cool, thank you Marshall!
>
> I know where I could look in ruta-ep-ide(-ui) :-)
>
> I'll open an issue.
>
>
> Best,
>
>
> Peter
>
> Am 08.04.2020 um 15:26 schrieb Marshall Schor:
>> I tried the follo
I tried the following:
1) in an environment with Java 13 installed, and Eclipse 4.15.0 (2020-03):
make a new Java project, with a main class that does System.out.println("here");
run it, and look at the launch configuration, it doesn't have the -p
C:\p\j\oracle13.0.2\lib\jrt-fs.jar
in the
ote:
> Hi,
>
> Am 06.04.2020 um 20:42 schrieb Marshall Schor:
>> Well, I wrote something incorrect, I think, re: the "signing" of the eclipse
>> update site jars.
>>
>> Our current process (when signing is to be done) is to not sign them when
>> vot
of modules.
Of course, that doesn't quite "fit", because the value of -p Eclipse puts in is
not a directory, but rather the jar.
-M
On 4/7/2020 4:26 PM, Marshall Schor wrote:
> Hi,
>
> I tried also importing the Example project, and then doing an eclipse Run on
> the
> Main s
Hi,
I tried also importing the Example project, and then doing an eclipse Run on the
Main script.
It ran in java 8, and got that famous error in Java 13:
java.lang.LayerInstantiationException: Package jdk.internal.jrtfs in both module
java.base and module jrt.fs
This was a completely
1 - 100 of 6178 matches
Mail list logo
