Missing artifact org.jboss.fuse:jboss-fuse-full:zip:6.2.1.redhat-084 when it does show in local repository - maven

I have a quickstart project that is failing to build with the following error.
Missing artifact org.jboss.fuse:jboss-fuse-full:zip:6.2.1.redhat-084
However, it does show in my local Maven repository, at least there is an entry.
Here is a screenshot of my local repository
How can I clear this error?

Related

Q: The proxy repo in Nexus cannot download the special SNAPSHOT structure from remote repo

there is a special SNAPSHOT structure in the remote repository as following.
i create a proxy repository in Nexus pointed to this remote repository. but an error happened while running mvn packaging. the error message is as following:
[ERROR] Failed to execute goal on project dispatch-admin: Could not resolve dependencies for project com.yueyue:dispatch-admin:jar:2.0.0-SNAPSHOT: Could not find artifact com.yueyue:order-search-interface:jar:1.2.1.SNAPSHOT in aliyun_release2 (http://192.168.200.224:8081/repository/aliyun_release2/)
and there is a warning while pulling the package as following
but it is OK while using remote repository for mvn packaging. and the message is shown as following while pulling the package.
what should i check first for this problem? many thanks in advance!

Failed to resolve artifact (snapshot) from my artifactory repository

I've got a local artifactory repository. I've got a dependency in one of my app's pom.xml like the following:
<dependency>
<groupId>org.activequant</groupId>
<artifactId>activequant-p2</artifactId>
<version>1.3-SNAPSHOT</version>
</dependency>
I deployed an activequant-p2-1.3-SNAPSHOT.jar to my 'ext-local-snapshot' repository. Artifactory deployed it under org/activequant/activequant-p2/activequant-p2-1.3-20130925.170928.jar . Now when i run 'mvn package':
Downloading: http://artifactory.myrepos.local/libs-snapshot/org/activequant/activequant-p2/1.3-SNAPSHOT/activequant-p2-1.3-SNAPSHOT.pom
[INFO] Unable to find resource 'org.activequant:activequant-p2:pom:1.3-SNAPSHOT' in repository snapshots (http://artifactory.myrepos.local/libs-snapshot)
And fails, because http://artifactory.myrepos.local/libs-snapshot/org/activequant/activequant-p2/1.3-SNAPSHOT/activequant-p2-1.3-SNAPSHOT.pom does not exist (It's under http://artifactory.myrepos.local/libs-snapshot/org/activequant/activequant-p2/1.3-SNAPSHOT/activequant-p2-1.3-20130925.170928.pom).
How should i deploy the artifact in my artifactory or configure my pom.xml to fix this problem?
Looked at this: Maven: Why is the -SNAPSHOT suffix missing from artifact file name? , which seems like the problem, but i'm using maven3 on the client side, so there's no 'uniqueVersion' tag at all. I tried changing the "Maven Snapshot Version Behavior" setting for my repository, but that does not fix the problem.
For some reason my local maven repository was dirty (no snapshot timestamps in metadata file downloaded). Running maven did no substitute the metadata, so i deleted my org/activequant/activequant-p2 manually from my local repos and all went ok.

Maven build error on maven install

I imported a maven project onto my eclipse. I clicked on Run As->Maven Install. But I got the following build error. Please help
plugin org.apache.maven.plugins:maven-jar-plugin:2.3.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-jar-plugin:jar 2.3.2:Could not transfer artifact org.apache.maven.plugins:maven-jar-plugin:pom: 2.3.2 from/to central(http://repo1.maven.org/maven2):Error transferring file: repo1.maven.org: Unknown host repo1.maven.org
I checked /m2/repository. But could not find anything related.
Somehow it is not able to download the required artifacts from the Maven Central repo.
A suggestion please check your network connectivity, are you behind any firewall or try to change your proxysettings.
Otherwise in the worst case try to download required artifacts manually and put them in .m2/repository (as per ur local system) and try to install again.
http://search.maven.org/#browse|672389075
It should work.
Thanks

Unable to find resource 'opensymphony:quartz-all:pom:1.6.3' in repository central

I inherited this project which used to build & run successfully (years ago...). Now when checked out from version control, as is, it complains:
Unable to find resource 'opensymphony:quartz-all:pom:1.6.3' in
repository central (http://repo1.maven.org/maven2)
But following that repository link (http://repo1.maven.org/maven2) leads to a browsable site that shows clearly that this resource is available: http://search.maven.org/#browse|1030701351 !
I have even been able to manually download it, and I can also find it in my local repo (C:\maven\repo\opensymphony\quartz-all\1.6.3\quartz-all-1.6.3).
So, my questions:
Why is Maven complaining at all, if it is there?
How did it get to my local repo, if Maven couldn't find it?
Your local repository is NOT in C:\maven ... it is in your users directory ~/.m2/repository
To debug what is really going on I would suggest to deactivate the ~/.m2/settings.xml (e.g. by renaming it) and do a clean build without any of the old artifacts and from a fresh local repository (just delete ~/.m2/repository)
That would tell you what is really missing.
If anything is missing that means it is not in the Centra Repository (http://search.maven.org). As a next step I would then install a repository manager in your network. I would recommend using Sonatype Nexus (open source, free book as documentation) and then add any other repositories or missing artifacts in there.

maven could not resolve dependency via my local nexus repository

I have setup an in-house Sonatype Nexus repository and configure the maven to check my local Nexus instead of getting artifacts directly from public repositories.
http://www.sonatype.com/books/nexus-book/reference/config-sect-intro.html
Our project was able to download the most artifacts except one artifact in Maven central.
Here is the build error:
Failed to execute goal on project shindig-gadgets: Could not resolve dependencies for project org.apache.shindig:shindig-gadgets:jar:3.0.0-SNAPSHOT: Could not find artifact com.ibm.icu:icu4j:jar:4.6 in nexus (http://my_nexus_repository:8081/nexus/content/groups/public) -> [Help 1]
I see that icu4j-4.6.jar does exist in the Maven central repository. On my local nexus repository, it doesn't exist. I see only icu4j-4.6.pom exists on my local nexus repository.
It's not like my nexus repository setting is totally broken. maven project has successfully downloaded numerous jar files from multiple public repositories via my local nexus maven repository except icu4j-4.6.jar.
I don't understand why I'm having a problem with only icu4j-4.6.jar. Would it be incorrectly cached on either my local maven or nexus maven repository?
If it was incorrectly cached, how can I clean the local maven or nexus maven repository?
The similar problem is described at
Missing maven dependency using nexus setup
icu4j-4.6.jar does not show up in the search list. Only icu4j-4.6.pom shows up in the search list. I don't think is Snapshot VS Release issue because icu4j-4.6.jar seems release jar.
Is it possible that the nexus repo just stopped responding for a while? You can try mvn -X (or -d?) to get detailed info about what is going on. You might also try configuring an alternative repo.
Perhaps you haven't enabled remote index downloads from Maven Central. This would explain why only the POM file appears in your local search (The only file which has been downloaded via the proxy repo).
There might be another issue causing the download failure for the jar itself.... I suppose try and solve one problem at a time :-)
Try adding -U to your mvn arguments to force an update of your local repository.
You could also have corrupt meta data in the repo. In which case, delete that artifact from the repo's cache and let it refresh.
If the artifact in question was cached in properly from the proxy repository, using mvn -U will fix the problem
However if you are seeing pom on your nexus ,this usually happens when the artifact from the proxy repository is not cached in properly. The way to fix is
1) Browse to the component in the Proxy Repository.
2) Invalidate the cache for the repository and reindex the Nexus repository.
3) run mvn clean -U

Resources