[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_7_gen_2010.zip
The bug is resolved. I deleted the APTClassloader and modified the
org.exoplatform.webui.config.annotation.EventConfig class.
instead of:
Phase phase() default Phase.PROCESS;
we can do:
Phase phase() default PROCESS;
and add a static import:
import static org.exoplatform.webui.event.Event.Phase.PROCESS;
it resolves the problem of duplicated class
So APTClassloader is not more useful
This plugin used the gatein.checkout.dir variable to resolve the root path where find the
classes to build the groovy scripts. I deleted and used the maven variables. All scripts
now compile except:
/groovy/dashboard/webui/component/UIDashboardPortlet.gtmpl
/groovy/applicationregistry/webui/component/UIApplicationRegistryPortlet.gtmpl
/groovy/gadget/webui/component/UIGadgetPortlet.gtmpl
the problem is about the dependencies
those two scripts import classes that are inside the same project
so when the annotation processor starts, it doesn't find those classes because they
are not still compiled
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_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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira