Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Tycho and single source RCP/RAP

Timo,

I am working on a single source application too. Could you share your whole POM or at least the part that shows the profiles? Also, how do you select a profile at build time?

Jay

On Oct 18, 2012 4:22 AM, "Timo Rohrberg" <rti.init@xxxxxxxxxxxxxx> wrote:
Hello Thorsten,

I guess, I had exactly the same problem in our single-sourcing RCP/RAP
application. I solved it by adding so-called "extra requirements"
definitions into my pom.xml configuration files to explicitely require
the corresponding semi-optional dependencies (in my case
org.eclipse.ui and org.eclipse.ui.views and the corresponding RAP
replacements). I placed that "extra requirements" definitions into
Maven profiles sections and select the appropriate profile for
building my application in "RCP-" and "RAP-"mode respectively.

The configuration of "extra dependencies" looks like this:

<plugin>
  <groupId>org.eclipse.tycho</groupId>
  <artifactId>target-platform-configuration</artifactId>
  <version>${tycho-version}</version>
  <configuration>
    <dependency-resolution>
      <optionalDependencies>ignore</optionalDependencies>
      <extraRequirements>
        <requirement>
          <type>eclipse-plugin</type>
          <id>org.eclipse.rap.ui</id>
          <versionRange>0.0.0</versionRange>
        </requirement>
        <requirement>
          <type>eclipse-plugin</type>
          <id>org.eclipse.rap.ui.views</id>
          <versionRange>0.0.0</versionRange>
        </requirement>
      </extraRequirements>
    </dependency-resolution>
  </configuration>
</plugin>

If you are interested in more details about my setup which - after
days of work and investigation - finally works quite smoothly, feel
free to ask.

Hope that helps.

Regards
Timo


2012/10/18 Thorsten Schlathoelter <tschlat@xxxxxx>:
> Hi,
> we have a single source RCP/RAP application that I am trying to build with tycho. The problem is that we need to mark specific ui bundles as optional because they are only present in either RAP or RCP target platform. E.g. org.eclipse.ui or org.eclipse.rap.ui. Actually these dependencies are semi optional. Depending on the platform to be build one representation has to be present.
>
> We need to configure tycho with
>
> <dependency-resolution>
>    <optionalDependencies>ignore</optionalDependencies>
> </dependency-resolution>
>
> in order to get the bundles resolved. But then when we try to compile, the respective optional platform bundles are not pulled from p2 into the maven repository. In the course this results in compile errors. The next problem is that the respective platform specific fragments do not compile because they depend on optional required bundles of their host plugin. Solving the fragment issue by adding the optional required bundles from the host to the fragment itself makes this post somewhat for the records. Because the fragment required bundle can be made non optional thus the dependencies are pulled from p2 and are available at compile time also for the host. Nevertheless if no such fragment exists which pulls the dependencies building single source RCP/RAP with tycho seems to be problematic.
>
> Any thoughts/hints on this?
>
> Regards,
> Thorsten
>
> _______________________________________________
> 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

Back to the top