December 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-722) JavaParser should support parsing and creating annotations on annotations.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-722?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-722. --------------------------------- Resolution: Cannot Reproduce Bug Already works by using for example: {code} JavaParser.parse(JavaAnnotation.class, "public @interface Test{}").addAnnotation(Deprecated.class); {code} > JavaParser should support parsing and creating annotations on annotations. > -------------------------------------------------------------------------- > > Key: FORGE-722 > URL: https://issues.jboss.org/browse/FORGE-722 > Project: Forge > Issue Type: Enhancement > Components: Parsers / File Manipulation > Affects Versions: 1.1.3.Final > Reporter: Lincoln Baxter III > Fix For: 1.1.4.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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-722) JavaParser should support parsing and creating annotations on annotations.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-722: ---------------------------------------- Summary: JavaParser should support parsing and creating annotations on annotations. Key: FORGE-722 URL: https://issues.jboss.org/browse/FORGE-722 Project: Forge Issue Type: Enhancement Components: Parsers / File Manipulation Affects Versions: 1.1.3.Final Reporter: Lincoln Baxter III Fix For: 1.1.4.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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-563) Create a class lookup index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-563?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-563: --------------------------------------- A nice library which may be useful: http://code.google.com/p/reflections/ > Create a class lookup index > --------------------------- > > Key: FORGE-563 > URL: https://issues.jboss.org/browse/FORGE-563 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.0.4.Final > Reporter: Jason Porter > Fix For: 2.0.0.Alpha1 > > > We need to support an index of classes and dependencies which contain them. > This would allow us to do wildcard expansion, and also allow facets to depend on a class, not a specific dependency. I believe Lincoln has the information about wildcard support, for the facet dependency idea my thoughts are an index like this would allow a facet to declare a class, or collection of classes, which it requires to function. For example the faces facet could depend on FacesContext, or PhaseListener or some other class. When a facet checks to see if a project has the dependencies it could match multiple jars instead one specific jar. Again in the faces example it could match Mojarra, MyFaces, JBoss spec jars, Geromino spec jars, etc. > We could keep a local cache and add to it, we could also have an online cache available which users could push to and also merge into their local cache. -- 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, 4 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: ---------------------------------- Labels: Starter (was: ) > 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.1.4.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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGE-720) Ability to install / uninstall addons from command line

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-720?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-720. --------------------------------- > Ability to install / uninstall addons from command line > ------------------------------------------------------- > > Key: FORGE-720 > URL: https://issues.jboss.org/browse/FORGE-720 > Project: Forge > Issue Type: Feature Request > Components: Usability > Reporter: Lincoln Baxter III > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha1 > > > {code}forge --install org.jboss.forge:example,2.0.0-SNAPSHOT{code} > the forge shell script itself should be able to kick off an installation of an addon > 1:18 > gastaldi > hum > 1:18 > lincolnthree > forge --install org.example:plugin,2.0.0-SNAPSHOT —repository=~/.forge/custom_addons_dir > 1:18 > kenfinnigan > so would that start forge, install an addon, and forge be ready with that addon? > 1:18 > lincolnthree > it would then shut down > but the addon would be installed > 1:18 > kenfinnigan > ah ok > 1:18 > lincolnthree > so basically like forge -e > but just for installing addons > removal should also be possible > and listing what's there > should be easy to do! > 1:19 > relatively -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-84) Create a VRaptor plugin

by Rubens Saraiva (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-84?page=com.atlassian.jira.p... ] Rubens Saraiva reassigned FORGEPLUGINS-84: ------------------------------------------ Assignee: Rubens Saraiva > Create a VRaptor plugin > ----------------------- > > Key: FORGEPLUGINS-84 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-84 > Project: Forge Plugins > Issue Type: Feature Request > Reporter: George Gastaldi > Assignee: Rubens Saraiva > > It would be interesting to create a scaffold and a specific plugin for dealing with the VRaptor framework (http://vraptor.caelum.com.br/) -- 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, 4 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.1.4.Final (was: 1.1.3.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 > Assignee: Lincoln Baxter III > Priority: Minor > Fix For: 1.1.4.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, 4 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.1.4.Final (was: 1.1.3.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.1.4.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, 4 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.4.Final (was: 1.1.3.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.4.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, 4 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.4.Final (was: 1.1.3.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.4.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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues December 2012