On 8/7/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
I used it a while ago but I think you can bypass it by just using mvn deploy (if the repos in the pom are the production locations).
What do you mean by 'production locations'? I've changed a couple of the <distributionManagement>/<repository> elements to point at the snapshot repo to avoid anything going to the ibiblio-rsync repository by accident.
My suggestion is to do a search for -SNAPSHOT *anywhere* in the POM's. The only ones that should be there are for shared and core.
+1, we've managed to do a couple of releases at Struts by changing the version numbers manually then tagging it.
Speaking of shared, are we going to release that one first? In the past we decided not to publicly release it on ibiblio but to make it available on the mayfaces repo on the zone since its needed for compiling from the source.
Matthias, where are you planning to build the release? On the zone, or on your local machine? And how are we going to handle the vote? I think we should tag and build it as 1.1.4, run the TCK, then vote. Other opinions? (The guidelines on the wiki may need to be revised.) -- Wendy
