[jira] [Created] (UIMA-5582) Launch external pingers with the user-supplied --jvm instead of DUCC's

[Burn Lewis (JIRA)]

Burn Lewis created UIMA-5582:


 Summary: Launch external pingers with the user-supplied --jvm 
instead of DUCC's
 Key: UIMA-5582
 URL: https://issues.apache.org/jira/browse/UIMA-5582
 Project: UIMA
  Issue Type: Improvement
  Components: DUCC
Reporter: Burn Lewis
Assignee: Burn Lewis
Priority: Minor
 Fix For: future-DUCC


Currently if JAVA_HOME is not in the environment DUCC uses the same JVM as DUCC 
to launch external pingers.  Instead use the jvm supplied by the user which is 
likely to be the same as the service.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (UIMA-5581) When a CLI request fails because ducc is down, say so

[Burn Lewis (JIRA)]

Burn Lewis created UIMA-5581:


 Summary: When a CLI request fails because ducc is down, say so
 Key: UIMA-5581
 URL: https://issues.apache.org/jira/browse/UIMA-5581
 Project: UIMA
  Issue Type: Improvement
  Components: DUCC
Reporter: Burn Lewis
Priority: Minor
 Fix For: future-DUCC


Currently a long stack trace ends with "Connection refused"



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (UIMA-5580) Avoid warning about empty classpath when creating resource manager

[Richard Eckart de Castilho (JIRA)]

Richard Eckart de Castilho created UIMA-5580:


 Summary: Avoid warning about empty classpath when creating 
resource manager
 Key: UIMA-5580
 URL: https://issues.apache.org/jira/browse/UIMA-5580
 Project: UIMA
  Issue Type: Bug
  Components: uimaFIT
Affects Versions: 3.0.0uimaFIT
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho


Use ResourceManager.setExtensionClassLoader instead of setExtensionClassPath to 
avoid permanently logging a warning message about an empty classpath.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[VOTE] uimaj sdk 3.0.0 beta rc3

[Marshall Schor]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Here's RC3 for uimaj-sdk 3.0.0-beta.

The fixes since the recent rc2 are UIMA-5532 and newer;
you can view all 68 Jiras for this version here:

https://issues.apache.org/jira/issues/?jql=project%20%3D
%2012310570%20AND%20fixVersion%20%3D%2012339590
%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC

shows all 68 changes, ordered by key descending.

The main fixes are:

  a) new logic to support modern and old style of logging
 (modern uses {} for substitutable parameters,
 old uses {n} n = a number.

  b) lazy initialization to match v2
 (better backwards compatibility) for JCas classes

  c) default method for new getComparator() in FSIteratorImplBase

  d) new getLogger() method in flow controllers

  e) bug in xmi deserialization of String Array of 0 length

  f) added way to get the JCas view from a FeatureStructure

  g) fixed migration tool to insert _FeatName and _TypeName

The v3 users guide has many updates and corrections;
any reviews appreciated :-)

Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheuima-1155/

Source and binary zip/tar staged to:
https://dist.apache.org/repos/dist/dev/uima/uimaj/
3.0.0-beta-rc3/artifacts/

