Hi guys, yes, I think something like a tools directory would be appropriate. I would ship it with myfaces-all.jar though, cause some users might want to use it.
The code generation stuff is really easy to use: - go to the directory of one of the custom components - you find a xxx.xml file there which tells you details about the component, the code generator uses these files. just implement the one you need to do for your component! next up, go to build/codegen, and use the build.xml file there for creating the generated code - you need to set the component you want to work on in the properties file. Finished - the code generator replaces all code in the component class between the predefined markes with the generated code, especially the value binding things are a pretty neat thing to have generated. regards, Martin On 6/21/05, John Fallows <[EMAIL PROTECTED]> wrote: > Hey Sean, > > We originally created a separate tools project for code that is only > used at build time and never ships. This code is currently being > migrated to Maven Plugins to decrease complexity within each project > that uses the build tools. > > Kind Regards, > John Fallows. > > On 6/20/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > I'm doing a test run of the svn reorg. I'm not sure where the code in > > myfaces/trunk/src/codegen belongs. Is this api, impl, share or > > component? > > > > I'm also not sure how the codegen works in MyFaces in general so if > > someone could provide me an explanation of how this works that would > > ne nice :-) > > > > I will have more of these types of questions over the next few days as > > I try to sort out everything in the repository. Please try to provide > > answers ASAP so we can move on to the other cool stuff after the reorg > > (like adding new sandbox components!) > > > > sean > > >
