Hi Michael,
if you need a new version of Agile Grid, then you need to:
1. perform the changes in the Agile Grid Source Forge Git Repository and create
the binary bundles.
2. create a CQ for the new version of the Agile Grid third party library.
I think it would be good to attach both, the source and the binary of the
specific version of Agile Grid to the CQ. This simplifies the integration into
the RMF repository
3. wait for approval of the CQ
4. After approval of the CQ: You should take the class files that are contained
in agile grid binary bundle and replace the class files that are in the Eclipse
RMF org.agilemore.agilegrid plugin.
Note: You should NOT change any other files in the Eclipse RMF
org.agilemore.agilegrid plugins (e.g. Manifest.MF, build.properties should not
be changed unless new files or packages have to be exported).
Note: The default CQs only allow for importing binaries. Do not import the
sources.happy May day, Mark -- Mark Brörkens Softwarearchitekt, Projekt- und Produktmanager Telefon: +49 30 69 535 878 Telefax: +49 30 62 908 067 Mobil: +49 151 61301259 (bevorzugt) http://www.itemis.de mark.broerk...@itemis.de http://xing.to/mark_broerkens http://twitter.com/MarkBroerkens itemis AG Mulackstraße 22 10119 Berlin Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus Am 30.04.2014 um 17:55 schrieb Michael Jastram <mich...@jastram.de>: > Hello Mark, > > Thanks for taking care of this. So, if we make changes to AgileGrid in the > past, I assume we have to create a new CQ and re-Import the binaries, correct? > > Thanks, and happy May day, > > - Michael > > On 30.04.2014 16:12, Mark Brörkens wrote: >> Dear RMF-Dev Members, >> >> == For your information == >> The RMF project uses Agile Grid framework that is hosted at Source Forge. >> The Eclipse IP-Team has approved to use and redistribute this third-party >> library. >> >> in the past we configured the Agile Grid source forge p2 repository in the >> target definition of the RMF build system which downloaded the binary and >> redistributed it as part of the RMF p2 repository. >> This approach had two disadvantages: >> * The Agile Grid bundles at Source Forge were not signed. Thus, during >> installation of RMF via a p2 update site the user had to confirm the >> installation of unsigned Agile Grid bundles. >> * Hosting the binaries of a third party library that correspond to a >> specific Eclipse CQ at an external site is a "no no" from the legal point of >> view. >> >> In order to overcome these two disadvantages, the Agile Grid binaries are >> now available in the RMF Git Repository and the references to the Source >> Forge p2 repository are removed from our target definitions. Additionally, >> the RMF build system makes sure that the Agile Grid binaries are packaged >> with the correct legal documentation. Additionally, it signs the agile grid >> plugin. >> >> == For those that are working on the RMF code == >> Please make sure that the new plugin org.agilemore.agilegrid is imported >> into your Eclipse development workspace. >> >> >> Kind regards >> >> >> Mark >> >> > > -- > Dr. Michael Jastram +49 (162) 274 83 94 http://jastram.de > Geschäftsführer Formal Mind GmbH http://formalmind.com > Gründer rheinjug e.V. http://rheinjug.de > Project Lead Eclipse Requirements Modeling Framework http://eclipse.org/rmf > _______________________________________________ > rmf-dev mailing list > rmf-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/rmf-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ rmf-dev mailing list rmf-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/rmf-dev
