Thank you for your answers. Why don't you want your test deps available when building? >
Because my test dependencies contain a plugin (from MoDisco) in a version that resulted from the previous build. This plugin is built again from source during the build, resulting in a different (greater) version number. If the test dependencies are also used for building, then p2 complains while provisioning the test platform that it can't install two different versions of the same dependency at the same time (the one from the binary dependencies, and the one that was just built), and makes the build fail. As a workaround, we are now committing the needed files instead of using the binary dependency. On Thu, Dec 24, 2009 at 1:52 AM, Nick Boldt <nickbo...@gmail.com> wrote: > Uh, yeah... they do. SVN checkout works fine on build.eclipse.org > > And as Dave points out, you can have one job for build and one for test. > > Or, even simpler, rather than having 3 buckets of IUs for build, > build+test, and test (I picture a Venn diagram with two overlapping > circles), simply include everything you need for building and/or testing in > the IUsToInstall property and you'll be set for the whole process. > > Why don't you want your test deps available when building? > > > David Carver wrote: > >> Another way to do this is to split your job into two, I believe. And if >> you are using the ANT based JOBs instead of the BASH jobs, you can specify >> change your dependencies in the JOB configuration and pass in the >> appropriate property settings. >> >> Unfortunately, if you are using SVN, currently the ANT based jobs doesn't >> support SVN checkout correctly via MAP files. There is an open bug for >> that. >> >> Dave >> >> Nicolas Bros wrote: >> >>> Hi, >>> >>> MoDisco uses Acceleo generators, which need the bundle in which they are >>> defined to be installed for building them (so that the required metamodel is >>> in the EMF registry). >>> In order to bootstrap the build, I added the binary bundle resulting from >>> the previous build to the binary dependencies. >>> Problem is, when provisioning the testing target platform, P2 complains >>> that it cannot install this bundle twice, with 2 different versions. >>> >>> So, I'd like to be able to specify different binary dependencies for >>> building and testing. >>> Would it be possible to add properties like: >>> additionalIUsToInstallForBuild >>> additionalIUsToInstallForTest >>> -- >>> Nicolas Bros >>> R&D >>> tel: 06 75 09 19 88 >>> nb...@mia-software.com <mailto:nb...@mia-software.com> >>> nbros....@gmail.com <mailto:nbros....@gmail.com> >>> Mia-Software, 410 clos de la Courtine >>> 93160 Noisy-le-Grand >>> http://www.mia-software.com >>> .: model driven agility :. >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> dash-dev mailing list >>> dash-dev@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/dash-dev >>> >>> >> >> >> _______________________________________________ >> dash-dev mailing list >> dash-dev@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/dash-dev >> > > -- > Nick Boldt :: http://nick.divbyzero.com > Release Engineer :: Eclipse Modeling & Dash Athena > > _______________________________________________ > dash-dev mailing list > dash-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/dash-dev > -- Nicolas Bros R&D tel: 06 75 09 19 88 nb...@mia-software.com nbros....@gmail.com Mia-Software, 410 clos de la Courtine 93160 Noisy-le-Grand http://www.mia-software.com .: model driven agility :.
_______________________________________________ dash-dev mailing list dash-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/dash-dev
