No problem, it give us a chance to better organize :-)
Hudson is capable to send a mail to the commiter only, but I guess with
some configuration (may be the commiter email info in the pom.xml).
Dimitri BAELI - eXo Platform SAS
On Fri, Oct 9, 2009 at 12:03 PM, Christophe Laprun <claprun(a)redhat.com>wrote:
On Oct 9, 2009, at 7:35 AM, Julien Viet wrote:
Last commit broke the build. And will probably block the night team in
VN :-)
http://builder.exoplatform.org/hudson/view/All/job/gatein-portal-trunk/97...
it is a snapshot issue. Chris has taken the initiative to do a minor
refactor of the portlet container (moving the LOCAL_PORTLET_INVOKER_ID
constant from one class to another) that is not yet visible to the world
depending on it.
Indeed. This was however fixed within the hour.
I see two issues here:
1/ modifying an API used by a consumer (outlined by org.gatein.pc.api
package name)
That modification was prompted by the use of hardcoded PC implementation
details in Portal and the subsequent effort to mitigate this issue.
2/ the usual issue of using snapshots with a random life cycle driven by
trunk development
True. We definitely need to setup a better development model for
post-beta02.
In the mean time, rollbacking is the way to go, with, if possible, an email
sent to the offending committer to notify them that their last commit was
rollbacked.
Sorry about that. :(
Cordialement / Best,
Chris
==
Principal Software Engineer / JBoss Enterprise Middleware Red Hat, Inc.
Follow JBoss Portal:
http://jbossportal.blogspot.com /
http://twitter.com/jbossportal
Follow me:
http://metacosm.codepuccino.com /
http://twitter.com/metacosm