I am using sonarqube 4.5.4,and hence the sonar.profile is deprecated for the sonar version of 4.5.4,Please suggest what alternative tag can be used for the same.
Regards,
Namratha
There's no replacement for this property. Instead, make your project-profile associations via the UI.
Related
I have the following case that is not covered by maven-enforcer-plugin (https://maven.apache.org/enforcer/enforcer-rules/index.html):
5 profiles:
scala-2.11
scala-2.12
spark-2.2
spark-2.3
spark-2.4
and the following enforcement rules:
exact one of scala 2.11 & 2.12 must be activated
exact one of spark 2.2, 2.3 & 2.4 must be activated
spark 2.2 & 2.3 is not compatible with scala 2.12
The existing maven plugin is too weak to implement this. What other options do I have?
It is relatively straightforward to write your own enforcer rule. I would aim for that.
On the other hand, I would check if it is really necessary to have all these profiles and to activate/deactivate them by command line.
I am using the YangUI on the REST API of ODL(Oxygen Release) and I want to use the config features of opendaylight-inventory but I can only see the operational ones. Like this.
¿What can be the problem?
I have solved installing the same features on a previous ODL release. I don't know why but I can't see config features on Oxygen.
I was reading https://www.elastic.co/blog/deprecating-rivers which stats that ES rivers (plugin) are getting deprecated. i.e. any plugin directly integrated with ElasticSearch server will no longer work beyond ES 3.x onwards.
Couchbase plugin is one of those kind.
I searched all the documents of couchbase plugin at http://developer.couchbase.com/documentation/server/4.5/connectors/elasticsearch-2.1/elastic-intro.html but could not find if they are using deprecated way or not?
Does anyone know? Should we keep using couchbase plugin or should start planning to write data directly to ES using our application.
We have couchbase data getting replicated to ES using couchbase plugin and XDCR.
I'm the maintainer of the Couchbase ES transport plugin. As Roi mention in his answer, the plugin doesn't use rivers, so it won't be deprecated. It currently supports any version of ES from 1.3 to 2.x, and I'm working on adding support for 5.x. It's taking a bit longer, because ES 5.x broke some configuration sharing features in unexpected ways.
I'd suggest always looking at our github repo for the latest plugin releases:
https://github.com/couchbaselabs/elasticsearch-transport-couchbase
The Couchbase plugin is not using Rivers, there is another River plugin which is not longer valid.
take a look here: https://github.com/couchbaselabs/elasticsearch-transport-couchbase
SonarQube Web Plugin created a lot of False Positives, because of the use of the JSP custom tags with "style" name.
Environment:
SonarQube 5.1
SonarQube Web Plugin 2.3
Jenkins 1.611
Sonar Runner 2.4
This is a bug in the rule. It marks all elements which local name is equal to style. Authors of the SonarQube Web Plugin have created an issue: SONARWEB-30. It will be fixed in 2.4 version.
The project https://github.com/neo4j-contrib/developer-resources/tree/gh-pages/language-guides/java/spring-data-neo4j produces a warning:
Class 'org.springframework.data.neo4j.support.index.IndexProvider' is marked deprecated
I use Spring Boot. The managed version for spring-data-neo4j is 3.2.2.RELEASE
Does anybody know how this deprecation can be resolved?
Yes that is intentional, as the "manual" index APIs are scheduled to go away in Neo4j 3.0 this is a hint that using the manual indexes will need to change then.
As Michael Hunger pointed out this deprecation can be ignored. Wit Neo4J 3.0 there will be an alternative available.