[JBoss JIRA] (ROASTER-5) Having method parameters a bit more typed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-5?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated ROASTER-5:
----------------------------------
Status: Closed (was: Pull Request Sent)
Fix Version/s: 2.1.1.Final
(was: 2.x Future)
Resolution: Done
> Having method parameters a bit more typed
> -----------------------------------------
>
> Key: ROASTER-5
> URL: https://issues.jboss.org/browse/ROASTER-5
> Project: Roaster
> Issue Type: Feature Request
> Components: API
> Affects Versions: 2.1.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.1.1.Final
>
>
> I want to create a Bean Validation implementation, that means that the {{isValid}} method takes two parameters. And the only way to add two parameters seems to be by a String
> {code}
> javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").setParameters("Number value, ConstraintValidatorContext context").setBody("return false;").addAnnotation(Override.class);
> {code}
> It would be nice to have typed parameters so the import is implicit, and things are a bit more typed :
> {code}
> javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").addParameter(Number.class, "value").addParameter(ConstraintValidatorContext.class, "context").setBody("return false;").addAnnotation(Override.class);
> {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
10 years, 9 months
[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1729:
----------------------------------------
Agreed.
I think a solution would be to detect if we are running in a test environment and let the producers call the appropriate method.
Perhaps by introducing a system property to the Furnace test harness?
> Test harness should set the Configuration directory to use the test temp dir by default
> ---------------------------------------------------------------------------------------
>
> Key: FORGE-1729
> URL: https://issues.jboss.org/browse/FORGE-1729
> Project: Forge
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 2.3.0.Final
> Reporter: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution:
> {code}
> static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH";
> String property = System.getProperty(USER_CONFIG_PATH);{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
10 years, 9 months
[JBoss JIRA] (ROASTER-5) Having method parameters a bit more typed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-5?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated ROASTER-5:
----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/forge/roaster/pull/12
> Having method parameters a bit more typed
> -----------------------------------------
>
> Key: ROASTER-5
> URL: https://issues.jboss.org/browse/ROASTER-5
> Project: Roaster
> Issue Type: Feature Request
> Components: API
> Affects Versions: 2.1.0.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I want to create a Bean Validation implementation, that means that the {{isValid}} method takes two parameters. And the only way to add two parameters seems to be by a String
> {code}
> javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").setParameters("Number value, ConstraintValidatorContext context").setBody("return false;").addAnnotation(Override.class);
> {code}
> It would be nice to have typed parameters so the import is implicit, and things are a bit more typed :
> {code}
> javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").addParameter(Number.class, "value").addParameter(ConstraintValidatorContext.class, "context").setBody("return false;").addAnnotation(Override.class);
> {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
10 years, 9 months
[JBoss JIRA] (ROASTER-5) Having method parameters a bit more typed
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/ROASTER-5?page=com.atlassian.jira.plugin.... ]
George Gastaldi reassigned ROASTER-5:
-------------------------------------
Assignee: George Gastaldi
> Having method parameters a bit more typed
> -----------------------------------------
>
> Key: ROASTER-5
> URL: https://issues.jboss.org/browse/ROASTER-5
> Project: Roaster
> Issue Type: Feature Request
> Components: API
> Affects Versions: 2.1.0.Final
> Reporter: Antonio Goncalves
> Assignee: George Gastaldi
> Fix For: 2.x Future
>
>
> I want to create a Bean Validation implementation, that means that the {{isValid}} method takes two parameters. And the only way to add two parameters seems to be by a String
> {code}
> javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").setParameters("Number value, ConstraintValidatorContext context").setBody("return false;").addAnnotation(Override.class);
> {code}
> It would be nice to have typed parameters so the import is implicit, and things are a bit more typed :
> {code}
> javaClass.addMethod().setPublic().setName("isValid").setReturnType("boolean").addParameter(Number.class, "value").addParameter(ConstraintValidatorContext.class, "context").setBody("return false;").addAnnotation(Override.class);
> {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
10 years, 9 months
[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default
by Jess Sightler (JIRA)
[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ]
Jess Sightler commented on FORGE-1729:
--------------------------------------
It seems intuitive to me that a temporary directory would be the default. The default of having a mvn clean install that manipulates the user's default configuration directory definitely breaks the principle of least surprise for me.
> Test harness should set the Configuration directory to use the test temp dir by default
> ---------------------------------------------------------------------------------------
>
> Key: FORGE-1729
> URL: https://issues.jboss.org/browse/FORGE-1729
> Project: Forge
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 2.3.0.Final
> Reporter: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution:
> {code}
> static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH";
> String property = System.getProperty(USER_CONFIG_PATH);{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
10 years, 9 months
[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:
------------------------------------------
No, this doesn't work either. It still looks for artifacts from the Maven Central, which is not accessible.
> 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
10 years, 9 months
[JBoss JIRA] (FORGE-1729) Test harness should set the Configuration directory to use the test temp dir by default
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1729?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1729:
-------------------------------------------
Thanks, right. My question, though, is should this happen automatically when running in a test environment? Seems like this is something that you might expect to be compartmentalized for you. WDYT?
> Test harness should set the Configuration directory to use the test temp dir by default
> ---------------------------------------------------------------------------------------
>
> Key: FORGE-1729
> URL: https://issues.jboss.org/browse/FORGE-1729
> Project: Forge
> Issue Type: Enhancement
> Components: Configuration
> Affects Versions: 2.3.0.Final
> Reporter: Lincoln Baxter III
> Fix For: 2.x Future
>
>
> Currently the UserConfiguration references the current users home directory while running tests - it should use the available system property while running tests in order to direct the config dir to a temp location for that test execution:
> {code}
> static final String USER_CONFIG_PATH = "org.jboss.forge.addon.configuration.USER_CONFIG_PATH";
> String property = System.getProperty(USER_CONFIG_PATH);{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
10 years, 9 months
[JBoss JIRA] (FORGE-1745) Cannot handle Freemaker templates from a main
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1745?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1745:
-------------------------------------------
Or add a private default constructor. But that would be nasty :)
> Cannot handle Freemaker templates from a main
> ---------------------------------------------
>
> Key: FORGE-1745
> URL: https://issues.jboss.org/browse/FORGE-1745
> Project: Forge
> Issue Type: Bug
> Components: Templates
> Affects Versions: 2.4.1.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I want to process a Freemaker template from a main class. The full code is here (https://github.com/agoncal/agoncal-sample-forge/blob/master/03-template/s...) and this is an abstract :
> {code}
> private void doIt() throws IOException {
> Furnace furnace = startFurnace();
> try {
> ResourceFactory resourceFactory = furnace.getAddonRegistry().getServices(ResourceFactory.class).get();
> TemplateProcessorFactory factory = furnace.getAddonRegistry().getServices(TemplateProcessorFactory.class).get();
> Resource<URL> templateResource = resourceFactory.create(getClass().getResource("RestEndpoint.jv"));
> Template template = new FreemarkerTemplate(templateResource); // Mark this resource as a Freemarker template
> TemplateProcessor processor = factory.fromTemplate(template);
> Map<String, Object> params = new HashMap<String, Object>(); //Could be a POJO also.
> params.put("name", "JBoss Forge");
> String output = processor.process(params); // should return "Hello JBoss Forge".
> System.out.println(output);
> } finally {
> furnace.stop();
> }
> }
> {code}
> But I get the following error :
> {code}
> Exception in thread "main" org.jboss.forge.furnace.exception.ContainerException: Failed to create proxy for type [class org.jboss.forge.addon.templates.freemarker.FreemarkerTemplate]
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:827)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:687)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceSingleParameterValue(ClassLoaderAdapterCallback.java:617)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceParameterValues(ClassLoaderAdapterCallback.java:489)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$100(ClassLoaderAdapterCallback.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:92)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:71)
> at org.jboss.forge.addon.templates.TemplateProcessorFactory_$$_javassist_381849cc-8aad-4339-adb9-66683e1ebbde.fromTemplate(TemplateProcessorFactory_$$_javassist_381849cc-8aad-4339-adb9-66683e1ebbde.java)
> at org.agoncal.sample.forge.template.RestEndpoint.doIt(RestEndpoint.java:47)
> at org.agoncal.sample.forge.template.RestEndpoint.main(RestEndpoint.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
> Caused by: java.lang.InstantiationException: org.jboss.forge.addon.templates.Template_$$_javassist_840b9c34-f23e-4d1e-8a3e-14ff4dfc9c4e
> at java.lang.Class.newInstance(Class.java:359)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:785)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:707)
> ... 15 more
> {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
10 years, 9 months
[JBoss JIRA] (FORGE-1745) Cannot handle Freemaker templates from a main
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/FORGE-1745?page=com.atlassian.jira.plugin... ]
Lincoln Baxter III commented on FORGE-1745:
-------------------------------------------
I'm not sure you need this step:
{code}Template template = new FreemarkerTemplate(templateResource); // Mark this resource as a Freemarker template{code}
Try passing the URL resource into the TemplateProcessorFactory directly. Otherwise we'll need to turn this into an interface.
> Cannot handle Freemaker templates from a main
> ---------------------------------------------
>
> Key: FORGE-1745
> URL: https://issues.jboss.org/browse/FORGE-1745
> Project: Forge
> Issue Type: Bug
> Components: Templates
> Affects Versions: 2.4.1.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I want to process a Freemaker template from a main class. The full code is here (https://github.com/agoncal/agoncal-sample-forge/blob/master/03-template/s...) and this is an abstract :
> {code}
> private void doIt() throws IOException {
> Furnace furnace = startFurnace();
> try {
> ResourceFactory resourceFactory = furnace.getAddonRegistry().getServices(ResourceFactory.class).get();
> TemplateProcessorFactory factory = furnace.getAddonRegistry().getServices(TemplateProcessorFactory.class).get();
> Resource<URL> templateResource = resourceFactory.create(getClass().getResource("RestEndpoint.jv"));
> Template template = new FreemarkerTemplate(templateResource); // Mark this resource as a Freemarker template
> TemplateProcessor processor = factory.fromTemplate(template);
> Map<String, Object> params = new HashMap<String, Object>(); //Could be a POJO also.
> params.put("name", "JBoss Forge");
> String output = processor.process(params); // should return "Hello JBoss Forge".
> System.out.println(output);
> } finally {
> furnace.stop();
> }
> }
> {code}
> But I get the following error :
> {code}
> Exception in thread "main" org.jboss.forge.furnace.exception.ContainerException: Failed to create proxy for type [class org.jboss.forge.addon.templates.freemarker.FreemarkerTemplate]
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:827)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:687)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceSingleParameterValue(ClassLoaderAdapterCallback.java:617)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceParameterValues(ClassLoaderAdapterCallback.java:489)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$100(ClassLoaderAdapterCallback.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:92)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:71)
> at org.jboss.forge.addon.templates.TemplateProcessorFactory_$$_javassist_381849cc-8aad-4339-adb9-66683e1ebbde.fromTemplate(TemplateProcessorFactory_$$_javassist_381849cc-8aad-4339-adb9-66683e1ebbde.java)
> at org.agoncal.sample.forge.template.RestEndpoint.doIt(RestEndpoint.java:47)
> at org.agoncal.sample.forge.template.RestEndpoint.main(RestEndpoint.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
> Caused by: java.lang.InstantiationException: org.jboss.forge.addon.templates.Template_$$_javassist_840b9c34-f23e-4d1e-8a3e-14ff4dfc9c4e
> at java.lang.Class.newInstance(Class.java:359)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:785)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:707)
> ... 15 more
> {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
10 years, 9 months
[JBoss JIRA] (FORGE-1745) Cannot handle Freemaker templates from a main
by Antonio Goncalves (JIRA)
[ https://issues.jboss.org/browse/FORGE-1745?page=com.atlassian.jira.plugin... ]
Antonio Goncalves commented on FORGE-1745:
------------------------------------------
Any work around ?
> Cannot handle Freemaker templates from a main
> ---------------------------------------------
>
> Key: FORGE-1745
> URL: https://issues.jboss.org/browse/FORGE-1745
> Project: Forge
> Issue Type: Bug
> Components: Templates
> Affects Versions: 2.4.1.Final
> Reporter: Antonio Goncalves
> Fix For: 2.x Future
>
>
> I want to process a Freemaker template from a main class. The full code is here (https://github.com/agoncal/agoncal-sample-forge/blob/master/03-template/s...) and this is an abstract :
> {code}
> private void doIt() throws IOException {
> Furnace furnace = startFurnace();
> try {
> ResourceFactory resourceFactory = furnace.getAddonRegistry().getServices(ResourceFactory.class).get();
> TemplateProcessorFactory factory = furnace.getAddonRegistry().getServices(TemplateProcessorFactory.class).get();
> Resource<URL> templateResource = resourceFactory.create(getClass().getResource("RestEndpoint.jv"));
> Template template = new FreemarkerTemplate(templateResource); // Mark this resource as a Freemarker template
> TemplateProcessor processor = factory.fromTemplate(template);
> Map<String, Object> params = new HashMap<String, Object>(); //Could be a POJO also.
> params.put("name", "JBoss Forge");
> String output = processor.process(params); // should return "Hello JBoss Forge".
> System.out.println(output);
> } finally {
> furnace.stop();
> }
> }
> {code}
> But I get the following error :
> {code}
> Exception in thread "main" org.jboss.forge.furnace.exception.ContainerException: Failed to create proxy for type [class org.jboss.forge.addon.templates.freemarker.FreemarkerTemplate]
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:827)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:687)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceSingleParameterValue(ClassLoaderAdapterCallback.java:617)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhanceParameterValues(ClassLoaderAdapterCallback.java:489)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.access$100(ClassLoaderAdapterCallback.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$1.call(ClassLoaderAdapterCallback.java:92)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:71)
> at org.jboss.forge.addon.templates.TemplateProcessorFactory_$$_javassist_381849cc-8aad-4339-adb9-66683e1ebbde.fromTemplate(TemplateProcessorFactory_$$_javassist_381849cc-8aad-4339-adb9-66683e1ebbde.java)
> at org.agoncal.sample.forge.template.RestEndpoint.doIt(RestEndpoint.java:47)
> at org.agoncal.sample.forge.template.RestEndpoint.main(RestEndpoint.java:35)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)
> Caused by: java.lang.InstantiationException: org.jboss.forge.addon.templates.Template_$$_javassist_840b9c34-f23e-4d1e-8a3e-14ff4dfc9c4e
> at java.lang.Class.newInstance(Class.java:359)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:785)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:34)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.enhance(ClassLoaderAdapterCallback.java:707)
> ... 15 more
> {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
10 years, 9 months