Hi, On Mon, Mar 17, 2008 at 9:47 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Matthias Wessendorf schrieb: > > > Hi, > > > > On Mon, Mar 17, 2008 at 9:10 AM, Bruno Aranda <[EMAIL PROTECTED]> wrote: > > > >> Good. Strangely enough I was using orchestra core 1.1-SNAPSHOT and moving > to > >> the released 1.1 fixes the issue. Thanks! > >> > > > > I am really glad that this fix made it into the released 1.1 > > > The problem was never in the pre-1.1 trunk; it was added after the 1.1 > release preparation branch was created. And it hasn't been fixed yet; > the 1.2-SNAPSHOT releases will have this problem (though it certainly is > fixable).
yeah, fixable ;-) > > It is in the 1.1-SNAPSHOT versions because I forgot to update the > version-number in the trunk pom from 1.1-SNAPSHOT to 1.2-SNAPSHOT after > creating the 1.1 release branch. So the latest code was being published ok, now I really got it. nice :-) > with the wrong snapshot version (now fixed). That's mildly embarrasing > but no big deal. If I had used the maven-release-plugin that problem > wouldn't have happened, but I'm still glad I didn't use it; cutting a > release is much simpler without it. hrm, I can't agree on that one. -M > > Regards, > Simon > > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
