a-ha. My maven ignorance has been showing again! If somebody lets the component generation run again, make sure you don't loose any existing code between the markers that is different from the generated one. I know we should have, but due to the missing code generation facility we haven't been careful with that; me including.
regards, Martin On 9/7/06, Manfred Geiler <[EMAIL PROTECTED]> wrote:
No, the config folder is the correct place, because the xml files are not needed during runtime. They are needed during compile time only (during the "process-sources" phase to be exact). They are now in the src folder and therefore not included in the jar - by luck, because maven ignores non-java files in the src tree. ;-) Putting them into the resource folder would make things even worse in that sense! Manfred On 9/7/06, Martin Marinschek <[EMAIL PROTECTED]> wrote: > You mean a resources folder, right? > > regards, > > Martin > > On 9/7/06, Manfred Geiler <[EMAIL PROTECTED]> wrote: > > Dennis, Lance, > > I am indeed of the opinion that is is NOT OK to modify this generated > > code parts. > > Code generation will get importance again when we do the 1.2 port. > > And: Code generation is still important and convenient for coding new > > tomahawk components. Well, nobody seems to use it by now. Reason might > > be (no, I'm sure it IS) the lack of docs. Yes, Lance, you are right, > > there are no docs. Mea culpa. > > And in defense I can not even say it's self-explaining. Because it is not! ;-) > > > > Ok, I give you a very short intro: > > > > Codegenerator can be used by doing a "mvn clean install > > -Pregenerate-component-code" > > You can try it in core/api for instance. > > > > Base for the generation of these code parts is an according xml file > > that looks like this: > > http://svn.apache.org/viewvc/myfaces/core/trunk/api/src/main/java/javax/faces/component/html/HtmlCommandButton.xml?view=markup > > and sits in the same src dir as the component's java file. > > (which is nonsense and should be in a config folder according to the > > maven standard dir layout, of course) > > > > There are some quirks: No dtd or xsd, and so on > > But: it works! And it did a great job in the early days of MyFaces. > > > > HTH and thanks for your interest in this nostalgic thingy :-) > > > > Manfred > > > > > > > > On 9/5/06, L Frohman <[EMAIL PROTECTED]> wrote: > > > Thanks, > > > There is a codegenerator under "build-tools" under "maven". > > > No documentation? (stupid question?) > > > > > > -----Original Message----- > > > From: Dennis Byrne [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, September 05, 2006 12:11 PM > > > To: MyFaces Development > > > Subject: Re: GENERATED CODE BEGIN (do not modify!) > > > > > > Large parts of the original code base were generated. The generator has > > > recently been committed. Check svn ... I forget the name, but it is a > > > seperate sub project. > > > > > > Is anyone else of the opinion that it is now "OK" to modify this code? One > > > doesn't have to look to far to find plenty of undocumented cases where many > > > of us have done this, and for good reasons. > > > > > > Dennis Byrne > > > > > > >-----Original Message----- > > > >From: L Frohman [mailto:[EMAIL PROTECTED] > > > >Sent: Tuesday, September 5, 2006 03:00 PM > > > >To: ''MyFaces Development'' > > > >Subject: re: GENERATED CODE BEGIN (do not modify!) > > > > > > > >In several of the myfaces components, there is code marked > > > > > > > >"GENERATED CODE BEGIN (do not modify!)" > > > > > > > >(in particular org.apache.myfaces.component.html.ext.HtmlPanelGroup) > > > >How is this generated? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > http://www.irian.at > > Your JSF powerhouse - > JSF Consulting, Development and > Courses in English and German > > Professional Support for Apache MyFaces >
-- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
