August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-597) Completer API should allow inter-dependent completion proposals for command arguments

by Lincoln Baxter III (JIRA)

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (FORGE-657) Missing mime-mapping in web.xml

by George Gastaldi (JIRA)

George Gastaldi created FORGE-657: ------------------------------------- Summary: Missing mime-mapping in web.xml Key: FORGE-657 URL: https://issues.jboss.org/browse/FORGE-657 Project: Forge Issue Type: Bug Components: Java EE APIs Reporter: George Gastaldi To eliminate the annoying log jboss server log: {code} 23:59:54,914 AVVERTENZA [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-1) JSF1091: No mime type could be found for file favicon.ico. To resolve this, add a mime-type mapping to the applications web.xml {code} you should add on web.xml: {code:xml} <mime-mapping> <extension>ico</extension> <mime-type>image/x-icon</mime-type> </mime-mapping> {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

13 years, 8 months

3
4
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by Richard Kennard (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] Richard Kennard resolved FORGE-619. ----------------------------------- Resolution: Done > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-658) Fix broken tests with End of Stream exceptions

by George Gastaldi (JIRA)

George Gastaldi created FORGE-658: ------------------------------------- Summary: Fix broken tests with End of Stream exceptions Key: FORGE-658 URL: https://issues.jboss.org/browse/FORGE-658 Project: Forge Issue Type: Bug Components: Test Harness Affects Versions: 1.0.7.Final Reporter: George Gastaldi Priority: Blocker Fix For: 1.0.7.Final Some tests are failing with this error: {code} testOmittedRequiredOptionIsFilled(org.jboss.forge.shell.test.ExecutionParserTest): End of stream: No more queued input. {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

13 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-304) Add getSupportedPackagingTypes() to PackagingFacet to allow build tools to specity supported packaging types

by Lincoln Baxter III (JIRA)

Add getSupportedPackagingTypes() to PackagingFacet to allow build tools to specity supported packaging types ------------------------------------------------------------------------------------------------------------ Key: SEAMFORGE-304 URL: https://issues.jboss.org/browse/SEAMFORGE-304 Project: Seam Forge Issue Type: Feature Request Components: Plugin API Affects Versions: 1.0.0.Beta2 Reporter: Lincoln Baxter III Fix For: 1.0.0.Beta3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-340: ------------------------------------------ Yes, I think that makes sense. I would be fine with simply adding an {code}@Option(name="checkoutDir") Resource checkoutDir{code} And let users save the source somewhere if they want. Otherwise just default to /tmp > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: FORGE-340 > URL: https://issues.jboss.org/browse/FORGE-340 > Project: Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Priority: Minor > Labels: Starter > Fix For: 1.0.7.Final > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-340: ------------------------------------- Labels: Starter (was: ) Fix Version/s: 1.0.7.Final (was: Future) > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: FORGE-340 > URL: https://issues.jboss.org/browse/FORGE-340 > Project: Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Priority: Minor > Labels: Starter > Fix For: 1.0.7.Final > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-545) Upgrade to Arquillian 1.0.0.Final

by George Gastaldi (JIRA)

George Gastaldi created FORGE-545: ------------------------------------- Summary: Upgrade to Arquillian 1.0.0.Final Key: FORGE-545 URL: https://issues.jboss.org/browse/FORGE-545 Project: Forge Issue Type: Library Upgrade Reporter: George Gastaldi Upgrade Forge tests to Arquillian 1.0.0.Final -- 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

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (FORGE-528) quickstart example "forge-from-scratch" does not work

by Gernot P (JIRA)

Gernot P created FORGE-528: ------------------------------ Summary: quickstart example "forge-from-scratch" does not work Key: FORGE-528 URL: https://issues.jboss.org/browse/FORGE-528 Project: Forge Issue Type: Bug Affects Versions: 1.0.2.Final Reporter: Gernot P running quickstart example "forge-from-scratch" (https://github.com/jbossas/quickstart/tree/master/forge-from-scratch) I get an error "***ERROR*** [run] String index out of range: -1" Here's the console output (I'm using Forge1.0.2Final): ? [named=The name of the new project (of type java.lang.String)]: forge5 ? [topLevelPackage=The top-level java package for the project [e.g: "com.example.project"] (of type java.lang.String)]: test ***SUCCESS*** Created project [forge5] in new working directory [D:\/workspace/jsf-jboss/forge5] Wrote D:\/workspace/jsf-jboss/forge5 Wrote D:\/workspace/jsf-jboss/forge5/pom.xml Wrote D:\/workspace/jsf-jboss/forge5/src/main/java Wrote D:\/workspace/jsf-jboss/forge5/src/test/java Wrote D:\/workspace/jsf-jboss/forge5/src/main/resources Wrote D:\/workspace/jsf-jboss/forge5/src/test/resources Wrote D:\/workspace/jsf-jboss/forge5/src/main/java/test Wrote D:\/workspace/jsf-jboss/forge5/src/main/resources/META-INF/forge.xml ***SUCCESS*** Installed [forge.maven.WebResourceFacet] successfully. Warning: The encoding 'UTF-8' is not supported by the Java runtime. Wrote D:\/workspace/jsf-jboss/forge5/src/main/webapp Wrote D:\/workspace/jsf-jboss/forge5/pom.xml Wrote D:\/workspace/jsf-jboss/forge5/src/main/resources/META-INF/persistence.xml ***ERROR*** [run] String index out of range: -1 [forge5] forge5 $ -- 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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] (FORGE-526) Classifiers not considered correctly in dependency resolution

by Sandro Sonntag (JIRA)

Sandro Sonntag created FORGE-526: ------------------------------------ Summary: Classifiers not considered correctly in dependency resolution Key: FORGE-526 URL: https://issues.jboss.org/browse/FORGE-526 Project: Forge Issue Type: Bug Affects Versions: 1.0.2.Final Reporter: Sandro Sonntag Added consideration of classifiers. With this change its possible add the same artifact with different classifiers. This is very important for GWT appliactions because they need a class and a source jar to compile. With out that the dependency is always overridden and the classifier is ignored. This codesample does not work: Dependency hibernateValidatorSources = DependencyBuilder .create("org.hibernate:hibernate-validator:4.2.0.Final:compile:jar").setClassifier("sources"); Dependency hibernateValidator = DependencyBuilder .create("org.hibernate:hibernate-validator:4.2.0.Final:compile:jar"); installer.install(project, hibernateValidatorSources, hibernateValidatorSources.getScopeTypeEnum()); installer.install(project, hibernateValidatorSources, hibernateValidatorSources.getScopeTypeEnum()); best regards Sandro -- 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

13 years, 8 months

2
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012