August 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-220) Forge should listen to filesystem changes on the system and publish events for plugins to observe

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-220: --------------------------------------- The JDK 7.0 WatchService class (http://docs.oracle.com/javase/tutorial/essential/io/notification.html) could help. Maybe we can activate this feature only when Forge is running under JDK 7+ ? > Forge should listen to filesystem changes on the system and publish events for plugins to observe > -------------------------------------------------------------------------------------------------- > > Key: FORGE-220 > URL: https://issues.jboss.org/browse/FORGE-220 > Project: Forge > Issue Type: Feature Request > Components: JBoss Tools Integration, Plugin API, Resources API > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > {code}Event<ResourceCreated> > Event<ResourceModified> > Event<ResourceDeleted>{code} > etc... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-220) Forge should listen to filesystem changes on the system and publish events for plugins to observe

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-220?page=com.atlassian.jira.plugin.... ] George Gastaldi commented on FORGE-220: --------------------------------------- Wasn't this already done ? > Forge should listen to filesystem changes on the system and publish events for plugins to observe > -------------------------------------------------------------------------------------------------- > > Key: FORGE-220 > URL: https://issues.jboss.org/browse/FORGE-220 > Project: Forge > Issue Type: Feature Request > Components: JBoss Tools Integration, Plugin API, Resources API > Affects Versions: 1.0.0.Alpha3 > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha1 > > > {code}Event<ResourceCreated> > Event<ResourceModified> > Event<ResourceDeleted>{code} > etc... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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: (was: 1.0.0.Alpha4) Git Pull Request: https://github.com/forge/core/pull/22 (was: https://github.com/forge/core/pull/22) > 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.0.7.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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-561) Forge generating only five fields for search.xhtml?

by easy koala (JIRA)

easy koala created FORGE-561: -------------------------------- Summary: Forge generating only five fields for search.xhtml? Key: FORGE-561 URL: https://issues.jboss.org/browse/FORGE-561 Project: Forge Issue Type: Enhancement Reporter: easy koala -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
4
0 / 0

[JBoss JIRA] (FORGE-619) bad support of field with the following naming pattern aFIELD

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-619?page=com.atlassian.jira.plugin.... ] George Gastaldi closed FORGE-619. --------------------------------- > bad support of field with the following naming pattern aFIELD > ------------------------------------------------------------- > > Key: FORGE-619 > URL: https://issues.jboss.org/browse/FORGE-619 > Project: Forge > Issue Type: Bug > Reporter: Anthony Patricio > Assignee: Richard Kennard > > Step to reproduce the issue, create an entity from forge with a field named aFIELD > Check the get/set generated method, > As per the javabean naming convention, we should have getaFIELD,setaFIELD but we have getAFIELD setAFIELD. > When generated by eclipse then scaffolding, problem can appear, more important if the id is following the same naming pattern. > Richard fixed almost everything related to meta widget. > However the ForgePropertyStyle still needs some polishing. > Check the forum reference. > Cheers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-568) Allow running / debugging from projects in Eclipse

by George Gastaldi (JIRA)

George Gastaldi created FORGE-568: ------------------------------------- Summary: Allow running / debugging from projects in Eclipse Key: FORGE-568 URL: https://issues.jboss.org/browse/FORGE-568 Project: Forge Issue Type: Enhancement Components: JBoss Tools Integration Reporter: George Gastaldi Assignee: Koen Aers It would be nice to just run the version you are developing in debug mode inside Forge Console (Eclipse) and immediately see what's going on. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (FORGE-623) license change plugin

by Jose Donizetti Brito Junior (JIRA)

Jose Donizetti Brito Junior created FORGE-623: ------------------------------------------------- Summary: license change plugin Key: FORGE-623 URL: https://issues.jboss.org/browse/FORGE-623 Project: Forge Issue Type: Feature Request Reporter: Jose Donizetti Brito Junior follow Lincoln's license change how on the forge-dev list. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (FORGE-622) sed plugin based on uinx sed.

by Jose Donizetti Brito Junior (JIRA)

Jose Donizetti Brito Junior created FORGE-622: ------------------------------------------------- Summary: sed plugin based on uinx sed. Key: FORGE-622 URL: https://issues.jboss.org/browse/FORGE-622 Project: Forge Issue Type: Feature Request Components: Builtin Plugins Reporter: Jose Donizetti Brito Junior -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (FORGE-613) Create a XML Schema for forge.xml

by George Gastaldi (JIRA)

George Gastaldi created FORGE-613: ------------------------------------- Summary: Create a XML Schema for forge.xml Key: FORGE-613 URL: https://issues.jboss.org/browse/FORGE-613 Project: Forge Issue Type: Enhancement Reporter: George Gastaldi Actually it's difficult to understand which options are valid on forge.xml file. Having a XML Schema would help. Plugins with specific properties could specify its own XML Schema as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] (FORGE-598) CommandCompleter should permit the highlight of some candidate items (for use then as recommended candidate)

by Rafael Benevides (JIRA)

13 years, 8 months

3
4
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues August 2012