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.
Related
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.
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 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 wonder if you can help me over here:
For some reasons, my NuGet packages were successfully built but they were using the previous version not the latest update.
For example:
For version 1.0 = I have property name = Jane
For version 2.0 = I updated the name property to = James but still getting Jane for the subsequent NuGet package updates.
I have checked the log that TeamCity actually did download the latest update from Mercurial server but still giving me the last version after build inside the package.
Thank you.
Finally, I knew what was wrong here.
I need to build the NuGet solution first and then continue with NuGet packaging and publishing in TeamCity.
I hope this answer will save somebody's time in the future.
I am using Eclipse Helios (3.6). I want to use Mercurial for version management of the program. I have take the help of the below link to find out the plugin but not got any success:
Mercurial Eclipse Plugin
Can any one please help to install Mercurial plugins inside my Eclipse and I also don't know how to use also. I have gone through the video also but not clear.
http://www.youtube.com/watch?v=9OBg6Zv0Tns
My question is that I want to use Mercurial in my project for version control. I know what Mercurial is, but don't know how to use it.
I want to know what is the initial setup that I have do if I want to use Mercurial set up in my project.
When I am trying to add new software It is giving me following error.
the 'Duplicate Location' error message in your screenshot would indicate that there is already an update site setup for that URL.
In the screen before doing the 'add repository' look at the list of current update sites and you may find one for Mercurial already. Make sure it is selected and a list of all the features for that update site will be listed for you. Then you can select the MercurialEclipse and MercurialBinaries features and install then in Eclipse
The Mercurial Eclipse homepage is here: http://javaforge.com/project/HGE.
They have installation instructions there:
[...] you can get the plugin easily using the Eclipse Update Manager, just click Help → Software Updates in Eclipse. The Eclipse Update Site for MercurialEclipse is available at this URL:
http://cbes.javaforge.com/update
If you are not familiar with getting new software and updates to Eclipse, please read this article.