Hi Ivo, 2011/12/2 Ivo Ladage-van Doorn <[email protected]>: > Hi All, > > Currently there is a folder named ‘amdatu-libraries’ which contains some > utility services/helper classes. Issue > http://jira.amdatu.org/jira/browse/AMDATU-264 states that the utilities > library should be removed. I think we have to agree upon how to deal with > these kind of generic services/utility classes. While developing the amdatu > gadget container demo, I encountered more of these generic services/utility > classes.
I created the issue with regard to the "utilities" library as I have a bad experience with these kind of artifacts becoming dependency black holes. Subsequently I (re)factorred out the "fsutil" and "warsupport" as part of the libraries module before we splitted into platform and subprojects. Right now I am just assuming they are part of the platform and may well be subject to change under AMDATU-264. I think for any (new) utility type of construct it important to answer... 1) Who owns it? 2) What is its purpose/promise (inline or library bundle)? 3) Is it usefull to share around (and support it like an API)? > A small evaluation of generic services/helper classes: > > · Fsstorage classes (currently contained by amdatu-libraries) - Base > and utility classes for components that use simple filesystem storage Platform, inline, keep it alive as long as we are using it. > · Utility services (currently contained by amdatu-libraries) – > Contains all kind of utility methods, like the ServiceDependentActivator, > the AtomSyndicationLink, XML utilities and some unit test helper classes. Platform (mostly), I think there could be a commons library bundle for selective platform stuff like ServiceDependentActivator. Atom/XML not sure what they do and where they should go.. maybe as part of web. test support should go to a test support library. > · Warsupport (currently contained by amdatu-libraries) - Supporting > classes for the Amdatu WAR assembly Platform specific, not for reuse > · Performance test framework (used by the subprojects) Not sure. Platform is not using it and probably wont until it integrates into the build infrastructure and lifecycle, Separate project maybe? > · Dashboard plugin (currently contained by OpenSocial, but since the > plugin can also be used without OpenSocial, this might not be the right > location) I think not all modules must be required within a project. So I have no problem with OpenSocial providing a more generic module. If you think it should not be part of Open Social your effectively saying it should have it's own project. I have no problem with that either. Guess it's a granularity issue :) > · REST doclet (which I created to automatically generate online > documentation from REST services by introspecting the code and javadoc) No clue.. where is it what does it do? Might be interesting to include in generic platform build infrastructure. > · Email service (used by the gadget container demo) No clue.. where is it what does it do? Could probably be a project / might also be interesting to AMS > And then we have more artifacts in the trunk which are not officially part > of platform or any subproject, like; > > · Amdatu-maven-plugin Platform infra > · Amdatu-release Platform > · Amdatu-release-demo Separate Project http://jira.amdatu.org/jira/browse/AMDATUDEMO > · Amdat-parent Amdatu platform > · etc/checkstyle Platform infrastructure? It could be generic but we should kill this non artifact nonsense. Didn't even know you had hidden a module in there :D > > I don’t think all these artifacts should be contained by a single ‘misc’ > project with just one release cycle; these artifacts are all independent > artifacts which should be released separately. I suggest we move all these > artifacts to a new folder named something like ‘amdatu-utils’, where each > artifact has its own version, lifecycle and owner. I noticed that the Felix > project has something similar; ‘Felix Utils’. Not sure we want to group them under a "utils" because they have such different purposes and scopes. Why not keep them at level one like for example "amdatu-maven-plugin" and "maven-ace-client"? grz Bram > > 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] | www.gxsoftware.com | > twitter.com/GXSoftware > > > > > _______________________________________________ > Amdatu-developers mailing list > [email protected] > http://lists.amdatu.org/mailman/listinfo/amdatu-developers > _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
