January 2013 - forge-issues - Jboss List Archives

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-93?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-93: ------------------------------------ Fix Version/s: 1.2.1.Final (was: 1.2.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.2.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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-44) Usage: dark blue on black background?

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-44?page=com.atlassian.jira.plugin.s... ] Lincoln Baxter III updated FORGE-44: ------------------------------------ Fix Version/s: 1.2.1.Final (was: 1.2.0.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.1.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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-163) Add ability to generate Entity Query classes with Persistence plugin (using Named Queries)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-163?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-163: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.0.Final) > Add ability to generate Entity Query classes with Persistence plugin (using Named Queries) > ------------------------------------------------------------------------------------------ > > Key: FORGE-163 > URL: https://issues.jboss.org/browse/FORGE-163 > Project: Forge > Issue Type: Feature Request > Components: Builtin Plugins, Java EE APIs > Affects Versions: 1.0.0.Beta1 > Reporter: Jason Porter > Priority: Minor > Fix For: 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-167) Add support for ProfileBuilder in MavenCoreFacet (or create MavenProfileFacet)

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-167?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-167: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.0.Final) > Add support for ProfileBuilder in MavenCoreFacet (or create MavenProfileFacet) > ------------------------------------------------------------------------------ > > Key: FORGE-167 > URL: https://issues.jboss.org/browse/FORGE-167 > Project: Forge > Issue Type: Enhancement > Components: Maven Integration > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Assignee: Paul Bakker > Priority: Minor > Labels: Starter > Fix For: 1.2.1.Final > > > {code} MavenPluginFacet mavenPluginFacet = getProject().getFacet(MavenPluginFacet.class); > int nrOfPlugins = getNumberOfPlugins(); > MavenPluginBuilder plugin = MavenPluginBuilder.create() > .setDependency( > DependencyBuilder.create() > .setGroupId("org.apache.maven.plugins") > .setArtifactId("maven-site-plugin") > .setVersion("3.0") > ); > MavenPluginAdapter mvnPlugin = new MavenPluginAdapter(plugin); > MavenCoreFacet facet = project.getFacet(MavenCoreFacet.class); > Profile profile = new Profile(); > profile.setId(profileId); > profile.getBuild().addPlugin(theplugin); > > Model pom = facet.getPOM(); > pom.addProfile(profile); > > facet.setPOM(pom); > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-177) Improve error handling in setBody method of MethodImpl

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-177?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-177: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.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.2.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

13 years, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-179?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-179: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.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.2.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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-160) Have scaffolding put labels etc in i18n property files

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-160?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-160: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.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.2.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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-233) Allow user to specify a custom Eclipse formatting profile

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-233?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-233: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.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.2.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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-360) FacesPlugin should automatically add the faces mapping if the servlet version < 3

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-360?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-360: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.0.Final) > FacesPlugin should automatically add the faces mapping if the servlet version < 3 > --------------------------------------------------------------------------------- > > Key: FORGE-360 > URL: https://issues.jboss.org/browse/FORGE-360 > Project: Forge > Issue Type: Enhancement > Components: Builtin Plugins > Affects Versions: 1.0.0.Beta3 > Reporter: Brian Leathem > Labels: HackNight, Starter > Fix For: 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, 3 months

1
0
0 / 0

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

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-340?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III updated FORGE-340: ------------------------------------- Fix Version/s: 1.2.1.Final (was: 1.2.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.2.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

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues January 2013