Just a reminder, because the parent pom in the M5 branch is different
from the one in trunk (but versioned the same), you need to remember to
rebuild it from the correct stream (branches/jbosstools-3.3.0.M5, trunk)
before attempting to build any components, sites, features, tests, or
This will ensure that anything you don't have built locally on disk will
be fetched as upstream binary dependency from the correct place on
(ie., the nightly trunk sites or the nightly
This also means if you depend on our parent pom but your sources are
elsewhere (eg., Savara, Scribble, pi4soa, Teiid), your job must fetch &
build the correct version of the parent pom from the correct branch of SVN.
Any questions / confusions, don't hesitate to ask.
On 12/04/2011 11:19 AM, Nick Boldt wrote:
3.3.indigo jobs  are now enabled.
Trunk jobs  are now disabled to save space/time on slaves. This means
work toward Beta1 will NOT be built automatically in Jenkins for the
next few days.
Please compile your stuff locally using maven to verify your commits
don't break trunk. You'll also have to run your tests locally (with
maven/m2e, not just in Eclipse w/ PDE JUnit runner, please).
When we are set to give the first M5 builds to QE, I will turn the trunk
jobs  back on.
On 12/03/2011 07:15 PM, Nick Boldt wrote:
> Branches created:
> Note that we are code frozen for M5, which means only urgent fixes
> should be done in the branch, associated w/ a JIRA.
> Trunk remains open for new development work.
> Where applicable, please remember to commit changes in BOTH trunk and
> the new branch.
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio