Re: Shooting oneself in the foot by merging master-v2 into master
Good advice. We should update the uima website GIT pages with the summary of these bits of wisdom :-) -Marshall On 1/30/2020 2:52 PM, Richard Eckart de Castilho wrote: > Hi, > > so you might remember that I have advertised that we make bugfixes in > master-v2 and then just merge master-v2 into master at regular intervals to > bring these fixes also into V3. > > Yesterday, I shot myself in the foot which this approach quite a bit... > > I fixed two issues in uimaFIT master-v2 and then set up a pull-request to > merge master-v2 into master. > > So far so good. Normally, I don't do this with a PR because I simply use my > admin permissions to locally merge the "maintenance" branch into the "master" > branch and then push master - but I can't do that on uimaFIT because master > is a protected branch requiring PRs and I don't have admin rights because > INFRA doesn't yield admin permissions on the ASF repos. > > ... anyway ... > > So I had a PR master-v2 -> master... but there was a small conflict between > the two branches that I had to resolve. > > I used the GitHub web interface to resolve the conflict - nice ;) > > BUT then I noticed that doing this caused GitHub to merge master into > master-v2 - now THAT shouldn't have happened. > > "Fortunately", master-v2 hadn't yet been protected when this happened, so I > deleted master-v2 and re-created it - I had just shortly before created it > anyway. > > But still, it had some side effects, e.g. that some PRs that were already > targeting master-v2 were auto-closed by GitHub and I had to re-create these > pull requests. > > So lesson learned is: > > NEVER EVER set up a PR from master-v2 to master > (or from any protected branch to any other protected branch for that matter) > > ... even if that's what you would like to do - better create a new branch off > master-v2 (e.g. "sync-master-v2-with-master") and then do a PR with that one. > > Cheers, > > -- Richard
[jira] [Updated] (UIMA-6183) NullPointerException in RutaLiteralMatcher.java:72
[
https://issues.apache.org/jira/browse/UIMA-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Waitelonis updated UIMA-6183:
--
Description:
For some of the following rule/document examples a NullPointerException is
thrown in RutaLiteralMatcher.java:72:
RUTA Script:
DECLARE Anno;
"W"{->MARK(Anno)};
Document content to reproduce:
-> working
-> not working (NPE thrown)
working
-> not working (NPE thrown)
The NPE is thrown in line 72 of RutaLiteralMatcher.java:
71: RutaBasic beginAnchor = stream.getBeginAnchor(begin);
72: if (beginAnchor.getEnd() == end) {
(beginAnchor is null)
was:
For some of the following rule/document examples a NullPointerException is
thrown in RutaLiteralMatcher.java:72:
RUTA Script:
DECLARE Anno;
"W"{->MARK(Anno)};
Document content to reproduce:
-> working
-> not working (NPE thrown)
working
-> not working (NPE thrown)
The NPE is thrown in line 72 of RutaLiteralMatcher.java:
RutaBasic beginAnchor = stream.getBeginAnchor(begin);
> NullPointerException in RutaLiteralMatcher.java:72
> ---
>
> Key: UIMA-6183
> URL: https://issues.apache.org/jira/browse/UIMA-6183
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
> Environment: UIMA Rute 2.8.0 workbench in fresh installation of
> Eclipse IDE for Enterprise Java Developers. (Version: 2019-12 (4.14.0) Build
> id: 20191212-1212) on MacOS 10.12.6
>Reporter: Jörg Waitelonis
>Priority: Major
>
> For some of the following rule/document examples a NullPointerException is
> thrown in RutaLiteralMatcher.java:72:
> RUTA Script:
> DECLARE Anno;
> "W"{->MARK(Anno)};
> Document content to reproduce:
> -> working
> -> not working (NPE thrown)
> working
> -> not working (NPE thrown)
> The NPE is thrown in line 72 of RutaLiteralMatcher.java:
> 71: RutaBasic beginAnchor = stream.getBeginAnchor(begin);
> 72: if (beginAnchor.getEnd() == end) {
> (beginAnchor is null)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6183) NullPointerException in RutaLiteralMatcher.java:72
[
https://issues.apache.org/jira/browse/UIMA-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Waitelonis updated UIMA-6183:
--
Description:
For some of the following rule/document examples a NullPointerException is
thrown in RutaLiteralMatcher.java:72:
RUTA Script:
DECLARE Anno;
"W"{->MARK(Anno)};
Document content to reproduce:
-> working
-> not working (NPE thrown)
working
-> not working (NPE thrown)
The NPE is thrown in line 72 of RutaLiteralMatcher.java:
RutaBasic beginAnchor = stream.getBeginAnchor(begin);
was:
For some of the following rule/document examples a NullPointerException is
thrown in RutaLiteralMatcher.java:72:
RUTA Script:
DECLARE Anno;
"W"{->MARK(Anno)};
Document content to reproduce:
-> working
-> not working (NPE thrown)
working
-> not working (NPE thrown)
The NPE is thrown in line 72 of RutaLiteralMatcher.java:
RutaBasic beginAnchor = stream.getBeginAnchor(begin);
('beginAnchor' is null)
> NullPointerException in RutaLiteralMatcher.java:72
> ---
>
> Key: UIMA-6183
> URL: https://issues.apache.org/jira/browse/UIMA-6183
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
>Affects Versions: 2.8.0ruta
> Environment: UIMA Rute 2.8.0 workbench in fresh installation of
> Eclipse IDE for Enterprise Java Developers. (Version: 2019-12 (4.14.0) Build
> id: 20191212-1212) on MacOS 10.12.6
>Reporter: Jörg Waitelonis
>Priority: Major
>
> For some of the following rule/document examples a NullPointerException is
> thrown in RutaLiteralMatcher.java:72:
> RUTA Script:
> DECLARE Anno;
> "W"{->MARK(Anno)};
> Document content to reproduce:
> -> working
> -> not working (NPE thrown)
> working
> -> not working (NPE thrown)
> The NPE is thrown in line 72 of RutaLiteralMatcher.java:
> RutaBasic beginAnchor = stream.getBeginAnchor(begin);
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (UIMA-6181) Fix complaints about maven-plugin-plugin in Eclipse
[ https://issues.apache.org/jira/browse/UIMA-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6181: - Fix Version/s: (was: parent-pom-13) parent-pom-14 > Fix complaints about maven-plugin-plugin in Eclipse > --- > > Key: UIMA-6181 > URL: https://issues.apache.org/jira/browse/UIMA-6181 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 2.10.5SDK, 3.2.0SDK, parent-pom-14 > > > When importing the UIMAJ code into Eclipse, m2e complains about the > maven-plugin-plugin not being covered by its lifecycle management. > Add a profile with activates for m2e builds and which tells Eclipse m2e to > ignore the maven-plugin-plugin goals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (UIMA-6183) NullPointerException in RutaLiteralMatcher.java:72
Jörg Waitelonis created UIMA-6183:
-
Summary: NullPointerException in RutaLiteralMatcher.java:72
Key: UIMA-6183
URL: https://issues.apache.org/jira/browse/UIMA-6183
Project: UIMA
Issue Type: Bug
Components: Ruta
Affects Versions: 2.8.0ruta
Environment: UIMA Rute 2.8.0 workbench in fresh installation of
Eclipse IDE for Enterprise Java Developers. (Version: 2019-12 (4.14.0) Build
id: 20191212-1212) on MacOS 10.12.6
Reporter: Jörg Waitelonis
For some of the following rule/document examples a NullPointerException is
thrown in RutaLiteralMatcher.java:72:
RUTA Script:
DECLARE Anno;
"W"{->MARK(Anno)};
Document content to reproduce:
-> working
-> not working (NPE thrown)
working
-> not working (NPE thrown)
The NPE is thrown in line 72 of RutaLiteralMatcher.java:
RutaBasic beginAnchor = stream.getBeginAnchor(begin);
('beginAnchor' is null)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (UIMA-6180) Exclude plugins from m2e builds
[ https://issues.apache.org/jira/browse/UIMA-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho resolved UIMA-6180. -- Resolution: Fixed > Exclude plugins from m2e builds > --- > > Key: UIMA-6180 > URL: https://issues.apache.org/jira/browse/UIMA-6180 > Project: UIMA > Issue Type: Improvement > Components: uimaFIT, uimaFIT-Maven-Plugin >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 2.5.0uimaFIT, 3.0.1uimaFIT > > Time Spent: 20m > Remaining Estimate: 0h > > Exclude the gmaven-plugin and the maven-plugin-plugin executions from m2e > builds. This silences warnings about no m2e connectors for these plugins when > importing into a fresh Eclipse. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6181) Fix complaints about maven-plugin-plugin in Eclipse
[ https://issues.apache.org/jira/browse/UIMA-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026996#comment-17026996 ] Richard Eckart de Castilho commented on UIMA-6181: -- Changes added to parent-pom. > Fix complaints about maven-plugin-plugin in Eclipse > --- > > Key: UIMA-6181 > URL: https://issues.apache.org/jira/browse/UIMA-6181 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: parent-pom-13, 2.10.5SDK, 3.2.0SDK > > > When importing the UIMAJ code into Eclipse, m2e complains about the > maven-plugin-plugin not being covered by its lifecycle management. > Add a profile with activates for m2e builds and which tells Eclipse m2e to > ignore the maven-plugin-plugin goals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6181) Fix complaints about maven-plugin-plugin in Eclipse
[ https://issues.apache.org/jira/browse/UIMA-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Eckart de Castilho updated UIMA-6181: - Fix Version/s: parent-pom-13 > Fix complaints about maven-plugin-plugin in Eclipse > --- > > Key: UIMA-6181 > URL: https://issues.apache.org/jira/browse/UIMA-6181 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: parent-pom-13, 2.10.5SDK, 3.2.0SDK > > > When importing the UIMAJ code into Eclipse, m2e complains about the > maven-plugin-plugin not being covered by its lifecycle management. > Add a profile with activates for m2e builds and which tells Eclipse m2e to > ignore the maven-plugin-plugin goals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (UIMA-6181) Fix complaints about maven-plugin-plugin in Eclipse
[ https://issues.apache.org/jira/browse/UIMA-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026983#comment-17026983 ] Marshall Schor edited comment on UIMA-6181 at 1/30/20 8:44 PM: --- It's already in the general UIMA parent-pom, so changes should be made there, and the copies in uimaj: master (v3) should be removed (once the uima-wide pom has been updated / released.) was (Author: schor): It's already in the general UIMA parent-pom, so changes should be made there. > Fix complaints about maven-plugin-plugin in Eclipse > --- > > Key: UIMA-6181 > URL: https://issues.apache.org/jira/browse/UIMA-6181 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 2.10.5SDK, 3.2.0SDK > > > When importing the UIMAJ code into Eclipse, m2e complains about the > maven-plugin-plugin not being covered by its lifecycle management. > Add a profile with activates for m2e builds and which tells Eclipse m2e to > ignore the maven-plugin-plugin goals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-6181) Fix complaints about maven-plugin-plugin in Eclipse
[ https://issues.apache.org/jira/browse/UIMA-6181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026983#comment-17026983 ] Marshall Schor commented on UIMA-6181: -- It's already in the general UIMA parent-pom, so changes should be made there. > Fix complaints about maven-plugin-plugin in Eclipse > --- > > Key: UIMA-6181 > URL: https://issues.apache.org/jira/browse/UIMA-6181 > Project: UIMA > Issue Type: Improvement >Reporter: Richard Eckart de Castilho >Assignee: Richard Eckart de Castilho >Priority: Minor > Fix For: 2.10.5SDK, 3.2.0SDK > > > When importing the UIMAJ code into Eclipse, m2e complains about the > maven-plugin-plugin not being covered by its lifecycle management. > Add a profile with activates for m2e builds and which tells Eclipse m2e to > ignore the maven-plugin-plugin goals. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Shooting oneself in the foot by merging master-v2 into master
Hi, so you might remember that I have advertised that we make bugfixes in master-v2 and then just merge master-v2 into master at regular intervals to bring these fixes also into V3. Yesterday, I shot myself in the foot which this approach quite a bit... I fixed two issues in uimaFIT master-v2 and then set up a pull-request to merge master-v2 into master. So far so good. Normally, I don't do this with a PR because I simply use my admin permissions to locally merge the "maintenance" branch into the "master" branch and then push master - but I can't do that on uimaFIT because master is a protected branch requiring PRs and I don't have admin rights because INFRA doesn't yield admin permissions on the ASF repos. ... anyway ... So I had a PR master-v2 -> master... but there was a small conflict between the two branches that I had to resolve. I used the GitHub web interface to resolve the conflict - nice ;) BUT then I noticed that doing this caused GitHub to merge master into master-v2 - now THAT shouldn't have happened. "Fortunately", master-v2 hadn't yet been protected when this happened, so I deleted master-v2 and re-created it - I had just shortly before created it anyway. But still, it had some side effects, e.g. that some PRs that were already targeting master-v2 were auto-closed by GitHub and I had to re-create these pull requests. So lesson learned is: NEVER EVER set up a PR from master-v2 to master (or from any protected branch to any other protected branch for that matter) ... even if that's what you would like to do - better create a new branch off master-v2 (e.g. "sync-master-v2-with-master") and then do a PR with that one. Cheers, -- Richard
[jira] [Updated] (UIMA-2311) wrong or no svn:eol-style set on many files in uimacpp
[ https://issues.apache.org/jira/browse/UIMA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-2311: - Fix Version/s: 3.0.0C > wrong or no svn:eol-style set on many files in uimacpp > -- > > Key: UIMA-2311 > URL: https://issues.apache.org/jira/browse/UIMA-2311 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework >Reporter: Marshall Schor >Assignee: Edward Epstein >Priority: Minor > Fix For: 3.0.0C > > > Files that developers edit with text editors are usually marked with the svn > property svn:eol-style native. This insures that when they are checked out, > the line endings are converted to the client's style of line endings, and > when changes are checked in, the line endings are normalized, so that lines > which are not changed don't appear in the diff. > Without this, we have seen cases where a file is stored with some line ending > in SVN, checked out onto a machine with different default line endings, > edited and saved (causing the line-endings to be changed to that machine's > default style), and then committed. The commit shows as if every line has > been changed, whereas the real change might have been just a few lines. This > makes for difficult reviewing of the commits, of course. > I found many examples in the uimacpp project where the svn:eol-style is > missing, or where it was set to LF (which might be alright, but native is > probably safer). > Committers: It is highly recommended that you can set up your SVN to > automatically tag "new" files with the right svn:eol-style, by following the > instructions here: http://www.apache.org/dev/svn-eol-style.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-4899) UIMACPP access violation in destroyJNI()
[
https://issues.apache.org/jira/browse/UIMA-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Epstein updated UIMA-4899:
-
Fix Version/s: 3.0.0C
> UIMACPP access violation in destroyJNI()
>
>
> Key: UIMA-4899
> URL: https://issues.apache.org/jira/browse/UIMA-4899
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
>Affects Versions: 2.8.1SDK
> Environment: Windows 10 64bit
>Reporter: Benjamin De Boe
>Assignee: Edward Epstein
>Priority: Major
> Fix For: 3.0.0C
>
>
> When running a bunch of threads accessing separate AE instances of the
> UIMACPP DaveDetector in JNI mode, the process crashes with an access
> violation on the call to "delete pInstance" in destructorJNI in jni/jni.cpp.
> The code below should allow you to reproduce the issue and takes three
> command-line arguments:
> 1: the full path to DaveDescriptor.xml
> 2: whether to use simple threads ("n") or separate processes ("y")
> 3: (optional, default 20) size of the CAS pool to use, which we found out has
> an impact in reproducing the issue.
> /*
> * To change this license header, choose License Headers in Project
> Properties.
> * To change this template file, choose Tools | Templates
> * and open the template in the editor.
> */
> package com.intersys.uima.test;
> import java.io.File;
> import java.net.URL;
> import java.net.URLClassLoader;
> import org.apache.uima.UIMAFramework;
> import org.apache.uima.analysis_engine.AnalysisEngine;
> import org.apache.uima.cas.CAS;
> import org.apache.uima.resource.ResourceSpecifier;
> import org.apache.uima.util.CasCreationUtils;
> import org.apache.uima.util.CasPool;
> import org.apache.uima.util.Level;
> import org.apache.uima.util.XMLInputSource;
> /**
> *
> * @author bdeboe
> */
> public class Standalone implements Runnable {
> private String text;
> private AnalysisEngine ae;
> private CasPool pool;
> public Standalone(String txt, AnalysisEngine ae, CasPool pool) {
> this.text = txt;
> this.ae = ae;
> this.pool = pool;
> }
> public static void main(String[] args) throws Exception {
> String descPath = ((args != null) && (args.length > 0)) ? args[0] :
> "C:\\InterSystems\\UIMA\\bin\\DaveDetector.xml";
>
> if ((args != null) && (args.length > 1) && (args[1].charAt(0) ==
> 'y')) {
> async(descPath);
> return;
> }
>
>int casPoolSize = ((args != null) && (args.length > 2)) ?
> Integer.valueOf(args[2]) : 20;
> XMLInputSource in = new XMLInputSource(descPath);
> ResourceSpecifier specifier
> = UIMAFramework.getXMLParser().parseResourceSpecifier(in);
> AnalysisEngine ae = UIMAFramework.produceAnalysisEngine(specifier);
> CasPool pool = (casPoolSize > 0) ? new CasPool(casPoolSize, ae) :
> null;
> String loremIpsum = "Lorem ipsum dolor sit amet, consectetur
> adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
> aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
> nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in
> reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
> Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia
> deserunt mollit anim id est laborum.";
> for (int i = 0; i < 25; i++) {
> Standalone task = new Standalone(loremIpsum,
> UIMAFramework.produceAnalysisEngine(specifier), (casPoolSize > 0) ? pool :
> null);
> Thread t = new Thread(task);
> t.start();
> }
> }
> public static int async(String descriptor) throws Exception {
> String javaHome = System.getProperty("java.home");
> String javaBin = javaHome
> + File.separator + "bin"
> + File.separator + "java";
> //String classpath = System.getProperty("java.class.path");
> URL[] urls = ((URLClassLoader)
> Thread.currentThread().getContextClassLoader()).getURLs();
> StringBuilder classPath = new StringBuilder();
> for (URL url : urls) {
> classPath.append(url.getPath()).append(";");
> }
> System.out.println(javaBin.concat(" -cp
> ").concat(classPath.toString()).concat("
> ").concat(Standalone.class.getCanonicalName()).concat("
> ").concat(descriptor));
> ProcessBuilder builder = new ProcessBuilder(
> javaBin, "-cp", classPath.toString(),
> Standalone.class.getCanonicalName(), descriptor);
> builder.redirectErrorStream(true);
> builder.redirectOutput(ProcessBuilder.Redirect.INHERIT);
> Process[] processes = new Process[4];
> processes[0] = builder.start();
> processes[1] =
[jira] [Updated] (UIMA-5235) Update UIMAC++ build Mac OSX instructions
[ https://issues.apache.org/jira/browse/UIMA-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-5235: - Fix Version/s: (was: 2.4.1C) 3.0.0C > Update UIMAC++ build Mac OSX instructions > - > > Key: UIMA-5235 > URL: https://issues.apache.org/jira/browse/UIMA-5235 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework >Affects Versions: 2.4.0C > Environment: Mac OS X >Reporter: William Colen >Assignee: Edward Epstein >Priority: Minor > Fix For: 3.0.0C > > Attachments: UIMA-5235.patch > > > The instructions to build UIMAC++ was not enough to do it successfully. There > where issues with GCC and APR (UIMA-5234). > Also, the binary distribution can not be executed in Mac OS X, but the > documentations leads us to believe it can. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-5236) Can not compile UIMA C++ examples in Mac OS X
[ https://issues.apache.org/jira/browse/UIMA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-5236: - Fix Version/s: (was: 2.4.1C) 3.0.0C > Can not compile UIMA C++ examples in Mac OS X > - > > Key: UIMA-5236 > URL: https://issues.apache.org/jira/browse/UIMA-5236 > Project: UIMA > Issue Type: Bug > Components: C++ Framework >Affects Versions: 2.4.0C > Environment: Mac OS X >Reporter: William Colen >Assignee: Edward Epstein >Priority: Critical > Fix For: 3.0.0C > > Attachments: UIMA-5236.patch > > > There is a few issues in base.mak that make it difficult to build annotators > in Mac OS X. > Users must fix not only the path to APR includes as stated in the README, but > also for ICU and XERCES-C. The same for the libraries. > The BIN_LINKFLAGS is not set, but required to build it successfully. > Also, at least for Sierra, the default CC compiler will not work. Tried to > change compiler to g++5 and could compile. > The includes that comes with the binary distribution are not compatible with > MAC OS X, so it should not be used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6140) Update of UIMA C++ to run with modern compilers
[ https://issues.apache.org/jira/browse/UIMA-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-6140: - Fix Version/s: 3.0.0C > Update of UIMA C++ to run with modern compilers > --- > > Key: UIMA-6140 > URL: https://issues.apache.org/jira/browse/UIMA-6140 > Project: UIMA > Issue Type: Bug > Components: C++ Framework >Reporter: Daniel Gruhl >Assignee: Edward Epstein >Priority: Major > Fix For: 3.0.0C > > Original Estimate: 0.1h > Remaining Estimate: 0.1h > > The C++ codebase is getting a bit dated, and in fact will not compile and run > on modern machines. This whole project needs to be brought back up to spec. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6175) Changes needed for UIMA C++ release 3.0.0
[ https://issues.apache.org/jira/browse/UIMA-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-6175: - Fix Version/s: 3.0.0C > Changes needed for UIMA C++ release 3.0.0 > - > > Key: UIMA-6175 > URL: https://issues.apache.org/jira/browse/UIMA-6175 > Project: UIMA > Issue Type: Task > Components: C++ Framework >Reporter: Eddie Epstein >Assignee: Edward Epstein >Priority: Major > Fix For: 3.0.0C > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6172) Eliminate errors/warnings resulting from UIMA-6140: "Update of UIMA C++ to run with modern compilers"
[ https://issues.apache.org/jira/browse/UIMA-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-6172: - Fix Version/s: 3.0.0C > Eliminate errors/warnings resulting from UIMA-6140: "Update of UIMA C++ to > run with modern compilers" > - > > Key: UIMA-6172 > URL: https://issues.apache.org/jira/browse/UIMA-6172 > Project: UIMA > Issue Type: Bug > Components: C++ Framework >Reporter: Eddie Epstein >Assignee: Edward Epstein >Priority: Major > Fix For: 3.0.0C > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (UIMA-6173) Make it easier to test UIMA C++ interoperability with UIMA-AS
[ https://issues.apache.org/jira/browse/UIMA-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein updated UIMA-6173: - Fix Version/s: 3.0.0C > Make it easier to test UIMA C++ interoperability with UIMA-AS > - > > Key: UIMA-6173 > URL: https://issues.apache.org/jira/browse/UIMA-6173 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework >Reporter: Eddie Epstein >Assignee: Edward Epstein >Priority: Minor > Fix For: 3.0.0C > > > The existing UIMACPP SDK includes a C++ Meeting Annotator that is compatible > with the Java version in the UIMA SDK, but it does not include a way to test > it with the UIMA-AS SDK. Another deployment descriptor and instructions in > README.4bin should make this much easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (UIMA-2290) start maven values with Apache UIMA instead of just UIMA
[ https://issues.apache.org/jira/browse/UIMA-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026920#comment-17026920 ] Edward Epstein commented on UIMA-2290: -- UIMA-C++ ok > start maven values with Apache UIMA instead of just UIMA > --- > > Key: UIMA-2290 > URL: https://issues.apache.org/jira/browse/UIMA-2290 > Project: UIMA > Issue Type: Improvement > Components: addons, C++ Framework, Ruta, Sandbox >Reporter: Marshall Schor >Assignee: Marshall Schor >Priority: Trivial > > Branding guidelines say the "first use" of a name in websites / documentation > of various kinds should use Apache XXX. Page > http://www.apache.org/foundation/marks/pmcs.html#naming says 'The first and > most prominent reference to a project or product on each page must use the > "Apache Foo" form of its name. Other references may use either "Apache Foo" > or "Foo" as appropriate for the subject matter.' > It is probably a grey area of whether or not the element constitutes a > "first and most prominent reference". However, the element by default > is picked up in the NOTICE file and used to create the appropriate Notice, so > this weighs in favor of having this be the Apache UIMA form. > Therefore, in all projects defining their own element starting with > just UIMA, change this to Apache UIMA. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-2311) wrong or no svn:eol-style set on many files in uimacpp
[ https://issues.apache.org/jira/browse/UIMA-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-2311: Assignee: Edward Epstein (was: Bhavani Iyer) > wrong or no svn:eol-style set on many files in uimacpp > -- > > Key: UIMA-2311 > URL: https://issues.apache.org/jira/browse/UIMA-2311 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework >Reporter: Marshall Schor >Assignee: Edward Epstein >Priority: Minor > > Files that developers edit with text editors are usually marked with the svn > property svn:eol-style native. This insures that when they are checked out, > the line endings are converted to the client's style of line endings, and > when changes are checked in, the line endings are normalized, so that lines > which are not changed don't appear in the diff. > Without this, we have seen cases where a file is stored with some line ending > in SVN, checked out onto a machine with different default line endings, > edited and saved (causing the line-endings to be changed to that machine's > default style), and then committed. The commit shows as if every line has > been changed, whereas the real change might have been just a few lines. This > makes for difficult reviewing of the commits, of course. > I found many examples in the uimacpp project where the svn:eol-style is > missing, or where it was set to LF (which might be alright, but native is > probably safer). > Committers: It is highly recommended that you can set up your SVN to > automatically tag "new" files with the right svn:eol-style, by following the > instructions here: http://www.apache.org/dev/svn-eol-style.txt -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-6140) Update of UIMA C++ to run with modern compilers
[ https://issues.apache.org/jira/browse/UIMA-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-6140: Assignee: Edward Epstein (was: Eddie Epstein) > Update of UIMA C++ to run with modern compilers > --- > > Key: UIMA-6140 > URL: https://issues.apache.org/jira/browse/UIMA-6140 > Project: UIMA > Issue Type: Bug > Components: C++ Framework >Reporter: Daniel Gruhl >Assignee: Edward Epstein >Priority: Major > Original Estimate: 0.1h > Remaining Estimate: 0.1h > > The C++ codebase is getting a bit dated, and in fact will not compile and run > on modern machines. This whole project needs to be brought back up to spec. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-5236) Can not compile UIMA C++ examples in Mac OS X
[ https://issues.apache.org/jira/browse/UIMA-5236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-5236: Assignee: Edward Epstein (was: Eddie Epstein) > Can not compile UIMA C++ examples in Mac OS X > - > > Key: UIMA-5236 > URL: https://issues.apache.org/jira/browse/UIMA-5236 > Project: UIMA > Issue Type: Bug > Components: C++ Framework >Affects Versions: 2.4.0C > Environment: Mac OS X >Reporter: William Colen >Assignee: Edward Epstein >Priority: Critical > Fix For: 2.4.1C > > Attachments: UIMA-5236.patch > > > There is a few issues in base.mak that make it difficult to build annotators > in Mac OS X. > Users must fix not only the path to APR includes as stated in the README, but > also for ICU and XERCES-C. The same for the libraries. > The BIN_LINKFLAGS is not set, but required to build it successfully. > Also, at least for Sierra, the default CC compiler will not work. Tried to > change compiler to g++5 and could compile. > The includes that comes with the binary distribution are not compatible with > MAC OS X, so it should not be used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-5235) Update UIMAC++ build Mac OSX instructions
[ https://issues.apache.org/jira/browse/UIMA-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-5235: Assignee: Edward Epstein (was: Eddie Epstein) > Update UIMAC++ build Mac OSX instructions > - > > Key: UIMA-5235 > URL: https://issues.apache.org/jira/browse/UIMA-5235 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework >Affects Versions: 2.4.0C > Environment: Mac OS X >Reporter: William Colen >Assignee: Edward Epstein >Priority: Minor > Fix For: 2.4.1C > > Attachments: UIMA-5235.patch > > > The instructions to build UIMAC++ was not enough to do it successfully. There > where issues with GCC and APR (UIMA-5234). > Also, the binary distribution can not be executed in Mac OS X, but the > documentations leads us to believe it can. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-4899) UIMACPP access violation in destroyJNI()
[
https://issues.apache.org/jira/browse/UIMA-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Epstein reassigned UIMA-4899:
Assignee: Edward Epstein
> UIMACPP access violation in destroyJNI()
>
>
> Key: UIMA-4899
> URL: https://issues.apache.org/jira/browse/UIMA-4899
> Project: UIMA
> Issue Type: Bug
> Components: C++ Framework
>Affects Versions: 2.8.1SDK
> Environment: Windows 10 64bit
>Reporter: Benjamin De Boe
>Assignee: Edward Epstein
>Priority: Major
>
> When running a bunch of threads accessing separate AE instances of the
> UIMACPP DaveDetector in JNI mode, the process crashes with an access
> violation on the call to "delete pInstance" in destructorJNI in jni/jni.cpp.
> The code below should allow you to reproduce the issue and takes three
> command-line arguments:
> 1: the full path to DaveDescriptor.xml
> 2: whether to use simple threads ("n") or separate processes ("y")
> 3: (optional, default 20) size of the CAS pool to use, which we found out has
> an impact in reproducing the issue.
> /*
> * To change this license header, choose License Headers in Project
> Properties.
> * To change this template file, choose Tools | Templates
> * and open the template in the editor.
> */
> package com.intersys.uima.test;
> import java.io.File;
> import java.net.URL;
> import java.net.URLClassLoader;
> import org.apache.uima.UIMAFramework;
> import org.apache.uima.analysis_engine.AnalysisEngine;
> import org.apache.uima.cas.CAS;
> import org.apache.uima.resource.ResourceSpecifier;
> import org.apache.uima.util.CasCreationUtils;
> import org.apache.uima.util.CasPool;
> import org.apache.uima.util.Level;
> import org.apache.uima.util.XMLInputSource;
> /**
> *
> * @author bdeboe
> */
> public class Standalone implements Runnable {
> private String text;
> private AnalysisEngine ae;
> private CasPool pool;
> public Standalone(String txt, AnalysisEngine ae, CasPool pool) {
> this.text = txt;
> this.ae = ae;
> this.pool = pool;
> }
> public static void main(String[] args) throws Exception {
> String descPath = ((args != null) && (args.length > 0)) ? args[0] :
> "C:\\InterSystems\\UIMA\\bin\\DaveDetector.xml";
>
> if ((args != null) && (args.length > 1) && (args[1].charAt(0) ==
> 'y')) {
> async(descPath);
> return;
> }
>
>int casPoolSize = ((args != null) && (args.length > 2)) ?
> Integer.valueOf(args[2]) : 20;
> XMLInputSource in = new XMLInputSource(descPath);
> ResourceSpecifier specifier
> = UIMAFramework.getXMLParser().parseResourceSpecifier(in);
> AnalysisEngine ae = UIMAFramework.produceAnalysisEngine(specifier);
> CasPool pool = (casPoolSize > 0) ? new CasPool(casPoolSize, ae) :
> null;
> String loremIpsum = "Lorem ipsum dolor sit amet, consectetur
> adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
> aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
> nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in
> reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
> Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia
> deserunt mollit anim id est laborum.";
> for (int i = 0; i < 25; i++) {
> Standalone task = new Standalone(loremIpsum,
> UIMAFramework.produceAnalysisEngine(specifier), (casPoolSize > 0) ? pool :
> null);
> Thread t = new Thread(task);
> t.start();
> }
> }
> public static int async(String descriptor) throws Exception {
> String javaHome = System.getProperty("java.home");
> String javaBin = javaHome
> + File.separator + "bin"
> + File.separator + "java";
> //String classpath = System.getProperty("java.class.path");
> URL[] urls = ((URLClassLoader)
> Thread.currentThread().getContextClassLoader()).getURLs();
> StringBuilder classPath = new StringBuilder();
> for (URL url : urls) {
> classPath.append(url.getPath()).append(";");
> }
> System.out.println(javaBin.concat(" -cp
> ").concat(classPath.toString()).concat("
> ").concat(Standalone.class.getCanonicalName()).concat("
> ").concat(descriptor));
> ProcessBuilder builder = new ProcessBuilder(
> javaBin, "-cp", classPath.toString(),
> Standalone.class.getCanonicalName(), descriptor);
> builder.redirectErrorStream(true);
> builder.redirectOutput(ProcessBuilder.Redirect.INHERIT);
> Process[] processes = new Process[4];
> processes[0] = builder.start();
> processes[1] = builder.start();
>
[jira] [Assigned] (UIMA-6175) Changes needed for UIMA C++ release 3.0.0
[ https://issues.apache.org/jira/browse/UIMA-6175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-6175: Assignee: Edward Epstein (was: Eddie Epstein) > Changes needed for UIMA C++ release 3.0.0 > - > > Key: UIMA-6175 > URL: https://issues.apache.org/jira/browse/UIMA-6175 > Project: UIMA > Issue Type: Task > Components: C++ Framework >Reporter: Eddie Epstein >Assignee: Edward Epstein >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-6173) Make it easier to test UIMA C++ interoperability with UIMA-AS
[ https://issues.apache.org/jira/browse/UIMA-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-6173: Assignee: Edward Epstein (was: Eddie Epstein) > Make it easier to test UIMA C++ interoperability with UIMA-AS > - > > Key: UIMA-6173 > URL: https://issues.apache.org/jira/browse/UIMA-6173 > Project: UIMA > Issue Type: Improvement > Components: C++ Framework >Reporter: Eddie Epstein >Assignee: Edward Epstein >Priority: Minor > > The existing UIMACPP SDK includes a C++ Meeting Annotator that is compatible > with the Java version in the UIMA SDK, but it does not include a way to test > it with the UIMA-AS SDK. Another deployment descriptor and instructions in > README.4bin should make this much easier. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (UIMA-6172) Eliminate errors/warnings resulting from UIMA-6140: "Update of UIMA C++ to run with modern compilers"
[ https://issues.apache.org/jira/browse/UIMA-6172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edward Epstein reassigned UIMA-6172: Assignee: Edward Epstein (was: Eddie Epstein) > Eliminate errors/warnings resulting from UIMA-6140: "Update of UIMA C++ to > run with modern compilers" > - > > Key: UIMA-6172 > URL: https://issues.apache.org/jira/browse/UIMA-6172 > Project: UIMA > Issue Type: Bug > Components: C++ Framework >Reporter: Eddie Epstein >Assignee: Edward Epstein >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Moving UIMA Ruta to Git Repo
Hi, the vote has passed with the following result: +1 : Peter Klügl, Jaroslaw Cwiklik, Viorel Morari, Eddie Epstein, Richard Eckart de Castilho, Marshall Schor No other votes received. Thanks. Peter Am 20.01.2020 um 17:14 schrieb Peter Klügl: > Hi, > > > after Ruta v3 is released and UIMA-AS is also moving, I think it's time > that UIMA Ruta also switches to GIT. > > > I would like to move UIMA Ruta to Git. Let me know with +1 or otherwise > to move UIMA Ruta to a writable GIT repo and switch to using GIT for > source control system. > > > [ ] +1 OK to move UIMA Ruta from SVN to (writable) GIT for source control > > [ ] 0 don't care > > [ ] -1 not OK to move UIMA Ruta from SVN to (writable) GIT for source > control because... > > Thanks. > > > Peter > > -- Dr. Peter Klügl R&D Text Mining/Machine Learning Averbis GmbH Salzstr. 15 79098 Freiburg Germany Fon: +49 761 708 394 0 Fax: +49 761 708 394 10 Email: peter.klu...@averbis.com Web: https://averbis.com Headquarters: Freiburg im Breisgau Register Court: Amtsgericht Freiburg im Breisgau, HRB 701080 Managing Directors: Dr. med. Philipp Daumke, Dr. Kornél Markó
