Hi, Let's start discussing some of these generic components then. Below a description of four of them. What should we do with these? Performance test framework This artifact facilitates running a performance test of two Amdatu versions against each other, including statistics analysis. It is used by the three subprojects auth, Cassandra and opensocial to generate performance reports. It is a generic component which can be used by any Amdatu projects, but it is Amdatu specific.
Integration test utility classes The integration tests of auth, cassandra and opensocial share some utility classes for service lookup, rest calls and authorization logic (login/logout). Currently the same utility classes are copy/pasted over the three subprojects, but as soon as you start copy/pasting code you should ask yourself if that is really necessary. Configuration utility class The OSGi configadmin api is quite rudimentary. So a configuration utility class supporting type casting and providing default values (needed for backwards compatibility) is used and copy/pasted many times in auth/cassandra/opensocial. Email service The demo environment hosts an Amazon-SES based email service. This is implemented as osgi bundle of which the source code is still in my sandbox. It doesn't belong to any of the existing subprojects. Regards, Ivo From: [email protected] [mailto:[email protected]] On Behalf Of Martijn van Berkum Sent: dinsdag 6 maart 2012 15:13 To: [email protected]; [email protected] Subject: Re: [Amdatu-users] New subproject 'Amdatu Tooling' Hello, As discussed this monday, the board is not in favor about this proposal for a generic name where all kinds of code can be placed. Code categories like 'commons', 'generic', 'tools', 'other' or 'misc' have a tendency to grow into a chaos category; unmanaged, unfocused code that has no clear live cycle, vision, roadmap or goal which can lead to 'abandonware'. It doesn't fit a component based architecture, where every component is reusable and has a clear purpose. We would like to see deeper research about what exactly the problem behind this proposal is. A review per proposed component, and see what solutions are available for example. We expect a choice (per component) which can be either to remove the component, reuse it from another open source project or move it in one of the existing Amdatu projects. A last resort (because of focus and limited resources) could be to create a new Amdatu project for a specific component, this needs to be agreed upon by the board of course. Hans & Martijn GX Software | Martijn van Berkum | CTO | Wijchenseweg 111 | 6538 SW Nijmegen | The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 388 86 21 | M +31(0)6 - 15 05 08 53 | [email protected]<mailto:[email protected]> | www.gxsoftware.com<http://www.gxsoftware.com/> | twitter.com/GXSoftware<http://twitter.com/GXSoftware> | twitter.com/<applewebdata://1EC93020-F934-47AC-86EB-948E6223309C/twitter.com/njitram>njitram<applewebdata://1EC93020-F934-47AC-86EB-948E6223309C/twitter.com/njitram> From: Martijn van Berkum <[email protected]<mailto:[email protected]>> Date: Fri, 2 Mar 2012 12:01:38 +0100 To: <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: [Amdatu-users] New subproject 'Amdatu Tooling' Hi, Just a heads-up. This is not forgotten, we simply don't have had time yet to discuss this. We will discuss this probably on Monday. Martijn GX Software | Martijn van Berkum | CTO | Wijchenseweg 111 | 6538 SW Nijmegen | The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 388 86 21 | M +31(0)6 - 15 05 08 53 | [email protected]<mailto:[email protected]> | www.gxsoftware.com<http://www.gxsoftware.com/> | twitter.com/GXSoftware<http://twitter.com/GXSoftware> | twitter.com/<applewebdata://1EC93020-F934-47AC-86EB-948E6223309C/twitter.com/njitram>njitram<applewebdata://1EC93020-F934-47AC-86EB-948E6223309C/twitter.com/njitram> From: Ivo Ladage-van Doorn <[email protected]<mailto:[email protected]>> Reply-To: <[email protected]<mailto:[email protected]>> Date: Mon, 27 Feb 2012 14:29:28 +0000 To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [Amdatu-users] New subproject 'Amdatu Tooling' Hi Board and others, Today Marcel, Bram, Arthur and myself had a discussion about the 'generic components' issue. There are several generic components in Amdatu which do not belong to an existing (sub)project and are or could be used by several (sub)projects. Examples are the REST doclet (generates REST documentation for JAX-RS annotated services), the performance test framework (which currently does not belong to any of the subprojects), the Amdatu maven plugin (moved to GIT but not released with the platform) and some utility classes used by integration tests (currently copy/pasted over three subprojects). Our proposal is to create a new subproject 'Amdatu Tooling' which hosts these generic components. We noticed that all components provide tooling for Amdatu developers, hence this name. For the new subproject we would like to create one new JIRA project. From this subproject, the artifacts contained by it will be released individually. If the board approves, I will create the new subproject, create a new GIT repo and move the REST doclet to it. So @Board; wdyt? Regards, Ivo GX Software | Ivo Ladage-van Doorn|Product Architect |Wijchenseweg 111 | 6538 SW Nijmegen| The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 388 86 21 |[email protected]<mailto:[email protected]>| www.gxsoftware.com<http://www.gxsoftware.com>| twitter.com/GXSoftware<http://twitter.com/GXSoftware> _______________________________________________ Amdatu-users mailing list [email protected]<mailto:[email protected]>http://lists.amdatu.org/mailman/listinfo/amdatu-users
_______________________________________________ Amdatu-users mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-users
