5:33 p.m.
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-Beta02, 3.0.0-Beta01, 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
4:06 a.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
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
5:57 a.m.
New subject: [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...
]
Thomas Heute updated GTNPORTAL-66:
----------------------------------
Affects Version/s: (was: 3.0.0-CR01)
(was: 3.0.0-GA)
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_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
12:52 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
Here a first example of annotation processor:
/*
* Copyright (C) 2003-2007 eXo Platform SAS.
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU Affero General Public License
* as published by the Free Software Foundation; either version 3
* of the License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, see<http://www.gnu.org/licenses/>;.
*/
package org.exoplatform.webui.config.annotation.processor;
import java.io.IOException;
import java.io.InputStream;
import java.util.Map;
import java.util.Set;
import java.util.Map.Entry;
import javax.annotation.processing.AbstractProcessor;
import javax.annotation.processing.RoundEnvironment;
import javax.annotation.processing.SupportedAnnotationTypes;
import javax.annotation.processing.SupportedSourceVersion;
import javax.lang.model.SourceVersion;
import javax.lang.model.element.AnnotationMirror;
import javax.lang.model.element.AnnotationValue;
import javax.lang.model.element.Element;
import javax.lang.model.element.ExecutableElement;
import javax.lang.model.element.TypeElement;
import org.exoplatform.commons.utils.IOUtil;
import org.exoplatform.groovyscript.GroovyScriptBuilder;
import org.exoplatform.groovyscript.TemplateCompilationException;
import org.exoplatform.resolver.ClasspathResourceResolver;
/**
* An annotation processor to compile the Groovy templates
*
* @author <a href="mailto:jedim@vige.it">Luca Stancapiano</a>
* @version $Revision$
*/
@SupportedAnnotationTypes(value = {
"org.exoplatform.webui.config.annotation.ComponentConfig" })
@SupportedSourceVersion(SourceVersion.RELEASE_6)
public class GroovyAnnotationProcessor extends AbstractProcessor {
@Override
public boolean process(Set<? extends TypeElement> annotations,
RoundEnvironment roundEnv) {
for (Element element : roundEnv.getRootElements()) {
for (AnnotationMirror element2 : element.getAnnotationMirrors()) {
Map<? extends ExecutableElement, ? extends AnnotationValue> elementsMap =
element2
.getElementValues();
for (Entry<? extends ExecutableElement, ? extends AnnotationValue> entry :
elementsMap
.entrySet()) {
if (entry.getKey().getSimpleName().toString().equals(
"template")) {
String url = (String) entry.getValue().getValue();
InputStream is = null;
byte[] bytes = null;
try {
is = new ClasspathResourceResolver()
.getInputStream(url);
bytes = IOUtil.getStreamContentAsBytes(is);
} catch (Exception ex) {
ex.printStackTrace();
return false;
} finally {
try {
if (is != null)
is.close();
} catch (IOException ioex) {
ioex.printStackTrace();
return false;
}
}
String text = new String(bytes);
GroovyScriptBuilder compiler = new GroovyScriptBuilder(
null, text);
try {
compiler.build();
} catch (TemplateCompilationException tcex) {
tcex.printStackTrace();
return false;
}
}
}
}
}
return true;
}
}
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_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
1:18 p.m.
New subject: [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: GroovyAnnotationProcessor.java
here a better formatted class
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_07, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-CR01
Attachments: GroovyAnnotationProcessor.java
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
5:08 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
I moved the processor inside component.scripting project so it is close to the groovy
compiler.
Instead of mysema plugin I use the standard maven-compiler-plugin in the
component.scripting pom.xml. I add a -proc:none param so the processor is not used in this
project because it need to be compiled before.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<compilerArgument>-proc:none</compilerArgument>
</configuration>
</plugin>
I added a javax.annotation.processor.Processing file inside
src/main/resources/META-INF/services folder of the project containing the custom processor
name class so java 6 knows that there is a processor to execute. This processor will be
execute by all projects that have the component.scripting as dependency in our pom.xml. So
the dependency has to be added in the poms of the projects that use the interested
annotations.
Actually I'm resolving a problem of classloading compiling all portal project. Here
there is the error:
/GATEIN/portal/webui/core/src/main/java/org/exoplatform/webui/config/annotation/EventConfig.java:[42,30]
incompatible types
found : org.exoplatform.webui.event.Event.Phase
required: org.exoplatform.webui.event.Event.Phase
It seems that this class is added by two different classloaders. I f I put off the
processor the compile is ok
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_07, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-CR01
Attachments: GroovyAnnotationProcessor.java
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
5:47 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
I localized the problem. Here I reproduce it:
we have two projects:
scripting - it contains the annotation processor
--------------------------------------------------------------
[sviluppo@cicius scripting]$ find
.
./target
./target/classes
./src
./src/main
./src/main/java
./src/main/java/org
./src/main/java/org/exoplatform
./src/main/java/org/exoplatform/annotation
./src/main/java/org/exoplatform/annotation/processor
./src/main/java/org/exoplatform/annotation/processor/GroovyAnnotationProcessor.java
./src/main/resources
./src/main/resources/META-INF
./src/main/resources/META-INF/services
./src/main/resources/META-INF/services/javax.annotation.processing.Processor
here the annotation processor:
package org.exoplatform.annotation.processor;
import java.util.Set;
import javax.annotation.processing.AbstractProcessor;
import javax.annotation.processing.RoundEnvironment;
import javax.annotation.processing.SupportedAnnotationTypes;
import javax.annotation.processing.SupportedSourceVersion;
import javax.lang.model.SourceVersion;
import javax.lang.model.element.TypeElement;
@SupportedAnnotationTypes(value = {
"org.exoplatform.webui.config.annotation.ComponentConfig" })
@SupportedSourceVersion(SourceVersion.RELEASE_6)
public class GroovyAnnotationProcessor extends AbstractProcessor {
@Override
public boolean process(Set<? extends TypeElement> annotations,
RoundEnvironment roundEnv) {
return true;
}
}
here the javax.annotation.processing.Processor descriptor file:
org.exoplatform.annotation.processor.GroovyAnnotationProcessor
core - it contains an annotation and an annotated class
-------------------------------------------------------------------------
[sviluppo@cicius core]$ find
.
./target
./target/classes
./src
./src/main
./src/main/java
./src/main/java/org
./src/main/java/org/exoplatform
./src/main/java/org/exoplatform/webui
./src/main/java/org/exoplatform/webui/config
./src/main/java/org/exoplatform/webui/config/annotation
./src/main/java/org/exoplatform/webui/config/annotation/EventConfig.java
./src/main/java/org/exoplatform/webui/event
./src/main/java/org/exoplatform/webui/event/Event.java
Here an annotation:
package org.exoplatform.webui.config.annotation;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
import org.exoplatform.webui.event.Event.Phase;
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.TYPE})
public @interface EventConfig {
Phase phase() default Phase.PROCESS;
}
and here a class containing a enum (Phase) used in the annotation:
package org.exoplatform.webui.event;
public class Event<T>
{
static public enum Phase {
ANY, DECODE, PROCESS, RENDER
}
}
Here the compiling operations:
[sviluppo@cicius java]$ pwd
/utenze/sviluppo/prova/scripting/src/main/java
[sviluppo@cicius java]$ javac -d ../../../target/classes
org/exoplatform/annotation/processor/GroovyAnnotationProcessor.java
[sviluppo@cicius java]$ cd ../../../target/classes
[sviluppo@cicius classes]$ jar cvf exo.portal.component.scripting-3.0.0-CR01-SNAPSHOT.jar
*
aggiunto manifesto
la voce META-INF/ sarà ignorata
aggiunta in corso di: META-INF/services/ (in = 0) (out = 0) (archiviato 0%)
aggiunta in corso di: META-INF/services/javax.annotation.processing.Processor (in = 62)
(out = 50) (compresso 19%)
aggiunta in corso di: org/ (in = 0) (out = 0) (archiviato 0%)
aggiunta in corso di: org/exoplatform/ (in = 0) (out = 0) (archiviato 0%)
aggiunta in corso di: org/exoplatform/annotation/ (in = 0) (out = 0) (archiviato 0%)
aggiunta in corso di: org/exoplatform/annotation/processor/ (in = 0) (out = 0) (archiviato
0%)
aggiunta in corso di: org/exoplatform/annotation/processor/GroovyAnnotationProcessor.class
(in = 819) (out = 434) (compresso 47%)
[sviluppo@cicius java]$ cd ../../../core/src/main/java
[sviluppo@cicius java]$ javac -cp
../../../../scripting/target/classes/exo.portal.component.scripting-3.0.0-CR01-SNAPSHOT.jar
org/exoplatform/webui/event/Event.java
org/exoplatform/webui/config/annotation/EventConfig.java
org/exoplatform/webui/config/annotation/EventConfig.java:13: incompatible types
found : org.exoplatform.webui.event.Event.Phase
required: org.exoplatform.webui.event.Event.Phase
Phase phase() default Phase.PROCESS;
^
1 error
If we put off the 'default Phase.PROCESS;' code, the compile succeed.
if we put off the exo.portal.component.scripting-3.0.0-CR01-SNAPSHOT.jar from the
classpath the compile succeed too.
I find strange that there is a different java syntax when you compile a enum together an
annotation processor. It could be a javac bug
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_07, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-CR01
Attachments: GroovyAnnotationProcessor.java
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
5:51 p.m.
New subject: [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: prova.zip
I include a zip with the example to reproduce this error
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_07, jboss 5.1, mvn 2.2.1
Reporter: Luca Stancapiano
Priority: Minor
Fix For: 3.0.0-CR01
Attachments: GroovyAnnotationProcessor.java, 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
5:53 p.m.
New subject: [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:
--------------------------------------
Environment: jdk 1.6.0_17, jboss 5.1, mvn 2.2.1 (was: jdk 1.6.0_07, jboss 5.1, mvn
2.2.1)
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, 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
5:23 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
To understand this problem I posted a quetion on
http://forums.sun.com/thread.jspa?threadID=5416155&tstart=0
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, 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
11:39 a.m.
New subject: [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...
]
Thomas Heute updated GTNPORTAL-66:
----------------------------------
Fix Version/s: 3.0.0-CR01
(was: 3.0.0-Beta03)
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, 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
4:45 a.m.
New subject: [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_28_nov_2009.zip
I have a new version of the annotation processor. Now the resolution of the namespace
war:, resources:, system: and app: is resolved. Remains:
- test cases
- bug fixing in the jdk 6
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_28_nov_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
10:09 a.m.
New subject: [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_28_nov_2009.zip
I add the main pom.xml. It allows to add the META-INF/services directory in the scripting
jar
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_28_nov_2009.zip,
patch_28_nov_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
5:26 a.m.
New subject: [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_6_dec_2009.zip
Here a new version of the annotation processor. The templateId and template name was null.
I filled them. Remains:
- test cases
- bug fixing in the jdk 6
- new: actually the compiler by the annotation processor doesn't resolve the
classpath.I have to copy the compile time classpath in the annotation processor
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_28_nov_2009.zip,
patch_28_nov_2009.zip, patch_6_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
6:26 p.m.
New subject: [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_dec_2009.zip
New version of the annotation processor. I resolved the third point creating a
APTClassLoader. It adds all jar inside gatein project in the current classloader.
Remains:
- test cases
- bug fixing in the jdk 6
- verify where the class files are created
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_28_nov_2009.zip,
patch_28_nov_2009.zip, patch_6_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
2:48 a.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Thomas Heute commented on GTNPORTAL-66:
---------------------------------------
Thanks a lot for looking into this.
I havent't followed too closely but have 2 questions:
- Is there a workaround for the JDK6 bug ? Did you get Sun interest to fix it ?
- Can this be used to precompile the groovy templates and reduce the first time access
when unzipping and running 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-Beta04
Attachments: GroovyAnnotationProcessor.java, patch_28_nov_2009.zip,
patch_28_nov_2009.zip, patch_6_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
4:33 a.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://jira.jboss.org/jira/browse/GTNPORTAL-66?page=com.atlassian.jira.p...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
- Is there a workaround for the JDK6 bug ? Did you get Sun interest to fix it ?
I signalized the problem in the bugs resolution application of the sun and actually there
is no response actually. Some day ago I've seen some interest to this in the sun
forums (http://forums.sun.com/thread.jspa?threadID=5416155&tstart=0). I think in
theese days I will know something more. Actually to resolve this problem you should delete
the 'default' operator by the enums. An example of 'default' operator is
inside the org.exoplatform.webui.event.Event.Phase class
- Can this be used to precompile the groovy templates and reduce the first time access
when unzipping and running GateIn ?
It compiles the groovy scripts through the exo groovy compiler, so I suppose it builds
new class files. I have verify if the achievement is the same as for the runtime compiling
(verify where the class files are created )
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_28_nov_2009.zip,
patch_28_nov_2009.zip, patch_6_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
4:35 a.m.
New subject: [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_dec_2009.zip
I added a new patch. I added an APTConstants, deleted the singleton for the APTClassLoader
and user the init method of the annotation processor.
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_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
3:41 p.m.
New subject: [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
2:21 p.m.
New subject: [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
6:29 a.m.
New subject: [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_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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 p.m.
New subject: [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_groovy_11-02-2010.zip
new update for groovy APT based on trunk gatein 11 february 2010 revision.
The previous version added the jars in the WEB-INF/lib of the gatein application.
No more jars in those folders.
Updated the name of the project. Now: GateIn Portal Component Maven Groovy APT
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,
patch_groovy_11-02-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
3:58 a.m.
New subject: [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...
]
Thomas Heute updated GTNPORTAL-66:
----------------------------------
Priority: Optional (was: Minor)
Probably won't have the time to look at it for 3.0 Final :-/
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: Optional
Fix For: 3.0.0-GA
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,
patch_groovy_11-02-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
9:15 a.m.
New subject: [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...
]
Julien Viet updated GTNPORTAL-66:
---------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0-GA)
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: Optional
Fix For: 3.1.0
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,
patch_groovy_11-02-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
2:14 a.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Thomas Heute updated GTNPORTAL-66:
----------------------------------
Fix Version/s: 3.2.0-M02
(was: 3.2.0-M01)
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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: Optional
Fix For: 3.2.0-M02
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,
patch_groovy_11-02-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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:51 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Minh Hoang TO reassigned GTNPORTAL-66:
--------------------------------------
Assignee: Minh Hoang TO
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
Fix For: 3.2.0-M02
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,
patch_groovy_11-02-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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:53 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Minh Hoang TO updated GTNPORTAL-66:
-----------------------------------
Original Estimate: 1 day
Remaining Estimate: 1 day
Labels: portal-s64 (was: )
Verify if precompiling of groovy template could improve significantly starting time
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
Labels: portal-s64
Fix For: 3.2.0-M02
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,
patch_groovy_11-02-2010.zip, prova.zip
Original Estimate: 1 day
Remaining Estimate: 1 day
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:13 p.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Luca Stancapiano commented on GTNPORTAL-66:
-------------------------------------------
Let me know for problems
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
Labels: portal-s64
Fix For: 3.2.0-M02
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,
patch_groovy_11-02-2010.zip, prova.zip
Original Estimate: 1 day
Remaining Estimate: 1 day
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:38 p.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Boleslaw Dawidowicz updated GTNPORTAL-66:
-----------------------------------------
Fix Version/s: 3.2.0-CR01
(was: 3.2.0-Beta01)
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
Fix For: 3.2.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,
patch_groovy_11-02-2010.zip, prova.zip
Original Estimate: 1 day
Remaining Estimate: 1 day
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Boleslaw Dawidowicz updated GTNPORTAL-66:
-----------------------------------------
Fix Version/s: 3.2.0-GA
(was: 3.2.0-CR01)
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
Fix For: 3.2.0-GA
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,
patch_groovy_11-02-2010.zip, prova.zip
Original Estimate: 1 day
Remaining Estimate: 1 day
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:06 p.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Boleslaw Dawidowicz updated GTNPORTAL-66:
-----------------------------------------
Fix Version/s: 3.3.0.CR01
(was: 3.2.0-GA)
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
Fix For: 3.3.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,
patch_groovy_11-02-2010.zip, prova.zip
Original Estimate: 1 day
Remaining Estimate: 1 day
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
New subject: [JBoss JIRA] (GTNPORTAL-66) Processor for the annotations reading groovy templates
[
https://issues.jboss.org/browse/GTNPORTAL-66?page=com.atlassian.jira.plug...
]
Boleslaw Dawidowicz closed GTNPORTAL-66.
----------------------------------------
Fix Version/s: (was: 3.4.0.Final)
Resolution: Out of Date
Groovy templates are being reworked as part of webui removal
Processor for the annotations reading groovy templates
------------------------------------------------------
Key: GTNPORTAL-66
URL: https://issues.jboss.org/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
Assignee: Minh Hoang TO
Priority: Optional
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,
patch_groovy_11-02-2010.zip, prova.zip
Original Estimate: 1 day
Remaining Estimate: 1 day
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, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4545
days inactive
5551
days old
31 comments
8 participants
participants (8)
-
Boleslaw Dawidowicz (JIRA) -
Boleslaw Dawidowicz (Updated) (JIRA)
-
Julien Viet (JIRA)
-
Luca Stancapiano (Commented) (JIRA)
-
Luca Stancapiano (JIRA)
-
Minh Hoang TO (Assigned) (JIRA)
-
Minh Hoang TO (Updated) (JIRA)
-
Thomas Heute (JIRA)