No problem. I only stumbled across them due to the SLF4J and ActiveMQ 5.6 problems. :)
While the problem with SLF4J is just a warning and not fatal, it can cause problems because the SLF4J binding that is chosen is essentially done at random. I've been trying to remove the extra bindings that UIMA inserts and just use the default ActiveMQ ones, but that causes test failures. My next step is to remove the ActiveMQ bindings but that necessitates using the individual jars instead of activemq-all. The ActiveMQ 5.6 problem I'm referring to is explained here. https://stackoverflow.com/questions/12938083/what-where-is-net-sf-josql On Tue, Feb 18, 2014 at 10:20 AM, Jaroslaw Cwiklik <uim...@gmail.com> wrote: > Hi, thanks for spotting references to 5.4.1. I will create JIRA and fix > these. The fixes will be in the next release. > > I will take a look at SLF4J to see if this can be fixed. From what I > remember this is just a Warning not a Fatal > condition. Nevertheless, its worth looking into. Will create JIRA to > investigate. > > Could you clarify " there are problems with ActiveMQ 5.6 referring to > nonexistent > artifacts"? I would like to know more detail about this. > > Jerry C > > > > > On Tue, Feb 18, 2014 at 10:10 AM, Bai Shen <baishen.li...@gmail.com> > wrote: > > > Firstly, the following files still refer to ActiveMQ 5.4.1 > > > > src/main/assembly/src.xml > > src/main/examples/run_configuration/UIMA Run Remote Async AE.launch > > src/main/eclipseProject/classpath > > > > > uimaj-as-activemq/src/main/java/org/apache/uima/aae/jmx/monitor/JmxMonitor.java > > > > Secondly, I'm getting multiple SLF4J binding errors due to the inclusion > of > > activemq-all.jar and slf4j-log4j12-1.6.4.jar Is there a plan to change > > this? > > > > Lastly, there are problems with ActiveMQ 5.6 referring to nonexistent > > artifacts. Will 2.5 use the fixed 5.7 version? > > > > Thanks. > > >
