L.S.,
Just did an update from SVN and found a problem with the code generation
feature. When you do a mvn compile -P regenerate-component-code in the
main myfaces directory, the build fails with
Embedded error: The following error occurred while executing this line:
C:\projects\myfaces\core\api\build.xml:5: taskdef class
org.apache.myfaces.codegen.component.ComponentGeneratorTask cannot be
found
However, if I issue the same command in the core or core/api
directories, the code generation process works well. I suppose there is
a difference in how Maven handles the build process (the embedded ant
build uses another classpath), but I'm not familiar enough with Maven to
see what's going on here. Any pointers on where to look?
Thanks,
Gert Vanthienen
Manfred Geiler wrote:
Hi all,
After finding some spare time yesterday and rummaging in the myfaces
attic, I was able to re-add the long missed code generation feature.
Hooray.
Gert Vanthienen was kind enough to offer his help on re-installing the
full code gen feature.
Gert,
I just checked in the code generator. It is already adapted to the new
maven build structure.
You can find the generator code (with the Velocity template) in the
/maven/build-tools module.
I tested the codegen with the core/api module where I already added it
to the pom.xml
By default code generation is turned off during a normal build. You
can try it out with
mvn compile -P regenerate-component-code
Please look at these open tasks:
1. add code generation feature to tomahawk module
2. look for manually changed code parts that are now incompatible to
regeneration
i.e. generate code and do some svn diffing to find dangerous
generated code part modifications
3. revert and check in trivial (whitespace) changes that happened
manually some time ago. The goal is to have a state where code
(re)generation does not change anything with current code state.
4. Write a Wiki page "HowToGenerateComponentCodeParts"
For 2. and 3. we should wait for the 1.1.2 release to be out - which
hopefully can happen during the next days.
Thanks,
Manfred
On 4/13/06, *Manfred Geiler* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Werner,
Look at the component classes. Everything between the BEGIN and
END GENERATED CODE markers was generated by a Velocity template
from the according component xml files.
In a few minutes I will checkin the reborn codegenerator - stay
tuned.
Manfred
On 4/13/06, * Werner Punz* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
Manfred Geiler schrieb:
> Ok, I just spent a few minutes and found the old
codegenerator on the attic.
> Will try to integrate it into current maven structure.
> Please stay tuned!
>
> Thanks,
> Manfred
>
Manfred, just a question, what was the scope of the old
codegenerator,
does it generated boilerplate code for the components?
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.4.1/310 - Release Date: 12/04/2006
