September 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-680) CDI events for plugin installation / removal

by George Gastaldi (JIRA)

George Gastaldi created FORGE-680: ------------------------------------- Summary: CDI events for plugin installation / removal Key: FORGE-680 URL: https://issues.jboss.org/browse/FORGE-680 Project: Forge Issue Type: Feature Request Components: Plugin API Reporter: George Gastaldi Fix For: 1.1.0.Final Forge should fire events when plugins are installed / removed -- 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
3
0 / 0

[JBoss JIRA] (FORGE-150) Implementations of JavaParser Interfaces should maintain equality with other implementations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-150?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-150: ---------------------------------- Fix Version/s: 1.1.1.Final (was: 1.1.0.Final) > Implementations of JavaParser Interfaces should maintain equality with other implementations > -------------------------------------------------------------------------------------------- > > Key: FORGE-150 > URL: https://issues.jboss.org/browse/FORGE-150 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.0.Alpha4 > Reporter: Jason Porter > Fix For: 1.1.1.Final > > > Until I saw how to create an Import (which I still don't agree with having to be tied to the Implementation) I thought about creating my own implementation for a test (a mock would be even better) so I looked at the equals for the ImportImpl and it does not keep equality with other implementations because it checks to see if the class is the same. It also checks internal state instead of using the interface methods. -- 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-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.1.1.Final (was: 1.1.0.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.1.1.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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-179) The 'open' and 'edit' commands should be configurable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-179?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-179: ---------------------------------- Fix Version/s: 1.1.1.Final (was: 1.1.0.Final) > The 'open' and 'edit' commands should be configurable > ----------------------------------------------------- > > Key: FORGE-179 > URL: https://issues.jboss.org/browse/FORGE-179 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Labels: Starter > Fix For: 1.1.1.Final > > > 'open' and 'edit' currently use the default system application, but if hooks were provided into this system, they could instead be used to open files using a user-specified application, or even trigger editors to open in JBoss Tools. > Koen, I am asigning this to you because I want your feedback here. If running forge in eclipse, these commands should probably be a no-op, and your eclipse system will simply intercept the output and open/edit the desired file, yes? -- 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-119) org.jboss.forge.parser.java.Parameter should support examining annotations

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-119?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-119: ---------------------------------- Fix Version/s: 1.1.1.Final (was: 1.1.0.Final) > org.jboss.forge.parser.java.Parameter should support examining annotations > -------------------------------------------------------------------------- > > Key: FORGE-119 > URL: https://issues.jboss.org/browse/FORGE-119 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.0.6.Final > Reporter: Jason Porter > Fix For: 1.1.1.Final > > > There is no way to get annotations on a parameter currently without parsing the string. This should be available as an API in the JavaParser > {code}parameter.getAnnotations(){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, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-340) Change default plugin checkout location to use the .forge/plugins-sources directory

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-340: ---------------------------------- Fix Version/s: 1.1.1.Final (was: 1.1.0.Final) > Change default plugin checkout location to use the .forge/plugins-sources directory > ----------------------------------------------------------------------------------- > > Key: FORGE-340 > URL: https://issues.jboss.org/browse/FORGE-340 > Project: Forge > Issue Type: Task > Components: Shell > Affects Versions: 1.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Rodney Russ > Priority: Minor > Labels: Starter > Fix For: 1.1.1.Final > > > {code}$ forge git-plugin git@github.com:repo/etc{code} > needs to use ~/.forge/plugins-sources/ instead of the /tmp directory - so that developers can hack on installed plugins more easily. > this code lives here: > https://github.com/forge/core/blob/master/shell/src/main/java/org/jboss/f... -- 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-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.1.1.Final (was: 1.1.0.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.1.1.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, 8 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.1.1.Final (was: 1.1.0.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.1.1.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, 8 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.1.1.Final (was: 1.1.0.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 > Fix For: 1.1.1.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, 8 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.1.1.Final (was: 1.1.0.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.1.1.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

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