[news.eclipse.tools.buckminster] Re: Don't know how to materialize a tes

["Tas Frangoullides" <tfrangoullides@xxxxxxxxxxxxxxxxxx>]

Hi,

I've worked round most of the problems. The least satisfatory aspect is that 
I've had to create my own update site of the eclipse test framework. I've 
then used an ant script to call p2 director a few times to install the test 
environment. It works but I've really gone outside of buckminster's 
capabilities to achieve it. As a next step I'll probably try and bring 
things back under buckminster control by wrapping piecces of it as 
buckminster actions, however this still isn't ideal.

Are there any plans to bring the functionality offered by p2 director into 
buckminster. I think it could be worthwhile and if it leveraged resource 
maps to locate the installable units that would be really tidy.

Thanks,
Tas






"Tas Frangoullides" <tfrangoullides@xxxxxxxxxxxxxxxxxx> wrote in message 
news:h58s3m$5uh$1@xxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I'm trying to add testing to my buckminster build for an RCP product. I 
> figured the following would be good steps to perform after building the 
> product site.
>
> Install the product from the newly created site using headless director
> Install Eclipse Test Framework into the product
> Install Test Plugins into the product
> Run tests and collect results
>
> This is proving quite tricky. The first issue is that the eclipse test 
> framework has dependencies on bundles which are not in my product (such as 
> org.hamcrest.core). As a temporary workaround I installed the 
> org.eclipse.platform into the product just to see if I can get it working. 
> The next problem is that I've only been able to find an archive version of 
> the eclipse test framework and no update site and I don't know how to get 
> director to install it.
>
> I was wondering if I could use the p2 materializer to create the new test 
> environement thinking this would be great if it worked becuase using 
> buckminster would enable the test framework dependencies to also be 
> resolved. This almost work in that the right plugins are copied across but 
> they are not actually "installed" when the product is launched.
>
> Johannes has a solution that work for him, building a seperate rcp product 
> that includes the test dependencies. I'm thinking maybe I should do that, 
> but I still have the problem of getting the eclipse test framework 
> installed from a zip archive.
>
> Thanks,
> Tas