This is a follow-up question of "ClearCase snapshot views on ClearTeam Explorer", about the actual installation.
I installed CTE plugin version 8.0.0 into Clearcase - and of course, I see the dynamic views just fine.
Now, I would like to see snapshots as well.
I see the discussion on ccrc.zip and ccrc_extension.zip.
And "Rational ClearCase Release Notes version 8.0.1.x"
So do I need to update CTE 8.0.0 (already installed) to 8.0.1.6? Do I also somehow install ccrc.zip and ccrc_extension.zip.
I am using Helios version of Eclipse and find that IBM documents lacking on newer versions of Eclipse.
do I need to update CTE 8.0.0 (already installed) to 8.0.1.6
Yes, or the CTE plugin wouldn't be able to display snapshot views.
But that assume that your ClearCase web server is also at least at 8.0.1.6.
The installation/update should be similar for newer version of Eclipse, but do check the Rational ClearCase System requirements matrix to see if your version of Eclipse is supported.
Related
For my app i need FFmpeg, so i went to official website, for windows builds it said go here :-
https://github.com/BtbN/FFmpeg-Builds/releases/tag/autobuild-2021-01-20-13-01
But now i have a problem.
Which version of ffmpeg is newer ?
ffmpeg-N-100679 or ffmpeg-n4.3.1-29 ?
Is that "N" version unstable and "n4" version stable ?
Any help would be appreciated 🙂
Which is newer?
ffmpeg-N-100679-g24dc6d386c is newer. It is from the git master branch, and is a snapshot of the current, up-to-date FFmpeg code for the date it was released. It corresponds to commit 24dc6d386c (note I omitted the g prefix) which is from 2021-01-20.
4.3.1 is from 2020-07-11. Since new features are not backported to release versions (only certain bug fixes) it is just an extension of 4.3 which was released on 2020-06-08. The FFmpeg Download page contains the dates for releases.
So ffmpeg-N-100679-g24dc6d386c is about 7 months newer than 4.3.1.
Which do I use?
ffmpeg-N-* for general users. If you want the latest code and features. Required for anyone who wants to submit a bug report. If you experience a problem with the newest release. It is stable ~98% of the time I'd guess from using it over many years.
Release version: if you are required to stay within a certain API version. For distros, distributors, users of the FFmpeg libraries, etc.
Versions with N-xxxxx are nightly builds / snapshots and are unstable (but newer). Use them only for testing or if the last release has a bug that is already fixed and only available in the nightly.
Otherwise I recommend to use the latest release (currently 4.3.1). This is typically more stable.
How can I download the user docs/documentation/manual for older ElasticSearch for offline usage?
Recently, the online documentation for older versions of ElasticSearch (for example, ElasticSearch 1.3.2) started to show this message:
WARNING: Version 1.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
What worries me most is the may be removed part. Right now, we don't have the resources to upgrade our software to support the latest ElasticSearch version, so we will need to keep working with the older versions for a while. How I will be able to give maintenance to our software if the Elastic company decides to remove the documentation for older versions of ElasticSearch? There is any way to download it from https://www.elastic.co/ or build it from some repository?
Thank you very much for your help!
You can clone the official elasticsearch repository to a local machine, change to branch to the version you want, in your cause branch 1.3, then you will have the documentation in the directory docs.
The documentation is in the .asciidoc format, you can try build it following the official instructions, or using other asciidoc to pdf/html converters.
I just upgraded from SonarQube 6.1 to 6.7.7. For SonarJava, it automatically installed 4.15.0.12310 (it was 4.10.0.10260 before). In the Marketplace, when I hover over the available versions from 5.0-5.13, it says “Incompatible”. When I hover over 5.13.1+, it says “Requires system update”. What does it mean for it to be incompatible if it doesn’t require a system update?
I am seeing this with various other plugins as well, such as SonarPython, which had 1.8 automatically installed. I had to manually install 1.9.1 in order to get this bug fix (which is why I originally upgraded the server): https://community.sonarsource.com/t/python-s1481-code-smell-unused-local-variables-should-be-removed-false-positive-with-string-interpolation/8961
I could manually install newer versions of other plugins as well, but I don’t know if that’s safe.
I also can’t find an official plugin compatibility matrix, since this only shows 7.9+: https://docs.sonarqube.org/latest/instance-administration/plugin-version-matrix/
Incompatible means that the plugin does not work with the version of SonarQube you have installed.
An example of an incompatible plugin would be one where the plugin relied on an API that was removed in your current SonarQube version. You may be able to use that version of the plugin if you downgraded your SonarQube instance to a previous version.
Requires system update means you need to upgrade SonarQube in order to install the plugin.
For what it's worth, the states as described by the API documentation are:
Update status values are:
COMPATIBLE: plugin is compatible with current SonarQube instance.
INCOMPATIBLE: plugin is not compatible with current SonarQube instance.
REQUIRES_SYSTEM_UPGRADE: plugin requires SonarQube to be upgraded before being installed.
DEPS_REQUIRE_SYSTEM_UPGRADE: at least one plugin on which the plugin is dependent requires SonarQube to be upgraded.
http://www.springsource.org/downloads/sts-ggts
I am trying to download new STS tool. On the above site I find
Milestone Version and Release Version. Can anyone tell me what these terms mean? Which is Users version to be used and is completely developed and not under-development?
The release version is the one you want, "release" means it's considered to be done and ready for the public. "Milestone" means it's a stable checkpoint made available for community developers to test. You'd pick the milestone one if there are new features or bugfixes you want to try out that haven't been included in a release yet.
Is there a stable version of SlickGrid that should be used for deployment or is it recommended practice to take a snapshot of the github repository and use that for deployment? I see a number of tags but none that is very recent (e.g., tag 2.02 is 7 months old and there have been lots of commits since then).
Up to now I have been tracking the SlickGrid github repository for development but I'd like to fix to a version before deploying. It would be nice if there was a recommended stable package download available (maybe there is and I haven't come across it?).
SlickGrid 2.1 is available as a release on github - official mailing list announcement here.