I just noticed that Apache Jenkins is failing now with Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal on project uimaj-as-activemq: Could not resolve dependencies for project org.apache.uima:uimaj-as-activemq:jar:2.5.0-SNAPSHOT: The following artifacts could not be resolved: net.sf.josql:josql:jar:1.5, net.sf.josql:gentlyweb-utils:jar:1.5: Could not find artifact net.sf.josql:josql:jar:1.5 in eclipsePlugins
This artifact must have been yanked recently from maven repos. I guess this should expedite the fix :) Jerry Cwiklik On Tue, Feb 18, 2014 at 12:52 PM, Jaroslaw Cwiklik <uim...@gmail.com> wrote: > Got it. Thanks for clarifying this. > > Jerry Cwiklik > > > On Tue, Feb 18, 2014 at 12:24 PM, Bai Shen <baishen.li...@gmail.com>wrote: > >> I don't need a newer version of AMQ. I was attempting to fix the SLF4J >> issue and had to change AMQ to 5.7 just to get everything to build. So >> far >> I haven't noticed any problems with using 5.7 instead of 5.6. >> >> The problem with the test cases is from removing the SLF4J dependencies >> from the UIMA pom. >> >> Just wanted to clarify that they are two separate issues. >> >> >> On Tue, Feb 18, 2014 at 11:32 AM, Jaroslaw Cwiklik <uim...@gmail.com> >> wrote: >> >> > Just checked and it looks like the josql (SQL for Java Objects) is a >> > dependency from activemq-optional. Will look into how to deal with this. >> > Dont have an opinion on this yet. >> > >> > The AMQ 5.6 has been in heavy use in our production environment and >> moving >> > to a newer version will require thorough testing which takes time. >> > >> > There is a workaround if you need a newer version of AMQ for your >> runtime. >> > Simply install AMQ where you want and set ACTIVEMQ_HOME environment >> > variable to the location of ActiveMQ you intend to use. >> > >> > Jerry Cwiklik >> > >> > >> > >> > On Tue, Feb 18, 2014 at 10:55 AM, Bai Shen <baishen.li...@gmail.com> >> > wrote: >> > >> > > 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. >> > > > > >> > > > >> > > >> > >> > >
