July 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1014) Web Root directory is hard-coded to src/main/webapp

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1014?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1014. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 1.3.4.Final 2.0.0.Alpha7 Resolution: Done Fixed > Web Root directory is hard-coded to src/main/webapp > --------------------------------------------------- > > Key: FORGE-1014 > URL: https://issues.jboss.org/browse/FORGE-1014 > Project: Forge > Issue Type: Bug > Components: Maven Plugin > Affects Versions: 1.3.3.Final > Reporter: Fred Bricon > Assignee: George Gastaldi > Fix For: 1.3.4.Final, 2.0.0.Alpha7 > > > Similar to FORGE-103, the web root directory is hard coded to src/main/webapp in https://github.com/forge/core/blob/c178b19bbae655b04648be21e2a368a5e57cf7... > An eclipse project converted to maven uses WebContent as <warSourceDirectory> : > {noformat} > <plugin> > <artifactId>maven-war-plugin</artifactId> > <version>2.4</version> > <configuration> > <warSourceDirectory>WebContent</warSourceDirectory> > <failOnMissingWebXml>false</failOnMissingWebXml> > </configuration> > </plugin> > {noformat} > Scaffolding UI from entities generates resources under src/main/webapp. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1015) Java source/target versions should be configurable in MavenJavaSourceFacet

by Fred Bricon (JIRA)

Fred Bricon created FORGE-1015: ---------------------------------- Summary: Java source/target versions should be configurable in MavenJavaSourceFacet Key: FORGE-1015 URL: https://issues.jboss.org/browse/FORGE-1015 Project: Forge Issue Type: Bug Components: Maven Plugin Affects Versions: 1.3.3.Final Reporter: Fred Bricon I see https://github.com/forge/core/blob/master/project-model-maven/src/main/ja... has hardcoded source/target versions for the maven-compiler-plugin configuration IMHO, these (along the encoding) should be overrideable via CLI options. Also, the default version should be inferred from the currently running JVM. One caveat though, is that would make forge build tests dependent on the running JVM. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1015) Java source/target versions should be configurable in MavenJavaSourceFacet

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/FORGE-1015?page=com.atlassian.jira.plugin... ] Fred Bricon updated FORGE-1015: ------------------------------- Issue Type: Enhancement (was: Bug) > Java source/target versions should be configurable in MavenJavaSourceFacet > -------------------------------------------------------------------------- > > Key: FORGE-1015 > URL: https://issues.jboss.org/browse/FORGE-1015 > Project: Forge > Issue Type: Enhancement > Components: Maven Plugin > Affects Versions: 1.3.3.Final > Reporter: Fred Bricon > > I see https://github.com/forge/core/blob/master/project-model-maven/src/main/ja... has hardcoded source/target versions for the maven-compiler-plugin configuration > IMHO, these (along the encoding) should be overrideable via CLI options. Also, the default version should be inferred from the currently running JVM. One caveat though, is that would make forge build tests dependent on the running JVM. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1013) Java resource path is hard-coded to src/main/resources

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1013?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1013. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 1.3.4.Final 2.0.0.Alpha7 Resolution: Done Fixed > Java resource path is hard-coded to src/main/resources > ------------------------------------------------------ > > Key: FORGE-1013 > URL: https://issues.jboss.org/browse/FORGE-1013 > Project: Forge > Issue Type: Bug > Components: Maven Plugin > Affects Versions: 1.3.3.Final > Reporter: Fred Bricon > Assignee: George Gastaldi > Fix For: 1.3.4.Final, 2.0.0.Alpha7 > > > After converting a stock Eclipse project (having just an src/ source folder) to Maven (Configure...>Convert to Maven), the java and resource directories are set to src. > When configuring persistence via forge, a new persistence.xml is generated under src/main/resources. Turns out MavenResourceFacet has hard-coded paths for main and test resources : https://github.com/forge/core/blob/c178b19bbae655b04648be21e2a368a5e57cf7... > The resource paths should be inferred from the Maven pom instead, (<resources> and <testResources> nodes) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1013) Java resource path is hard-coded to src/main/resources

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/FORGE-1013?page=com.atlassian.jira.plugin... ] Fred Bricon updated FORGE-1013: ------------------------------- Component/s: Maven Plugin (was: Resources API) > Java resource path is hard-coded to src/main/resources > ------------------------------------------------------ > > Key: FORGE-1013 > URL: https://issues.jboss.org/browse/FORGE-1013 > Project: Forge > Issue Type: Bug > Components: Maven Plugin > Affects Versions: 1.3.3.Final > Reporter: Fred Bricon > > After converting a stock Eclipse project (having just an src/ source folder) to Maven (Configure...>Convert to Maven), the java and resource directories are set to src. > When configuring persistence via forge, a new persistence.xml is generated under src/main/resources. Turns out MavenResourceFacet has hard-coded paths for main and test resources : https://github.com/forge/core/blob/c178b19bbae655b04648be21e2a368a5e57cf7... > The resource paths should be inferred from the Maven pom instead, (<resources> and <testResources> nodes) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1014) Web Root directory is hard-coded to src/main/webapp

by Fred Bricon (JIRA)

Fred Bricon created FORGE-1014: ---------------------------------- Summary: Web Root directory is hard-coded to src/main/webapp Key: FORGE-1014 URL: https://issues.jboss.org/browse/FORGE-1014 Project: Forge Issue Type: Bug Components: Maven Plugin Affects Versions: 1.3.3.Final Reporter: Fred Bricon Similar to FORGE-103, the web root directory is hard coded to src/main/webapp in https://github.com/forge/core/blob/c178b19bbae655b04648be21e2a368a5e57cf7... An eclipse project converted to maven uses WebContent as <warSourceDirectory> : {noformat} <plugin> <artifactId>maven-war-plugin</artifactId> <version>2.4</version> <configuration> <warSourceDirectory>WebContent</warSourceDirectory> <failOnMissingWebXml>false</failOnMissingWebXml> </configuration> </plugin> {noformat} Scaffolding UI from entities generates resources under src/main/webapp. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1013) Java resource path is hard-coded to src/main/resources

by Fred Bricon (JIRA)

Fred Bricon created FORGE-1013: ---------------------------------- Summary: Java resource path is hard-coded to src/main/resources Key: FORGE-1013 URL: https://issues.jboss.org/browse/FORGE-1013 Project: Forge Issue Type: Bug Components: Resources API Affects Versions: 1.3.3.Final Reporter: Fred Bricon After converting a stock Eclipse project (having just an src/ source folder) to Maven (Configure...>Convert to Maven), the java and resource directories are set to src. When configuring persistence via forge, a new persistence.xml is generated under src/main/resources. Turns out MavenResourceFacet has hard-coded paths for main and test resources : https://github.com/forge/core/blob/c178b19bbae655b04648be21e2a368a5e57cf7... The resource paths should be inferred from the Maven pom instead, (<resources> and <testResources> nodes) -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-554?page=com.atlassian.jira.plugin.... ] Vineet Reynolds updated FORGE-554: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/forge/core/pull/332 The fix was to ensure that PathspecParser computed the options relative to the supplied path instead of the drive root. > Tab AutoCompletion in forge ignores already typed options > --------------------------------------------------------- > > Key: FORGE-554 > URL: https://issues.jboss.org/browse/FORGE-554 > Project: Forge > Issue Type: Bug > Components: UI - Shell, Usability, Windows > Environment: Windows 7 64bits > Reporter: George Gastaldi > Fix For: 1.x Future > > > Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-554) Tab AutoCompletion in forge ignores already typed options

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-554?page=com.atlassian.jira.plugin.... ] Vineet Reynolds reassigned FORGE-554: ------------------------------------- Assignee: Vineet Reynolds > Tab AutoCompletion in forge ignores already typed options > --------------------------------------------------------- > > Key: FORGE-554 > URL: https://issues.jboss.org/browse/FORGE-554 > Project: Forge > Issue Type: Bug > Components: UI - Shell, Usability, Windows > Environment: Windows 7 64bits > Reporter: George Gastaldi > Assignee: Vineet Reynolds > Fix For: 1.x Future > > > Inside a project, when you "cd" and press <TAB> to navigate between nested folders, the prompt resets to "cd" only, losing the folders previously selected when typing. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (FORGE-85) Shell cannot parse command values containing '!' exclaimation points

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-85?page=com.atlassian.jira.plugin.s... ] Vineet Reynolds edited comment on FORGE-85 at 7/14/13 10:17 AM: ---------------------------------------------------------------- Escaping of exclamation marks was fixed upstream in jline2, a few months back. I've ported it to a topic branch on my clone: https://github.com/VineetReynolds/forge-core/tree/FORGE-85. But this alone does not solve the problem yet. The FSH parser tokenizes '\!'s differently. Thus, a command invocation provided to the parser, like {{new-project --named example --finalName example!test}}, is turned into {{new-project --named example --finalName example ! test}}. The tokens '!' and 'test' are eventually ignored as arguments to the new-project plugin, due to the spaces injected by the FSH parser. was (Author: vineet.reynolds): Escaping of exclamation marks was fixed upstream in jline2, a few months back. I've ported it to a topic branch on my clone: https://github.com/VineetReynolds/forge-core/tree/FORGE-85. But this alone does not solve the problem yet. The FSH parser tokenizes '!'s differently. Thus, a command invocation provided to the parser, like {{new-project --named example --finalName example!test}}, is turned into {{new-project --named example --finalName example ! test}}. The tokens '!' and 'test' are eventually ignored as arguments to the new-project plugin, due to the spaces injected by the FSH parser. > Shell cannot parse command values containing '!' exclaimation points > -------------------------------------------------------------------- > > Key: FORGE-85 > URL: https://issues.jboss.org/browse/FORGE-85 > Project: Forge > Issue Type: Bug > Components: UI - Shell > Affects Versions: 1.0.0.Beta2 > Reporter: Lincoln Baxter III > Labels: HackNight > Fix For: 1.x Future > > Attachments: Forge-85.patch > > > {code} > [pfdemo] pfdemo $ echo sdfdf! > sdfdf ! > [pfdemo] pfdemo $ echo sdfdf!sdf > ***ERROR*** Exception encountered: !sdf: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > [pfdemo] pfdemo $ echo 'asdf!asdf` > ***ERROR*** Exception encountered: !asdf`: event not found (type "set VERBOSE true" to enable stack traces) > [pfdemo] pfdemo $ > {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

12 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues July 2013