March 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-163) Add ability to generate Entity Query classes with Persistence plugin (using Named Queries)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-163?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-163: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Add ability to generate Entity Query classes with Persistence plugin (using Named Queries) > ------------------------------------------------------------------------------------------ > > Key: FORGE-163 > URL: https://issues.jboss.org/browse/FORGE-163 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Beta1 > Reporter: Jason Porter > Priority: Minor > Fix For: 1.2.3.Final > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-127) Change Strings to take CharacterSequence in classes building java source files

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-127?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-127: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Change Strings to take CharacterSequence in classes building java source files > ------------------------------------------------------------------------------ > > Key: FORGE-127 > URL: https://issues.jboss.org/browse/FORGE-127 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.0.0.Alpha4 > Reporter: Jason Porter > Priority: Minor > Fix For: 1.2.3.Final > > > I'm using org.jboss.forge.parser.java.Method right now and noticing everything takes a string. A nice enhancement would be to accept CharacterSequence (http://download.oracle.com/javase/6/docs/api/java/lang/CharSequence.html) instead of String. This has the added bonus of being able to pass a StringBuilder without having to call toString() on it. Other CharacterSequences may also find ease of use with this change. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-133) Entity command should provide an option for using a Mapped Superclass

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-133?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-133: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Entity command should provide an option for using a Mapped Superclass > --------------------------------------------------------------------- > > Key: FORGE-133 > URL: https://issues.jboss.org/browse/FORGE-133 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Priority: Optional > Labels: Starter > Fix For: 1.2.3.Final > > > Instead of putting version and ID in the entity itself, the entity command should allow for using a Mapped superclass (hopefully trying to check for version and id in the process, so that those fields may be omitted from the entity itself.) > {code} > /* > * Copyright 2010 - Lincoln Baxter, III (lincoln(a)ocpsoft.com) - Licensed under the Apache License, > * Version 2.0 (the "License"); you may not use this file except in compliance > * with the License. You may obtain a copy of the License at > * http://www.apache.org/licenses/LICENSE-2.0 - Unless required by applicable > * law or agreed to in writing, software distributed under the License is > * distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY > * KIND, either express or implied. See the License for the specific language > * governing permissions and limitations under the License. > */ > import java.io.Serializable; > import java.util.Date; > import javax.persistence.Column; > import javax.persistence.GeneratedValue; > import javax.persistence.GenerationType; > import javax.persistence.Id; > import javax.persistence.MappedSuperclass; > import javax.persistence.PersistenceException; > import javax.persistence.PrePersist; > import javax.persistence.PreUpdate; > import javax.persistence.Temporal; > import javax.persistence.TemporalType; > import javax.persistence.Version; > @MappedSuperclass > public abstract class PersistentObject<E extends PersistentObject<?>> implements Serializable > { > private static final long serialVersionUID = -1272280183658745494L; > @Id > @GeneratedValue(strategy = GenerationType.AUTO) > @Column(name = "id", updatable = false, nullable = false) > private Long id = null; > @Version > @Column(name = "version") > private int version = 0; > @Temporal(TemporalType.TIMESTAMP) > @Column(name = "lastUpdate") > private Date lastUpdate; > @Temporal(TemporalType.TIMESTAMP) > @Column(name = "createdOn", updatable = false, nullable = false) > private Date createdOn; > @PrePersist > void prePersistSetCreationTimestamp() > { > createdOn = new Date(); > } > @PreUpdate > void preUpdateSetLastUpdatedTimestamp() > { > lastUpdate = new Date(); > } > protected static boolean getBooleanValue(final Boolean value) > { > return Boolean.valueOf(String.valueOf(value)); > } > public Long getId() > { > return id; > } > public boolean isPersistent() > { > return getId() != null; > } > @SuppressWarnings("unchecked") > public E setId(final Long id) > { > if (this.id != null) > { > throw new PersistenceException("Cannot alter immutable ID of persistent object with id: " + id); > } > this.id = id; > return (E) this; > } > public int getVersion() > { > return version; > } > @SuppressWarnings("unused") > private void setVersion(final int version) > { > this.version = version; > } > public Date getLastUpdate() > { > return lastUpdate; > } > @SuppressWarnings("unchecked") > public E setLastUpdate(final Date lastUpdate) > { > this.lastUpdate = lastUpdate; > return (E) this; > } > public Date getCreatedOn() > { > return createdOn; > } > @SuppressWarnings("unchecked") > public E setCreatedOn(final Date createdOn) > { > this.createdOn = createdOn; > return (E) this; > } > } > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-160) Have scaffolding put labels etc in i18n property files

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-160?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-160: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Have scaffolding put labels etc in i18n property files > ------------------------------------------------------ > > Key: FORGE-160 > URL: https://issues.jboss.org/browse/FORGE-160 > Project: Forge > Issue Type: Enhancement > Components: Scaffold > Affects Versions: 1.0.0.Alpha4 > Reporter: Ronald van Kuijk > Priority: Optional > Labels: scaffold > Fix For: 1.2.3.Final > > > To support easy i18n, the labels for e.g. colums or input fields should be put in files. > Decide on: > - label conventions > - use of jsf i18n or seam i18n > - ... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-35) add-constraint is missing NotEmpty

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-35?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-35: --------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > add-constraint is missing NotEmpty > ---------------------------------- > > Key: FORGE-35 > URL: https://issues.jboss.org/browse/FORGE-35 > Project: Forge > Issue Type: Bug > Components: Builtin Plugins > Affects Versions: 1.0.6.Final > Reporter: Pete Muir > Assignee: Kevin Pollet > Labels: Starter > Fix For: 1.2.3.Final > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-125) Field/Entity plugins should warn when using potential SQL tokens an entity names or field names

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-125?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-125: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Field/Entity plugins should warn when using potential SQL tokens an entity names or field names > ----------------------------------------------------------------------------------------------- > > Key: FORGE-125 > URL: https://issues.jboss.org/browse/FORGE-125 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Fix For: 1.2.3.Final > > > It's currently possible to easily create an entity or field that will break JPA because of usage of SQL reserved words. > E.g: "order" or "limit" -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-44) Usage: dark blue on black background?

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-44?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-44: --------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Usage: dark blue on black background? > ------------------------------------- > > Key: FORGE-44 > URL: https://issues.jboss.org/browse/FORGE-44 > Project: Forge > Issue Type: Bug > Components: Shell, Windows > Affects Versions: 1.0.0.Beta2 > Environment: Windows 7 > Reporter: Martin Dames > Priority: Minor > Labels: background, black, blue, cmd,, color,, dark,, shell,, windows, > Fix For: 1.2.3.Final > > > Hi, > im trying Seam Forge 1.0.0Beta2 on my windows machine and it really makes no fun. I can rarely see the "holding" text and its driving me crazy... I tried to change the cmd shell background and text colors.. but besides this is not a task a normal user should do... this does not work. > So, please change your colors a little bit more eye friendly! :) > I would add a screenshot if I could.... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-177) Improve error handling in setBody method of MethodImpl

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-177?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-177: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Improve error handling in setBody method of MethodImpl > ------------------------------------------------------ > > Key: FORGE-177 > URL: https://issues.jboss.org/browse/FORGE-177 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.6.Final > Reporter: Paul Bakker > Priority: Minor > Fix For: 1.2.3.Final > > > When this method is called with a String, but the String doesn't parse correctly, the method fails silently. Instead of a ParseException or something like that it just returns an empty body. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-233) Allow user to specify a custom Eclipse formatting profile

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-233?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-233: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Allow user to specify a custom Eclipse formatting profile > --------------------------------------------------------- > > Key: FORGE-233 > URL: https://issues.jboss.org/browse/FORGE-233 > Project: Forge > Issue Type: Feature Request > Components: Parsers / File Manipulation > Affects Versions: 1.0.0.Alpha3 > Reporter: Dan Allen > Labels: Starter > Fix For: 1.2.3.Final > > > Allow the user to specify an Eclipse formatting profile in the local configuration (~/.forge). When creating (or updating) Java files, use the Eclipse formatter (or alternative) to format the code using the formatting 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, 9 months

