Facing issue when try to fix corrupted plugin to rebuild. giving error as below.
Using- Sonatype Nexus™ Open Source Edition, Version: 1.8.0.1
========================================================================
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-enforcer-plugin' does not exist or no valid version could be found
Related
I managed to get the latest Yarn v1.13.0 installed on Xubuntu 16 with their curl installation instruction.
Now I'm getting this errors trying to install a project's dependencies.
An expected error occurred:
"https://registry.yarnpkg.com/event-stream/-/event-stream-3.3.6.tgz:
Request failed \"404 Not Found\
Same 'Not Found' message is displayed by the error url.
Seems to be caused by the security issue https://github.com/dominictarr/event-stream/issues/116?utm_content=educational&utm_campaign=2018-11-28&utm_source=email-sendgrid&utm_term=13952972&utm_medium=833442
How do I fix it? How do I find the project deps that use the corrupted version of event-stream?
Seemingly was caused by an older version of Nodemon prolly affected by the security issue above. Updating it to the latest version in package.json seemed to have helped.
I recently upgraded my Sonar Version to 5.5 and all the compatible plugins with it.
Here are the versions of the plugins installed:-
sonar-ldap-plugin-1.5.1.jar
sonar-javascript-plugin-2.13.jar
sonar-java-plugin-3.14.jar
sonar-build-breaker-plugin-2.1.jar
sonar-php-plugin-2.8.jar
sonar-findbugs-plugin-3.3.jar
If I use sonar-findbugs-plugin-3.3.jar, the Sonar is not getting Up and throwing below error :-
java.lang.IllegalArgumentException: The rule 'EC_INCOMPATIBLE_ARRAY_COMPARE' of repository 'findbugs' is declared several times
If I downgrade the Jar to sonar-findbugs-plugin-3.2.jar it works but fails to analyse the Project and throws below error :-
An API incompatibility was encountered while executing org.sonarsource.scanner.maven:sonar-maven-plugin:3.0.2:sonar
I have tried the versions - 3.3,3.3.1 and 3.3.2
Any Help ?
I am trying to upgrade to Jira 7 from version 6. I used the rapid upgrade method. It installs fine but I get an error on the browser “There is a problem with your Jira Access”. I went through the logs and I see that 6 plugins are failed to load during the Jira startup. Somehow they are disabled. I replaced couple of these .jar files with latest .jar and re-started the service, but I get the same error.
I also ran this query update pluginstate set pluginenabled='true' in the db but no luck.
Here is the log:
net.customware.plugins.connector.salesforce.salesforce-connector-plugin' - 'ServiceRocket Salesforce.com Connector Plugin - Plugin' failed to load.
Cannot start plugin: net.customware.plugins.connector.salesforce.salesforce-connector-plugin
Unresolved constraint in bundle net.customware.plugins.connector.salesforce.salesforce-connector-plugin [206]: Unable to resolve 206.0: missing requirement [206.0] osgi.wiring.bundle; (osgi.wiring.bundle=net.customware.plugins.connector.atlassian.jira-connector-plugin) [caused by: Unable to resolve 204.0: missing requirement [204.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.rpc)]
It was loaded from C:\JIRA_data\plugins\installed-plugins\salesforce-connector-plugin-6.0.8.jar.
We had the same problem last week, upgrading from 6.4.13 to 7.1.6. There are some incompatible plugins that crash Jira 7 when started, despite an apparently successful upgrade. Please refer to this page for details on the target plugins, as well as a way to solve the problem:
https://confluence.atlassian.com/jirakb/upgrading-to-jira-7-throws-a-nosuchmethoderror-on-com-atlassian-crowd-embedded-api-user-781396615.html
I am using STS 3.6.0 and during STS startup I am getting error:
org.eclipse.osgi.internal.framework.EquinoxConfiguration$1
Could not fetch model of type 'EclipseProject' using Gradle installation 'C:\build-tools\gradle-1.10'.
And I can't run Gradle task for the project. Any suggestion?
The error message looks similar to the error in this bug [1].
This bug is actually caused by a bug in Eclipse 4.4.2 [2]. There are a few things you can do to avoid this bug:
You can try a more recent version of gradle tooling (and/or STS)
install the workaround from eclipse update site as explained in comment 51 [3] of the Eclipse bug
[1] https://issuetracker.springsource.com/browse/STS-3922
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122#c51
I'm running Eclipse with RoboVM plugin and I wanted to try IOSDemo sample project described on robovm.org (http://www.robovm.org/docs.html). When creating the project in Eclipse and running it I got following error message.
An internal error occurred during: "Launching IOSDemo".
java.lang.IllegalAccessError: tried to access method java.lang.Object.clone()Ljava/lang/Object; from class soot.toolkits.scalar.LocalSplitter
I found out that it's related to JDK version (I'm running JDK 8.0 ea, build 112). When running on JDK 1.7.0_45 and building the project on cmd line it builds and runs OK.
Is it known problem, is there any workaround or fix? Thanks
This is most probably due to a bug [1] in the recent early access builds of Java8. It looks like the bug was resolved a few days ago but as far as I can see the fix didn't make it into the b113 build. Please use the latest Java7 release or an earlier Java8 EA build until a Java8 build is available with this fix included.
[1] https://bugs.openjdk.java.net/browse/JDK-8026394