[gatein-issues] [JBoss JIRA] Updated: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano updated GTNPORTAL-66:
--------------------------------------
Attachment: patch_15_dic_2009.zip
new patch. Now:
1- jdk 6 bug doen't appare because I use a new Classloader (APTClassloader in the
groovy-plugin project)
2 - all templates are compiled at runtime
remains:
1 - there three templates that doesn't compile. I have to see them
2 - I have to see if the compile of templates can be used as cache at runtime so they are
not compiled at runtime
3 - the exo.portal.webui.core uses the chromatic plugin. It seems that the crhomatic
plugin need to get the parameter "-proc:none" in the java compiler. If we use
that parameter, my plugin doesn't compile the templates inside that project
4 - I've taken a part of the annotation processor from
http://source.mysema.com/display/maven/Maven+Plugins. That plugin doesn't resolve the
jdk 6 bug so I have to customized. I wanted extend that plugin but it is not extensible.
It uses only private methods. So I cablated it in my plugin
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-Beta04
Attachments: GroovyAnnotationProcessor.java, patch_15_dic_2009.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, 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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira