Issue Type: Bug Bug
Affects Versions: 2.1-alpha-2
Assignee: Unassigned
Attachments: pom.xml
Components: rpm
Created: 19/Apr/13 8:04 AM
Description:

When I execute:
mvn clean install deploy

I get:
[INFO] Wrote: /workarea/luva/eperott/rpm-test/target/rpm/rpm-test/RPMS/noarch/rpm-test-0.0.1-SNAPSHOT20130419122755.noarch.rpm
[INFO] Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.ON7NeS
[WARNING] + umask 022
[WARNING] + cd /workarea/luva/eperott/rpm-test/target/rpm/rpm-test/BUILD
[WARNING] + /bin/rm -rf /workarea/luva/eperott/rpm-test/target/rpm/rpm-test/buildroot
[WARNING] + exit 0
[WARNING] Artifact org.example:rpm-test:rpm:rpm:0.0.1-SNAPSHOT already attached to project, ignoring duplicate
[INFO]
[INFO] — maven-install-plugin:2.3.1:install (default-install) @ rpm-test —
[INFO] Installing /workarea/luva/eperott/rpm-test/pom.xml to /slask/eperott/maven/repository/org/example/rpm-test/0.0.1-SNAPSHOT/rpm-test-0.0.1-SNAPSHOT.pom
[INFO] Installing /workarea/luva/eperott/rpm-test/target/rpm/rpm-test/RPMS/noarch/rpm-test-0.0.1-SNAPSHOT20130419122754.noarch.rpm to /slask/eperott/maven/repository/org/example/rpm-test/0.0.1-SNAPSHOT/rpm-test-0.0.1-SNAPSHOT-rpm.rpm

This gave me some trouble at first. However I've noticed, that the bug does not trigger if I do:
mvn clean deploy
or:
mvn clean install

So the bug is only triggered in case I use a combination of "clean install deploy"

The bug appear with the simple attached pom file.

Environment: uname -a
Linux sekalvd015 2.6.32-220.el6.x86_64 #1 SMP Wed Nov 9 08:03:13 EST 2011 x86_64 x86_64 x86_64 GNU/Linux

mvn --version
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
Maven home: /opt/local/dev_tools/maven/latest
Java version: 1.6.0_24, vendor: Sun Microsystems Inc.
Java home: /proj/vau/devcs/opt/java/1.6.24/linux/jre
Default locale: en_US, platform encoding: ISO-8859-1
OS name: "linux", version: "2.6.32-220.el6.x86_64", arch: "i386", family: "unix"
Project: Mojo RPM Plugin
Priority: Minor Minor
Reporter: Per Otterström
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to