-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-
bounces@xxxxxxxxxxx] On Behalf Of Esteban Dugueperoux
Sent: Montag, 19. November 2012 15:07
To: tycho-user@xxxxxxxxxxx
Subject: [tycho-user] Eclipse product materialization with feature patch
failed
Hi Tycho community,
We have a Eclipse based product whose build is tycho driven (release
0.16.0), our product includes some feature patchs about some GMF
plugins, but when building (mvn package) for Eclipse 3.8 the
materialize-products goal failed with the following message from p2 :
Cannot complete the install because one or more required items could not
be found.
Software being installed: OurProduct X.Y.Z.timestamp
(com.examle.outproduct.product OurProduct X.Y.Z.timestamp)
Missing requirement: Graphical Modeling Framework (GMF) Runtime
1.6.0.v20120517-1809-7d9X7FFYnmMJUVOKcqPSgIiK281V
(org.eclipse.gmf.feature.group
1.6.0.v20120517-1809-7d9X7FFYnmMJUVOKcqPSgIiK281V) requires
'org.eclipse.gmf.runtime.emf.clipboard.core [1.5.0.v20120514-1615]' but
it could not be found
Cannot satisfy dependency:
From: OurProduct X.Y.Z.timestamp (com.examle.outproduct.product
OurProduct X.Y.Z.timestamp)
To: org.eclipse.gmf.runtime.sdk.feature.group 0.0.0
Cannot satisfy dependency:
From: Graphical Modeling Framework (GMF) Runtime SDK
1.6.0.v20120517-1809-67R09E9QuFflXswwIO_z0E3d4k_X
(org.eclipse.gmf.runtime.sdk.feature.group
1.6.0.v20120517-1809-67R09E9QuFflXswwIO_z0E3d4k_X)
To: org.eclipse.gmf.feature.group
[1.6.0.v20120517-1809-7d9X7FFYnmMJUVOKcqPSgIiK281V]
Our pom.xml to build includes :
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-repository-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<includeAllDependencies>true</includeAllDependencies>
</configuration>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-director-plugin</artifactId>
<version>${tycho-version}</version>
<executions>
<execution>
<!-- install the product for all configured os/ws/arch
environments
using p2 director -->
<id>materialize-products</id>
<goals>
<goal>materialize-products</goal>
</goals>
</execution>
<execution>
<!-- (optional) create product zips (one per os/ws/arch) -->
<id>archive-products</id>
<goals>
<goal>archive-products</goal>
</goals>
</execution>
</executions>
<!-- (optional) customize the root folder name of the product
zip -->
<configuration>
<products>
<product>
<id>${product-id}</id>
<rootFolder>OurProduct</rootFolder>
<archiveFileName>OurProduct-X.Y</archiveFileName>
</product>
</products>
</configuration>
</plugin>
<!-- workaround for
https://bugs.eclipse.org/bugs/show_bug.cgi?id=349421 -->
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.5</version>
<executions>
<execution>
<id>copy-resources</id>
<phase>generate-resources</phase>
<goals>
<goal>copy-resources</goal>
</goals>
<configuration>
<outputDirectory>${project.build.directory}/products/${product-
id}/icons/</outputDirectory>
<nonFilteredFileExtensions>
<nonFilteredFileExtension>ico</nonFilteredFileExtension>
<nonFilteredFileExtension>xpm</nonFilteredFileExtension>
</nonFilteredFileExtensions>
<resources>
<resource>
<directory>icons</directory>
</resource>
</resources>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
If I comments the plugin section about materialize-products and
archive-products, I leave only the p2 repo build, the build succeeds and
the produced artifact includes our forks . And in the opposite If I
disable the references to our forks, the product materialization
succeeds but without our forks.
There is a know issue about the product materialization including
feature patchs?
In our use cases we have forked
"org.eclipse.gmf.runtime.emf.clipboard.core" plugin with 2 feature patch
because the plugin is available through 2 GMF features :
org.eclipse.gmf.runtime.sdk
and
org.eclipse.gmf
Best Regards.
--
Esteban Dugueperoux
Obeo
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
