]
Luca Stancapiano updated GTNPORTAL-66:
--------------------------------------
Attachment: patch_23_gen_2010.zip
I add a new patch. This patch compile all groovy scripts inside gatein. Remains:
- resove the conflict with the chromattic APT. Chromattic APT need the webui.core project
do not use the APT at compile time. But the Groovy resolver need it to compile the groovy
script inside the project
- actually it creates compiled classes from the groovy scripts but they are not
persistent. The persistence is useful to get a fast caching of the groovy pages inside
Gatein
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL:
https://jira.jboss.org/jira/browse/GTNPORTAL-66
Project: GateIn Portal
Issue Type: Task
Components: Common integration
Affects Versions: 3.0.0-Beta01, 3.0.0-Beta02
Environment: jdk 1.6.0_17, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-CR01
Attachments: GroovyAnnotationProcessor.java, patch_15_dic_2009.zip,
patch_23_gen_2010.zip, patch_28_nov_2009.zip, patch_28_nov_2009.zip, patch_6_dec_2009.zip,
patch_7_dec_2009.zip, patch_7_dec_2009.zip, patch_7_gen_2010.zip, prova.zip
maybe useful a mechanism that validates the groovy templates passed in the
org.exoplatform.webui.config.annotation.ComponentConfig annotation declared in the
exo.portal.webui.core project.
This annotation is actually used in the exo.portal.component.dashboard project.
Using the Pluggable Annotation Processing API for java 6 (here some detail of the
technology:
http://www.javabeat.net/articles/14-java-60-features-part-2-pluggable-ann...)
we can validate the groovy templates so we are not forced to load them at runtime and we
avoid a boring testing navigations.
The idea is introduce the Pluggable Annotation Processing in the pom.xml so we validate
the templates through the 'mvn install' command
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: