I am using maven 2.2.1 and when i try to build my project i am getting the below exception.
Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-surefire-plugin at /Users/<<userid>>/.m2/repository/org/apache/maven/plugins/maven-surefire-plugin/2.8.1/maven-surefire-plugin-2.8.1.pom
As in the error message,i just deleted the below directory from my local repo. And then ran the clean install, on the project again resolved the issue.
/.m2/repository/org/apache/maven/plugins/maven-surefire-plugin/2.8.1
Related
In my react native project I don't have "react-native-reanimated" but when I rebuilt my project I got this error:
"Project "react-native-reanimated" was not found in the root project
So when I install react-native-reanimated I get an NDK install error, but when I install the ndk and get the apk from the project, the app won't open and crashes.
So I uninstalled react-native-reanimated and ndk and cmake but again I got the error "project 'react-native-reanimated' was not found in the root project"
please help me
Android Studio Error Message Picture
Possible gradle related issue - try out the solutions in this post:
Android: Project 'MyProject' not found in root project 'MyProject'
But basically, delete the .gradle folder in your project's root folder and resync gradle from Android Studio.
try to run below command
npm install --force react-native-reanimated
Fix the upstream dependency conflict, or retry
this command with --force, or --legacy-peer-deps
it work for me
Should I install #vue/composition-api in package.json dependencies rather than in devDependencies?
I see on npm registry that it is in dependencies
Following the logic of vue-property-decorator or vue-class-component, this are installed as dependencies.
I would say this is actual dependency for your project once is build, so it is not a dev dependency.
Error in installing the AndroMDA. while installing the maven archetype code = mvn archetype:create -DgroupId=testapp -DartifactId=testapp. It is saying BUILD FALIURE
When I try to install the searchable plugin in a grails app, I'm told that grails can't resolve the following dependencies:
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.grails.plugins#searchable;0.6.3: java.lang.NullPointerException at org.apache.ivy.plugins.resolver.AbstractResolver.initRepositoryCacheManagerFromSettings(AbstractResolver.java:396)
::::::::::::::::::::::::::::::::::::::::::::::
Grails version is 2.0.3
What can i do?
Are you trying to install it from a zip file? This might be caused by GRAILS-9006, which prevents plugins from being installed via a local directory, to be fixed in Grails 2.0.4.
Try uncommenting the mavenCentral line in BuildConfig.groovy then try the install-plugin again.
//mavenLocal()
mavenCentral()
//mavenRepo...
I'm new to Maven so I may be missing something obvious, but
I've got a maven project and when I try to "mvn package" this project it fails with
ERROR BUILD ERROR INFO
------------------------------------------------------------------------ [INFO] Failed to resolve artifact.
Missing:
---------- 1) org.apache.maven.wagon:wagon-ftp:jar:1.0-rc1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-ftp -Dversion=1.0-rc1-SNAPSHOT -Dpackaging=ja r -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.maven.wagon -DartifactId=wagon-ftp -Dversion=1.0-rc1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) com.cgs:domain:jar:1.0-SNAPSHOT
2) org.apache.maven.wagon:wagon-ftp:jar:1.0-rc1-SNAPSHOT
----------
1 required artifact is missing.
for artifact: com.cgs:domain:jar:1.0-SNAPSHOT
from the specified remote repositories: ibiblio.org (http://mirrors.ibiblio.org/pub/mirrors/maven2)
The first thing I don't understand is the version it requires 1.0-rc1-SNAPSHOT. The projects' site says the current version is 1.0-beta-5. And I suppose beta goes before RC.
Anyway, I've tried to download the latest wagon-ftp JAR (1.0 beta 6 jar) and deploy it according to the instructions in the error message.
But guess what, this gave me the same error.
I've just found the solution as I was typing the end of this question.
The problem was that I was running "mvn install:install-file" from the same directory the failing project POM was in. It installed fine when I run it from another directory without a pom.xml.