I'm learning Kotlin and Spring Boot and recently am running into an antivirus warning about a file called oneeva.a!ml while building my project and gradle downloads kotlin-util-io-1.6.21.jar
org.gradle.internal.resolve.ArtifactResolveException: Could not download kotlin-util-io-1.6.21.jar (org.jetbrains.kotlin:kotlin-util-io:1.6.21)
This happens when I try to build a new Spring Boot project. No one else online seems to have encountered this before. Does anyone have any guidance?
edit: This problem occurs when creating a new spring initializer build using Gradle but not on Maven.
edit 2022-05-14: New gradle projects are working fine now without any differences in configuration
I also got the same issue after creating a new project on Android Studio Bumblebee | 2021.1.1 Patch 3 . I tried manually downloading kotlin-util-io-1.6.21.jar but it is getting blocked on my Windows machine due to some virus detected. Downgrading to kotlin-util-io-1.6.20 worked for me.
Got it resolved by updating your Windows Defender database through Windows Update.
I just updated antivirus database to the latest version, works again.
See: https://youtrack.jetbrains.com/issue/KT-52297
Related
I downloaded Intellij Idea and was using it just fine for a while. I don't know what happened between the time it was working and when it started to not work. When I would click the shortcut, my mouse would give me the loading wheel and then nothing would happen. In task manager, there is a task called "IntelliJ Idea" running. I uninstalled and reinstalled twice, and then installed it with the JetBrains toolbox, but this is still happening. I saw another thread about this from 4 years ago, but none of the solutions worked for me.
Other thread: Intellij IDEA won't start
I thought I would post this since I recently came across a similar issue with IntelliJ IDE Community Edition but for MacOS and it seems like the same issue could potentially happen on Windows.
I was using the JetBrains Toolbox to manage the installations and updates and after a recent update, when trying to start the app it would simply attempt to start and get killed straight away. After not having much luck with the logs I eventually found the exception that was being thrown when it attempted to start:
java.lang.UnsupportedClassVersionError: com/intellij/util/lang/PathClassLoader has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
So from this I realized that the app was trying to run with an older version of Java and I found how to change it in this post. In my case the 'idea.jdk' file was located in '/Users/user/Library/Application Support/JetBrains/IdeaIC2021.2' and for some reason was not updated after the application update.
Build and deploy settings are missing from ibm mobile first development server hybrid project.
After clicking on Run as(as in attachment) even from a newly created project..not finding any options. Unable to start application.
Please let me know why it is happening, if any have faced this error before. The image below shows that there's nothing in "Run As...".
Something is wrong with your installation.
Try again in a new Eclipse workspace.
If it fails as well, re-install the Studio plug-in in a fresh Eclipse instance.
I'm trying to run a trivial http echo app against the 3.50 CE runtime and I get the following stack trace(s) when I try to run
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Failed to deploy artifact 'default', see below +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
java.lang.NullPointerException
at org.mule.module.launcher.DefaultArchiveDeployer.guardedDeploy(DefaultArchiveDeployer.java:274)
...
Exception in thread "main" java.lang.NullPointerException
at org.mule.module.launcher.DefaultArchiveDeployer.addZombieApp(DefaultArchiveDeployer.java:325)
Additional context:
I've just started working with Mule (using the Eclipse Plugin). I initially had the trial package which is configured for Enterprise edition and I had that working with some of the trivial examples - hello world and echo.
I then downloaded the community runtimes and changed the targets on the projects, at that point I had been getting No Application Name errors, and I tried rebuilding them as new projects with CE targets from the start.
I also had been running them as mule applications, but this page
https://developer.mulesoft.com/docs/display/current/Studio+in+Eclipse
seems to indicate I must use maven ( I've set that up - although the automatic POM management doesn't seem to be working) but I still get the above failure.
There's no indication of why it's failing, as far as I can tell my projects output is valid.
Any suggestions welcome.
For what it's worth this is working now (fixed it shortly after posting the question even though it's been a blocker since yesterday).
If anyone else runs aground of the same issue..
I wasn't using the latest Community Edition runtime so I upgraded using the eclipse plugin install from (http://studio.mulesoft.org/r4/studio-runtimes).
I think this might have had something to do with it as I had previously been using the r4 plugin (http://studio.mulesoft.org/r4/plugin) with the Eclipse hosted 3.5 CE. Possibly the plugin is not backward compatible with the Runtimes.
basically once I completed the install and restarted I upgraded my project to use the new CE (changing the project setting and the flow xml). It worked first time.
Oddly all my Mule-Maven options have disappeared, but that's a separate question.
I have a problem when deploying my Worklight project on the server . It shows the following Error Message :
FWLSE3041E: No MBean found for Worklight project 'MyProject'. Possibly the Worklight runtime web application for Worklight project 'MyProject' is not running. If it is running, use JConsole to inspect the available MBeans.
and when I tried to preview my application it showed this message :
SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized:420'
I had the same issue using Worklight 6.2 CLI, but recreating the project did not work.
One issue that I had was that worklight did not build a .war-file properly, so I copied the .war-file from a backup.
Edit: This happens regularly in our project now, and we have no idea why. We fix it by invoking any procedure, which makes it work until you restart the server. Worklight must be building something when invoking a procedure that it does not do when building.
I Solved The problem by creating a new Worklight Project and copied all my files , it works just fine :) I used Worklight 6.1 instead of 6.2
I solved this by fixing a recently created security test in
server/conf/authenticationConfig.xml
The problem was I mispelled the Realm name I previously defined.
I solved this problem by deleting the application from the worklight server and rebuild it.
Delete WorklightServerConfig folder in workspace and rebuild your application.
I was able to fix this in MobileFirst 7.0 (Fka Worklight) by opening the Servers view, Window -> Show View -> Servers. Then expanding the MobileFirst Development Server and right click on the project in question, chose delete.
Once you do that go back to the applications' directory in the "apps" directory and right click -> Run As -> Run On MobileFirst Development Server
This should rebuild and deploy the project on the server.
I solved the problem by using ibm jdk not open jdk. My solution is to make sure the env parameters are correct
export JAVA_HOME = $your_ibm_jdk
export PATH + $your_ibm_jdk/bin:$PATH
run java -version to make sure the setting work
I'm unable to build Android project using Android Studio 0.1.3. Everything worked fine until latest SVN update of the project. This is strange, because no settings were changed (SDK, dependencies etc.). I also didn't update any tools. I keep getting the error:
Android Packager: [trunk] File /home/matis/.AndroidStudioPreview/system/compile-server/apilot_f8e91252/android/intermediate_artifacts/trunk/classes.dex not found. Try to rebuild project
There are no errors in source code, I can build and deploy it on a device without problems using Eclipse. I'm using SDK rev. 17 with SDK Tools rev. 22.
I tried to build source from earlier SVN revision, but the same thing happens.
Has anyone else experienced similar problem? How can I solve it?
Update
After some investigation I found out that dx tool doesn't get called at all (I modified its script so it would create some file if run), but aapt is called properly.