March 2012 - forge-issues - Jboss List Archives

by Esteve Aviles (Created) (JIRA)

Proxy support ------------- Key: FORGE-421 URL: https://issues.jboss.org/browse/FORGE-421 Project: Forge Issue Type: Enhancement Components: Shell, Windows Affects Versions: 1.0.0.Beta5 Environment: Windows7 -32b Reporter: Esteve Aviles Priority: Optional Is there any way to configure forge to use proxy. I have problems while trying to install new plugins: -set DEFAULT_PLUGIN_REPO https://raw.github.com/forge/plugin-repository/master/repository.yaml -forge install-plugin arquillian -Connecting to remote repository [https://raw.github.com/forge/plugin-repository/master/repository.yaml]... ***ERROR*** [forge install-plugin] Connection to https://raw.github.com refused I am behind a firewall. I have no problem in downloading it with an explorer. Maven also works fine. Thanks -- 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

12 years, 1 month

9
24
0 / 0

[JBoss JIRA] (FORGE-525) project add-dependency should accept properties

by Jason Porter (JIRA)

Jason Porter created FORGE-525: ---------------------------------- Summary: project add-dependency should accept properties Key: FORGE-525 URL: https://issues.jboss.org/browse/FORGE-525 Project: Forge Issue Type: Enhancement Components: Maven Integration Affects Versions: 1.0.2.Final Reporter: Jason Porter Here's some sample input: {code} $ project set-property --name arquillian.version --value 1.0.0.CR6 Set property [arquillian.version=1.0.0.CR6] $ project add-dependency org.jboss.arquillian:arquillian-bom:::${arquillian.version} ***INFO*** The command [add-dependency] takes [1] unnamed argument(s), but found [2]. ***INFO*** Swallowed unknown token [{] for command [add-dependency]. ***INFO*** Swallowed unknown token [arquillian.version] for command [add-dependency]. ***INFO*** Swallowed unknown token [}] for command [add-dependency]. ***INFO*** Could not parse [org.jboss.arquillian:arquillian-bom:::$]... please try again... ? [[ groupId:artifactId {:version :scope :packaging} ] (of type org.jboss.forge.project.dependencies.Dependency)]: [killed] ***INFO*** Aborted. $ project add-dependency "org.jboss.arquillian:arquillian-bom:::${arquillian.version}" ***INFO*** Could not parse [org.jboss.arquillian:arquillian-bom:::${arquillian.version}]... please try again... {code} Either one of those two should work. -- 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

12 years, 1 month

2
6
0 / 0

[JBoss JIRA] (FORGE-523) field plugin fails to create enum attribute

by George Gastaldi (JIRA)

George Gastaldi created FORGE-523: ------------------------------------- Summary: field plugin fails to create enum attribute Key: FORGE-523 URL: https://issues.jboss.org/browse/FORGE-523 Project: Forge Issue Type: Bug Reporter: George Gastaldi Having an entity named X and an enumeration named Y, running {code} field custom --named enumAtt --type Y.java {code} creates the following entry: {code} @Column private java enumAtt; .. getters and setters ... {code} it should read: {code} @Column @Enumerated private Y enumAtt; {code} -- 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

12 years, 1 month

3
10
0 / 0

[JBoss JIRA] (FORGE-527) CommandExecutionException while creating new project

by Pavol Srna (JIRA)

Pavol Srna created FORGE-527: -------------------------------- Summary: CommandExecutionException while creating new project Key: FORGE-527 URL: https://issues.jboss.org/browse/FORGE-527 Project: Forge Issue Type: Bug Affects Versions: 1.0.1.Final Reporter: Pavol Srna Priority: Critical Fix For: 1.0.2.Final I hit on this here: https://issues.jboss.org/browse/JBIDE-11178 As Lincoln said the fix should go into 1.0.1 and it is still not there even in 1.0.2. Can you guys please have a look? -- 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

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] (FORGE-522) faces setup ERROR: null without explanation

by Hendy Irawan (JIRA)

Hendy Irawan created FORGE-522: ---------------------------------- Summary: faces setup ERROR: null without explanation Key: FORGE-522 URL: https://issues.jboss.org/browse/FORGE-522 Project: Forge Issue Type: Bug Components: Java EE APIs Affects Versions: 1.0.1.Final Environment: Ubuntu 11.10 64-bit, JBoss AS 7.1.1 Reporter: Hendy Irawan Faces setup not working without any error message : {code} [dsembed] dsembed $ faces setup Warning: The encoding 'UTF-8' is not supported by the Java runtime. ? Do you also want to install the Faces servlet and mapping? [y/N] y Warning: The encoding 'UTF-8' is not supported by the Java runtime. ***ERROR*** [faces setup] null {code} The project to reproduce is here: https://github.com/soluvas/dsembed/zipball/faces-setup-bug The problem is...... I exited Forge then restarted it then I try 'faces setup' again and now it works: {code} faces setup Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. ? Do you also want to install the Faces servlet and mapping? [y/N] y Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. ***SUCCESS*** JavaServer Faces is installed. Wrote /home/ceefour/git/dsembed/src/main/webapp/WEB-INF/web.xml {code} So what was it..? -- 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

12 years, 1 month

3
3
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by Shameera Rathanayaka (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] Shameera Rathanayaka edited comment on FORGE-85 at 3/31/12 3:42 PM: -------------------------------------------------------------------- Hi, I went through the code base , encounter that exclaimation mark of the given parameters, is use to identify "Event Designators" in ConsoleReader class. If we allow to pass any string contain '!' marks then the existing "Event Designators" support will drop. This is because, In the expandEvents method it throws event not found IllegalArgumentException when it detect size of the history is zero or history event is not match with the given syntax. we can provide a chance to "echo" plugin as a special case(i have attached patch for this) but not for all if so we need to drop the "Event Destignators" support feature. was (Author: shameera): Hi, I went through the code base , encounter that "!-exclaimation" of the given parameters, is use to identify "Event Designators" in ConsoleReader class. If we allow to pass any string contain '!' marks then the existing "Event Designators" support will drop. This is because, In the expandEvents method it throws event not found IllegalArgumentException when it detect size of the history is zero or history event is not match with the given syntax. we can provide a chance to "echo" plugin as a special case(i have attached patch for this) but not for all if so we need to drop the "Event Destignators" support feature. > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.2.Final > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by Shameera Rathanayaka (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] Shameera Rathanayaka edited comment on FORGE-85 at 3/31/12 3:41 PM: -------------------------------------------------------------------- Hi, I went through the code base , encounter that "!-exclaimation" of the given parameters, is use to identify "Event Designators" in ConsoleReader class. If we allow to pass any string contain '!' marks then the existing "Event Designators" support will drop. This is because, In the expandEvents method it throws event not found IllegalArgumentException when it detect size of the history is zero or history event is not match with the given syntax. we can provide a chance to "echo" plugin as a special case(i have attached patch for this) but not for all if so we need to drop the "Event Destignators" support feature. was (Author: shameera): Hi, I went through the code base , encounter that '!' of the given parameters, is use to identify "Event Designators" in ConsoleReader class. If we allow to pass any string contain '!' marks then the existing "Event Designators" support will drop. This is because, In the expandEvents method it throws event not found IllegalArgumentException when it detect size of the history is zero or history event is not match with the given syntax. we can provide a chance to "echo" plugin as a special case(i have attached patch for this) but not for all if so we need to drop the "Event Destignators" support feature. > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.2.Final > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by Shameera Rathanayaka (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] Shameera Rathanayaka updated FORGE-85: -------------------------------------- Attachment: Forge-85.patch Hi, I went through the code base , encounter that '!' of the given parameters, is use to identify "Event Designators" in ConsoleReader class. If we allow to pass any string contain '!' marks then the existing "Event Designators" support will drop. This is because, In the expandEvents method it throws event not found IllegalArgumentException when it detect size of the history is zero or history event is not match with the given syntax. we can provide a chance to "echo" plugin as a special case(i have attached patch for this) but not for all if so we need to drop the "Event Destignators" support feature. > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Mike Brock > Priority: Critical > Fix For: 1.0.2.Final > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {code} -- 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

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-481) JavaParser.parse gets confused on inner classes

by Richard Kennard (JIRA)

Richard Kennard created FORGE-481: ------------------------------------- Summary: JavaParser.parse gets confused on inner classes Key: FORGE-481 URL: https://issues.jboss.org/browse/FORGE-481 Project: Forge Issue Type: Bug Reporter: Richard Kennard While developing the AeroGear scaffold, I discovered that if I do... {noformat} // Generate ObjectMapperProviderTemplate.jv JavaClass objectMapperProvider = JavaParser.parse(JavaClass.class, this.objectMapperProviderTemplate.render(context)); objectMapperProvider.setPackage(serviceBean.getPackage()); result.add(ScaffoldUtil.createOrOverwrite(this.prompt, java.getJavaResource(objectMapperProvider), objectMapperProvider.toString(), true)); {noformat} ...with a ObjectMapperProviderTemplate.jv of... {noformat} import java.io.IOException; import java.lang.reflect.Method; import javax.persistence.Entity; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; import javax.ws.rs.ext.ContextResolver; import javax.ws.rs.ext.Provider; import org.codehaus.jackson.JsonGenerator; import org.codehaus.jackson.JsonParser; import org.codehaus.jackson.JsonProcessingException; import org.codehaus.jackson.map.DeserializationConfig; import org.codehaus.jackson.map.DeserializationContext; import org.codehaus.jackson.map.JsonSerializer; import org.codehaus.jackson.map.ObjectMapper; import org.codehaus.jackson.map.SerializationConfig; import org.codehaus.jackson.map.SerializerProvider; import org.codehaus.jackson.map.deser.BeanDeserializer; import org.codehaus.jackson.map.deser.CustomDeserializerFactory; import org.codehaus.jackson.map.deser.StdDeserializerProvider; import org.codehaus.jackson.map.introspect.BasicBeanDescription; import org.codehaus.jackson.map.ser.BeanSerializer; import org.codehaus.jackson.map.ser.CustomSerializerFactory; import org.codehaus.jackson.type.JavaType; /** * Custom JSON ObjectMapper that knows how to lookup JPA entities based on ids. */ @Provider public class ObjectMapperProvider implements ContextResolver<ObjectMapper> { private final ObjectMapper mapper; @PersistenceContext private EntityManager entityManager; public ObjectMapperProvider() { this.mapper = new ObjectMapper(); // Serialize CustomSerializerFactory serializer = new CustomSerializerFactory() { @Override protected JsonSerializer<Object> constructBeanSerializer( SerializationConfig config, BasicBeanDescription beanDesc) { BeanSerializer beanSerializer = (BeanSerializer) super .constructBeanSerializer(config, beanDesc); return new JpaSerializer(beanSerializer); } }; this.mapper.setSerializerFactory(serializer); // Deserialize this.mapper.setDeserializerProvider(new StdDeserializerProvider( new CustomDeserializerFactory() { protected BeanDeserializer constructBeanDeserializerInstance( DeserializationConfig config, JavaType type, BasicBeanDescription beanDesc) { return new JpaDeserializer(type); } })); } @Override public ObjectMapper getContext(Class<?> type) { return this.mapper; } // // Inner classes // private class JpaSerializer extends JsonSerializer<Object> { private BeanSerializer delegate; private Method serializeFields; public JpaSerializer(BeanSerializer delegate) { this.delegate = delegate; try { this.serializeFields = BeanSerializer.class.getDeclaredMethod( "serializeFields", Object.class, JsonGenerator.class, SerializerProvider.class); } catch (Exception e) { throw new RuntimeException(e); } this.serializeFields.setAccessible(true); } @Override public void serialize(Object value, JsonGenerator jgen, SerializerProvider provider) throws IOException, JsonProcessingException { jgen.writeStartObject(); // Special support for toString... provider.getKeySerializer().serialize("toString", jgen, provider); provider.findTypedValueSerializer(String.class, true).serialize( value.toString(), jgen, provider); // ...then delegate try { this.serializeFields.invoke(this.delegate, value, jgen, provider); } catch (Exception e) { throw new IOException(e); } jgen.writeEndObject(); } } private class JpaDeserializer extends BeanDeserializer { public JpaDeserializer(JavaType type) { super(type); } public Object deserializeFromString(JsonParser jp, DeserializationContext ctxt) throws IOException, JsonProcessingException { // Special support for JPA entities... if (this.getBeanClass().isAnnotationPresent(Entity.class)) { return ObjectMapperProvider.this.entityManager.find( this.getBeanClass(), Long.valueOf(jp.getText())); } // ...or delegate return super.deserializeFromString(jp, ctxt); } } } {noformat} ...then it ends up creating a Java file called JpaDeserializer.java, not ObjectMapperProvider.java. If I do... {noformat} // Generate ObjectMapperProviderTemplate.jv JavaClass objectMapperProvider = JavaParser.parse(JavaClass.class, this.objectMapperProviderTemplate.render(context)); objectMapperProvider.setPackage(serviceBean.getPackage()); result.add(ScaffoldUtil.createOrOverwrite(this.prompt, java.getJavaResource(serviceBean.getPackage() + ".ObjectMapperProvider.java"), objectMapperProvider.toString(), true)); {noformat} ...then it's fine. -- 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

12 years, 2 months

3
3
0 / 0

[JBoss JIRA] (FORGE-497) EJB facet requires JTA API in POM

by Pete Muir (JIRA)

Pete Muir created FORGE-497: ------------------------------- Summary: EJB facet requires JTA API in POM Key: FORGE-497 URL: https://issues.jboss.org/browse/FORGE-497 Project: Forge Issue Type: Bug Components: Builtin Plugins Affects Versions: 1.0.0.Final Reporter: Pete Muir If the JTA API is missing from the POM on an existing project the EJB facet won't be installed. This is not right, EJB is very usable without JTA. -- 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

12 years, 2 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2012