Eclipse update site (no need to download,
just use this as the link in Eclipse's install):
https://dist.apache.org/repos/dist/dev/uima/uimaj/
3.0.0-beta-rc3/uimaj-v3-pre-production/

SVN tag: https://svn.apache.org/repos/asf/uima/uv3/
uimaj-v3/tags/uimaj-3.0.0-beta/

Please vote on release:

[ ] +1 OK to release
[ ] 0 Don't care
[ ] -1 Not OK to release, because ...

Thanks.

- -Marshall


-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJZwXSjAAoJEHMl+QLhMDqZIwEQALSB38eotjQ06/j6qvPPRi3r
HAqf6ZBzlLwj2modIga8RN8INm8D00vkUg2mMLylN0aI342RioohQbf7A/6fjB51
3FCTnWPve0No1RhbM4ISEqeer+i7IH1F4elzIfM9NLF0MiB1j7+L4UFdWvZvzytD
MQ6OCUiU99o+RNnJ8T9SkEo3j0uZH6/iIuVNsKW6R06Y+CuwHN/891xc5wTNsGBl
qcjvsbvXjy9bE4vR4akZb6LACa2rs5Xm/mAcjBEPyk+GNg2V5iVy1+KRF5SHFYT2
SVQYZDfMQnY4feIFUxhl0Q4NatAjkDTkcJ14f2prkROQM9TQeqgcQU4xoOH+wUp+
CSjWGUWAtBNGtt4JQ2qwHQqR1ecc3gkRxKWdDnGgXOVIEOXwJVjpTy0ipoNS/Jne
XAIzjlk6O19ZkIdKVaVXSrk6wluK6neRd+C1uiGr2wPJdqATmci858RKc47NcEXo
gB9xw486CNxkwNwuo4fTChO9i/QNGdvMdYc4+vJk/aSSQFjv8IghxK5fcF8JACea
U2AyuahdcfzL4ncs59qQiq9mbRCfMRNrckgmNM16aa2mMkuoGDrgFhLoeNG4uxOj
1wi+HSHC3uDEKwh/yeOphVA+uh3O2CsWhatutrKmUKe8B8yKhusOCBTw0HDF6Q3X
8EXzj67lZPSYPMunOTwD
=sWKW
-END PGP SIGNATURE-

Re: Configuring build with maven 3.3.9

[Marshall Schor]

Hi,

Looks like there still may be a small issue. 
Running our build on a Windows system now starts and runs, until it gets to an
"integration test".

  The integration test runs 'maven within maven"; we use it to test new maven
plugins. 
  This test fails with the message:
 Maven invocation failed. Error configuring command-line. 
 Reason: Maven executable not found at:
   F:\jenkins\tools\maven\apache-maven-3.3.9\bin\mvn.bat

Any ideas on how to fix this?

-Marshall Schor


On 9/19/2017 9:27 AM, Marshall Schor wrote:
> Thanks, Gav!
>
> That seemed to do the trick...
>
> -Marshall
>
>
> On 9/14/2017 6:28 PM, Gav wrote:
>> Hi,
>>
>> All of the 'Latest' options for 'Ant,Maven'Java' etc are configured to work
>> for both Linux and Windows, have been for a while.
>>
>> Maven 3.3.9 used to be 'Latest' until 3.5.0 was released when that took
>> over the symlinking for Latest.
>>
>> So 3.3.9 used to work for both, then stopped.
>>
>> As there are still a few jobs using 3.3.9 , I have created a tool location
>> on the Windows nodes for 3.3.9 so your builds
>> should now 'just work' by choosing 'Maven 3.3.9'
>>
>> Give it a whirl and let me know.
>>
>> Gav...
>>
>>
>> On Fri, Sep 15, 2017 at 6:02 AM, Marshall Schor  wrote:
>>
>>> Hi,
>>>
>>> We have a build which needs maven 3.3.9.
>>>
>>> I see in the Jenkins pulldown menu for configuring builds, there are 2
>>> picks for
>>> maven 3.3.9:
>>>
>>>   - one is labeled "Maven 3.3.9"
>>>
>>>   - one is labeled "Maven 3.3.9 (Windows)"
>>>
>>>
>>> We are using the first ("Maven 3.3.9").  Our build is not set to restrict
>>> where
>>> it can be run.
>>>
>>> So, when it runs on a windows machine, it fails, saying it can't find
>>> Maven 3.3.9.
>>>
>>> -
>>>
>>> Do you require all builds which need this Maven, to have 2 configurations,
>>> one
>>> with the (Windows) pick, restricted to Windows machine, and the other
>>> without
>>> that, for Linux boxes?
>>>
>>> We would of course prefer not to have to duplicate our build configurations
>>> because of this - so if there's another better way, please let us know.
>>>
>>> Thanks. -Marshall
>>>
>>>
>

Build failed in Jenkins: UIMA-v3-sdk #236

[Apache Jenkins Server]

See 


Changes:

[schor] [maven-release-plugin] prepare for next development iteration

[schor] [maven-release-plugin] prepare release 
uimaj-eclipse-update-site-3.0.0-beta

[schor] [maven-release-plugin] prepare for next development iteration

[schor] [maven-release-plugin] prepare release uimaj-3.0.0-beta

--
[...truncated 1.52 MB...]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) @ jcasgen-maven-plugin ---
[INFO] Building jar: 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\jcasgen-maven-plugin-3.0.1-beta-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-plugin-plugin:3.5:addPluginArtifactMetadata 
(default-addPluginArtifactMetadata) @ jcasgen-maven-plugin ---
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
jcasgen-maven-plugin ---
[INFO] 
[INFO] --- findbugs-maven-plugin:3.0.3:findbugs (default) @ 
jcasgen-maven-plugin ---
[INFO] Fork Value is true
 [java] Warnings generated: 1
