The fusesource repositories have been migrated to jboss. You can find the artifact at: https://repository.jboss.org/nexus/content/groups/fs-public/net/sf/josql/josql/
An other alternative is to use the josql bundles under servicemix bundles: http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.josql which is the same artifact + osgi metadata. On Thu, Nov 14, 2013 at 8:51 PM, kishore g <[email protected]> wrote: > Olivier, can we upload this to maven central. > > If we cannot upload it to maven central, lets try to upload the jar to > sonatype or nexus repository. > > > > > > On Thu, Nov 14, 2013 at 10:14 AM, Kanak Biscuitwala > <[email protected]> wrote: >> >> We need to prioritize this. >> >> helix --> camel-josql --> net.sf.josql, but the repo containing >> net.sf.josql (http://repo.fusesource.com/maven2) has been emptied. >> Therefore, anyone building Helix from a clean local maven repo is unable >> to do so. >> >> Alexandre, you work at Red Hat, which now owns FuseSource, would you by >> any chance have some context about the present and future of the >> FuseSource Maven repository? >> >> Thanks, >> Kanak >> >> On 11/8/13 10:18 AM, "Alexandre Porcelli" <[email protected]> wrote: >> >> >Thank you all for quick reply.. >> > >> > So I can't remove (i'm using messaging service). >> > >> > Now a 2nd question: how are you resolving this dependency (assuming an >> >empty .m2)? Our Nexus doesn't have reference to it neither maven >> >central... >> > >> >Regards, >> >--- >> >Alexandre Porcelli >> >Principal Software Engineer >> >Red Hat Business Systems and Intelligence Group >> > >> >On Nov 8, 2013, at 4:14 PM, kishore g <[email protected]> wrote: >> > >> >> That is correct, its only used in messaging service to send messages. >> >>Josql is definitely something we want to remove the dependency. >> >> >> >> If you are not using this, you can remove it the dependency at runtime. >> >> >> >> thanks, >> >> Kishore G >> >> >> >> >> >> On Fri, Nov 8, 2013 at 9:29 AM, Kanak Biscuitwala >> >><[email protected]> wrote: >> >> It seems to be used for our messaging service to send messages, but for >> >> the most part it is used for the "scheduler message" functionality, >> >>which >> >> you likely don't use. The way the code is structured, you would have to >> >> rip methods out of DefaultMessagingService (namely send and >> >>sendAndWait). >> >> I believe Kishore has mentioned that josql is perhaps not even the best >> >> way to do this, and we're always trying to reduce dependencies, but it >> >> will require some work to create a replacement. >> >> >> >> On 11/8/13 9:02 AM, "Alexandre Porcelli" <[email protected]> wrote: >> >> >> >> >Hello Guys, >> >> > >> >> > We're facing some issues to resolve net.sf.josql:josql:jar:1.5 >> >>artifact >> >> >in our current setup... I'd like to know if this is really mandatory >> >> > or >> >> >if it's not used by `core` what parts use it that allowed me to check >> >>if >> >> >I'm using those parts somehow. >> >> > >> >> >Thanks in Advance, >> >> >--- >> >> >Alexandre Porcelli >> >> >Principal Software Engineer >> >> >Red Hat Business Systems and Intelligence Group >> >> > >> >> >> >> >> > >> > -- Ioannis Canellos Blog: http://iocanel.blogspot.com Twitter: iocanel
