Hi,
The 1.5.0.v20120514-1615 is the original release of the
org.eclipse.gmf.runtime.emf.clipboard.core plugin for GMF on
Eclipse 3.8, our forked of this plugin has the release
1.5.0.v20121109-1730. If I disable the product materialization, it
is the 1.5.0.v20121109-1730 release (our fork) which is existing
in the produced target/repository/ p2 repo. But this seems normal
:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=378794
Our build works like that :
1. We have com.example.patches.juno3.update maven project with a
category.xml declaring which feature patchs to use :
- org.eclipse.gmf.feature.patch (to have our
org.eclipse.gmf.runtime.emf.clipboard.core installed when
org.eclipse.gmf feature is installed)
- org.eclipse.gmf.runtime.sdk.feature.patch (to have our
org.eclipse.gmf.runtime.emf.clipboard.core installed when
org.eclipse.gmf.runtime.sdk feature is installed)
2. After feature patchs builded the resulting p2 repo is available
to our Eclipse based product build, this last has a
com.example.product.juno3 maven projet with a category.xml
declaring which features to use including our feature patchs :
<feature id="org.eclipse.gmf.feature.patch" version="0.0.0"
patch="true">
<category name="od"/>
</feature>
<feature id="org.eclipse.gmf.runtime.sdk.feature.patch"
version="0.0.0" patch="true">
<category name="od"/>
</feature>
It is this same maven project which has the product.product and in
its pom.xml defines the product materialization.
On 19/11/2012 15:50, Oberlies, Tobias wrote:
If you disable product materialization, is org.eclipse.gmf.runtime.emf.clipboard.core [1.5.0.v20120514-1615] included in the p2 repository?
Did you include both feature patches in your product?
Regards
Tobias
-----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
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user