September 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-675) Testing under Weblogic 12c

by George Gastaldi (JIRA)

George Gastaldi created FORGE-675: ------------------------------------- Summary: Testing under Weblogic 12c Key: FORGE-675 URL: https://issues.jboss.org/browse/FORGE-675 Project: Forge Issue Type: Feature Request Components: Test Harness Affects Versions: 1.0.6.Final Reporter: George Gastaldi Fix For: 1.0.7.Final It could be a nice thing if the Forge tests could run also in Weblogic 12c, maybe in a different profile. -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] (FORGE-617) Cannot access Stateful EJB from inner anonymous class

by Luca Masini (JIRA)

Luca Masini created FORGE-617: --------------------------------- Summary: Cannot access Stateful EJB from inner anonymous class Key: FORGE-617 URL: https://issues.jboss.org/browse/FORGE-617 Project: Forge Issue Type: Bug Components: Java EE APIs Reporter: Luca Masini -- 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

11 years, 8 months

4
22
0 / 0

[JBoss JIRA] (FORGE-663) Enforce environment validations on Maven build

by George Gastaldi (JIRA)

George Gastaldi created FORGE-663: ------------------------------------- Summary: Enforce environment validations on Maven build Key: FORGE-663 URL: https://issues.jboss.org/browse/FORGE-663 Project: Forge Issue Type: Feature Request Components: Forge Build Reporter: George Gastaldi Fix For: 1.0.7.Final It sounds like the Forge build could use some validations to ensure the person building the project has an environment that matches the minimum requirements. Obviously, you want as few validations as possible (to make it more portable) but you can work to eliminate them once you know what they are. http://maven.apache.org/plugins/maven-enforcer-plugin/ Also, newer versions of Maven are suppose to be able to differentiate between origins of dependencies in the local repository, so we should probably be looking closer at the cases when we tell users to clean it out. -- 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

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by Ricardo Martinelli Oliveira (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] Work on FORGE-275 started by Ricardo Martinelli Oliveira. > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Assignee: Ricardo Martinelli Oliveira > Priority: Minor > Labels: Starter > Fix For: 1.0.7.Final > > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-275) delete associated methods when deleting a field

by Ricardo Martinelli Oliveira (JIRA)

[ https://issues.jboss.org/browse/FORGE-275?page=com.atlassian.jira.plugin.... ] Ricardo Martinelli Oliveira reassigned FORGE-275: ------------------------------------------------- Assignee: Ricardo Martinelli Oliveira > delete associated methods when deleting a field > ----------------------------------------------- > > Key: FORGE-275 > URL: https://issues.jboss.org/browse/FORGE-275 > Project: Forge > Issue Type: Feature Request > Components: Brainstorming, Builtin Plugins > Affects Versions: 1.0.0.Alpha2, 1.0.0.Alpha3 > Reporter: Rodney Russ > Assignee: Ricardo Martinelli Oliveira > Priority: Minor > Labels: Starter > Fix For: 1.0.7.Final > > Attachments: Forge-275.patch > > > When removing a field, it would make sense to remove the associated methods. For example: > cd Person.java > rm firstName > *delete associated methods setFirstName() and getFirstName() (Y/n)? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-416) cascade=CascadeType.ALL added to @OneToOne mapped fields on scaffold from-entity com.cpox.model.partner.*

by Gabor Nagy (Created) (JIRA)

cascade=CascadeType.ALL added to @OneToOne mapped fields on scaffold from-entity com.cpox.model.partner.* --------------------------------------------------------------------------------------------------------- Key: FORGE-416 URL: https://issues.jboss.org/browse/FORGE-416 Project: Forge Issue Type: Bug Components: Forge Build Affects Versions: 1.0.0.Beta5 Reporter: Gabor Nagy {code:title=Address.java} @Entity public class Address implements Serializable { private static final long serialVersionUID = 1L; @Id @GeneratedValue private Long id; @Version private Integer version; ... } {code} {code:title=Partner.java} @Entity public class Partner implements Serializable { private static final long serialVersionUID = 1L; ... private @OneToOne(cascade=CascadeType.ALL) Address address4; ... } {code} One cascade=CascadeType.ALL added after each scaffolding. {code:title=Partner.java} @Entity public class Partner implements Serializable { private static final long serialVersionUID = 1L; ... private @OneToOne(cascade=CascadeType.ALL, cascade=CascadeType.ALL) Address address4; ... } {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

11 years, 8 months

6
9
0 / 0

[JBoss JIRA] (FORGE-660) Entity plugin doesn't create a new entity when entity exists on a different package

by George Gastaldi (JIRA)

George Gastaldi created FORGE-660: ------------------------------------- Summary: Entity plugin doesn't create a new entity when entity exists on a different package Key: FORGE-660 URL: https://issues.jboss.org/browse/FORGE-660 Project: Forge Issue Type: Bug Reporter: George Gastaldi Having: {code:java} [exemplo] model $ ls City.java State.java ex01/ [exemplo] model $ entity --named City --package ~.model.ex01 {code} When you create another entity with the same name on a subpackage, the City entity in subpackage ex01 is exactly the same as the one in the model package. Tested on Forge console with JBoss Tools. -- 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

11 years, 8 months

2
4
0 / 0

[JBoss JIRA] (FORGE-217) Need an auto-update feature for plugins and core libraries

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-217?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-217: ---------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done > Need an auto-update feature for plugins and core libraries > ---------------------------------------------------------- > > Key: FORGE-217 > URL: https://issues.jboss.org/browse/FORGE-217 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha2 > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 1.0.7.Final > > > Ability to tell forge to auto-update and restart itself at runtime. Prevents downloading new distributions every release. Just tell it which version to "become" or "upgrade to". -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-279) Add ability to generate Entity Instance classes with Persistence plugin

by Jason Porter (JIRA)

Add ability to generate Entity Instance classes with Persistence plugin ----------------------------------------------------------------------- Key: SEAMFORGE-279 URL: https://issues.jboss.org/browse/SEAMFORGE-279 Project: Seam Forge Issue Type: Enhancement Affects Versions: 1.0.0.Beta1 Reporter: Jason Porter The idea of the Entity Instance is pretty much a bunch of boiler plate code necessary to allow a JPA entity to be used by CDI and exposed to EL. See https://github.com/seam/seam-example-confbuzz/blob/develop/src/main/java/... for the basic boiler plate code. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
2
0 / 0

[JBoss JIRA] (FORGE-169) Persistence plugin should optionally add maven configuration for a meta-model generator

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-169?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-169: --------------------------------------- Awesome ! Go for it ! :) > Persistence plugin should optionally add maven configuration for a meta-model generator > --------------------------------------------------------------------------------------- > > Key: FORGE-169 > URL: https://issues.jboss.org/browse/FORGE-169 > Project: Forge > Issue Type: Enhancement > Components: Java EE APIs > Affects Versions: 1.0.6.Final > Reporter: Paul Bakker > Assignee: Ken Finnigan > Fix For: 1.0.7.Final > > > If JPA 2.0 is used, and the provider supports a meta-model generator it should be added to the pom file. -- 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, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues September 2012