I am trying to install mbtiles plugin for geoserver 2.9. I have successfully installed geoserver in tomcat 7.0 (in windows 10).
I downloaded geoserver from [http://ares.opengeo.org/geoserver/master/] It works fine without any plugin installed.
But when I try to install plugin mbtiles into the lib folder it gives me error message.
HTTP Status 404 - /geoserver
type Status report
message /geoserver
description The requested resource is not available.
Apache Tomcat/7.0.59
I know my tomcat is working fine and geoserver is there in the webapps folder.
I downloaded the mbtiles plugin from: [http://ares.opengeo.org/geoserver/master/community-2015-11-30/]. I know that my version of mbtiles plugin and geoserver is same. That is what was mentioned in geoserver documentation page.
I have 3 files in the mbtiles plugin:
gs-mbtiles-2.9-SNAPSHOT.jar
gt-mbtiles-15-SNAPSHOT.jar
sqlite-jdbc-3.8.6.jar
If I remove those files from lib folder then my geoserver works fine.
Can anyone suggest what am I missing here??
I tried with other versions of geoserver but I get the same error message like above.
Any help is appreciated.
Cheers
I had this problem for a while. At first look at log file which is in this directory \logs\wrapper.log it shows the errors and why they prevent running geoserver's service.
One of dependencies which mbtile plug-in has is wps plug-in. This plug-in is not loaded into geoserver by default. So before installing mbtiles plug-in at first install geoserver wps plug-in from this link
Select and download wps
Another thing that I have fount is that some times sqlite-jdbc-3.8.6.jar which is in mbtile's zip file has a bug.It is quite an old version. So if your problem exists replace this file with newest version from here
sqlite-jdbc download link
I hope this helps some one. If yes please vote it up.
You have to put it on:
/usr/share/opengeo/geoexplorer/WEB-INF/lib
Source: http://suite.opengeo.org/docs/latest/intro/installation/redhat/postinstall.html
Well, since opengeo-geoserver is a custom build from geoserver, it has some modifications that won't let you simply run the original geoserver plugins.
You'll have to open the jars and decompile the class files to modify the code of the plugin to match the structure of opengeo-geoserver...
Related
Issue : I am following the URL. https://docs.fedoraproject.org/en-US/java-packaging-howto/packaging_maven_project/ to create a spec file for the rpm package.
In the website "BuildRequires: maven-local" is mentioned in the spec file.
but when I tried to search 'maven-local' using yum search maven-local command, I could not find anything and as I was not able to install the component, I'm getting an error when I am trying to do rpmbuild.
Note: I even installed maven separately in my system but it did not help me to fix the issue.
(On Elasticsearch version 6.5.1)
How can I build/run Elasticsearch from source with local plugins?
I've tried the following command to install the plugins:
./distribution/build/cluster/run\ node0/elasticsear-6.5.1-SNAPSHOT/bin/elasticsearch-plugin install file:/<path_to_plugin_zip> and that says it successfully installed the plugin.
However, when I run elasticsearch via ./gradlew run --debug-jvm, it cleans out the contents of that directory before running ES.
The reason I installed the plugin into that particular directory is that I put a debugger in the PluginsService.java file, and saw that the Path pluginsDirectory parameter in the constructor was set to /Users/jreback/Desktop/elasticsearch/distribution/build/cluster/run node0/elasticsearch-6.5.1-SNAPSHOT/plugins.
So, how can I get my plugin installed on my local ES version and run ES such that the plugin code doesn't get removed as the process starts up? Many thanks in advance!
FWIW, I got this working with some manual code changes (there may be or likely is a more recommended way to do this, but this worked for me).
In my ES checkout, I made the following code change to server/src/main/java/org/elasticsearch/env/Environment.java:
replace this line: pluginsFile = homeFile.resolve("plugins"); with pluginsFile = Paths.get("<path to plugin directory");
(Also, you must import java.nio.file.Paths at the top of that file).
The directory structure for the directory you listed above should look like this:
- plugin parent directory (should whatever you put in the Environment.java file)
- plugin directory (name of the plugin)
- plugin-descriptor.properties file
- plugin jar file (generated from building the plugin in some prior step)
Then you should see that it loaded the plugin you've just added in the logs when you start up ES again.
I am trying to downloading Sonarqube from below link but it is always failing after after some time. can some body please share me another link from where i can download it.
https://www.sonarqube.org/downloads/
You can try downloading it from Maven Central if you constantly have issues with the official Website.
Just follow these steps:
Open http://repo1.maven.org/maven2/org/sonarsource/sonarqube/sonar-application
Go into the folder x.y.z that is the version you want to download ("6.3.1" for instance)
Download the file called "sonar-application-x.y.z.zip"
I'm trying to do code analysis of Java unit test using maven sonar plugin. But the plugin doesn't seem to take into account my sonar properties "sonar.*". I've tried to modify simple examples and it did work either. According to MSONAR-70, the issue has been fixed and I'm using the version 2.4.
For the test, I've tried it on a simple case:
Clone sonar-examples.git
use the project sonar-examples/projects/languages/java/maven/java-maven-simple as example
Renamed src/main to src/test
In the pom.xml, add to the properties section :
<sonar.sources>src/test/java</sonar.sources>
<sonar.binaries>target/test-classes</sonar.binaries>
Run mvn sonar:sonar.
--> the code analysis didn't took into account my settings. The project is created on SonarQube but code as not been analyzed.
If I use the sonar-runner command line, it's analyzing the code:
sonar-runner [...] -Dsonar.sources=src/test/java
-Dsonar.binaries=target/test-classes
-Dsonar.language=java
-Dsonar.sourceEncoding=UTF-8
-Dsonar.projectKey=org.codehaus.sonar:example-java-maven
-Dsonar.projectName="Simple Java Maven Project"
-Dsonar.projectVersion=1.0-SNAPSHOT
According to a previous revision of the question, the OP solved their problem like this:
We were using SonarQube 4.0 version. Updating the version to 4.4, made the properties be taken into account.
That was in 2014; the current version now is 5.5.
The steps to upgrade can be found here:
Stop the old SonarQube server
Download and unzip the new SonarQube distribution in a fresh directory, let's say NEW_SONARQUBE_HOME.
Start it using the default H2 database and use the update center to install the plugins you need.
Manually install any custom plugins.
Stop the new server.
Update the content of the sonar.properties and wrapper.conf files located in the NEW_SONARQUBE_HOME/conf directory with the content of the related files in the OLD_SONARQUBE_HOME/conf directory (web server URL, database settings, etc.). Do not copy-paste the old files.
If a custom JDBC driver is used, copy it into NEW_SONARQUBE_HOME/extensions/jdbc-driver/.
Back up your database.
Remove the data/es directory.
Start the new web server
Browse to http://localhost:9000/setup (replace "localhost:9000" with your own URL) and follow the setup instructions.
I saw the light and install the joda-time plugin for grails.
However, when I tried to commit my changes to source control I realised that grails had located the files in:
C:\Users\Steve\.grails\1.1.1\plugins
instead of somewhere under the project directory of:
f:\grails\projects\myproject
Yeah I'm using windows :-\
So now when someone pulls down my changes from source control they are missing all the joda-time plugin lovelyness and they are wanting to spank me :)
What should I be setting so that grails doesn't put anything under my user directory?
(It isn't installed as a global plugin - just as a project one - at least I think so, I ran "grails install-plugin joda-time" )
Many thanks in advance.
P.S. Currently listening to Plug In Baby by Muse....how coincidental :D
The plugin is listed in application.properties, so when someone gets your code Grails will install missing plugins the first time they run 'grails run-app' or other commands.
If you want to revert to 1.0.x behavior just create grails-app/conf/BuildConfig.groovy with the line
grails.project.plugins.dir='plugins'
and your plugins will be in with the rest of the project files.