> Hi > > In a discussion on dev list, I have noted this comment: > > Simon > > I guess the other solution is to just do nothing until the *real* 1.2.1 > > release goes out, overwriting the bad files. I believe that is expected > > to happen in the next week or so. But I feel a little uncomfortable > > about that, and at the least we would need to notify the user list.
+1 in case they still were online, we just could override them. But... as a matter of fact, they aren't (as mentioned before): -http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/myfaces/core/myfaces-impl/ -http://repo1.maven.org/maven2/org/apache/myfaces/core/myfaces-impl/ -http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/myfaces/core/myfaces-impl/ (btw. same is true for API as well, NO 1.2.1 online). > Wendy > IMO there should not be a "real" 1.2.1 release now -- we should move > on to 1.2.2 to avoid confusion in case anyone has downloaded these bad > jars. hu? the next logical step would be a 1.2.1, IMO. we would confuse the people much more in just providing a 1.2.2 now, IMO. I am pretty sure, that a 1.2.2 will even confuse our community a bit. So how to manage not confusing others? Like vendors, that plan to provide support for MyFaces ? I really think it is not a good a idea to release a 1.2.2 after 1.2.0. > > The bad artifacts were available about 2 weeks, until it was removed > from main repo, > so there is a possible confusion if anyone downloaded the bad > artifacts. (myfaces-impl 1.2.1 > artifacts and myfaces-core-project related artifacts). you'd get a "fresh" JAR... > > regards > > Leonardo Uribe > -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf mail: matzew-at-apache-dot-org
