I am trying to add the source jar files to a project on which I am working.
I have added the dependency into the pom file for the project.
I have manually added two repos into the om file. This the maven central and also the maven.google.
I have tried a forced an update but still not able to get the source for the SDK. The SDK-provider is fine.
The following artifacts could not be resolved:
com.dji:dji-sdk:jar:4.7.1, com.android.support:appcompat-
v7:jar:25.3.1, com.android.support.constraint:constraint-layout:jar:1.0.2: Could not find artifact com.dji:dji-sdk:jar:4.7.1 in my-repo1
(https://maven.google.com) -> [Help 1]
Am I missing something obvious?
Related
I have a Java project using gradle that uses some very old dependencies. One of them has a transitive dependency that works fine with jcenter() but now fails when I try to migrate to mavenCentral(). The artifact exists in Maven Central but has no pom file. Gradle gives me an error like this:
> Could not resolve all files for configuration ':myproject:compileClasspath'.
> Could not find woodstox:wstx-asl:3.2.7.
Searched in the following locations:
- https://repo.maven.apache.org/maven2/woodstox/wstx-asl/3.2.7/wstx-asl-3.2.7.pom
Any attempt on my part to browse the jcenter repository returns a 403 Forbidden so I can't tell if the pom file exists there but somehow Gradle is able to build the project using jcenter().
That leaves me with a few questions:
Are pom files required in (very old) maven artifacts?
How does gradle gain access to https://jcenter.bintray.com/?
Is there any way to find out if the jcenter artifact has a pom file?
If it doesn't have a pom file, why does gradle work with jcenter() but fails with mavenCentral?
Thanks in advance for any help!
We do not have project design in parent and module way.We have project A and project B . Project A has dependency of project B . we passing the version of the dependency jar by command prompt in eclipse, Its compiling and install properly. but its pom shows always error.and error is like
Missing artifact
com.testdependency:testdependency:jar:org.apache.maven.model.Build#5ae16e48
Passed the build parameter by command line like -Dbuild. Is there any way resolve this ?
pom.xml would need the dependencies present in your local .m2 repository. If you don't install the dependencies to your local repository, pom.xml can't find them. So, run a build on your dependency project with goals selected as clean install, which should insall the artifact to your local repository. Then in your eclipse, right click on the main project and execute Maven -> Update Project. This should resolve your issue.
Refer to this link for the details on the repositories
Previously I was building the project with the mule version 3.7.4. now, as mule version 3.8.4 is the latest one, so planned to build with this latest version. So,
from Anypoint Studio I have downloaded the latest version.
Then I updated my POM file with the 3.8.4 version. But it seems that with the same jars its not able to build the project.
Its gives error as
Failed to execute goal on project sho-pointofsales: Could not resolve dependencies for project com.sho:sho-pointofsales:mule:1.0-SNAPSHOT: Failed to collect dependencies at com.mulesoft.muleesb.modules:mule-module-tracking-ee:jar:3.8.4: Failed to read artifact descriptor for com.mulesoft.muleesb.modules:mule-module-tracking-ee:jar:3.8.4: Could not transfer artifact com.mulesoft.muleesb.modules:mule-module-tracking-ee:pom:3.8.4 from/to mule-ee-releases (https://repository-master.mulesoft.org/nexus/content/repositories/releases-ee/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1]
Although I placed this jar inside my local REPO. Don't know what is wrong I am doing.
Thanks in advance.
It exists: https://repository.mulesoft.org/nexus/content/repositories/releases-ee/com/mulesoft/muleesb/modules/mule-module-tracking-ee/
check your username and password in your settings.xml or pom etc for that repo.
But it's part of the platform anyway and doesn't need to be explicit in your pom. So just remove it from the pom or set it the scope to 'provided' on the dependency
Check following stuff:
a. You can either comment the enterprise repository in the pom.xml file.
b. Check if the enterprise repository is accessible from your browser.
c. verfiy username and password.
I have a local maven repository and installed a custom artifact. It works if i reference it in other projects. But now i want to use a server for a "own maven repository". If i delete the artifact from the local maven repository, i assumed that the project will not build when i do a maven clean and maven force update dependencies. The artifact cannot be found under .m2/ but Spring Source Tool Suite still can add the artifact to new Java Projects. Create New Java Project -> Edit Pom -> Maven Artifact is added, even if i deleted it from local repository .m2/ . How is this possible and how can i delete it completely, to be able to test if now all dependencies are updated from my server with the .m2/settings.xml configuration?
Your repository is just a directory/file structure. Go to your local repo, find the path (the group id is the path), and delete from the place where you start to see version numbers. When you rebuild, the artifact should be downloaded/replaced from your server/repo.
My build is failing with this error message (corporate stuff crossed out):
[ERROR] Failed to execute goal on project XXXX: Could not resolve
dependencies for project XXXX: The following artifacts could not be
resolved:
com.github.chrisbanes.actionbarpulltorefresh:library:jar:0.9.3,
com.github.castorflex.smoothprogressbar:library:jar:0.2.0: Cannot
access XXXX-release (http://repo.XXXX.corp/main/repo) in offline mode
and the artifact
com.github.chrisbanes.actionbarpulltorefresh:library:jar:0.9.3 has not
been downloaded from it before. -> [Help 1]
The funny thing is that actionbarpulltorefresh is not a dependency of this project. I double-checked and the string appears nowhere in the directory. It's a dependency of another project I built a couple of days ago, but not this one. It's also not mentioned in my users's settings.xml file, or anywhere in .m2 except that it's actually installed there.
Where could that error possibly be coming from?
It might be a transitive dependency, a dependency of a dependency.
This question might help you: How to determine which Maven dependency is needing a missing dependency?