[
https://issues.apache.org/jira/browse/UIMA-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170563#comment-16170563
]
Richard Eckart de Castilho commented on UIMA-5577:
--------------------------------------------------
Last time I checked, the uimaFIT v3 build failed because of a logging problem
in JCasGen.
{noformat}
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default
of goal org.apache.uima:jcasgen-maven-plugin:3.0.0-beta-SNAPSHOT:generate
failed: can't parse argument number:
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 31 more
Caused by: java.lang.IllegalArgumentException: can't parse argument number:
at java.text.MessageFormat.makeFormat(MessageFormat.java:1429)
at java.text.MessageFormat.applyPattern(MessageFormat.java:479)
at java.text.MessageFormat.<init>(MessageFormat.java:362)
at java.text.MessageFormat.format(MessageFormat.java:840)
at
org.apache.uima.util.impl.Slf4jLogger_impl.log(Slf4jLogger_impl.java:238)
at
org.apache.uima.util.impl.Slf4jLogger_impl.log2(Slf4jLogger_impl.java:261)
at
org.apache.uima.util.impl.Logger_common_impl.warn(Logger_common_impl.java:977)
at org.apache.uima.internal.util.Misc.addUrlsFromPath(Misc.java:257)
at org.apache.uima.internal.util.Misc.getURLs(Misc.java:211)
at org.apache.uima.internal.util.Misc.classpath2urls(Misc.java:274)
at
org.apache.uima.internal.util.UIMAClassLoader.<init>(UIMAClassLoader.java:166)
at
org.apache.uima.resource.impl.ResourceManager_impl.setExtensionClassPath(ResourceManager_impl.java:322)
at org.apache.uima.tools.jcasgen.Jg.createResourceManager(Jg.java:1565)
at org.apache.uima.tools.jcasgen.Jg.mergeTypeSystemImports(Jg.java:1585)
at org.apache.uima.tools.jcasgen.Jg.main1(Jg.java:690)
at org.apache.uima.tools.jcasgen.Jg.main0(Jg.java:577)
at
org.apache.uima.tools.jcasgen.maven.JCasGenMojo.execute(JCasGenMojo.java:219)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 32 more
Caused by: java.lang.NumberFormatException: For input string: ""
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:592)
at java.lang.Integer.parseInt(Integer.java:615)
at java.text.MessageFormat.makeFormat(MessageFormat.java:1427)
... 49 more
{noformat}
I believe with the latest changes to the SDK, that should be resolved, but I
would suggest to wait until a uimaFITv3 build has completed on Jenkins.
Also, once the UIMAv3 SDK build is successful again on Jenkins, I'd try doing
another DKPro Core build. Last time I tried, there it seemed as if there could
be issues with the CasCopier. In case you would like to have a glance yourself:
https://zoidberg.ukp.informatik.tu-darmstadt.de/jenkins/job/DKPro%20Core%20(GitHub)%20-%20UIMAv3/
More testing is good, but I'd wait a bit more with the next RC.
> 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)
