On Mon, Feb 10, 2014 at 1:15 AM, Florian Hopf <[email protected]> wrote: > On 10.02.2014 00:29, Svante Schubert wrote: >> >> Havn't done it for years, I would have to read in again myself, but >> guess Florian did it last time and might remember easier. > > > Well, I wouldn't remember what to do but fortunately this guide tells what > to do :) http://www.apache.org/dev/publishing-maven-artifacts.html >
That helped. I got further, including post to Nexus. But now I'm dying on step 5 of our instructions: rob@robuntu:~/odf/target/checkout$ mvn install -Prelease-distribution -pl=. -Duser.name=<robweir> [3] 16245 lt: command not found [4] 16266 gt: command not foundrobweir: command not found rob@robuntu:~/odf/target/checkout$ [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Couldn't find specified project in module list: /home/rob/odf/target/checkout/. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1 second [INFO] Finished at: Mon Feb 10 11:06:24 EST 2014 [INFO] Final Memory: 3M/38M [INFO] ------------------------------------------------------------------------ I tried as well with -Duser.name=robweir and get the same initial error about not finding specified project Any ideas? -Rob > >> >> By the way, I did not meant "repository.apache.org", I meant the Maven >> Central Sonatype repository. > > > We are not publishing to Maven Central directly. There is a Nexus instance > hosted at Apache that is used as a staging repository and then synced with > Maven Central. > > The sync with Maven central should only be done once the release has been > voted on. > > Rob: I suspect that the Maven release process on your local machine failed > quite late and you can't roll it back, but you can try to do the following: > > mvn release:rollback followed by another mvn release:prepare and mvn > release:perform. If the process can't continue because there are already > tags in SVN you can either use a new version for the release oder delete the > SVN tags manually. > > I'll try to be available if there are any questions. > > Regards > Florian > > -- > Florian Hopf > Freelance Software Developer > > http://blog.florian-hopf.de
