February 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-787) Forge update is not working correctly in Windows

by George Gastaldi (JIRA)

George Gastaldi created FORGE-787: ------------------------------------- Summary: Forge update is not working correctly in Windows Key: FORGE-787 URL: https://issues.jboss.org/browse/FORGE-787 Project: Forge Issue Type: Bug Affects Versions: 1.2.1.Final, 1.2.0.Final Environment: Windows 8 64bit, JDK 1.7.0_13 Reporter: George Gastaldi Fix For: 1.2.2.Final Running {code} forge update {code} in Forge 1.2.0.Final says that Forge is already up-to-date, instead of upgrading to 1.2.1.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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-786) Scaffolds shouldn't be so hard reliant on JPA Entities

by John Ament (JIRA)

John Ament created FORGE-786: -------------------------------- Summary: Scaffolds shouldn't be so hard reliant on JPA Entities Key: FORGE-786 URL: https://issues.jboss.org/browse/FORGE-786 Project: Forge Issue Type: Story Components: Builtin Plugins Affects Versions: 1.2.0.Final Reporter: John Ament Scaffolds are really nice, however they all need to work against JPA entities. What if you're not dealing with an entity, and instead have a data transformation layer that occurs first? HTML5/CSS3 type frameworks use rest and as a result the underlying object state may differ. Need to better support a scaffolding for non JPA entity classes. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-652) Remove jLine classes bundled inside Forge

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-652?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-652. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Alpha1 (was: 1.2.2.Final) Resolution: Out of Date JLine was replaced by Aesh in Forge 2 > Remove jLine classes bundled inside Forge > ----------------------------------------- > > Key: FORGE-652 > URL: https://issues.jboss.org/browse/FORGE-652 > Project: Forge > Issue Type: Enhancement > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > Forge should use the jline library instead of bundling the classes as a separate module (shell-impl). -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-553) Forge Console does not display special characters

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-553?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-553. --------------------------------- Fix Version/s: 2.0.0.Alpha1 (was: 1.2.2.Final) Resolution: Done In Forge 2, we changed the Shell implementation to aesh, that supports this feature. > Forge Console does not display special characters > ------------------------------------------------- > > Key: FORGE-553 > URL: https://issues.jboss.org/browse/FORGE-553 > Project: Forge > Issue Type: Bug > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: HackNight, annoying > Fix For: 2.0.0.Alpha1 > > > When you try typing accented characters, like áéíóú, they are erroneously displayed in Forge console. > There must be a way to set the encoding or leave as default -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-575) Upgrade Maven Integration APIs to 3.0.4

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-575?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-575. --------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Alpha1 (was: 1.2.2.Final) Resolution: Done > Upgrade Maven Integration APIs to 3.0.4 > --------------------------------------- > > Key: FORGE-575 > URL: https://issues.jboss.org/browse/FORGE-575 > Project: Forge > Issue Type: Library Upgrade > Reporter: George Gastaldi > Assignee: George Gastaldi > Priority: Minor > Labels: starter > Fix For: 2.0.0.Alpha1 > > -- 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

13 years, 2 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.2.Final (was: 1.2.1.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.2.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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (FORGE-93) AbstractResource.getFullyQualifiedName() returns wrong file path on Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-93?page=com.atlassian.jira.plugin.s... ] George Gastaldi updated FORGE-93: --------------------------------- Fix Version/s: 1.2.2.Final (was: 1.2.1.Final) > AbstractResource.getFullyQualifiedName() returns wrong file path on Windows > --------------------------------------------------------------------------- > > Key: FORGE-93 > URL: https://issues.jboss.org/browse/FORGE-93 > Project: Forge > Issue Type: Bug > Components: Resources API > Affects Versions: 1.0.6.Final > Reporter: Liu Jianhong > Assignee: Koen Aers > Priority: Minor > Fix For: 1.2.2.Final > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 1,cd to C:\Users > 2,Get path use AbstractResource.getFullyQualifiedName() and it returns /Users > 3,Execute "cd /Users" produces error of "[cd] no such resources:Users" > So,the following test failed: > org.junit.ComparisonFailure: expected:</Users[/Administrator]> but was:</Users[]> > at org.junit.Assert.assertEquals(Assert.java:123) > at org.junit.Assert.assertEquals(Assert.java:145) > at org.jboss.forge.shell.test.plugins.builtin.ChangeDirectoryPluginTest.testAbsolutePath(ChangeDirectoryPluginTest.java:137) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:251) > at org.jboss.arquillian.protocol.local.LocalMethodExecutor.invoke(LocalMethodExecutor.java:40) > at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:50) > at org.jboss.arquillian.impl.handler.ContainerTestExecuter.callback(ContainerTestExecuter.java:40) > at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63) > at org.jboss.arquillian.impl.context.AbstractEventContext.fire(AbstractEventContext.java:115) > at org.jboss.arquillian.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:157) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:244) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:207) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.jboss.arquillian.junit.Arquillian$5$1.evaluate(Arquillian.java:225) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:221) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:163) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:186) > at org.jboss.arquillian.junit.Arquillian$MultiStatementExecutor.execute(Arquillian.java:297) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:182) > at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:127) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) -- 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

13 years, 2 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.2.Final (was: 1.2.1.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.2.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

13 years, 2 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.2.Final (was: 1.2.1.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.2.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

13 years, 2 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.2.Final (was: 1.2.1.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.2.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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues February 2013