When I try to install the openJML plugin from the update site at http://jmlspecs.sourceforge.net/openjml-updatesite I get the following error:
An error occurred while collecting items to be installed
session context was:(profile=epp.package.java, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: ... (with about 4 or 5 jars)
I've tried installing previous versions of the plugin, but all result in similar "Artifact not found" errors. Anyone have any idea why this isn't working? Or have a workaround I could use to get the Eclipse plugin to work?
Thanks in advance!
A bug report has already been opened, but no one seems to care (yet):
http://sourceforge.net/p/jmlspecs/bugs/397/
Seems that you have to compile your own version of it.
Related
I'm getting this error "invalid version 0 on git_proxy_options" from libgit2. This did not happen until very recently (I have recompiled my code so it may be a version issue). I'm not using a proxy. Does anyone know anything about this? What causes this message? Is there anything I can do to stop the failure? Either a fix or or a work-around will do.
Specifically, I am using the Rust crate git2 version 0.13.23. I am doing a fetch that triggers the error. This is on Fedora 34 on x86_64. I have searched on this but there does not seem to be any matches that help.
git2 = {version="0.13.22", features = ["vendored-libgit2"]}
in Cargo.toml fixed the issue.
Interesting...
I had upgraded libgit2 to 1.3.0 from 1.1.1. That broke my existing cargo install, so I unpacked the previous libgit2.so.1.1 with a symlink to libgit2.so.1. That's when this error condition showed up. After thinking a bit I decided to symlink libgit2.so.1.3 to libgit2.so.1.1 and it built my new cargo version which linked to the new libgit2.so.1.3. Then I deleted my libgit2.so.1.1 stuff. Kinda weird, and usually you expect things not to work when it has been linked to a previous .so version.
I just cloned https://github.com/intuit/karate.git project and getting error message about missing "karate parser" package.
I tried to pull latest version of the katare which is 0.9.5 but still getting errors.
what am i missing?
here is the screenshot of error messages.
That code depends on generated code, so you have to do a Maven compile.
Why don't you follow the developer guide: https://github.com/intuit/karate/wiki/Developer-Guide
When updating the plugin data (http://<jenkins>/pluginManager/checkUpdatesServer) I get this exception:
java.security.cert.CertificateException: No subject alternative DNS name matching
updates.jenkins.io found.
at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214)
at sun.security.util.HostnameChecker.match(HostnameChecker.java:96)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455)
at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:436)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:200)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted
(X509TrustManagerImpl.java:124)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1596)
Caused: javax.net.ssl.SSLHandshakeException
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
(..)
Can somebody explain the issue? Is it an issue with our configuration or with the updates.jenkins.io site? Solutions / workarounds would be great.
Last successful update was 26 days ago.
We run Jenkins with the option
JAVA_ARGS="(..) -Djsse.enableSNIExtension=false"
Jenkins is at 2.107.1, but prior 2.89.4 had the same issue.
I ended up looking for the string "updates.jenkins.io" and got this match:
hudson.model.UpdateCenter.xml:5: <url>https://updates.jenkins.io/update-center.json</url>
Reading about this kind of error I suspected that this link might be outdated. Trying to locate a newer version I found this hudson.model.UpdateCenter.xml and it contained:
<url>http://updates.jenkins-ci.org/update-center.json</url>
So I updated my version and was able to update my plugin data.
I tried to find the file in the Jenkins repository but did not find it, perhaps it is generated at runtime. However this search seems to confirm that this URL is a good choice.
Just to preface this, I'm a Mura newbie.
I am attempting to create a new site in Mura 6.2 by importing the 'MuraBootstrap3' bundle - https://github.com/blueriver/MuraBootstrap3Bundle .
Once I create the site and import the bundle, I immediately get the following error message:
It appears to be an issue with SQL executing the insert command, but I'm not entirely sure why. Am I missing something in the setup? What am I not doing correctly?
Thanks!
Edit: I should mention that The database has already been setup and my default installation is running just fine.
Guust was correct, however the bundle you're looking for is here:
https://github.com/blueriver/MuraBootstrap3Bundle/blob/6f9e86a15fbd10d4b88b77dd2f5be467ce8f3582/MuraBundle_default_2015_03_30_12_29.zip
The bundle you've downloaded is for Mura 7.
I believe the last version of the bundle for Mura 6.x is the following commit:
https://github.com/blueriver/MuraBootstrap3Bundle/commit/c62e8fcfc8ba25fe1ca1ef186af1898e894a3c8e
This is the file I believe you'll need:
https://github.com/blueriver/MuraBootstrap3Bundle/blob/c62e8fcfc8ba25fe1ca1ef186af1898e894a3c8e/MuraBundle_default_2016_05_03_17_01.zip
Refer the raised jira issue in below link .
https://wso2.org/jira/browse/IDENTITY-4633
Any solutions for solving this issue..,
We tried to temperorly solve this issue by editing sqlscripts.java file by downloading it from github, compiled it and tried to pack in same jar file (using winzip, as jar files are zip finally).
As part of the change we had removed TOKEN_SCOPE column from relevant sql query, but still error in log describes 'invalid column TOKEN_SCOPE'
Kindly suggest to make any further changes or share me the jar file.
I am using wso2 identity server v5.1.0
Thanks.
This issue seems to be already reported in https://wso2.org/jira/browse/IDENTITY-4532
This issue is already fixed in 5.2.0 which will be released soon. You can try the 5.2.0 beta from https://github.com/wso2/product-is/releases/tag/v5.2.0-beta
You can find the fix from the PR in the jira I have pointed.