PCM Development/Palladio Concall/Minutes 20161017
Developer day @ SSP
- planned arrival approximately 13h
- => start of developer meeting at 14h
- participants, approx. 10
Block 1: Palladio Release Planning
14h till coffee break
- release date?
- included add-ons?
- platform: Mars vs. Neon
- review PCM meta-modell changes by Michael Langhammer et al.
- Sirius editors, progress?
Block 2: Palladio Developer Experience and Build Infrastructure
Coffee break till 18h
- Markus Hilbrich presents his developer experience paper as a kick-off
- development environment/workspace, best practices for setting up?
- build infrastructure
- Buckminster vs. Tycho/Maven
- how to create a new build job for my Palladio Addon?
Best practice Developer On-Boarding (question from fortiss)
- Falix: development environment, best practices how to setting up?
- Philipp: when doing refactoring, use buckminster to materialize all plugins; otherwise, install nightly into Eclipse, check out only plug-ins to be changed
- Steffen: recommends his students to use Eclipse's materialize wizard for any slightly larger project
- Felix: we do have error messages when trying to materialize
- Christian: solution to current problem
- cause: you try to materialize the target platform, which however points to local directory on the build server
- recommendation: don't materialize target platform, just download modelling tools Eclipse
- Christian: solution to current problem
- Philipp: EventSim is so far decoupled from integrated Palladio build; rmap files refer to nightly build rather than cmap files as often as possible
- don't know if materialization works as intended
- needs to be "fixed" before EventSim can be integrated into the release
- Steffen: by the way, Wiki build documentation is still in progress, planned to be completed soon
Build Infrastructure
- Felix: did you consider using Vagrant?
- Steffen: thinking of offering master thesis
- Steffen: or use Tycho?
- Stephan: parent POM required, no POMs on a per-plugin-base required
- Steffen: Tycho better maintained than Buckminster, but migration overhead considerable
- Stephan: stepwise migration should be possible
- Solution 1: generate update sites via Tycho, include update site in Buckminster
- Christian, Solution 2: maven (repository) reader in Buckminster
- Steffen: other direction works as well (read buckminster builds from maven)
- Stephan: we should systematically compare features Buckminster vs. Maven
- Steffen: likes materialization feature into workspace