[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
there is an interesting maven plugin for apt:
http://source.mysema.com/display/maven/Maven+Plugins
This seems the only mvn plugin that works with java 6 interfaces. We can add this in our
pom:
<plugin>
<groupId>com.mysema.maven</groupId>
<artifactId>maven-apt-plugin</artifactId>
<version>${com.mysema.maven.apt.version}</version>
<configuration>
<processor>org.exoplatform.webui.config.annotation.processor.GroovyAnnotationProcessor</processor>
<outputDirectory>target</outputDirectory>
</configuration>
<executions>
<execution>
<goals>
<goal>process</goal>
</goals>
</execution>
</executions>
</plugin>
But we need to host a new module in gatein mvn repository. We have to start with a binary
library containing the annotation processors. When we start 'mvn install' , it
starts the process only if there are compiled annotation processor classes. So in our pom
we could add something as:
<dependency>
<groupId>org.gatein.common</groupId>
<artifactId>common-apt</artifactId>
<version>${org.gatein.common.apt.version}</version>
</dependency>
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, 3.0.0-CR01, 3.0.0-GA
Environment: jdk 1.6.0_07, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-CR01
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