[INFO] Done FindBugs Analysis
[FINDBUGS] Searching for all files in 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target that 
match the pattern findbugsXml.xml
[FINDBUGS] Parsing 1 file in 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target
[FINDBUGS] Successfully parsed file 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\findbugsXml.xml
 of module Apache UIMA Maven: jcasgen-maven-plugin with 1 unique warning and 0 
duplicates.
[FINDBUGS] Computing warning deltas based on reference build #235
[INFO] 
[INFO] --- maven-pmd-plugin:3.6:cpd (default) @ jcasgen-maven-plugin ---
[DRY] Searching for all files in 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target that 
match the pattern cpd.xml
[DRY] Parsing 1 file in 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target
[DRY] Successfully parsed file 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\cpd.xml
 of module Apache UIMA Maven: jcasgen-maven-plugin with 0 unique warnings and 0 
duplicates.
[DRY] Computing warning deltas based on reference build #235
[INFO] 
[INFO] --- maven-pmd-plugin:3.6:pmd (default) @ jcasgen-maven-plugin ---
[PMD] Searching for all files in 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target that 
match the pattern pmd.xml
[PMD] Parsing 1 file in 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target
[PMD] Successfully parsed file 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\pmd.xml
 of module Apache UIMA Maven: jcasgen-maven-plugin with 5 unique warnings and 0 
duplicates.
[PMD] Computing warning deltas based on reference build #235
[INFO] 
[INFO] --- maven-invoker-plugin:1.8:install (integration-test) @ 
jcasgen-maven-plugin ---
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-parent\pom.xml to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-parent\3.0.1-beta-SNAPSHOT\uimaj-parent-3.0.1-beta-SNAPSHOT.pom
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-test-util\pom.xml to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-test-util\3.0.1-beta-SNAPSHOT\uimaj-test-util-3.0.1-beta-SNAPSHOT.pom
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-test-util\target\uimaj-test-util-3.0.1-beta-SNAPSHOT.jar
 to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-test-util\3.0.1-beta-SNAPSHOT\uimaj-test-util-3.0.1-beta-SNAPSHOT.jar
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-test-util\pom.xml to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-test-util\3.0.1-beta-SNAPSHOT\uimaj-test-util-3.0.1-beta-SNAPSHOT.pom
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-core\pom.xml to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-core\3.0.1-beta-SNAPSHOT\uimaj-core-3.0.1-beta-SNAPSHOT.pom
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-core\target\uima-core.jar 
to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-core\3.0.1-beta-SNAPSHOT\uimaj-core-3.0.1-beta-SNAPSHOT.jar
[INFO] Installing 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\uimaj-core\pom.xml to 
F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jcasgen-maven-plugin\target\local-repo\org\apache\uima\uimaj-core\3.0.1-beta-SNAPSHOT\uimaj-core-3.0.1-beta-SNAPSHOT.pom
[INFO] Installing F:\jenkins\jenkins-slave\workspace\UIMA-v3-sdk\jVinci\pom.xml 
to 

