mvn release:perform problems: deploys **.jar.asc as **.bundle.asc for bundles

releaseproblem123

Problem Screenshot: https://skitch.com/tonit/rfg6j/sonatype-nexus-maven-repository-manager

This is the tracked down first appearance of the misnamed artifact (bundle.asc vs. jar.asc) during mvn release:perform:

..
[INFO] [INFO] --- maven-install-plugin:2.3:install (default-install) @ pax-exam ---
[INFO] [INFO] Installing /Users/tonit/devel/oss/org.ops4j.pax.exam1/target/checkout/pax-exam/target/pax-exam-1.2.3.jar to /Users/tonit/.m2/repository/org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3.jar
[INFO] [INFO] Installing /Users/tonit/devel/oss/org.ops4j.pax.exam1/target/checkout/pax-exam/pom.xml to /Users/tonit/.m2/repository/org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3.pom
[INFO] [INFO] Installing /Users/tonit/devel/oss/org.ops4j.pax.exam1/target/checkout/pax-exam/target/pax-exam-1.2.3-javadoc.jar to /Users/tonit/.m2/repository/org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3-javadoc.jar
[INFO] [INFO] Installing /Users/tonit/devel/oss/org.ops4j.pax.exam1/target/checkout/pax-exam/target/pax-exam-1.2.3-sources.jar to /Users/tonit/.m2/repository/org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3-sources.jar
--> Here the problematic line comes:
[INFO] [INFO] Installing /Users/tonit/devel/oss/org.ops4j.pax.exam1/target/checkout/pax-exam/target/pax-exam-1.2.3.jar.asc to /Users/tonit/.m2/repository/org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3.bundle.asc


This leads to verification errors on nexus of cause. It cannot find the .asc file for 
org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3.jar
which is (wrong!) org/ops4j/pax/exam/pax-exam/1.2.3/pax-exam-1.2.3.bundle.asc

Any clue why ??

Did you try to use older maven-release version?

Another solution: switch to "jar" packaging from "bundle" with additional configuration for bundle plugin

Actually i am resisting to any workaround here since this worked for all previous releases.. and this is just a bugfix release.
So its not about changing anything to the product itself i guess.

What has changed indeed is the upgrade from of the maven release plugin to 2.1. I tried to downgrade to 2.0 but that had other, more sever sideeffects.
For sure, i will rewind all plugin versions to the ones used in 1.2.2. But that is just pointless and makes me feel with all maven haters in this moment. - although i usually defend maven at all costs. Unfortunately i am running out of time to track this - time consuming - thing down before going to holiday. (saturday).
Not sure if i can do this today - otherwise i would like to invite anyone at OPS4J to push the release - @dimitry, do you have release rights at OPS4J ? Otherwise if you will have time sometime before new years eve, ask on the mailinglist for assistance and push it.
;)