Hi, > I would say I'm cautiously optimistic about that their progress, we will > know more after the workshop. It would be nice to be able to contribute > through testing with this new project, but if that looks like too much > we could stay with a straight PDE build system.
My suggestion was to wait until they have something stable until they have somehing. Maybe this is the case after the workshop. > > I already have a skeleton pde build project setup, that could be > leveraged. Either way this is something I could help out with, as I > already know my way around PDE build. > > When you say you do not see the need for a build system do you mean just > this common build infrastructure? Of course using the eclipse pde UI is > an option, but an automated setup has a lot of benefits over manually > building in the UI. Well, this goes into the direction of the benefits of an automated build system. IMHO, the advanges of such a system reveil, if you have a working qa in mind. This means, not only to build the system but also check code quality and perform an automated tests. Currently, there is also a lack of unit test, which must be a basis for the tests. Probably, it would be better to start with this, doing the first step after the second. I hope that this is not going to be misunderstood that I am against such a build system, but you have to do some preparations first, before it makes sense to add an automatism for that. ~dirk _______________________________________________ vtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/vtp-dev
