April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-699) create a plugin for WildcardImportResolver

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-699?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-699: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > create a plugin for WildcardImportResolver > ------------------------------------------ > > Key: FORGE-699 > URL: https://issues.jboss.org/browse/FORGE-699 > Project: Forge > Issue Type: Story > Components: Parsers / File Manipulation > Affects Versions: 1.1.1.Final > Reporter: fiorenzo pizza > Assignee: fiorenzo pizza > Fix For: 1.2.4.Final > > > general notes > We need to create some WildcardImportResolver (Responsible for providing additional import resolution functionality for situations where classes have referenced a package or wild-card import) > summary: > - when start creation of index --> new-project > - when update the index --> re-open project | add|remove plugins to the project | add|remove maven dependencies | add|remove new class inside forge project > - where save the index --> always > - how information to save for future search --> className, jarName (null if the class is in the project), packageName, absoluteClassName > - how search inside the index --> (ram hashmap? ram db?) > - how generate new entry for the index --> cdi event > general considerations > 1) when forge create a new-project we should create some structure to add all classes used referenced by project > 2) we need to add all classes required from some plugin (persistence|scaffolding..) > 2) we need to add all classes inside maven dependencies > 3) we need to add all classes created in the project > 4) we need remove all deleted classes > 5) we need to remove all classes inside dependecies removed > 6) we need to update the index files, when forge project is reopen (the user could modify the project out of forge) > problems > 1) with a lot of jars, the indexing process should be slow!! > 2) how synchronize the access to index > 3) how we should synchronize of index update? > requirements > 1) we need some fast library to extract classes from jar files > 2) we should use cdi event to start a single jar indexing > HOW CREATE INDEX FROM JAR: > possibile libraries: jandex, tattletale, jarindexer > FIRST CANDIDATE: JANDEX > i started to hack jandex code, because jandex is very fast. > Jandex opens the jar files using java jar utilities: JarFile jar = new JarFile(jarFile); > and for every class generate a ClassInfo object: ClassInfo info = indexer.index(jar.getInputStream(entry)); > For my test, i removed some methods inside jandex: we don't care about annotations inside classes. Also i removed the generation of file index. > questions: > 1) why don't use H2, the Java SQL database, for memorize all informations about classes? > How memorize for a single class: > 1) classname, jar name (with version), package name, complete name -- 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-715) Error while working with resources named as Java/FSH keywords

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-715?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-715: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > Error while working with resources named as Java/FSH keywords > ------------------------------------------------------------- > > Key: FORGE-715 > URL: https://issues.jboss.org/browse/FORGE-715 > Project: Forge > Issue Type: Bug > Components: Forge Scripting Language, UI - Shell > Affects Versions: 1.1.2.Final > Reporter: George Gastaldi > Labels: annoying > Fix For: 1.2.4.Final > > > Type the following: > {code} > cd for > {code} > The following error is thrown > {code} > ***ERROR*** Exception encountered: 6 (type "set VERBOSE true" to enable stack traces) > {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-693) Need an auto-update feature for plugins

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-693?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-693: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > Need an auto-update feature for plugins > --------------------------------------- > > Key: FORGE-693 > URL: https://issues.jboss.org/browse/FORGE-693 > Project: Forge > Issue Type: Feature Request > Reporter: George Gastaldi > Fix For: 1.2.4.Final > > > FORGE-217 auto-updates the core and the core plugins. There should be a way to update the current installed plugins. > Depending on the time taken to check, this could be done in the Forge startup. -- 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-757) Forge tests should delete the created folders

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-757?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-757: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > Forge tests should delete the created folders > --------------------------------------------- > > Key: FORGE-757 > URL: https://issues.jboss.org/browse/FORGE-757 > Project: Forge > Issue Type: Bug > Components: Test Harness > Affects Versions: 1.2.0.Final > Reporter: George Gastaldi > Fix For: 1.2.4.Final, 2.0.0.Alpha3 > > > After running tests, Forge isn't removing the created temp folders inside the /tmp folder. That leads to insufficient disk space after some time if these files are not deleted. -- 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-816) Field command should "pick-up" the newly created field to provide a better user experience with Constraint command

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-816?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-816: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > Field command should "pick-up" the newly created field to provide a better user experience with Constraint command > ------------------------------------------------------------------------------------------------------------------ > > Key: FORGE-816 > URL: https://issues.jboss.org/browse/FORGE-816 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: Lincoln Baxter III > Labels: starter > Fix For: 1.2.4.Final > > > {code} > entity --named Customer > field string --named firstName > constraint size --min 0 --max 25 > {code} > Currently, the user must CD into the field in order to add constraints, which is not the most natural interaction. > This will not break scripts because field is still a member of a JavaResource, so new-field should still be available (must verify.) -- 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-833) java new-field improvements

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-833?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-833: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > java new-field improvements > --------------------------- > > Key: FORGE-833 > URL: https://issues.jboss.org/browse/FORGE-833 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Labels: starter > Fix For: 1.2.4.Final > > > It should be possible to add getters and setters when a new field is created using the following command: > {code} > java new-field --named partType --type ~.model.PartType --accessType PRIVATE --asJavaBean > {code} > Where: > - named: The field name > - type: the field type > - accessModifier: The access modifier of this field: (PUBLIC,PRIVATE,PROTECTED,PACKAGE) > - asJavaBean: generate getters and setters -- 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-819) JPAProvider should be pluggable

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-819?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-819: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > JPAProvider should be pluggable > ------------------------------- > > Key: FORGE-819 > URL: https://issues.jboss.org/browse/FORGE-819 > Project: Forge > Issue Type: Enhancement > Components: Java EE APIs > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Fix For: 1.2.4.Final > > > JPAProvider should be pluggable, allowing plugins to provide a new container without changing the core. > The enum should be still be used though (deprecated perhaps), since some external plugins may still be using it. -- 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-821) Plugin to secure application

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-821?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-821: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > Plugin to secure application > ---------------------------- > > Key: FORGE-821 > URL: https://issues.jboss.org/browse/FORGE-821 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins > Affects Versions: 1.2.2.Final > Reporter: George Gastaldi > Labels: starter > Fix For: 1.2.4.Final > > > The plugin should primarily: > - Add a <security-constraint> entry to the web.xml file. > - Introduce a SecurityFacet for interoperability with other plugins > - The ScaffoldPlugin could create entries for the login and login-error pages if the SecurityFacet is enabled in the current project -- 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-847) Add an option to the DependencyResolver to resolve a single artifact (no version range)

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-847?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-847: ---------------------------------- Fix Version/s: 1.2.4.Final (was: 1.2.3.Final) > Add an option to the DependencyResolver to resolve a single artifact (no version range) > --------------------------------------------------------------------------------------- > > Key: FORGE-847 > URL: https://issues.jboss.org/browse/FORGE-847 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.2.2.Final > Reporter: James Perkins > Fix For: 1.2.4.Final > > > Currently {{org.jboss.forge.project.dependencies.DependencyResolver}} only has a option to return a list of dependencies. This results in version range query which requires the repository to have a {{maven-metadata.xml}} file. It would be useful to have something like: > {code:java} > public DependencyResource resolveArtifact(Dependency dependency) > {code} > This would allow for a specific version to be looked up. It also would have better performance when a dependency version is defined. > Currently using a repository that does not have metadata files does not work. For example http://maven.repository.redhat.com/earlyaccess/all/ cannot be used due to this issue. Which means no EAP dependencies cannot be downloaded from a Forge plugin. -- 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] (FORGEPLUGINS-110) Openshift Plugin timeouts when 'rhc setup' is run

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-110?page=com.atlassian.jira.... ] George Gastaldi closed FORGEPLUGINS-110. ---------------------------------------- Resolution: Done I was resolved by clearing out the ~/.ssh/known_hosts file > Openshift Plugin timeouts when 'rhc setup' is run > ------------------------------------------------- > > Key: FORGEPLUGINS-110 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-110 > Project: Forge Plugins > Issue Type: Bug > Components: OpenShift Plugin > Environment: RHEL 6.3, Eclipse Juno running Forge console with JBoss Forge 1.2.2.FInal with Openshift Forge Plugin 1.0.6.Final > Reporter: George Gastaldi > Assignee: William DeCoste > Priority: Blocker > > Whenever you try to setup an app in openshift using the Openshift Forge plugin, the following error is thrown: > {code} > [judcon] judcon $ rhc setup > ***INFO*** Loaded OpenShift configuration from /home/ggastald/.openshift/express.conf > ? Enter the application name [judcon] [judcon] > ***INFO*** Using RHLOGIN:xxx@xxx.com for https://openshift.redhat.com > ? Enter your Red Hat Openshift password: ********************************* > ***INFO*** Found OpenShift User: xxx(a)xxx.com > Choose a JBoss Cartridge: > 1 - [Cartridge [name=jbossews-2.0]]* > 2 - [Cartridge [name=jbossas-7]] > 3 - [Cartridge [name=jbosseap-6.0]] > 4 - [Cartridge [name=jbossews-1.0]] > ? Choose an option by typing the number of the selection [*-default] [0] 3 > ***INFO*** Using JBoss Cartridge: jbosseap-6.0 > java.lang.RuntimeException: com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/forge/applications, connection timed out > at com.redhat.openshift.forge.OpenShiftFacet.install(OpenShiftFacet.java:86) > at org.jboss.forge.project.BaseProject.performInstallation(BaseProject.java:240) > at org.jboss.forge.project.BaseProject.installFacet(BaseProject.java:166) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) > at org.jboss.weld.proxies.Project$-1946286523$Proxy$_$$_WeldClientProxy.installFacet(Project$-1946286523$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.shell.project.FacetInstallationHandler.performInstallation(FacetInstallationHandler.java:105) > at org.jboss.forge.shell.project.FacetInstallationHandler.install(FacetInstallationHandler.java:81) > at org.jboss.forge.shell.project.FacetInstallationHandler.installRequest(FacetInstallationHandler.java:59) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) > at com.redhat.openshift.forge.OpenShiftPlugin.setup(OpenShiftPlugin.java:98) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:141) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) > at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:789) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:812) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:602) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) > at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172) > at java.lang.Thread.run(Thread.java:722) > Caused by: com.openshift.client.OpenShiftTimeoutException: Could not request url https://openshift.redhat.com/broker/rest/domains/forge/applications, connection timed out > at com.openshift.internal.client.RestService.request(RestService.java:111) > at com.openshift.internal.client.RestService.request(RestService.java:91) > at com.openshift.internal.client.RestService.request(RestService.java:76) > at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:137) > at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:307) > at com.openshift.internal.client.DomainResource$CreateApplicationRequest.execute(DomainResource.java:292) > at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:132) > at com.openshift.internal.client.DomainResource.createApplication(DomainResource.java:108) > at com.redhat.openshift.forge.Util.createApplication(Util.java:282) > at com.redhat.openshift.forge.OpenShiftFacet.internalInstall(OpenShiftFacet.java:134) > at com.redhat.openshift.forge.OpenShiftFacet.install(OpenShiftFacet.java:81) > ... 66 more > {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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013