[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[tycho-user] Tycho build extension not configured when running before package phase
|
Hi,
I am trying to build an eclipse-repository project and process the
generated metadata in between build steps.
Since I want to edit the repository's own p2content.xml before the site
gets assembled (in order do some processing on the categories) as well
as the final content.xml (in order to add repository references and do
some more processing), I would like to move the
tycho-p2-publisher-plugin to an earlier phase to get the execution order
for my processing right.
But something like
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-publisher-plugin</artifactId>
<executions>
<execution>
<id>publish-categories</id>
<phase>process-resources</phase>
<goals>
<goal>publish-categories</goal>
</goals>
</execution>
</executions>
</plugin>
with any phase earlier than package leads to
LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-categories (publish-metadata):
> Execution publish-metadata of goal
org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-categories
failed: Tycho build extension not configured for MavenProject
Judging by the exception, it seems the target platform is not available
at this point:
Caused by: java.lang.IllegalStateException: Tycho build extension not configured for MavenProject
at org.eclipse.tycho.core.utils.TychoProjectUtils.getTargetPlatform(TychoProjectUtils.java:70)
at org.eclipse.tycho.p2.facade.RepositoryReferenceTool.addTargetPlatformRepository(RepositoryReferenceTool.java:115)
at org.eclipse.tycho.p2.facade.RepositoryReferenceTool.getVisibleRepositories(RepositoryReferenceTool.java:96)
at org.eclipse.tycho.plugins.p2.publisher.AbstractPublishMojo.createPublisherService(AbstractPublishMojo.java:52)
at org.eclipse.tycho.plugins.p2.publisher.AbstractPublishMojo.execute(AbstractPublishMojo.java:36)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Is there any way around this?