<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi all:<br>
<br>
I went ahead and committed a significant change to the 'common'
component. I had +1's from build and from the PM (max). I had what
seemed like a +1 from the common lead (Dennis), but I know in my
heart he hadn't fully had time to evaluate the patch. <br>
<br>
The reasons I went ahead and committed this patch on the weekend are
that we have only 1 week left for freeze. With everyone pushing tons
of small changes in this week, the merge would only get more and
more difficult to perform, and a broken build would become more and
more troublesome. <br>
<br>
Even still, I had to merge in changes from Viacheslav Kabanovich who
made commits to o.j.t.common. <br>
<br>
So, what does this mean for everyone? It means anyone doing any work
on 'common' at all, anyone who has it in their dev workspace, or
anyone who builds it often locally, will need to cd trunk/common;
svn update; They will also need to make sure that the
o.j.t.common.core plugin is added to their workspace. <br>
<br>
There was only a small hiccup in the first build after commit. Two
classes I had crafted by hand by accident were not properly
svn-added. THe second and third builds all went off perfectly,
however. <br>
<br>
I hope I didn't step on anyone's toes here, but I figured if we had
any hope on getting it in before m1 is frozen, it had to be done
this weekend, and I figured the weekend is a very quiet and safe
time to do it (so long as I don't mess it up ;) ). <br>
<br>
Anyway, I am now resolving JBIDE-12469 which was associated with
this bug, and will open a new bug for m2. <br>
<br>
Remember: anyone doing any dev work on common will need to svn
update! If they have any uncommitted changes in their workspace
against o.j.t.common, they will probably need to merge these changes
in locally to the same class in the o.j.t.common.core plugin. <br>
<br>
Anyone importing o.j.t.common packages will be unaffected at this
time. HOWEVER, after m1 is released, there *WILL* be a package
rename, and at that time, ALL consumers of these classes will need
to re-organize their inputs. <br>
<br>
Just be alert everyone. WIth JBT scheduled for 4.0.0 next year, this
is going to be a very active year, with plugins, features, and
entire components being added, removed, moved around, or
significantly changed. <br>
<br>
Let's keep communication open to make sure everything gets done. <br>
<br>
- Rob Stryker, still making trouble. <br>
<div class="moz-forward-container"><br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" cellpadding="0"
cellspacing="0" border="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>Jenkins build is back to normal :
jbosstools-3.3_trunk.component--common #1056</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Sat, 25 Aug 2012 02:30:37 -0400 (EDT)</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:ci-builds@redhat.com">ci-builds@redhat.com</a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:rob.stryker@jboss.com">rob.stryker@jboss.com</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>See <a class="moz-txt-link-rfc2396E" href="http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--common/1056/changes"><http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--common/1056/changes></a>
</pre>
<br>
<br>
</div>
<br>
</body>
</html>