July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1023) FileResource should support reading directly to a String

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-1023: ----------------------------------------- Summary: FileResource should support reading directly to a String Key: FORGE-1023 URL: https://issues.jboss.org/browse/FORGE-1023 Project: Forge Issue Type: Feature Request Components: Resources API Affects Versions: 2.0.0.Alpha6 Reporter: Lincoln Baxter III -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1022?page=com.atlassian.jira.plugin... ] Burr Sutter commented on FORGE-1022: ------------------------------------ Diff: http://screencast.com/t/kmc3WaCMX0 > Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold > -------------------------------------------------- > > Key: FORGE-1022 > URL: https://issues.jboss.org/browse/FORGE-1022 > Project: Forge > Issue Type: Bug > Reporter: Burr Sutter > Attachments: StaffBean.java, StaffBean.java, StoreBean.java, StoreBean.java > > > The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1022?page=com.atlassian.jira.plugin... ] Burr Sutter updated FORGE-1022: ------------------------------- Attachment: StoreBean.java StoreBean.java - Forge 1.0.5.Final > Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold > -------------------------------------------------- > > Key: FORGE-1022 > URL: https://issues.jboss.org/browse/FORGE-1022 > Project: Forge > Issue Type: Bug > Reporter: Burr Sutter > Attachments: StaffBean.java, StaffBean.java, StoreBean.java, StoreBean.java > > > The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1022?page=com.atlassian.jira.plugin... ] Burr Sutter commented on FORGE-1022: ------------------------------------ The commands: @/* Clear the screen */; clear; @/* Create a new project in the current directory */; new-project; @/* This means less typing. If a script is automated, or is not meant to be interactive, use this command */; set ACCEPT_DEFAULTS true; @/* Install the hibernate-tools plug-in which supports DB Rev Eng */; forge install-plugin hibernate-tools; @/* Turn our Java project into a JPA project */; persistence setup --provider HIBERNATE --container JBOSS_AS7 ; @/* Reverse Engineer the Sakila DB */; generate-entities configure-settings --entityPackage model --driver org.h2.Driver --pathToDriver /Users/burr/gettingstarted/sakila-h2/h2-1.3.161.jar --url jdbc:h2:tcp://localhost/sakila --user sa --dialect org.hibernate.dialect.H2Dialect; scaffold setup --scaffoldType faces; scaffold from-entity model.* --overwrite; > Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold > -------------------------------------------------- > > Key: FORGE-1022 > URL: https://issues.jboss.org/browse/FORGE-1022 > Project: Forge > Issue Type: Bug > Reporter: Burr Sutter > Attachments: StaffBean.java, StaffBean.java, StoreBean.java > > > The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1022?page=com.atlassian.jira.plugin... ] Burr Sutter updated FORGE-1022: ------------------------------- Attachment: StoreBean.java StoreBean.java - Forge 1.3.2 > Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold > -------------------------------------------------- > > Key: FORGE-1022 > URL: https://issues.jboss.org/browse/FORGE-1022 > Project: Forge > Issue Type: Bug > Reporter: Burr Sutter > Attachments: StaffBean.java, StaffBean.java, StoreBean.java > > > The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1022?page=com.atlassian.jira.plugin... ] Burr Sutter updated FORGE-1022: ------------------------------- Attachment: StaffBean.java StaffBean.java - Forge 1.3.2 JBDS 7 > Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold > -------------------------------------------------- > > Key: FORGE-1022 > URL: https://issues.jboss.org/browse/FORGE-1022 > Project: Forge > Issue Type: Bug > Reporter: Burr Sutter > Attachments: StaffBean.java, StaffBean.java > > > The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/FORGE-1022?page=com.atlassian.jira.plugin... ] Burr Sutter updated FORGE-1022: ------------------------------- Attachment: StaffBean.java StaffBean.java - Forge 1.0.5.Final (JBDS 5) > Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold > -------------------------------------------------- > > Key: FORGE-1022 > URL: https://issues.jboss.org/browse/FORGE-1022 > Project: Forge > Issue Type: Bug > Reporter: Burr Sutter > Attachments: StaffBean.java, StaffBean.java > > > The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1022) Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold

by Burr Sutter (JIRA)

Burr Sutter created FORGE-1022: ---------------------------------- Summary: Forge 1.0.5 Faces Scaffold vs 1.3.2 Faces Scaffold Key: FORGE-1022 URL: https://issues.jboss.org/browse/FORGE-1022 Project: Forge Issue Type: Bug Reporter: Burr Sutter The 1.3.2 scaffold generates code that is different from 1.0.5 and it produces an error message in JBDS - basically due to the bi-directional relationship between Staff & Store in the Sakila database -- 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, 8 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-803?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-803: ------------------------------------------ Actually I shouldn't say that - I can imagine the scenario where someone would want to create a test that packages up one or more addons that use shrink-wrap resolved libraries, it just won't be a very common scenario. > 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: Build Tools - Maven > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > > 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

12 years, 8 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-803?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III commented on FORGE-803: ------------------------------------------ However, even for that, we already have a competing resolution API that integrates well with the Forge Resources API, so... that's another reason why I'm not really sure this fits. Please feel free to argue against, these are just my opinions of the current situation. > 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: Build Tools - Maven > Affects Versions: 2.0.0.Alpha1 > Reporter: George Gastaldi > > 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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013