[news.eclipse.tools.buckminster] Re: How to ensure the exact same target

[Thomas Hallgren <thomas@xxxxxxx>]

Hi Tas,
One option is to take advantage of the split between resolution and materialization. If you do an 
import with --bomfile <aFile> you'll get a Bill Of Material (BOM) file that represents the 
resolution. You can then appoint this BOM instead of a CQUERY from your MSPEC or when issuing 
another import. That way, you ensure that no new resolution takes place. The BOM appoints explicit 
versions and should guarantee that you always get the exact same version of everything that it contains.

Regards,
Thomas  Hallgren


Tas Frangoullides wrote:
> I am materializing a target platform by using a feature which includes 
> the features I want in my target platform. For example here is my feature
>
> <feature
>      id="com.mialos.tutorial.mailapp.targetplatform"
>      label="Targetplatform"
>      version="1.0.0.qualifier"
>      provider-name="ME">
>   <includes
>         id="org.eclipse.equinox.executable"
>         version="3.3.200"/>
>   <includes
>         id="org.eclipse.rcp"
>         version="3.5"/>
> </feature>
>
> Materialization works fine when the versions in the target feature are 
> available. I tried changing the rcp version to 3.6 and it failed as I 
> expected. However, when I tried changing it to 3.4 it still worked and 
> materialzed 3.5 instead. I can see how this might be desirable in some 
> applications but I really need the versions to be exact in this case. 
> How do I achieve it?
>
> Thanks,
> Tas