[jira] [Resolved] (UIMA-5577) uv3: Adjust new-style logging statements not to use parameter positions

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5577.
--
Resolution: Fixed

> uv3: Adjust new-style logging statements not to use parameter positions
> ---
>
> Key: UIMA-5577
> URL: https://issues.apache.org/jira/browse/UIMA-5577
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Reporter: Richard Eckart de Castilho
>Assignee: Richard Eckart de Castilho
> Fix For: 3.0.0SDK-beta
>
>
> Per UIMA-5556 new-style logging statements can not make use of parameter 
> positions anymore. However, there are several new-style logging statements in 
> the code that still make use of the parameter positions. Fix these.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

testing uv3 with dk-pro?

[Marshall Schor]

Hi,

Now that uimaFIT Jenkins build is back to normal, can anyone test uv3 with other
things, like dk-pro?

When you do this, please pay special attention to how logging is configured.

If you see messages that no logging is being done because no target for the
slf4j can be found, please try to fix this (possibly by adding a slf4j bridge
jar to th target of your choice).  The default binary distribution of uv3 has
"runners" that include by default the bridge to the former logger
(java.util.logger), for example.

Cheers. -Marshall

Jenkins build is back to normal : UIMA-uimaFIT v3 #35

[Apache Jenkins Server]

See 

Jenkins build is back to normal : UIMA-uimaFIT v3 » Apache UIMA uimaFIT - Examples #35

[Apache Jenkins Server]

See 

Re: Configuring build with maven 3.3.9

[Marshall Schor]

Thanks, Gav!

That seemed to do the trick...

-Marshall


On 9/14/2017 6:28 PM, Gav wrote:
> Hi,
>
> All of the 'Latest' options for 'Ant,Maven'Java' etc are configured to work
> for both Linux and Windows, have been for a while.
>
> Maven 3.3.9 used to be 'Latest' until 3.5.0 was released when that took
> over the symlinking for Latest.
>
> So 3.3.9 used to work for both, then stopped.
>
> As there are still a few jobs using 3.3.9 , I have created a tool location
> on the Windows nodes for 3.3.9 so your builds
> should now 'just work' by choosing 'Maven 3.3.9'
>
> Give it a whirl and let me know.
>
> Gav...
>
>
> On Fri, Sep 15, 2017 at 6:02 AM, Marshall Schor  wrote:
>
>> Hi,
>>
>> We have a build which needs maven 3.3.9.
>>
>> I see in the Jenkins pulldown menu for configuring builds, there are 2
>> picks for
>> maven 3.3.9:
>>
>>   - one is labeled "Maven 3.3.9"
>>
>>   - one is labeled "Maven 3.3.9 (Windows)"
>>
>>
>> We are using the first ("Maven 3.3.9").  Our build is not set to restrict
>> where
>> it can be run.
>>
>> So, when it runs on a windows machine, it fails, saying it can't find
>> Maven 3.3.9.
>>
>> -
>>
>> Do you require all builds which need this Maven, to have 2 configurations,
>> one
>> with the (Windows) pick, restricted to Windows machine, and the other
>> without
>> that, for Linux boxes?
>>
>> We would of course prefer not to have to duplicate our build configurations
>> because of this - so if there's another better way, please let us know.
>>
>> Thanks. -Marshall
>>
>>
>

[jira] [Resolved] (UIMA-5579) uv3 slf4j bridge new style broken

[Marshall Schor (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor resolved UIMA-5579.
--
Resolution: Fixed
  Assignee: Marshall Schor

> uv3 slf4j bridge new style broken
> -
>
> Key: UIMA-5579
> URL: https://issues.apache.org/jira/browse/UIMA-5579
> Project: UIMA
>  Issue Type: Bug
>  Components: Core Java Framework
>Reporter: Marshall Schor
>Assignee: Marshall Schor
> Fix For: 3.0.0SDK-beta
>
>
> The slf4j support for "new" style logging - accidentally treating these in 
> old style.  This is causing the downstream build of uimaFIT to fail



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)