Hi Harald, sounds reasonable to me. I'm +1 this way the prepare actually does prepare what is being released :)
regards, Achim 2012/6/4 Harald Wellmann <hwellmann...@googlemail.com>: > With the current Pax Exam milestone release, I had an issue that could > likely be addressed in the master POM: > > The release:perform goal failed with the javadoc plugin complaining about a > missing javax.faces class (which I never use directly), so I had to squash > the staging repository, delete the GitHub tag and start all over again... > > The lesson is that release:prepare should execute all goals running in > release:perform (except deploy, obviously) to avoid any unpleasant surprises > on the last mile. > > I haven't checked if there is anything special in the Pax Exam config or if > it's really in the master POM, but I do think the master is the place to > provide default settings to take care of this. > > WDYT? > > Regards, > Harald > > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home> Commiter & Project Lead blog <http://notizblog.nierbeck.de/> _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
