| Re: [tycho-user] Creating product problems |
Hi Mikhail, I have still problem that additional all still added (I didn't find any dependency (optional or not) on them. I also tested it with tycho 0.20.0. I have following case: parent pom contains - to allow 32bit and 64 bit build: <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>target-platform-configuration</artifactId> <version>${tycho-version}</version> <configuration> <environments> <environment> <os>win32</os> <ws>win32</ws> <arch>x86</arch> </environment> <environment> <os>win32</os> <ws>win32</ws> <arch>x86_64</arch> </environment> </environments> </configuration> </plugin> in product pom I have specified: <plugin> <groupId>org.eclipse.tycho</groupId> <artifactId>target-platform-configuration</artifactId> <version>${tycho-version}</version> <configuration> <environments> <environment> <os>win32</os> <ws>win32</ws> <arch>x86</arch> </environment> </environments> <target> <artifact> <groupId>myGroup</groupId> <artifactId>myGroup.smallapps.target</artifactId> <version>1.0.0</version> </artifact> </target> </configuration> </plugin> And during materialize product I get foolowing log, which says that envoriment has ben changed, but target platform is not changed. --- tycho-p2-director-plugin:0.20.0:materialize-products (materialize-products) @ mygroup.smallapplication.product --- [DEBUG] Configuring mojo org.eclipse.tycho:tycho-p2-director-plugin:0.20.0:materialize-products from plugin realm ClassRealm[plugin>org.eclipse.tycho:tycho-p2-director-plugin:0.20.0, parent: sun.misc.Launcher$AppClassLoader@f4a24a] [DEBUG] Configuring mojo 'org.eclipse.tycho:tycho-p2-director-plugin:0.20.0:materialize-products' with basic configurator --> [DEBUG] (f) directorRuntime = internal [DEBUG] (f) installFeatures = true [DEBUG] (f) profile = ""> [DEBUG] (f) project = MavenProject: mygroup:mygroup.smallapplication.product:20.0.2-SNAPSHOT @ C:\Apps\Jenkins\jobs\Quick_build\workspace\mygroup.smallapplication.product\pom.xml [DEBUG] (f) session = org.apache.maven.execution.MavenSession@102d72d [DEBUG] (f) source = targetPlatform [DEBUG] -- end configuration -- [INFO] Installing product mygroup.smallapplication.product.product for environment win32/win32/x86 to C:\WS\trunk\SAPP\products\mygroup.smallapplication.product.product\win32\win32\x86 [DEBUG] Calling director with arguments: [-metadataRepository, file:/C:/WS/trunk/SAPP/,file:/C:/WS/trunk/SAPP/targetPlatformRepository/, -artifactRepository, file:/C:/WS/trunk/SAPP/,file:/resolution-context-artifacts@C:%5CApps%5CJenkins%5Cjobs%5CQuick_build%5Cworkspace%5Cmygroup.smallapplication.product,file:/C:/Apps/Jenkins/jobs/Quick_build/workspace/mygroup.smallapplication.application/target/,file:/C:/Apps/Jenkins/jobs/Quick_build/workspace/mygroup.smallapplication.log4j.properties/target/,file:/C:/Apps/Jenkins/jobs/Quick_build/workspace/mygroup.smallapplication.mvn.feature/target/,file:/C:/Apps/Jenkins/jobs/Quick_build/workspace/mygroup.xentryapps.target.feature/target/,file:/C:/Apps/Jenkins/jobs/Quick_build/workspace/.repository/, -installIU, mygroup.smallapplication.product.product, -destination, C:\WS\trunk\SAPP\products\mygroup.smallapplication.product.product\win32\win32\x86, -profile, DefaultProfile, -profileProperties, org.eclipse.update.install.features=true, -roaming, -p2.os, win32, -p2.ws, win32, -p2.arch, x86] Installing mygroup.smallapplication.product.product 20.0.2.20140404_1. Operation completed in 5132 ms. Kind regards / S pozdravem Jan Pešta SW Engineer Sr. CertiCon a.s., www.certiconglobal.com Vaclavska 12 12000 Prague 2 Czech Republic Office Prague: +420 224 904 200 Office Pilsen: +420 224 904 406 Mobile: +420 604 794 306 E-mail: jan.pesta@xxxxxxxxxxx From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Kalkov > could I have more than one target platform definition in maven reactor? Yes, each module can have its own target platform. It is somewhat uncommon, but one may use this e.g. to customize a common target platform for each module. I would guess that you may have some optional greedy dependencies, which are not satisfied by PDE target platform and satisfied by Tycho one. So, defining a target platform more strictly may help. As for the additional properties in launcher.ini file, is it a problem for you? I don't think I've ever seen a launcher.ini without them. If I were you, I would also try it with Tycho-0.20.0, so we all use the same version. Kind regards, Eclipse Developer | Purple Scout AB | www.purplescout.com Kyrkogatan 20-22, SE-41110 Gothenburg, Sweden On Wed, Apr 2, 2014 at 8:01 AM, Jan Pešta <jan.pesta@xxxxxxxxxxx> wrote: Hi Jeff, Unfortunately not. I have a plan to introduce it later. According to this, could I have more than one target platform definition in maven reactor? I am building about 5 product in one go – there are lots of plugin shared – and I want to safe build time (and have proper setup for sonar analysis, etc.). I am asking, because this problem is for me with one small product, where I don’t need those features, but in other product those features are needed. Thanks, Jan Kind regards / S pozdravem Jan Pešta SW Engineer Sr. CertiCon a.s., www.certiconglobal.com Vaclavska 12 12000 Prague 2 Czech Republic Office Prague: +420 224 904 200 Office Pilsen: +420 224 904 406 Mobile: +420 604 794 306 E-mail: jan.pesta@xxxxxxxxxxx From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Jeff MAURY Do you use a target platform ? Jeff On Tue, Apr 1, 2014 at 1:37 PM, Jan Pešta <jan.pesta@xxxxxxxxxxx> wrote: Hi All, I have a problem to materialize product using tycho. First we are using tycho 0.17.0 and eclipse helios as target platform. I have product configuration which if I export directly from eclipse it works for me. When I export this product, it is completely different to what I get exporting it from eclipse. I found one issue – tycho product build add some features which I don’t want to have – and they are not defined in product file: Org.eclipse.equinox.p2.user.ui Org.eclipse.help Org.eclipse.platform With export (or PDE build) was only included referenced feature org.eclipse.rcp. Next thing is that launcher.ini file contains additional properties than specified in product file (which are not there if exported from eclipse or using PDE build). -startup plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.2.R36x_v20101222 I think this is not new questions, but I was unable to find any answer to my questions. Thanks, Jan Kind regards / S pozdravem Jan Pešta SW Engineer Sr. CertiCon a.s., www.certiconglobal.com Vaclavska 12 12000 Prague 2 Czech Republic Office Prague: +420 224 904 200 Office Pilsen: +420 224 904 406 Mobile: +420 604 794 306 E-mail: jan.pesta@xxxxxxxxxxx
--
|
