[JBoss JIRA] (FORGE-1707) Setting up Faces is giving an Error using Forge 2.3
by Arun Gupta (JIRA)
[ https://issues.jboss.org/browse/FORGE-1707?page=com.atlassian.jira.plugin... ]
Arun Gupta commented on FORGE-1707:
-----------------------------------
10:27:08,438 WARNING [org.jboss.forge.addon.facets.FacetFactoryImpl] (AeshProcess: 11) Could not install Facet of type [class org.jboss.forge.addon.facets.AbstractFacet_$$_javassist_f0361aaf-9a49-479e-ab97-cee855729cc4], due to exception: : java.lang.IllegalStateException: Could not resolve version for dependency [org.jboss.spec.javax.faces:jboss-jsf-api_2.0_spec:::].
at org.jboss.forge.addon.projects.impl.DependencyInstallerImpl.install(DependencyInstallerImpl.java:93)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) [furnace-api-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.projects.impl.DependencyInstallerImpl_$$_javassist_3bc0b298-fad0-4d89-bc79-7b45835ed3c8.install(DependencyInstallerImpl_$$_javassist_3bc0b298-fad0-4d89-bc79-7b45835ed3c8.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceLazyLoader.invoke(ExportedInstanceLazyLoader.java:64)
at org.jboss.forge.addon.projects.dependencies.DependencyInstaller_$$_javassist_2ab83b96-0190-4a21-bab0-4495a24d079a.install(DependencyInstaller_$$_javassist_2ab83b96-0190-4a21-bab0-4495a24d079a.java)
at org.jboss.forge.addon.javaee.AbstractJavaEEFacet.install(AbstractJavaEEFacet.java:77)
at org.jboss.forge.addon.javaee.faces.AbstractFacesFacetImpl.install(AbstractFacesFacetImpl.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) [furnace-api-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.facets.AbstractFacet_$$_javassist_f0361aaf-9a49-479e-ab97-cee855729cc4.install(AbstractFacet_$$_javassist_f0361aaf-9a49-479e-ab97-cee855729cc4.java)
at org.jboss.forge.addon.facets.AbstractFaceted.install(AbstractFaceted.java:76) [facets-api-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.facets.FacetFactoryImpl.install(FacetFactoryImpl.java:216) [facets-impl-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.facets.FacetFactoryImpl.install(FacetFactoryImpl.java:143) [facets-impl-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.facets.FacetFactoryImpl.install(FacetFactoryImpl.java:132) [facets-impl-2.3.0.Final.jar:2.3.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) [furnace-api-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.facets.FacetFactory_$$_javassist_06107339-d840-49b9-9fc4-2f9c900957f9.install(FacetFactory_$$_javassist_06107339-d840-49b9-9fc4-2f9c900957f9.java) [facets-api-2.3.0.Final.jar:2.3.0.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceLazyLoader.invoke(ExportedInstanceLazyLoader.java:64)
at org.jboss.forge.addon.facets.FacetFactory_$$_javassist_adeefdb6-8d03-40bb-8397-da9211c020f1.install(FacetFactory_$$_javassist_adeefdb6-8d03-40bb-8397-da9211c020f1.java) [facets-api-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.javaee.faces.ui.FacesSetupWizard.execute(FacesSetupWizard.java:63)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45]
at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:59) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34) [furnace-api-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:75) [furnace-proxy-2.3.0.Final.jar:2.3.0.Final]
at org.jboss.forge.addon.javaee.faces.ui.FacesSetupWizard_$$_javassist_e0fc22fd-256e-49df-b008-da7681f4d9a1.execute(FacesSetupWizard_$$_javassist_e0fc22fd-256e-49df-b008-da7681f4d9a1.java)
at org.jboss.forge.addon.ui.impl.controller.SingleCommandControllerImpl.execute(SingleCommandControllerImpl.java:88)
at org.jboss.forge.addon.shell.aesh.CommandAdapter.execute(CommandAdapter.java:74)
at org.jboss.aesh.console.AeshConsoleImpl$AeshConsoleCallbackImpl.execute(AeshConsoleImpl.java:292)
at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Setting up Faces is giving an Error using Forge 2.3
> ---------------------------------------------------
>
> Key: FORGE-1707
> URL: https://issues.jboss.org/browse/FORGE-1707
> Project: Forge
> Issue Type: Bug
> Reporter: Arun Gupta
>
> faces-setup
> Downloading: http://maven.repository.redhat.com/techpreview/all/org/jboss/spec/javax/f...
> ***ERROR*** Could not install JavaServer Faces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (FORGE-1705) Could not transfer artifact from/to central
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1705?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1705:
------------------------------------------
Yes, the settings.xml is like this, so no chance to have the maven central directly :
{code}
<repositories>
<repository>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>proto-snapshot-local</id>
<name>proto-snapshot-local</name>
<url>http://solar-repo.retraite.lan/proto-snapshot-local</url>
</repository>
<repository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>libs-release</name>
<url>http://stelar.traite.lan/libs-release</url>
</repository>
<repository>
<id>fmk-release-local</id>
<name>fmk-release-local</name>
<url>http://stelar.traite.lan/fmk-release-local</url>
</repository>
<repository>
<snapshots />
<id>snapshots</id>
<name>libs-snapshot</name>
<url>http://stelar.traite.lan/libs-snapshot</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<snapshots>
<enabled>false</enabled>
</snapshots>
<id>central</id>
<name>plugins-release</name>
<url>http://stelar.traite.lan/plugins-release</url>
</pluginRepository>
<pluginRepository>
<snapshots />
<id>snapshots</id>
<name>plugins-snapshot</name>
<url>http://stelar.traite.lan/plugins-snapshot</url>
</pluginRepository>
</pluginRepositories>
{code}
> Could not transfer artifact from/to central
> -------------------------------------------
>
> Key: FORGE-1705
> URL: https://issues.jboss.org/browse/FORGE-1705
> Project: Forge
> Issue Type: Task
> Components: Addon Manager
> Affects Versions: 2.3.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I am at a customer who uses a in-house Artifactory, no direct access to Maven Central. So when I setup JPA for example :
> {code}
> [MyProj]$ jpa-setup
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> {code}
> I get the following exception :
> {code}
> [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final from/to central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org from http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2... @ line 11, column 19
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:179) [maven-core-3.1.1.jar:3.1.1]
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:105) [maven-core-3.1.1.jar:3.1.1]
> at org.jboss.forge.addon.maven.projects.MavenBuildManager.getProjectBuildingResult(MavenBuildManager.java:88) [maven-impl-projects-2.3.0.Final.jar:2.3.0.Final]
> ... 79 more
> Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.MyProj:MyProj:1.0.0-SNAPSHOT
> {code}
> So it looks like, by default, it uses the {{http://repo.maven.apache.org/maven2}} which is not accessible. Is there a way not to specify this repository, but instead, rely on Maven configuration (here, the in-house Artifactory repository) ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (FORGE-1705) Could not transfer artifact from/to central
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1705?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1705:
----------------------------------------
Con you confirm that the maven central repo is overriden by a mirror in the settings.xml?
If you could paste a sample of their settings.xml that would help also.
Thanks
> Could not transfer artifact from/to central
> -------------------------------------------
>
> Key: FORGE-1705
> URL: https://issues.jboss.org/browse/FORGE-1705
> Project: Forge
> Issue Type: Task
> Components: Addon Manager
> Affects Versions: 2.3.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I am at a customer who uses a in-house Artifactory, no direct access to Maven Central. So when I setup JPA for example :
> {code}
> [MyProj]$ jpa-setup
> ***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
> {code}
> I get the following exception :
> {code}
> [ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final from/to central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org from http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2... @ line 11, column 19
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:179) [maven-core-3.1.1.jar:3.1.1]
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:105) [maven-core-3.1.1.jar:3.1.1]
> at org.jboss.forge.addon.maven.projects.MavenBuildManager.getProjectBuildingResult(MavenBuildManager.java:88) [maven-impl-projects-2.3.0.Final.jar:2.3.0.Final]
> ... 79 more
> Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.MyProj:MyProj:1.0.0-SNAPSHOT
> {code}
> So it looks like, by default, it uses the {{http://repo.maven.apache.org/maven2}} which is not accessible. Is there a way not to specify this repository, but instead, rely on Maven configuration (here, the in-house Artifactory repository) ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (FORGE-1436) Implement 'help' command as a source of general guidance and flow control
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/FORGE-1436?page=com.atlassian.jira.plugin... ]
Pavol Srna commented on FORGE-1436:
-----------------------------------
+1 for help. help was very intuitive and user friendly and very handy for new comers.
Can someone please explain how do I list all available commands using `man`?
> Implement 'help' command as a source of general guidance and flow control
> -------------------------------------------------------------------------
>
> Key: FORGE-1436
> URL: https://issues.jboss.org/browse/FORGE-1436
> Project: Forge
> Issue Type: Sub-task
> Components: UI - Shell
> Affects Versions: 2.0.0.Beta4
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I find this one usefull and it could even add more content (such as mentioning the {{man}} command...
> {code}
> [no project] Forge $ help
> Welcome to JBoss Forge, a next-generation interactive Shell and project-generation tool. If you find yourself lost, or uncertain how to complete an operation, you may press the <TAB> key for command-completion, or <TAB><TAB> for hints while typing a command.
> Type 'list-commands' for a list of available commands in the current Resource context.
> You are not working on a project. Type 'help new-project' to get started.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (FORGE-1705) Could not transfer artifact from/to central
by Antonio Goncalves (JIRA)
Antonio Goncalves created FORGE-1705:
----------------------------------------
Summary: Could not transfer artifact from/to central
Key: FORGE-1705
URL: https://issues.jboss.org/browse/FORGE-1705
Project: Forge
Issue Type: Task
Components: Addon Manager
Affects Versions: 2.3.0.Final
Reporter: Antonio Goncalves
Fix For: 2.x Future
I am at a customer who uses a in-house Artifactory, no direct access to Maven Central. So when I setup JPA for example :
{code}
[MyProj]$ jpa-setup
***ERROR*** No Facet of type [interface org.jboss.forge.addon.javaee.jpa.JPAFacet] is installed.
{code}
I get the following exception :
{code}
[ERROR] Non-resolvable import POM: Could not transfer artifact org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final from/to central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org from http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2... @ line 11, column 19
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:179) [maven-core-3.1.1.jar:3.1.1]
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:105) [maven-core-3.1.1.jar:3.1.1]
at org.jboss.forge.addon.maven.projects.MavenBuildManager.getProjectBuildingResult(MavenBuildManager.java:88) [maven-impl-projects-2.3.0.Final.jar:2.3.0.Final]
... 79 more
Caused by: org.apache.maven.model.building.ModelBuildingException: 1 problem was encountered while building the effective model for org.MyProj:MyProj:1.0.0-SNAPSHOT
{code}
So it looks like, by default, it uses the {{http://repo.maven.apache.org/maven2}} which is not accessible. Is there a way not to specify this repository, but instead, rely on Maven configuration (here, the in-house Artifactory repository) ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (FORGE-1704) Stale subflow pages are displayed and corresponding commands executed
by Vineet Reynolds (JIRA)
Vineet Reynolds created FORGE-1704:
--------------------------------------
Summary: Stale subflow pages are displayed and corresponding commands executed
Key: FORGE-1704
URL: https://issues.jboss.org/browse/FORGE-1704
Project: Forge
Issue Type: Bug
Components: UI - API
Affects Versions: 2.3.0.Final
Reporter: Vineet Reynolds
Priority: Blocker
This happens in scaffolding, but it is very likely an implementation issue with respect to subflows in the UI-API.
Stale subflow pages are displayed and their corresponding commands are executed even though they pages should not be displayed and are not relevant to the subflow sequence.
In scaffolding (see steps to reproduce), when I choose a scaffold provider, subflow pages from the originally selected provider are displayed in combination with the currently selected provider. Additionally, UICommands or WizardSteps from the original provider are executed, resulted in a weird scaffold being generated.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years
[JBoss JIRA] (FORGE-1582) Support the creation of nested Java source types
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1582?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1582:
------------------------------------------
I've been trying to create a Bean Validation constraint properly... in vain. What I want to achieve is the following (notice the @List annotation) :
{code}
@Target({METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER})
@Retention(RUNTIME)
@Documented
@Constraint(validatedBy = {})
public @interface Email {
String message() default "wrong email address";
Class<?>[] groups() default {};
Class<? extends Payload>[] payload() default {};
@Target({METHOD, FIELD, ANNOTATION_TYPE, CONSTRUCTOR, PARAMETER})
@Retention(RUNTIME)
@interface List {
Email[] value();
}
}
{code}
This is the code I've written. Both annotation are generated separately... but I don't know how to add listAnnotation inside emailAnnotation. Any idea ?
{code}
public class Main {
public static void main(String[] args) {
// This is the inner annotation List
final JavaAnnotationSource listAnnotation = Roaster.create(JavaAnnotationSource.class);
listAnnotation.setName("List");
listAnnotation.addAnnotation(Retention.class).setEnumValue(RUNTIME);
listAnnotation.addAnnotation(Target.class).setEnumValue(METHOD, FIELD, PARAMETER, TYPE);
listAnnotation.addAnnotationElement("Email[] value()");
System.out.println(listAnnotation);
// This is the annotation @Email
final JavaAnnotationSource emailAnnotation = Roaster.create(JavaAnnotationSource.class);
emailAnnotation.setPackage("org.agoncal.proj.constraints").setName("Email");
emailAnnotation.addImport(Payload.class);
emailAnnotation.addAnnotation(Documented.class);
emailAnnotation.addAnnotation(Retention.class).setEnumValue(RUNTIME);
emailAnnotation.addAnnotation(Target.class).setEnumValue(METHOD, FIELD, PARAMETER, TYPE);
emailAnnotation.addAnnotation(Constraint.class).setLiteralValue("validatedBy", "{}");
emailAnnotation.addAnnotationElement("String message() default \"wrong email address\"");
emailAnnotation.addAnnotationElement("Class<?>[] groups() default {}");
emailAnnotation.addAnnotationElement("Class<? extends Payload>[] payload() default {}");
// I was expecting to have a method like that so I could add annotation inside another one
// emailAnnotation.addAnnotationElement(emailAnnotation);
System.out.println(emailAnnotation);
}
}
{code}
> Support the creation of nested Java source types
> ------------------------------------------------
>
> Key: FORGE-1582
> URL: https://issues.jboss.org/browse/FORGE-1582
> Project: Forge
> Issue Type: Feature Request
> Components: Parsers / File Manipulation
> Affects Versions: 2.x Future
> Reporter: Matt Benson
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years