SonarQube's web service api/tests is deprecated since SonarQube 5.2.
What would be a new good way to access this information?
api/tests has been deprecated in 5.6, but it still exists.
The related tickets are SONAR-7619 and SONAR-7623, but we haven't add any description...
The reason of this deprecation is that this feature is not highly used (as most IDEs provide this information easily), and it does not bring a lot of value in SonarQube.
For the moment this API is still there but it may be removed in SonarQube 7.X.
Related
is it possible to reduce/limit the Qt API features to specific earlier versions?
In the API documentation there is e.g. information that methods are introduced with version major.minor.
Can you restrict the API features of an installed newer version to the earlier ones without installing?
I don't think so, because there are no version conditions in the header files.
But maybe you know for sure...
Is there a tool which detects the usage of incompatible API to a specific version?
Thanks
Markus
Pentaho Data Integration 8.0.x is using Janino 2.5.16, released in 2010 for compiling the User Defined Java Class step. There is a JIRA in pentaho for updating this to use a newer Janino version which would bring new java 8 related features in pentaho v8.2.0 GA. But there is no info on when will this be released.
Is there any other way I can use a newer janino version (janino-3.0.8.jar) with exiting pentaho for UDJC? I tried to copy updated jar in the lib and also added commons-compiler-3.0.8.jar to fulfill dependency. Now when I open Spoon, I get the following error:
Please advise on how this can be achieved. I understand that just replacing the jar may not be enough but just want if something else can be done.
This is not easy. Even now, since you got ClassNotFound, public api of janino is changed. Some classes are removed some are changed. What is actual needs to update it?
If you need really complicated business logic, then create custom plugin. Documentation and tutorials are available and you can look into sources of current builtin plugins (sources are available on github).
What important new version of janino has, that old doesn't (beside java8 support)? Checkout kettle engine, look into sources of UserDefinedClass step, change code to support new janino version, test and make own build of pdi kettle, and try to send push request to maintainers of repository.
Any of this quite complicated, This plugin is builtin into engine, and you have to make own build. Own build means, you have to support it by yourself. This is non trivial, project is huge and now even bigger and continue evolving, I spent several days to make my first custom build (version of 4, was in ivy) just for purpose to know better and debug complicated cases, and it used never in production.
Maintainers of repository must have good reason to include your changes into stream, it must be well tested and it is long procedure and most probably doesn't worth it. A lots of changed since 2010, I probable have seen in release notes, new version of java already have abilities to compile at runtime.
My advice is to make you own plugin.
I am supposed to migrate a website from Sitecore 7.1 to 8.0
I am mainly concerned with Lucene Search and indexing part of search functionality which is to be migrated as well.
I just need a heads-up for errors and bugs for the same and a question (for which no answer was found on web) is that will the search functionality be severely affected by the migration? what care should be taken while migrating?
Any helpful and relevant links are appreciated.
From what comes into my mind, there were certain changes in search configuration
contentSearch/configuration/defaultIndexConfiguration/analyzer
has moved to:
contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/analyzer
there were also changes in ContentSearch namespaces
Also check EncodedNameReplacements setting for media library as it may break some of your links.
If you are using modules - check modules compatibility table by this link https://kb.sitecore.net/articles/541788 as some of them may not yet be available for 8.0. Sitecore.Kernel is now on .NET 4.5 so please keep .NET version updgrade in mind as well
I usually get two clean installations with following versions and check configuration changes in diff tool, where applicable, you may find this practice helpful as well.
Please go carefully through upgrade notes from Sitecore and consider if they have to be performed on your solution. Official upgrade notes to 8.0 can be found here https://dev.sitecore.net/en/Downloads/Sitecore_Experience_Platform/8_0/Sitecore_Experience_Platform_8_0.aspx (but you may need SDN account to access that)
Some other useful references:
https://theagilecoder.wordpress.com/2015/03/09/keystone-considerations-when-upgrading-to-sitecore-7-5-or-sitecore-8/
http://laubplusco.net/quick-tip-upgrading-sitecore-fast-easy/
http://www.velir.com/blog/index.php/2015/06/25/the-art-of-the-sitecore-upgrade/
I have an MVC App which uses Azure AD, it works very well using the WindowsAzure.AD.Graph.2013_04_05 helper project that Microsoft made available. This project is now outdated, but looking at the new Nuget Package, the two require code changes.
I have two questions, How long can I use the old one before I find myself locked out of my own app. Second, has anyone migrated between them?
What I have is very simple, its just an Auth Filter which checks if a user is in one or more groups.
You should have at least a year from the announcement of a REST version being deprecated; a REST version is not the same as a NuGet package version, so you'll need to understand the underlying version in use.
Please refer to this Microsoft support policy on Azure-related REST APIs and libraries: http://support.microsoft.com/gp/azure-cloud-lifecycle-faq
When i try to use the statement google.load("dojo", "1.6.1") in a web app I am developing, I receive the error:
Module: 'dojo' with version '1.6.1' not found!
This latest version of dojo, enables a certain amount of support for IE 9.0, and that is why I need to reference it. Is this supported by Google as a library? Either way, if anyone has suggestions as to how I can work around this?
1.6.1 is not yet in the Google ajax library repositories. See the latest version note here. I'm sure it will be within a day or two. There is a note on the dojo download page in big red letters saying that the CDN's are still behind on 1.6.0 and saying where to get notified when they are updated.
You can always use the "1.6" nomenclature to always have the latest version and your app will move up to 1.6.1 as soon as it hits the Google CDN. If a couple days is really going to make or break you you should consider compiling and using your own local version. Dojo makes this really easy.