We're currently including SWTBot 2.0.5 in the JBT 4.1 (Kepler-based)
target platform to allow tests to build & run.
However, 2.1 is now available. Does anyone want this new version
included in the Kepler-based target platform for JBT 4.1?
If so, please open a JIRA requesting it be evaluated & then added to our
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Tycho 0.17.0 is about to be released. For us, this affects the following
[JBIDE-11558] Repositories are missing source feature titles [Open,
Major, (Build/Releng, updatesite, UpStream), mickael_istria]
[JBIDE-13420] descriptionURL attribute is missing in feature.properties
file for org.jboss.tools.openshift.egit.integration.test.feature,
org.jboss.ide.eclipse.as.test.feature [Closed, Major, (JBossAS/Servers,
openshift), dgolovin] https://issues.jboss.org/browse/JBIDE-13420
[JBDS-2497] Building JBDS product w/ -Ppack200 results in NPE and build
failure [Open, Major, (Build), mickael_istria]
If you get a chance to test building your project w/ Tycho 0.17.0,
please do so & report any problems in JIRA or to Eclipse Bugzilla, as
appropriate. You can test using the instructions posted below, or simply
$ mvn clean install -DtychoVersion=0.17.0-SNAPSHOT
Unless something blocks it, I expect that we'll be moving up to this new
version in the parent pom in master branch in the next week or so.
-------- Original Message --------
Subject: [tycho-user] please test staged tycho 0.17.0
Date: Mon, 18 Mar 2013 10:58:05 +0000
From: Sievers, Jan <jan.sievers(a)sap.com>
Reply-To: Tycho user list <tycho-user(a)eclipse.org>
To: Tycho user list <tycho-user(a)eclipse.org>
Tycho milestone release 0.17.0 has been staged.
For details of new features and bugfixes, see release notes .
Please help by testing the staged milestone build.
To use it, change your tycho version to 0.17.0 and add snippet  to
We encourage you to also test with an empty local Maven repository,
so that p2's new Apache httpclient v4 is tested more extensively.
We plan to promote this release on Friday unless major regressions are
found (and EclipseCon is canceled ;).
tycho-user mailing list
It doesn't but at least now test are actually running, instead of wainting for display.sleep to return control.
Sent from my phone
Rob Stryker <rstryker(a)redhat.com> wrote:
>jbosstools-dev mailing list
>The problem is (was) that:
>* The ESB tests require the ESB UI which requires Zest - tests build fails on master for 7.0
>* Zest is not in the JBT test package, but it is in the JBTIS test package
we probably need Zest for other reasons anyway so that probably makes sense to add to core TP anyway.
>* Adding JBTIS TP repo to our root pom in integration-tests would affect all our tests:
>-> The tests would run slower
Hopefully not...did you see a big effect ?
>-> The JBTIS test package might affect our tests - we might miss issues of plugins not being in the JBT test package
not following what you mean here ? if JBTIS test package does affect your test we want to know about it ;)
That said you should be using JBTIS since that is where the esb plugins are. Can't just use jbosstools core as base for this.
>So - what are the solutions?
Split out the github repository and move the integration-platform tests to a separate repo.
>* We had talked about this in the past - creating a new SOA test repo
integration-test repo - its no longer just SOA.
>-> The SOA 6 tests will be affected (remember that the ESB examples are still not configured here with JBTIS)
>-> This will mean that existing 4.0.x work would move to the new repo
you'll need to migrate the history very carefully yes.
>-> Everyone using the SOA tests will have to adapt
>-> What else can go wrong?
>Need to tell Drools tests - BRMS team - Lukas Petroviky
>- the BRMS team has no one to do the testing at the moment.
maybe this was discussed a while ago but is it ok that a security warning occurs during installing any jboss tool?
Quality Assurance Associate
JBoss SOA Platform
IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
I invited jbossbot into #jbosstools and it will be reporting on pushes and pullrequests on jbosstools/jbosstools-* repositories.
It should not be too noisy, but if it does we can easily disable and even throttle some of it.
jbossbot also will take over doing jira lookups and unfortunately only support JBIDE-34324 format and not jbide-34324 so
get used to use the capslock key for that :)
jbott will thus now just do what is needed for transcript.jboss.org.
Thought this was worth sharing - i'm not sure if we will be affected by it but
I could imagine our target platform and/or product builds might need a refresh
to adjust for the changes coming in M6.
----- Forwarded message from David M Williams <david_williams(a)us.ibm.com> -----
>From: David M Williams <david_williams(a)us.ibm.com>
>To: eclipse-dev(a)eclipse.org, Eclipse Cross Project Issues <cross-project-issues-dev(a)eclipse.org>
>Date: Thu, 14 Mar 2013 00:08:30 -0400
>Subject: [eclipse-dev] Heads up .... a change to Eclipse Platform's traditional milestone composite repository coming for M6
>This note is primarily for those that build against the Eclipse Platform's
>composite repository at .../eclipse/updates/4.3milestones after the
>Platform milestone is delivered. While that's not a recommend practice, I
>get the impression lots of people do it. For everyone else, you will just
>find this information very interesting, I'm sure, but it will not effect
>Traditionally, we leave each milestone "connected" to the composite. This
>allows rolling back an installation. But, there has been so many changes
>since M5, due to the build technology used and other changes since Juno
>SR2, that we plan to provide only M6 at that composite site, for M6. This
>will help "force" issues to appear, if there are any, rather than waiting
>until the end of the release and then everyone being surprised. Many
>details are in bug 395030 
>Bug 395030 - Disconnect old milestone repos for M6
>But, I'll summarize here:
>There are 6 or 12 changes related to things we intentionally removed, that
>would be a factor regardless of the build technology used (such as the
>"org.junit4" change many of you already discovered).
>There are 6 or 12 known issues related to things missing from the new
>build that we plan to correct by M7 (mostly missing *.source bundles).
>But, there are several hundred changes related to the "low level" p2 IUs
>(tooling* and *_root IUs) that are involved in building products or RCP
>apps for specific platforms or Operating Systems. We are assuming that the
>exact names of these IUs don't really matter to anyone, and that
>everything needed really is there and working, just named differently ...
>but ... that's the reason we plan on forcing the issue by providing only
>M6 at that composite repo. More details are in the bug so you can read
>ahead of time, but let us know, in that bug or a new one, if there are
>issues encountered. We will of course leave the older repos (M1 to M5a)
>around in case an "emergency work around" is needed for the milestone, but
>we'll cross that bridge if or when we get to it. We expect things to go
>smoothly, we just want to make sure.
>eclipse-dev mailing list
>To change your delivery options, retrieve your password, or unsubscribe from this list, visit
----- End forwarded message -----