Before we do this, we have to be careful on our vision: - Are we looking to define internal utilities shared among Trinidad/Tomahawk/Tobago? - Are we looking to define public APIs shared among these projects? - Are we going to have a common package name for all such code?
IMO, we should: - Have no components at all in here, at least to start, whether or not they render markup. - Use a common package name - Be very cautious and slow as we build this up, being *really* sure about the APIs we're adding. This should be a foundational stone for a long time. - Start enforcing a public vs. private API split for real, and be rigorous about when we change public APIs without preserving backwards compatibility. Also, I don't think build dependencies belong in here, at least not in terms of a packaged JAR. Whether they live in a "commons" in terms of SVN locations is fine. -- Adam On 5/3/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
Greetings from the ApacheCon in Amsterdam. It was discussed a lot on the list and Bernd and I are now taking the time to layout a "apache-myfaces-commons-[SUBSET]-VERSION.jar" file. Commons: -What should go into a commons JAR? Non renderKit related things like -Converters and Validators -NonFacesRequestServlet from Tobago -FacesContextFactory from Tobago to ensure a kind of common layer for doing uploads -the selectItems component from Tomahawk -what are we missing ??? Build dependencies: - Trinidad's plugins/utils to generate stuff like the TagClass file. The vision: Why this is needed ? It is kind of hard to actually use only some "common" pieces of Tomahawk. At least to add a custom validator, the complete jar is needed. The vision is also to add some "common" pieces from Trinidad/tobago to it. For Tomahawk this will not mean, you have to introduce a new namespace for adding the converter/validator, the "commons-jar" can be a rt dependency so that the TLD file is only referencing to the classes w/in the commons.jar. What are you missing ? We will compile a list into the MyFaces wiki, based on your feedback/comments -Bernd/Matthias
