Hi, the policies require us to create a source artifact including LICENSE and DISCLAIMER, not matter if it is just a pom file or not.
The first snippet I added helped, when you do when you do: mvn package -Papache-release I wanted to try it and after I liked it I did: mvn deploy -Papache-release Well, first I forgot to revert version number and to rename the tag. But thats not my actual problem. It seem the profile doesn't deploy it to the staging repo as I was used to it. It finally ended up here: https://repository.apache.org/content/repositories/snapshots/org/apache/onami/org.apache.onami.parent/2-incubating-SNAPSHOT/ No idea why it didn't went "live" into snapshots without staging. Well, I messed it up, sorry. Then I removed the snipped, looked at ASF parent and added the plugin to create a source artifact from there into our own release profile. then: mvn -Prelease deploy It ended up in the snapshots repository too. Now my assumption is it happens because of the (surprise) -SNAPSHOT ending. Before I create more mess, I want to confirm the following steps with you folks. 1) I am renaming this tag: http://svn.apache.org/repos/asf/incubator/onami/tags/parent-1-incubating/ to http://svn.apache.org/repos/asf/incubator/onami/tags/parent-1-incubating-RC1 2) I am doing: mvn release:prepare mvn release:perform 3) then I do: svn co http://svn.apache.org/repos/asf/incubator/onami/tags/parent-1-incubating/ cd parent-1-incubating mvn deploy I am not sure if I need -Prelease in the last mvn deploy. If not, would it be better to move the maven-assembly-plugin I added to the "standard" location outside the profile? Some more eyes welcome! Thanks Christian -- http://www.grobmeier.de https://www.timeandbill.de
