On Tue, Nov 11, 2008 at 2:29 PM, Leonardo Uribe <[EMAIL PROTECTED]> wrote: > > > On Tue, Nov 11, 2008 at 8:11 AM, Matthias Wessendorf <[EMAIL PROTECTED]> > wrote: >> >> On Tue, Nov 11, 2008 at 2:03 PM, Matthias Wessendorf <[EMAIL PROTECTED]> >> wrote: >> > Hi, >> > >> > the pom.xml currently contains an execute part like >> > "mvn release:prepare -DprepareRelease=true" >> > >> > however, when I run that, the maven guy still want's that I run some >> > manual steps... >> > Like (when trying to release something that is named 1.0.10-SNAPSHOT) it >> > want's >> > the "real" JAR, the "source" JAR and the "javadoc" JAR for 1.0.10 ... >> > >> > Eh.... isn't that guy currently building it??? Or do I just miss some >> > (weird) extra steps >> > (for maven) ? >> >> >> here are some logs (ok it is named 1.2.10-SNAPSHOT, but that should be >> only cosmetics (even for maven)) >> >> >> It asks me if the *final* version should be named "1.2.10" and the >> next "1.2.11-SNAPSHOT" etc. Fine! As expected. >> >> However, for some reason the plugin isn't able to build all the >> required things... (not expected ;-) ) >> >> Missing: >> ---------- >> 1) org.apache.myfaces.trinidad:trinidad-api:test-jar:tests:1.2.10 >> >> Try downloading the file manually from the project website. >> >> Then, install it using the command: >> mvn install:install-file >> -DgroupId=org.apache.myfaces.trinidad -DartifactId=trinidad-api >> -Dversion=1.2 >> >> Alternatively, if you host your own repository you can deploy >> the file there: >> mvn deploy:deploy-file >> -DgroupId=org.apache.myfaces.trinidad -DartifactId=trinidad-api >> -Dversion=1.2.1 >> oryId=[id] >> >> Path to dependency: >> 1) org.apache.myfaces.trinidad:trinidad-impl:jar:1.2.10 >> 2) >> org.apache.myfaces.trinidad:trinidad-api:test-jar:tests:1.2.10 >> >> ---------- >> 1 required artifact is missing. >> >> for artifact: >> org.apache.myfaces.trinidad:trinidad-impl:jar:1.2.10 >> >> from the specified remote repositories: >> central (http://repo1.maven.org/maven2), >> java.net (http://download.java.net/maven/1), >> apache.snapshots >> (http://people.apache.org/repo/m2-snapshot-repository) >> >> >> the pom in question is here: >> https://svn.apache.org/repos/asf/myfaces/trinidad/trunk_1.2.x/pom.xml >> >> > >> > -M >> > >> > -- >> > Matthias Wessendorf >> > >> > blog: http://matthiaswessendorf.wordpress.com/ >> > sessions: http://www.slideshare.net/mwessendorf >> > twitter: http://twitter.com/mwessendorf >> > >> >> >> >> -- >> Matthias Wessendorf >> >> blog: http://matthiaswessendorf.wordpress.com/ >> sessions: http://www.slideshare.net/mwessendorf >> twitter: http://twitter.com/mwessendorf > > Hi > > After see that bug, I always do mvn install (to build the missing artifacts > on local repository), mvn release:rollback and try again. I know, it is ugly > (this should not happen) but works. Personally, I only use maven release > plugin for prepare releases (in other words create the branch, check no > snapshot versions used and other validations, and update the pom versions)
same here :-) > in a automated way. Any suggestion about how to do those tasks automatically > without this plugin? actually, I found this: http://jira.codehaus.org/browse/MRELEASE-3 -M > > regards > > Leonardo Uribe > > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
