Re: maven.xml is pointing to the wrong version of OpenEJB in branches/1.1

[David Jencks]

On Sep 23, 2006, at 6:15 AM, Vamsavardhana Reddy wrote: Is branches/1.1 frozen?  I thought it is only tags/* that are frozen. no branches/x.x are frozen: they can be fixed  all tags/* are frozen and they cannot be changed This problem suggests to me that m:co and similar goals have no place in a build script and if we keep the facility they need to go in something that isn't a build script. I also wonder if we should be zipping up the maven repo used for a released build and stashing it in the svn tag for the release.  e.g start with empty m repo, build g, remove all g artifacts from the repo, and zip it up.  Checking that g then builds offline is probably a good idea too. thanks david jencks Vamsi On 9/23/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote: On 9/23/06, Jay D. McHugh <[EMAIL PROTECTED]> wrote: > Hello all. > > I didn't figure this was worth a JIRA. It still is ;-) > The maven.xml file in branches/1.1 is still pointing to codehaus for its > openejb checkout (and an older version too). > > Here is a patch (my first patch for Geronimo!) Thanks Yay for having caught it! I don't know if I can patch the branch after it's released? I mean, to me the branch is frozen. OTOH, it's unreasonable to create another branch just to patch 1.1 - it doesn't require a separate release. I'd like to hear others' opinion before proceeding. Unless I hear an objection, I'll patch it after 48h have passed. Jacek -- Jacek Laskowski http://www.laskowski.net.pl