April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-846) Create a template processor addon

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-846?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-846: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Create a template processor addon > --------------------------------- > > Key: FORGE-846 > URL: https://issues.jboss.org/browse/FORGE-846 > Project: Forge > Issue Type: Feature Request > Components: Blessed Plugins > Affects Versions: 2.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 2.0.0.Alpha4 > > > We need an addon to manipulate templates. This addon will be used in the New Project addon and in the scaffold in a first moment. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-803) Promote usage of ShrinkWrap Resolver instead of using Aether directly

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-803?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-803: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Promote usage of ShrinkWrap Resolver instead of using Aether directly > --------------------------------------------------------------------- > > Key: FORGE-803 > URL: https://issues.jboss.org/browse/FORGE-803 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > The MavenDependencyResolver should use ShrinkWrap Resolver APIs instead of using the Aether APIs directly. > This is believed to bring some performance enhancements also, due to internal improvements in the latest version of SWR. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-861) Forge 2 does not start upon installation into Eclipse. Must restart eclipse.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-861?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-861: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Forge 2 does not start upon installation into Eclipse. Must restart eclipse. > ---------------------------------------------------------------------------- > > Key: FORGE-861 > URL: https://issues.jboss.org/browse/FORGE-861 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha2 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha4 > > > Technically this issue is in the JBDS side, but since it is related to Forge 2 only, I put the issue here for now. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-877) Addon sub-module is not imported into eclipse workspace

by George Gastaldi (JIRA)

George Gastaldi created FORGE-877: ------------------------------------- Summary: Addon sub-module is not imported into eclipse workspace Key: FORGE-877 URL: https://issues.jboss.org/browse/FORGE-877 Project: Forge Issue Type: Bug Affects Versions: 2.0.0.Alpha3 Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 2.0.0.Alpha4 When a new forge addon is created using the "New Project" addon, and the option "Split project" is chosen, the addon submodule is not imported -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-820) No XPathFactory implementation found inside a forge addon

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-820?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III closed FORGE-820. ------------------------------------ Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Final) Resolution: Done Fixed in Forge Modules Fork 3: https://github.com/jbossas/jboss-modules/pull/34 > No XPathFactory implementation found inside a forge addon > --------------------------------------------------------- > > Key: FORGE-820 > URL: https://issues.jboss.org/browse/FORGE-820 > Project: Forge > Issue Type: Bug > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Alpha4 > > > The following test fails: > {code:java} > @RunWith(Arquillian.class) > public class XPathContainerTest > { > @Deployment > public static ForgeArchive getDeployment() > { > ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class) > .addClasses(XPathContainerTest.class) > .addBeansXML(); > return archive; > } > @Test > public void testContainerStartup() > { > Assert.assertNotNull(XPathFactory.newInstance().newXPath()); > } > } > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] Vineet Reynolds commented on FORGE-875: --------------------------------------- I would assume that it is the generate.fsh script referenced in the [Forge-from-scratch JDF quickstart|http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/forge...]. It contains the following line: {noformat} scaffold setup --scaffoldType faces; ... {noformat} and the {{FacesScaffold}} contains a {{@RequiresFacet}} declaration on {{CDIFacet}}. This should activate the Facet, but I suspect this probably does not install it completely. > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Story > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Priority: Blocker > Labels: forge > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-876) Cannot @Inject UIInput<FileResource<?>> input; Deployment exception results.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-876: ---------------------------------------- Summary: Cannot @Inject UIInput<FileResource<?>> input; Deployment exception results. Key: FORGE-876 URL: https://issues.jboss.org/browse/FORGE-876 Project: Forge Issue Type: Story Components: Container, Plugin API Affects Versions: 2.0.0.Alpha2 Reporter: Lincoln Baxter III Fix For: 2.0.0.Alpha3 {code} org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [UIInput<FileResource<Object>>] with qualifiers [@Service] at injection point [[BackedAnnotatedField] @Inject org.jboss.forge.ui.impl.UIInputResourceInjectionTest.firstName] at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:403) at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:325) at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:177) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:208) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:519) at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:505) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:480) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:536) at org.jboss.weld.bootstrap.api.helpers.ForwardingBootstrap.validateBeans(ForwardingBootstrap.java:75) at org.jboss.weld.environment.se.Weld.initialize(Weld.java:138) at org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup.call(AddonRunnable.java:171) at org.jboss.forge.container.impl.AddonRunnable$AddonContainerStartup.call(AddonRunnable.java:133) at org.jboss.forge.container.util.ClassLoaders.executeIn(ClassLoaders.java:34) at org.jboss.forge.container.impl.AddonRunnable$3.call(AddonRunnable.java:106) at org.jboss.forge.container.impl.AddonRunnable$3.call(AddonRunnable.java:98) at org.jboss.forge.container.LockManagerImpl.performLocked(LockManagerImpl.java:48) at org.jboss.forge.container.impl.AddonRunnable.run(AddonRunnable.java:97) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-820) No XPathFactory implementation found inside a forge addon

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-820?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III reassigned FORGE-820: ---------------------------------------- Assignee: Lincoln Baxter III > No XPathFactory implementation found inside a forge addon > --------------------------------------------------------- > > Key: FORGE-820 > URL: https://issues.jboss.org/browse/FORGE-820 > Project: Forge > Issue Type: Bug > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > Assignee: Lincoln Baxter III > Priority: Blocker > Fix For: 2.0.0.Final > > > The following test fails: > {code:java} > @RunWith(Arquillian.class) > public class XPathContainerTest > { > @Deployment > public static ForgeArchive getDeployment() > { > ForgeArchive archive = ShrinkWrap.create(ForgeArchive.class) > .addClasses(XPathContainerTest.class) > .addBeansXML(); > return archive; > } > @Test > public void testContainerStartup() > { > Assert.assertNotNull(XPathFactory.newInstance().newXPath()); > } > } > {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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-875: --------------------------------------- Hi Randy, Where is this generate.fsh script you mentioned ? > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Story > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Priority: Blocker > Labels: forge > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (FORGE-875) the `scaffold setup --scaffoldType faces; ` command. failed to create beans.xml

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-875?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-875: ------------------------------------- Priority: Blocker (was: Major) > the `scaffold setup --scaffoldType faces;` command. failed to create beans.xml > ------------------------------------------------------------------------------ > > Key: FORGE-875 > URL: https://issues.jboss.org/browse/FORGE-875 > Project: Forge > Issue Type: Story > Affects Versions: 1.2.2.Final > Environment: Mac: OS X 10.8.3, 2.66 GHz Intel Core i7, 4GG 1067 MHz DDR3 > Running Forge Console in JBoss Developers Studio version 6.1.0.GA, Deploying to JBoss EAP 6.0.1 > Reporter: Randy Thomas > Priority: Blocker > Labels: forge > > I generated a sample project using the generate.fsh script. I deployed the war file to EAP 6 and everything seemed to be working fine. > The welcome page comes up for the app with no problems. However, an error is generated upon the attempt to add data to the database. > I was able to resolve the problem by adding the following lines to the script: > @/* Add beans.xml for CDI */; > touch src/main/webapp/WEB-INF/beans.xml > Lincoln indicated that this should have already been done by the > `scaffold setup --scaffoldType faces;` command. -- 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

11 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013