I generate app thanks to jhipster but when I run it I have the following error:
.m2\repository\org\liquibase\liquibase-core\3.5.3\liquibase-core-3.5.3.jar referenced one or more files that do not exist: .m2\repository\org\liquibase\liquibase-core\3.5.3\lib\snakeyaml-1.13.jar
The error happens in my IDE and when I run mvnw.
I can't find any solutions or workarounds.
Ok it seems that in fact my application failed to start cause my application-dev.yml was malformatted. But the error message what really not explicite and believed that the error come from the liquibase classpath.
Related
I've found myself in a strange predicament—after a recent upgrade to my local app dependencies, the application breaks whenever I make reference to the node process object. Specifically it throws the following errors:
Babel Error: Cannot find module '#babel/plugin-proposal-logical-assignment-operators'
So far, I've tried to resolve this issue with a yarn add of the missing dependency, without success. Could anyone shed light on the issue at hand, or how I might be able to resolve it?
Thanks for your consideration.
I resolved this issue by deleting node_modules and running yarn install.
I am trying to create a basic mulesoft plugin
mvn org.mule.extensions:mule-extensions-archetype-maven-plugin:1.2.0:generate
When I try and execute mvn eclipse:clean
I get
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.6.1 is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-site-plugin:3.6.1: Plugin org.apache.maven.plugins:maven-site-plugin:3.6.1 or one of its dependencies could not be resolved: Failure to find org.apache.maven.plugins:maven-site-plugin:jar:3.6.1 in http://repository.mulesoft.org/releases/ was cached in the local repository, resolution will not be reattempted until the update interval of mulesoft-plugin-releases has elapsed or updates are forced
How do I resolve this? I am using eclipse/studio not IntelliJ.
Any pointers?
That is a warning, not an error. It should not cause any issue. Just ignore it.
I am trying to run ./gradlew in jhipster project and getting next error with ':bower' task:
:cleanResources
:bootBuildInfo
:bower FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':bower'.
> A problem occurred starting process 'command 'bower''
.......
Caused by: net.rubygrapefruit.platform.NativeException: Could not start 'bower'
at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:27)
at net.rubygrapefruit.platform.internal.WrapperProcessLauncher.start(WrapperProcessLauncher.java:36)
at org.gradle.process.internal.ExecHandleRunner.run(ExecHandleRunner.java:68)
... 2 more
Caused by: java.io.IOException: Cannot run program "bower" (in directory "/Users/vovkvlad/coding/learning/Java/jHipProj"): error=2, No such file or directory
at net.rubygrapefruit.platform.internal.DefaultProcessLauncher.start(DefaultProcessLauncher.java:25)
... 4 more
I have seen similar problems on stackoverflow:
Running JHipster Gradle task from Intellij IDEA
jhipster - error executing task :bower
But first link complains only about failure in IntelliJ (and in my case the same error occurs in the terminal)
And second link gives pretty strange answer with removing node which seems strange to me, and may be not applicable since 2 years have past.
So, do anyone have a key to what am I doing wrong?
I will be grateful for any kind of help/hint.
Thanks in advance for help!
EDIT: I have bower installed globally, so that it can be found under one of the paths in $PATH. And bower is recognized from the terminal.
I was having this same issue. I was able to fix it by stopping the gradle daemon using ./gradlew --stop. Here is a link to a post where I found the solution.
i got the same issue, and fixed it with command below.
gradle --stop
In my case, i use Eclipse with Buildship plugin, it starts a Grade Daemon to build project by itself, and the classpath of NodeJS & Bower is difference when running application in terminal.
I am current using mean.io as development framework of my application and have been using growlNotifications plug-in for certain time and it works perfect on both server and client side.
while after some coding commit (does not affect the plug-in), the following error appear on the production server:
Uncaught Error: [$injector:modulerr] Failed to instantiate module acleague due to:
Error: [$injector:modulerr] Failed to instantiate module growlNotifications due to:
Error: [$injector:nomod] Module 'growlNotifications' is not available! You either...<omitted>...3)
but it won't have any problem running on local. I ensure that the bower install work perfectly on production server and i did nth in the grunt file.
Could anyone help me or even give me some hints to solve this problem? Thanks a lot!
As I was set the bower component as latest, the production server will run the bower update command to get the latest one while local does not.
So I upgraded the plugin and run it on both sides, it works now.
For 2 days, I have been trying to fix my Android Studio setup, but despite a lot of googling have had no luck fixing this problem. Gradle keeps giving me the error
Error:Execution failed for task ':Android-Tabbedout-30:processQaReleaseResources'.
Error: A library uses the same package as this project
You can temporarily disable this error with android.enforceUniquePackageName=false
However, this is temporary and will be enforced in 1.0
If I add in the enforceUniquePackageName=false to the gradle file, then the project can be successively refreshed by Gradle, but once I try to run it I get this error:
Error Code:
2
Output:
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define
Any ideas on how to fix this?
I was searching for that same problem and i find this on github
https://github.com/DWorkS/AStickyHeader/issues/12
And this solved my problem.
All this says is to rename the package name on the AndroidManifast.xml file.
And its done.