Default Target Platform is empty while launching Eclipse by Maven testshttps://www.eclipse.org/forums/index.php/mv/msg/204853/655133/#msg_655133
I'm trying to integrate some SWTBot-Tests to our maven build process. The integration works and Eclipse is executed with all plug-ins I need to run my tests. During the test I'm creating plug-in projects with dependencies to org.eclipse.ui for example. These dependencies should be resolved by the default target platform of eclipse. If I launch the tests from within Eclipse the default target platform contains all required plug-ins. But if I launch those tests from within the Maven build the target platform contains only an osgi and some launcher bundles.

Sounds like a mistake in the Maven build, but lets discuss what Maven Tycho does: It creates a directory it uses as %ECLIPSE_HOME%. This directory contains a plugins folder containing the osgi and the launcher bundles. It also contains a configuration folder in which they place the config.ini file. This config.ini file defines all bundles which should be installed / started for the Eclipse test instance. They can be resolved correctly, but all references to bundles point to my local Maven Repository. So the configuration by Tycho looks fine, but different to what %ECLIPSE_HOME% normally looks like. Normally all installed plugins will be located in the plugins directory of %ECLIPSE_HOME%. In this case not, but is that really wrong?

Is it correct, that PDE is not using the config.ini file to resolve the contents of the default target platform?

I already started a discussion on the tycho-users mailinglist with that problem, but they are not sure about what PDE requires in this case. The discussion can be found here: http://software.2206966.n2.nabble.com/Eclipse-UI-Tests-with- maven-osgi-test-plugin-td6036492.html
You can also find a simple test project there which can be build with maven to demonstrate the problem.]]>Johannes Lerch2011-02-18T13:07:17-00:00Re: Default Target Platform is empty while launching Eclipse by Maven testshttps://www.eclipse.org/forums/index.php/mv/msg/204853/665935/#msg_665935
I'd like to make a "up" on this topic since it is a blocking point for testing PDE-related projects with Tycho. Actually what is happening is that with Tycho, there is no real ${eclipse_home}, and instead of that, the bundles are listed in config.ini. Then the default target platform, which points to ${eclipse_home} contains no bundle and then PDE does not succeed to build bundles in development workspace.

Having target platform resolution based on actual bundles of the IDE rather than listing available ones in ${eclipse_home} is a blocking requirement to have Tycho working for projects dealing with PDE (PDE, EMF, GMF-Tooling, XText... and all other project that generate some bundles).

Should I open a bug report or a feature request for that?

Regards

Le 18/02/2011 14:07, Johannes Lerch a écrit :
> Hi,
>
> I'm trying to integrate some SWTBot-Tests to our maven build process. The integration works and Eclipse is executed with all plug-ins I need to run my tests. During the test I'm creating plug-in projects with dependencies to org.eclipse.ui for example. These dependencies should be resolved by the default target platform of eclipse. If I launch the tests from within Eclipse the default target platform contains all required plug-ins. But if I launch those tests from within the Maven build the target platform contains only an osgi and some launcher bundles.
>
> Sounds like a mistake in the Maven build, but lets discuss what Maven Tycho does: It creates a directory it uses as %ECLIPSE_HOME%. This directory contains a plugins folder containing the osgi and the launcher bundles. It also contains a configuration folder in which they place the config.ini file. This config.ini file defines all bundles which should be installed / started for the Eclipse test instance. They can be resolved correctly, but all references to bundles point to my local Maven Repository. So the configuration by Tycho looks fine, but different to what %ECLIPSE_HOME% normally looks like. Normally all installed plugins will be located in the plugins directory of %ECLIPSE_HOME%. In this case not, but is that really wrong?
>
> Is it correct, that PDE is not using the config.ini file to resolve the contents of the default target platform?
>
>
> I already started a discussion on the tycho-users mailinglist with that problem, but they are not sure about what PDE requires in this case. The discussion can be found here: http://software.2206966.n2.nabble.com/Eclipse-UI-Tests-with- maven-osgi-test-plugin-td6036492.html
> You can also find a simple test project there which can be build with maven to demonstrate the problem.

--
Mickael Istria -- BonitaSoft S.A.http://www.bonitasoft.com/products/BPM_download.php
Eclipse Community Award 2011: Best Modeling Tool]]>Mickael Istria2011-04-18T08:46:53-00:00Re: Default Target Platform is empty while launching Eclipse by Maven testshttps://www.eclipse.org/forums/index.php/mv/msg/204853/665995/#msg_665995
--
Mickael Istria -- BonitaSoft S.A.http://www.bonitasoft.com/products/BPM_download.php
Eclipse Community Award 2011: Best Modeling Tool]]>Mickael Istria2011-04-18T14:03:33-00:00Re: Default Target Platform is empty while launching Eclipse by Maven testshttps://www.eclipse.org/forums/index.php/mv/msg/204853/987608/#msg_987608
I'm also having the same issue. I was wondering if you managed to find some feasible workaround for it?

I checked the bugs, but there does not seem to be any development.

Thanks
Filip]]>Filip Krikava2012-11-27T10:24:08-00:00Re: Default Target Platform is empty while launching Eclipse by Maven testshttps://www.eclipse.org/forums/index.php/mv/msg/204853/987647/#msg_987647
> Hi,
>
> I'm also having the same issue. I was wondering if you managed to find
> some feasible workaround for it?
> I checked the bugs, but there does not seem to be any development.
>
> Thanks
> Filip