How can resolve an artifact from a remote Repo from within my Component

How can resolve an artifact from a remote Repo from within my Component Here is a template of my Component code. It will take GAV co-ordinates as argument. How can I use the GAV co-ordinates to download the artifact from my remote Nexus repo? @org.codehaus.plexus.component.annotations.Componen

RE: Reload MavenProject MavenSession and BuildPluginManager

I tried the following but the project version didn't work Artifact artifact = project.getArtifact(); try { artifactResolver.resolve(artifact, remoteArtifactRepositories, localRepository); System.out.println("proj

RE: Reload MavenProject MavenSession and BuildPluginManager

Not really an option as this may only run locally and my Mojo may be configured to only create a local Git branch On 9 Feb 2014 01:51, "mgainty [via Maven]" < ml-node+s40175n5783730...@n5.nabble.com> wrote: > > Date: Sat, 8 Feb 2014 09:59:27 -0800 > > From: [hidden email]

Reload MavenProject MavenSession and BuildPluginManager

How can my Moo reload/refresh MavenProject MavenSession and BuildPluginManager components. I need to do this after my Mojo switches the a different Git branch. -- View this message in context: http://maven.40175.n5.nabble.com/Reload-MavenProject-MavenSession-and-BuildPluginManager-tp5783698.ht

Re: allowMajorUpdates for mvn versions:update-properties

I raised a JIRA: http://jira.codehaus.org/browse/MVERSIONS-220 -- View this message in context: http://maven.40175.n5.nabble.com/allowMajorUpdates-for-mvn-versions-update-properties-tp5754676p5756003.html Sent from the Maven - Users mailing list archive at Nabble.com.

allowMajorUpdates for mvn versions:update-properties

Hi, I have a number of dependency versions defined as properties. For good reason. The version properties are used in both the and rpm build section of the pom.xml So, as part of a release I only want to update to the next minor version for this property. For example, use-latest-versions allow

I need to run 2 profiles to deploy to 2 seperate Nexus repositories

Hi, How can I get Maven to run 2 separate Profiles to deploy the build artifacts to 2 separate Nexus repos? I have tried the following but only the second profile deploys to its Nexus repo. mvn clean deploy -P nexus-one,nexus-two Note: the settings file passed doesn't contain any profiles.

Re: Maven clean install throws Checksum failed on download

OK, Its downloading from Nexus repos and I guess they have been around for a while. I'm on Maven 2.2.1. So I guess there's not much that can be done the fix Nexus other than deleting its artifacts and redeploy them. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-clea

Maven clean install throws Checksum failed on download

I'm getting a number of errors in my build like the following: *** CHECKSUM FAILED - Checksum failed on download: local = '2b0cd22fcfe2c88328b8c30eb57bc24b4b20ed'; remote = '746e3c8abfad7fdc3d6384dd1a9b6b448140ef' - RETRYING *** CHECKSUM FAILED - Checksum failed on download: local = '2b0cd22fcfe2c

Re: Maven versioning

So how does release work with SVN. If all my projects are at 1.0.0-SNAPSHOT. What will running the mvn release command do? Will it result in 1.0.1-SNAPSHOT? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-versioning-tp5709659p5709665.html Sent from the Maven - Users mail

Maven versioning

Hi, New to Maven and have a couple of questions around versioning. Should all projects within a multi-module project have the same version? Should all projects related to each other keep the same version number? Any best practices on changing version numbers? Thanks -- View this message in co

Deploy a txt file with mvn deploy:deploy-file?

Hi, I need to deploy a txt file with license info to a remote Nexus repository. Can this be done with mvn deploy:deploy-file mvn deploy:deploy-file -DgroupId=com.xyz -DartifactId=zyx-component -Dversion=1.0.0 -Dfile=C:/licesne.txt -Dpackaging=txt -Durl=http://my.nexus.url I tried the above but p