| Re: [mdt-papyrus.dev] Papyrus night build |
|
Hi, if you want to re-invent EEF, of course, fell free to do it. But, remember that several commiters are involved in the Papyrus and EEF project. So, if you want to change something inside EEF project, you already can. And remember that EEF project has been designed at the beginning with the Papyrus requirements. For exemple, if you want to externalise the backbone as autonomous project, you will have exactly the same problem of build and version dependences. But perhaps you just misunderstood the sentence "Since EEF has no Stable builds ( just Integration or nightly ), you cannot rely on a specific version of it.". He says just that there isn't any official version of EEF component already released. But it isn't a problem because papyrus team is involve inside EEF (the backbone hasn't any release, but it works). GERARD Sebastien 166342 a écrit : Dear all, I think that will close the question on if we will continue or not to use the EEF component. I think that we will have for now to have our own solution for that purpose (even if we reuse some good idea of EEF). Best... Sébastien. -----Message d'origine----- De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Stéphane Bouchet Envoyé : vendredi 4 décembre 2009 10:40 À : mdt-papyrus.dev@xxxxxxxxxxx Objet : Re: [mdt-papyrus.dev] Papyrus night build Hi remi, Since EEF has no Stable builds ( just Integration or nightly ), you cannot rely on a specific version of it. I got the same problem for EEF itself. What i did is to use the p2 ability to install a feture from an update site. So you could use the EEF's integration update site to use the runtime. Here is the steps : in your build.properties file ( in your releng project ), remove the EEF build in the dependencyURL properties, and add this : # can also specify repos (local/remote sites or local zips) THEN a list of features to install (see below) repositoryURLs=http://download.eclipse.org/modeling/emft/eef/updates/0.7.1/ # multiple installs as a single operation (requires Eclipse 3.5) featureIDsToInstall=org.eclipse.emf.eef.runtime This should work and install the latest EEF runtime automaticcally. PS : for more infos about installing this way, take a look to : http://wiki.eclipse.org/Common_Build_Infrastructure/Defining_Binary_Dependencies Cheers, -------- Message original --------Sujet: [mdt-papyrus.dev] Papyrus night build Date: Wed, 2 Dec 2009 18:27:15 +0100 De: SCHNEKENBURGER Remi 211865 <Remi.SCHNEKENBURGER@xxxxxx> Répondre à :: Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx> Pour :: Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx> Dear all, The night build of Papyrus is currently working on Athena. You can find the job at the following address: https://build.eclipse.org/hudson/job/cbi-papyrus-0.7-nightly/ I still have problem with the eef runtime dependency, as there is no stable build on which I can rely for build. Consequently: - The user has to install himself the eef runtime. I am thinking about putting the eef runtime feature in the archived update site of papyrus. - Every week, the build is broken, as the Integration build number on which I rely is deleted. As mentioned in today's telco, I removed some of the plugins in the build: the autolayout tools. I will reintegrate them as soon as possible, i.e. they are moved in a more convenient place in the SVN. I also removed the sequence diagram, as it had dependencies to UML2 tools project. (I apologize, as I forgot to mention it in the telco) Regards, Remi --------------------------------------- Rémi SCHNEKENBURGER +33 1 69 08 48 48/ CEA LIST, Boîte courrier 65, F-91191 Gif sur Yvette Cedex/ ---------------------------------------_______________________________________________ mdt-papyrus.dev mailing list mdt-papyrus.dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev |
begin:vcard fn:Etienne Juliot n:Juliot;Etienne org:Obeo adr;quoted-printable:;;2 rue Robert Schuman;Rez=C3=A9;;44400;France email;internet:etienne.juliot@xxxxxxx tel;work:02 51 13 55 94 tel;cell:06 86 78 14 82 url:http://www.obeo.fr version:2.1 end:vcard