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"
Related
I need your help.
I downloaded maven 3-5-0-src.zip file from maven site. I started to unzip process after a few seconds I got an this error.
Error: System doesn't find this path.
Cannot create
C:\Users\AppData\Local\Temp\wz85b2\apache-maven-3.5.0\maven-core\src\test\resources\org\apache\maven\extension\test-extension-repo\org\apache\maven\core\test\test-lifecycle-and-artifactHandler\1\test-lifecycle-and-artifactHandler-1.pom.sha1.
I can't install maven on my computer. How can solve this?
The ...-src.zip file only contains the source files for your reference.
You need to download and install the binary zip file at apache-maven-3.5.0-bin.zip if you're planning to use maven to build stuff.
Otherwise, the above error looks suspiciously like a Windows path length problem.
I am trying to build aperturejs with Readme.md instructions.
I cloned the repository and tried the command mvn clean install in the root directory of ApertureJs.
I got the following Build Error as in the screenshot,
I am using the latest version of Maven - 3.3.9
Thanks in advance.
By reading the error in your console, I could feel that you are not authorized to access the particular repository, which is shown in your console.
Copy the repository url and try it from a browser - hope you will not be able to access the repository, since you are not authorized.
Raise appropriate access and after getting access, then try mvn clean install.
Below is the Quick fix till the time you get the access:
Copy and Paste the respective jar/pom/folder from your colleague machine, in your .m2/repository/...
Run the mvn clean install with -o option so that it will look into your local repository for building your application
Thank you. The issue is solved. I posted this issue to Uncharted Software's Salt Repository and exactly like Clement Said, I was trying to access a repository that no more has access publicly. Therefore they gave a workaround.
It is available here -> https://github.com/unchartedsoftware/aperturejs/issues/22
Thanks a lot.
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...
I am using Sonar 4.5.1 and sonar-pdfreport-plugin-1.4 to run the build. PDF report is not getting generated an is showing below message : Internal error: Can't retrieve project info. Parent project node is empty. Authentication?.
I saw a bug posted for this (https://jira.sonarsource.com/browse/SONARPLUGINS-3854) but would like to know what is the workaround available for this issue. User Authentication is already set for this in General Settings->Pdf report but doesn't work either.
This issue has been fixed in commit a49b8f61afbf47b5f7976d0a759cb0efcd6c5bce.
For now you cannot download jar with this fix, but you can download sources and build custom version:
fetch sources (by git clone https://github.com/SonarQubeCommunity/sonar-pdf-report.git or download zip)
execute maven command mvn clean install
copy generated jar to sonar/data/extensions/plugins
I uploaded file using mvn deploy:deploy-file but I uploaded wrong file. How can I update or remove this file if I don't have direct access to nexus?
Ask your Nexus admin to delete it through the UI.
If this is a SNAPSHOT, you also have the option of deploying the same file using the same version number. That way, when others reference 1.2.3-SNAPSHOT, they get the intended version. And eventually the bad SNAPSHOT will probably get deleted through a scheduled job. This is a decent workaround while you contact your Nexus administrator.