1
0
0 / 0

[JBoss JIRA] (FORGE-385) Current directory is poor default for new-project location when existing project is detected

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-385?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-385: ---------------------------------- Fix Version/s: 1.2.3.Final (was: 1.2.2.Final) > Current directory is poor default for new-project location when existing project is detected > -------------------------------------------------------------------------------------------- > > Key: FORGE-385 > URL: https://issues.jboss.org/browse/FORGE-385 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Beta3 > Reporter: Dan Allen > Priority: Minor > Labels: Starter > Fix For: 1.2.3.Final > > > When creating a new project using the new-project command, forge will offer the current directory as the target location if a project with the same name is found. > {code} > $ new-project --named example --topLevelPackage org.example > ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. > Where would you like to create the project? [Press ENTER to use the current directory: dallen] > {code} > This default is a recipe for disaster. If there is a project in the way, then using the current directory puts that project *in* the project being created. Additionally, if the current directory is $HOME, then the project will get overlaid in a directory which has many other files and directories. > A better default is to append a number to the end of the project name. For example: > {code} > $ new-project --named example --topLevelPackage org.example > ***ERROR*** [/home/dallen/example] already contains a project; please use a different folder. > Where would you like to create the project? [Press ENTER to use an alternative directory: example2] > {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, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues March 2013