I tried to install the Nexus Artifact Usage Plugin into my Nexus 2.12.1-01: I copied it to the plugin-repository folder and restarted Nexus, but all I got was:
Unfortunately, this error message does not help very much.
Is this plugin deprecated?
Should it be replaced?
Or is there some kind of trick to make it work?
Sonatype told me that this plugin is not supported and probably won't work with newer versions of Nexus. It is unclear whether there is a reasonable replacement.
Related
What I am looking to do is take my local maven repo (stored in .m2/repository/) and upload all the artefacts up to a ProGet server.
I cant seem to find any documents or maven plugin even that gives me this functionality?
Can anyone help please?
You could try the Wagon Maven Plugin but its latest version is almost two years old and I experienced things not working with recent Maven versions.
You could use the Exec Maven Plugin to run a script that uploads your files.
I have added the latest version of AEM Mocks (2.7.2) as a Maven dependency in my AEM project. When I try to build my project, I get an error saying that this artifact cannot be found: com.day.commons:day-commons-gfx:jar:2.1.28. So I looked online, found it and added it as a dependency. But now I get the same error when trying to build. Does this artifact still exist? When trying various recent versions of AEM Mocks, I found that they all depend on this missing artifact.
For now, I downgraded to version 2.3.0, which works fine without that artifact but I would like to use the most recent version if possible.
Can anyone please help? Thanks!
This artifact is defined as a workaround, it is explained here in comment:
https://github.com/wcm-io/wcm-io-testing/blob/develop/aem-mock/core/pom.xml#L254:
Workaround for AEM 6.5: The new uber-jar does no longer contain the package com.day.imageio.plugins
It works without any issues for me, so I would check if you have correctly configured Maven repositories. To do it, in your Maven project root type:
mvn help:evaluate
and then:
${project.repositories}
It should list your project effective repositories. Ensure that there is Central Repository (https://repo.maven.apache.org/maven2/) listed. If it is there, then maybe your corporate network cuts requests to external repositories or it was temporarily down.
For my project I need to store jar after each build at some other url. Is there a way to get it done by Jenkins job.
I am quite new to jenkins.
You can find a good explanation on how to publish your artifact to a repository (best practice) here. This is equivalent for Maven3 and Maven2.
The answer refers to Artifactory. Make sure to also take a look at Nexus and Archiva as khmarbaise noted.
tl;dr
If using Artifactory, add the Maven Artifactory Plugin to your pom.
I searched everywhere and I cannot seem to be able to find maven Dependencies artifact for com.adobe.fdf
I am working on a very old project and am importing com.adobe.fdf.FDFDoc
Does anyone know what should I do?
I think it is not available within a public Maven repository - maybe because of the license. You have to download it from the Adobe website and install it by yourself at your local Maven repository.
Please see the maven-install-plugin: Goal install-file
I am trying to follow this tutorial:
http://docs.jboss.org/richfaces/latest_3_3_X/en/cdkguide/html_single/
I am hitting a roadblock with the maven commands.
First the org.richfaces.cdk version 3.3.3.Final was not found in the central repository, so I had to manually install version 4.2.2.Final to my local repository by downloading the file maven-richfaces-resources-plugin-4.2.2.Final.jar
I then had to manually install the org.richfaces.cdk plugin to my local respository.
Next, to run the command in section 4.1. I had to change archetype:create to archetype:generate. Running this command showed that maven couldn't find META-INF/archetype.xml in the jar file. I am stuck at this point. Any pointers?
Per this thread, that version of richfaces is in the JBoss Maven Repo, not Central
https://community.jboss.org/thread/172034?_sscc=t
In general, Software Vendors maintain their own Maven repos and do not push out every release to Central. SpringSource, Atlassian, and Oracle (java.net) come to mind.
Archetypes are dependencies just like project dependencies / plugins, so you will likely need to add the JBoss repository to your pom.xml or settings.xml in order for the archetype to work. See the above link for how to do that.
I figured it out! noahz's answer helped but wasn't the complete solution. I am still going to accept his answer. After substituting the Atlassion repo for the Jboss maven repo in settings.xml, I was still seeing the 'BUILD FAILURE' error saying it couldn't find the richfaces artifact. Maven was still looking in the central repo not in the Atlassian repo. So after a bit of research found that the central repo could be overriden with a tag. Follow this link:http://maven.apache.org/guides/mini/guide-mirror-settings.html.
Build is now successful.