maven-deploy-plugin

I would like to be able to deploy only the POM artifact (file) without the main artifact (JAR, WAR, etc), when running mvn deploy and version is a SNAPSHOT version. Why? We several developers working on multiple Maven projects. We have a Hudson server with a job per Maven project and version (e.g. foo-1.2, foo-1.3). Each job builds the project and deploys it to a Nexus server (upon success). Maven projects under development are marked as such by using -SNAPSHOT postfix in the version. For example: 1.2-SNAPSHOT, 1.3-SNAPSHOT. Here's a sample scenario how a developer work is damaged due to this

I have done some zip packaging in maven using the below descriptor and pom file. But in maven by default it created both jar and zip in target folder. Now i want to deploy only zip contents where i am using deploy:deploy-file plugin. but it is not deploying instead it is showing error. Not sure what is wrong with tag and how it should be resolved. Pom file: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion>

I have created a working maven archetype for a Vaadin/Hibernate/Spring project. I am able to install this archetype to my local repository and use it to generate new maven projects. Now I want to deploy the archetype to my companies internal repository, so it might be used by other developers. However, when I run mvn deploy I recieve the following error message: [ERROR] Failed to execute goal org.apache.maven.plugins: maven-deploy-plugin:2.7:deploy (default-deploy) on project vaadin-hibernate-archetype: Failed to deploy artifacts/metadata: No connector available to access repository maven

Is it possible to in some way tell the maven deploy:file goal to deploy to two independent artifactories based on whether the version of the project is a snapshot / release? I'm hoping there might be a property which indicates the fact the version has -SNAPSHOT prepended, or perhaps the default artifactory to deploy to (which has been worked out based on the version number already). I thought about using two different profiles and working out if its a snapshot in ant by parsing the pom.xml file, but I'd rather a cleaner solution if possible. Currently, my deploy plugin looks as follows, but

i am using Apache Maven 3.0 Nexus Open Source Edition, Version: 1.8.0.1 this is part of my pom.xml <plugin> <artifactId>maven-deploy-plugin</artifactId> <version>2.5</version> </plugin> <plugin> <artifactId>maven-release-plugin</artifactId> <version>2.1</version> </plugin> <distributionManagement> <repository> <id>nexus</id> <name>nexus</name> <url>http://myrepo/nexus/content/repositories/releases</url> </repository> </distributionManagement> it is a very simple project. when i do mvn release:prepare mvn release:perform everything runs fine: ... [INFO] [INFO] --- maven-deploy-plugin:2.5:deploy

I'm using the maven-antrun-plugin to do a bunch of work with Ant, which ultimately results in a zip file. I'd like to deploy the zip file to our maven server (Artifactory). The maven-antrun-portion works as intended and successfully creates the zip file; however deployment fails with the following error message: org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project projectname: The packaging for this project did not assign a file to the build artifact My POM file is as follows: <project

I'm using maven-deploy-plugin in multi-module project with deployAtEnd property set to true . After executing mvn deploy in root project, deploy plugin is executed for each subproject - I can see something like: [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ subproject-name --- [INFO] Deploying package:subproject-name:v1.1 at end Last invocation is for root project: [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ parent-project --- [INFO] Deploying package:parent-project:v1.1 at end and that's all, actual deployment is not executed. How do I make deploy plugin

I've a problem when publishing component to a Nexus repository, Maven upload the file twice: first time with maven-deploy-plugin groupId/artifactId/version parameters (that's what I want) second time with pom groupId/artifactId/version parameters (that's what I DON'T want) I launch packaging/deployment with the following command (see pom.xml file at the bottom): mvn clean package deploy:deploy-file -e -f pom.xml Here is the snippet of maven output console when handling deploy phase (the 6 first lines are correct but notice the 2 last lines with pom groupId/artifactId/version): [INFO] --- maven