Embedded Apache DS with jetty - conflicting slf4j-api versions - jetty

Seems like Apache Ds has a dependency on slf4j-api v1.5 while jetty needs slf4j-api v1.6. These versions are not compatible with each other. Anyone else run into same issue?

Related

Services in Redmine-Plugin

i've made a plugin for redmine, with 2 services.
But, on my remote-machine, the services seems not to be loaded.
Do services in redmine-plugins work in general?
Do i have to set any autoload-paths?
Is there a version-difference, in Redmine?
On my local Macbook, within redmine-4.0.4 all works fine (env: production and development). But on my Debian, there is redmine-3.4.2 i receipt this error
NameError (uninitialized constant TimesController::SearchTimes):
plugins/billing/app/controllers/times_controller.rb:41:in `select'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'
Services are just Ruby objects so they surely work in Redmine plugins.
Redmine autoloads only controllers, helpers and models paths under the plugin's /app directory. Plugin starting point /init.rb should manually require other files which usually resides in /lib folder.
Redmine 3.x and 4.x versions are very different, but much of these changes are caused by Rails itself.

Multiple Informatica Powercenter Clients on same machine?

I have Informatica Powercenter Server version 9.1.0. The client on my machine is version 9.6.1. Since the client and server versions have to be same, I need to install Informatica Powercenter Client version 9.1.0. Can I install client version 9.1.0 without uninstalling version 9.6.1?
It's possible in general. I've had some issues due to using same domains.infa config file by both clients. What made it even more difficult was the fact that the repositories in each version had very same names - the host was the only difference. Check this out in case of issues. Otherwise you should be perfectly fine.
Yes it is. I am using both 9.6 and 10.1 in a same machine.
As long as you are connected to correct server repository you are good to go
I don't believe this should be an issue (am running 8.6.1 and 9.1 on my machine) check you have enough space for both though.

Ember CLI livereload does not detect changes

Livereload
I'm having problems getting Ember CLI (1.13.15) to detect changes. When I create a new application with
ember init
And run the development server with
ember serve
The project compiles and I see the page. When I change something, the server detects changes in the console, but nothing happens even if I refresh page. The changes become visible only after I rerun the ember serve
Slow build
Also on an empty app it takes 30 sec to build app on Samsung 850 Pro SSD & i7 2600k with admin rights and after ember-cli-windows run. (the build on half slower MacBook Air is almost instantaneous).
Versions
Windows 10 with all the updates
ember-cli: 1.13.15
node: 4.2.6
npm: 2.14.10
I just encountered this as well -- seemingly out of nowhere, at once, on several different projects. Making sure I had this in .ember-cli was a winning fix:
"liveReload": true,
"watcher": "polling"
[Update]
I already had liveReload: true, so adding the watcher setting seems to be what was needed. Furthermore the projects that I implemented this for were using ember-cli at 1.13.13, 2.2.0-beta.6 and 2.3.0-beta.1, with the following system config:
node: 4.2.4
npm: 2.14.10
os: darwin x64
There's currently a known issue in ember-cli where the open port for livereload isn't detected correctly (https://github.com/ember-cli/ember-cli/pull/5391). You should be able to get around this for now by running ember serve --host 0.0.0.0.
For now, the best solution seems to be sticking to the old versions. Also there seems to be an issue with latest sass plugin not recognizing changes so I recommend downgrading both to:
ember-cli: 1.13.8,
ember-cli-sass: 4.2.1

camel-example-cxf Not Deployed in ServiceMix 4.4.2

I was trying to run the camel-example-cxf example project which I downloaded from Camel website. (downloaded apache-camel-2.10.2)
I built the project using the pom.xml & the build was successful.
However when I tried to deploy it in servicemix (apache-servicemix-4.4.2) I am getting the following error.
karaf#root> ERROR: Bundle org.apache.camel.camel-example-cxf [43] Error starting file:/C:/apache-servicemix-4.4.2/deploy
/camel-example-cxf-2.10.2.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.camel.camel-example-cxf [43]: Unable to resolve 43.0: missing requirement [43.0] package; (&(package=org.apache.activemq.broker)(version>=5.7.0)(!(version>=6.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle org.apache.camel.camel-example-cxf [43]: Unable to resolve 43.0: missing requirement [43.0] package; (&(package=org.apache.activemq.broker)(version>=5.7.0)(!(version>=6.0.0)))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3446)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1734)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1163)
at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:619)
Please help
Apache ServiceMix 4.4.2 does not support Camel 2.10. You need to use the Camel version that it's shipped with, which is Camel 2.8.
Apache ServiceMix 4.5.0 will ship with Camel 2.10 and ActiveMQ 5.7. This release is in the works currently.
I had the same issue (but with activemq jar) and found that while running maven build i was using a different version than what servicemix had. you can find the version of jar file that are used by servicemix by using "exports" command (type export on servicemix command line) and you would come to know the version. if that is different than what you used for maven build then you would get that error. You have two option then
1. install different bundle in servicemix (with same version as used for maven build)
2. change the pom.xml to build maven build.

How do I setup virtualenv on a production Windows server using IIS and Helicon Zoo?

We are currently testing Django on a live server using Windows 2008 webserver and IIS7. To run Django projects on IIS we use Helicon Zoo (Python hosting package with Django).
The plan is to host multiple clients on that webserver and we would like to use virtualenv, so we can upgrade python packages for specific clients, without affecting the others.
The specific question is; when we have several virtualenvs on the server, how do we set up the different Django sites under IIS to use a specific virtualenv?
Thanks in advance for your time and answers,
Erik
It is not quite clear to me whether you need different versions of Python or different versions of modules, used in the application.
To have different python versions you can install another python manually, then go to applicationHost.config file, find . Engines declarations will be listed there. Create a copy of "python.2.7.wsgi" and edit the copy, name it like "python.2.5.wsgi" and change executable name path. This is how you can declare more engines with different versions and settings. Here you can find more information: Helicon Zoo Module documentation
As for Python modules, it is supposed that modules are installed locally in the client's web site in \python_modules\ directory. When you create new Django application using Helicon Zoo, it is configured to use isolated environment by default, you only need to learn how to use it right and tell your clients to follow guidelines. You can find the information in this article: Running Django on Windows (with performance tests)