Currently I am going to verify FIWARE.
Release 7.5 was announced, but there are components whose version is lower in the core component.
cygnus
Release7.4 : version2.0.0
Release7.5 : version1.9.0
sth-comet
Release7.4 : version2.4.0
Release7.5 : version2.3.0
I want to know the reason why the version of the component is going down.
With regards to Cygnus, the short history is that FIWARE wrongly used "Cygnus" as software name in FIWARE 7.4 for a component that in FIWARE 7.5 was renamed to "Draco". Cygnus stills existing of course but release 2.0.0 has not come yet. Last Cygnus available version in the moment of writting this is Cygnus 1.10.0, to be included as part of FIWARE release 7.5.1.
With regards to STH, probably FIWARE releases are still using this fork as reference, when it should be using the original one. Note the original repository is the most updated and the one which uses version 2.4.0 at the present moment.
#fgalan is correct, some elements were inconsistently labelled in release 7.4 and 7.5. A patch release has finally corrected this.
As of 7.5.1, the following versions are correct:
cygnus 1.10.0
sth-comet 2.5.0
draco FIWARE_7.5
The new draco generic enabler had been initially released as cygnus 2.x which was incorrect.
Related
I am getting problem in web smooch widget.
Here is complete question posted in git repo.
https://github.com/alavers/smooch-bot-example/issues/40
The version of Web Messenger you are using was deprecated in Summer 2017 is no longer supported. You'll need to update to a version > 4.0.0 in order to keep using your integration. Installation instructions can be found in the documentation. See the v4.0.0 release notes for notable changes when switching from the 3.x version series.
Note also that the GitHub repository you linked is not an official Smooch repository and is not actively monitored for support requests.
I'm trying to replicate the installation guide to integrate Wirecloud 1.0.1 with the latest version of IDM Keyrock.
I'd like to understand if the guide in the documentation is valid again for this version of WC.
Thanks in advance for the answers.
As you suspected, the linked documentation is not valid for WireCloud v1.0.1, you linked to the latest branch of the documentation, that is the documentation for the development version of WireCloud.
The documentation on how to configure WireCloud v1.0.1 to use the IdM can be found in this link.
We know that is not clear that the latest branch is the one used for document the development version, but Read The Docs does not allow us to rename (or we do not know yet how to do it) this branch using a more meaningful name (e.g. develop). The default branch is stable (pointing to the documentation of the latest stable version of WireCloud) but it has proben to not be enough. We have created a ticket for improving this aspect.
I am trying to install SonarLint for Eclipse Ganymede (3.4.2) - and our project is very old, so we're using JDK 1.5 here. So is it possible to run SonarLint for JDK 5?
First of all, JDK 5 is so old, I can't really be certain of anything...
But here are some key factors that are important to understand:
Java code is analyzed by the Java analyzer (known today as "SonarJava"). SonarLint is a plugin in Eclipse (and other IDEs) that executes the SonarJava, and uses the results from it to annotate the code you are editing.
The JDK version that the SonarJava itself requires to run, is not the same thing as the JDK version of the source code it is able to analyze (= the subject of the analysis). For example, SonarJava may not run at all on JDK 7, but able to analyze code that is written in JDK 6.
If you use SonarLint in standalone mode, it uses its embedded version of the SonarJava, you cannot use another version. If you use SonarLint in connected mode, it uses SonarJava installed in the SonarQube to which you are connected. Here you have some freedom of choice in the version of the SonarJava, but not unlimited, because SonarLint may not be compatible with all versions of SonarJava, for example recent versions require a certain minimum version.
As per the product news, the current version of SonarLint requires Java 8 and more recent Eclipse than Juno. But you may be able to find an older version of SonarLint that can run in an older Eclipse, and support a version of SonarJava that is able to run on your JDK, and analyze code written for your target JDK version.
Based on the above points, you can dig into the older releases of SonarLint and find something suitable. These links should be useful in your search:
Product news of SonarLint for Eclipse. These also include links to the detailed release notes, which usually contain information about the version of embedded SonarJava
Releases of SonarLint for Eclipse
Homepage of SonarJava
I am installing the orion pep proxy but I think that I have not downloaded the correct version and I am having errors when using a local instance of KeyRock to validate and generate tokens.
I know that the latest version is 0.6.0 but i do not know how to complete the following command to obtain the last version:
./create-rpm.sh
Which is the difference between version and number?
Could you help me with this?
Thanks in advance
The idea of having those two numbers is to help the Release Engineer in debugging their releases, or changes they make to the packagin process itself. The "release number" indicates the version of the package, not the one of the software. E.g.: if you are packaging version 0.6.0, you usually will use release number 1; but, if you find out that you want to add some dependencies for the spec, or you want to update the package to change part of the packaging process, for example, and you try to replace the installed version with a new one, the system will claim the package is up-to-date; in that case, you increase the release number (as the software itself, that is, the Node.js files that constitute the PEP Proxy) hasn't change.
Hope this clarifies the behavior.
I got a site using Symfony 2.0 and want to upgrade it to last version of Symfony (2.4 from what I see on github).
I have already done one step: upgrade to 2.1. I fixed all issues and now I am ready to upgrade to 2.2 (I am not sure I could go to the current version directly). From my understanding, to do so, I need to retrieve the composer.json on github and add my own dependencies (only one). Is that right?
I tried to do it and it failed. Furthermore Symfony folder under vendor is empty after this attempt. I checked the composer.json for 2.2 and I do not see any symfony specified in it. Did I miss something?
Any help would be more than welcome :o)
ok the problem was only due to the fact that I was getting the composer.json from the wrong github repository. Be sure to use the one from the symfony-standard repository.
You can update from Symfony 2.0 to Symfony 2.4 directly. And yes, for it you need original composer.json file of Symfony 2.4 in symfony/symfony-standard repository and add to it your own dependencies if you have