Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] running swtbot with my eclipse target platform without shipping it

Found the issue: /Tonny

Tonny Madsen
My profiles: LinkedIn Twitter Blogger SlideShare

On Mon, May 27, 2013 at 9:43 AM, Tonny Madsen <tonny.madsen@xxxxxxxxx> wrote:
We do exactly this. We have the following POM parents:

...parent - with the top-level properties, profiles, plug-in declarations, ...
...core.parent - parent for all core bundles - EMF models, debug, log,... - basically stuff that does not use org.eclipse.ui or friends and will be used in both client and server
...core.test.parent - parent for all tests for core bundles
...client.parent - parent for all client UI bundles (with IDE, BIRT, and many other things)
...client.test.parent - parent for all tests for client bundles
...server.parent - parent for all server bundles (with Equinox, RAP, BIRT Runtime, ...)
...server.test.parent - parent for all tests for server bundles

Each of these currently have their own target platform (except the top-level parent). We do have a number of things that are used for both the client and the server and use UI, but we have compiled these as part of the server as RAP basically is a reduced RCP - we do test these in two test bundles for the client and the server - just to make sure, "everything" works...

Our biggest problem in the development is that it is NOT possible to have a common target platform that can be used in the Eclipse IDE - as it is not possible to combine RCP and RAP bundles - and we would want a separate TP for every bundle anyway... (I think, there are a longstanding Bugzilla on this)...

Also note that the needed test bundles for the target platform differs a little between RCP and RAP, so it does not really make so much sense to try to have a layered approach to target platforms.

So... we have 6 different target platforms - maintained by hand - where two of them are used by the developers (client.test and server.test).

(Actually, we have 8 different target platforms, as we also have the client target platforms based on 4.x as well as 3.x...)


Tonny Madsen
My profiles: LinkedIn Twitter Blogger SlideShare

On Fri, May 24, 2013 at 10:16 AM, Oberlies, Tobias <tobias.oberlies@xxxxxxx> wrote:

The missing “scoped dependencies” in PDE/OSGi is the reason why Tycho separates tests and productive code into separate module.


And every module has its own target platform. In most projects, all module’s target platforms have the same (external) content because they have the same target platform configuration. But you are free to configure each module separately. And if the configuration is complicated, you may want to introduce an additional parent for your tests.





From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Tonny Madsen
Sent: Freitag, 24. Mai 2013 07:07
To: Tycho user list
Subject: Re: [tycho-user] running swtbot with my eclipse target platform without shipping it


Wouldn't it be very nice, if we could separate the two sets? Have two target platforms - one for the product and one with the additional stuff needed for testing - as used in maven. And yes, I know this is not supported by PDE either...




Tonny Madsen

My profiles: Image removed by sender. LinkedIn Image removed by sender. Twitter Image removed by sender. Blogger Image removed by sender. SlideShare


On Fri, May 24, 2013 at 5:06 AM, Mengxin Zhu <kane.zhu@xxxxxxxxxxxxx> wrote:

Target platform always defines the plug-ins required by runtime of your product and for compiling and test purposes. Which plug-ins can be shipped with your product is defined by your .product file.

Mengxin Zhu

On 05/24/2013 05:16 AM, Peter Kahn wrote:

Hi all,

What's the right way to run SWT bot tests against our explicitly defined target platform?


We are creating an eclipse app and have swtbot plugins to run tests against it.  If we add our custom plugins, SWTbot plugins and our SWTbot tests to the target platform we can run the tests against our app.  This also means we would ship the tests with the app.

What are our options?

- multiple target platform definitions?

- component scope in target platform (similar to maven dependency scope)?

- different organization between our app and SWTbot tests to use implicit target definition?

Please let me know if you know of a good example.  The doc below has TBD right where I'd like more information.

When I'm done, I'll add in what I find to the doc.



Peter Kahn
Awareness - Intention - Action


tycho-user mailing list


tycho-user mailing list


tycho-user mailing list

Back to the top