Re: [cbi-dev] Building the doc: selecting a version for the eclipserun p

["Sievers, Jan" <jan.sievers@xxxxxxx>]

it pulls from the target platform of the current project (which includes intra-reactor dependencies).

Turns out Igor commented in the same direction already:

        // igorf: I am not convinced that using project dependencies is expected/desired here. Original usecase
        // for eclipse-run mojo was to build documentation index, which most likely does not require project
        // dependencies, but some other unrelated set of bundles.  

Tobias is currently working on bug 393686 so I think he has more knowledge here.

That said, you *may* be able to pin dependenies to specific versions with perfect version match.
Note I'm making this up on the fly and did not try it:

<plugin>
  <groupId>org.eclipse.tycho.extras</groupId>
  <artifactId>tycho-eclipserun-plugin</artifactId>
  <configuration>
    <dependencies>
      <dependency>
        <type>p2-installable-unit</type>
        <artifactId>my.iu.id</artifactId>
        <version>[1.0.0.pinnedversion,1.0.0.pinnedversion]</version>
      </dependency>
    </dependencies>
  </configuration>
</plugin>

this would be a workaround at best. 

Jan

From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx] On Behalf Of Paul Webster
Sent: Mittwoch, 21. November 2012 19:20
To: Common-build Developers discussion
Subject: [cbi-dev] Building the doc: selecting a version for the eclipserun plugin

I think we talked about it in the meeting, but we hit a problem running our doc build the first time:
Bug 393686 - tycho-eclipserun-plugin fails to run during build

I've asked on the bug, it turns out we probably want to specify an existing version of eclipse somewhere, as we don't want to build with what we're currently building.

Does eclipserun pull from p2 repos?  Would it be possible to specify the product IU and so effectively select an existing version?

Later,
Paul

-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR