November 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1335) Creating new project, JVM IBM 1.7

by Martin Basovnik (JIRA)

[ https://issues.jboss.org/browse/FORGE-1335?page=com.atlassian.jira.plugin... ] Martin Basovnik updated FORGE-1335: ----------------------------------- Description: Problem with creating of new project on JVM ibm17. LOG: {noformat} [no project] test-forge $ new-project --named IBM ? Use [/home/mbasovni/development/test-forge/IBM] as project directory? [Y/n] Wrote /home/mbasovni/development/test-forge/IBM Wrote /home/mbasovni/development/test-forge/IBM/pom.xml Wrote /home/mbasovni/development/test-forge/IBM/src/main/java Wrote /home/mbasovni/development/test-forge/IBM/src/test/java Wrote /home/mbasovni/development/test-forge/IBM/src/main/resources Wrote /home/mbasovni/development/test-forge/IBM/src/test/resources ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) {noformat} was: Problem with creating of new project on JVM ibm17. LOG: [no project] test-forge $ new-project --named IBM ? Use [/home/mbasovni/development/test-forge/IBM] as project directory? [Y/n] Wrote /home/mbasovni/development/test-forge/IBM Wrote /home/mbasovni/development/test-forge/IBM/pom.xml Wrote /home/mbasovni/development/test-forge/IBM/src/main/java Wrote /home/mbasovni/development/test-forge/IBM/src/test/java Wrote /home/mbasovni/development/test-forge/IBM/src/main/resources Wrote /home/mbasovni/development/test-forge/IBM/src/test/resources ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) > Creating new project, JVM IBM 1.7 > --------------------------------- > > Key: FORGE-1335 > URL: https://issues.jboss.org/browse/FORGE-1335 > Project: Forge > Issue Type: Bug > Affects Versions: 1.4.3.Final > Environment: JVM: IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20130205_137358 (JIT enabled, AOT enabled) > OS: Ubuntu 13.04 64 bit > Reporter: Martin Basovnik > > Problem with creating of new project on JVM ibm17. > LOG: > {noformat} > [no project] test-forge $ new-project --named IBM > ? Use [/home/mbasovni/development/test-forge/IBM] as project directory? [Y/n] > Wrote /home/mbasovni/development/test-forge/IBM > Wrote /home/mbasovni/development/test-forge/IBM/pom.xml > Wrote /home/mbasovni/development/test-forge/IBM/src/main/java > Wrote /home/mbasovni/development/test-forge/IBM/src/test/java > Wrote /home/mbasovni/development/test-forge/IBM/src/main/resources > Wrote /home/mbasovni/development/test-forge/IBM/src/test/resources > ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1335) Creating new project, JVM IBM 1.7

by Martin Basovnik (JIRA)

Martin Basovnik created FORGE-1335: -------------------------------------- Summary: Creating new project, JVM IBM 1.7 Key: FORGE-1335 URL: https://issues.jboss.org/browse/FORGE-1335 Project: Forge Issue Type: Bug Affects Versions: 1.4.3.Final Environment: JVM: IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20130205_137358 (JIT enabled, AOT enabled) OS: Ubuntu 13.04 64 bit Reporter: Martin Basovnik Problem with creating of new project on JVM ibm17. LOG: [no project] test-forge $ new-project --named IBM ? Use [/home/mbasovni/development/test-forge/IBM] as project directory? [Y/n] Wrote /home/mbasovni/development/test-forge/IBM Wrote /home/mbasovni/development/test-forge/IBM/pom.xml Wrote /home/mbasovni/development/test-forge/IBM/src/main/java Wrote /home/mbasovni/development/test-forge/IBM/src/test/java Wrote /home/mbasovni/development/test-forge/IBM/src/main/resources Wrote /home/mbasovni/development/test-forge/IBM/src/test/resources ***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces) -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1334) Addon installation "forge -i core" takes forever and repeatedly downloads metadata files

by Lincoln Baxter III (JIRA)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1334) Addon installation "forge -i core" takes forever and repeatedly downloads metadata files

by Lincoln Baxter III (JIRA)

11 years

1
0
0 / 0

[JBoss JIRA] (FORGE-1330) Rename new-project

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/FORGE-1330?page=com.atlassian.jira.plugin... ] Catherine Robson commented on FORGE-1330: ----------------------------------------- Yeah, this one is challenging. 'new-project' is certainly more intuitive from a first use standpoint - but project-new will become more intuitive over time once people are used to the Forge formatting of other object actions. Is there any reason why we cannot support both as valid entries to perform the action? This might be the best solution if it is possible. > Rename new-project > ------------------ > > Key: FORGE-1330 > URL: https://issues.jboss.org/browse/FORGE-1330 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > I know this one hurts a bit, but we should really rename : > {code} > new-project > {code} > To : > {code} > project-new > {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

1
0
0 / 0

[JBoss JIRA] (FORGE-1321) Failure to install addons when using secure repositories

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] Vineet Reynolds resolved FORGE-1321. ------------------------------------ Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done Pushed: https://github.com/forge/furnace/commit/d47bb7ee0f8b672a92f8b0646e4fea668... Colllect and VersionRange requests performed by Aether involving a set of supplied repositories, are done with the authentication info determined upfront. Mirrors are determined for any repositories before-hand, followed by determination of authentication info for both mirrors and repositories. > Failure to install addons when using secure repositories > -------------------------------------------------------- > > Key: FORGE-1321 > URL: https://issues.jboss.org/browse/FORGE-1321 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.0.0.Beta4 > > > After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon: > {noformat} > forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell > Using Forge at forge-distribution-2.0.0.Beta2 > Warning: JAVA_HOME environment variable is not set. > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell > at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199) > at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > > Forge version [2.0.0.Beta1] > {noformat} > The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords > Additional info: > {noformat} > <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1321) Failure to install addons when using secure repositories

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] Vineet Reynolds updated FORGE-1321: ----------------------------------- Summary: Failure to install addons when using secure repositories (was: Failure to install addons when using Artifactory repositories using centrally secured passwords) > Failure to install addons when using secure repositories > -------------------------------------------------------- > > Key: FORGE-1321 > URL: https://issues.jboss.org/browse/FORGE-1321 > Project: Forge > Issue Type: Bug > Components: Build Tools - Maven > Affects Versions: 2.0.0.Beta3 > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > Fix For: 2.x Future > > > After FORGE-1307, Forge seems to be able to access secure repositories, but fails to install the addon: > {noformat} > forge-distribution-2.0.0.Beta2$ ./bin/forge --install shell > Using Forge at forge-distribution-2.0.0.Beta2 > Warning: JAVA_HOME environment variable is not set. > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > Downloading: http://xxxxxx/artifactory/repo/org/jboss/forge/addon/shell/maven-metadata... > java.lang.IllegalArgumentException: No Artifact version found for org.jboss.forge.addon:shell > at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:199) > at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:144) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > > Forge version [2.0.0.Beta1] > {noformat} > The Artifactory repository used this feature: http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords > Additional info: > {noformat} > <dbeer> think I have found part of issue I have removed security constraint briefly from our server and is now downloading a load of forge addon snapshots, will investigate the security further tomorrow > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1333) Forge "man" pages are missing for most UI Commands

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ] Lincoln Baxter III updated FORGE-1333: -------------------------------------- Summary: Forge "man" pages are missing for most UI Commands (was: Should command "man" give information about Forge commands ?) > Forge "man" pages are missing for most UI Commands > -------------------------------------------------- > > Key: FORGE-1333 > URL: https://issues.jboss.org/browse/FORGE-1333 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > This is more a question because I don't know what {{man}} is suppose to do. This is what I get : > {code} > [Test.java]$ man grep > No manual entry for grep > [Test.java]$ man echo > No manual entry for echo > {code} > I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual -- 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

1
0
0 / 0

[JBoss JIRA] (FORGE-1332) No default nor completion for --typeName

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1332?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1332. ---------------------------------- Fix Version/s: 2.0.0.Beta4 (was: 2.x Future) Resolution: Done > No default nor completion for --typeName > ---------------------------------------- > > Key: FORGE-1332 > URL: https://issues.jboss.org/browse/FORGE-1332 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > Assignee: George Gastaldi > Fix For: 2.0.0.Beta4 > > > When I create a new field on an existing entity I write this : > {code} > jpa-new-field --entity org.model.Test --fieldName lastname --typeName String > ***SUCCESS*** Field lastname created > {code} > If I don't write {{String}} the command doesn't give me completion. I would expect that writing the following and hitting TAB would give me some basic datatypes (String, int, float...) > {code} > jpa-new-field --entity org.model.Test --fieldName lastname --typeName > {code} > And why not having {{String}} as the default type ? This command would create a {{lastname}} of type {{String}} by default : > {code} > jpa-new-field --entity org.model.Test --fieldName lastname > {code} > Instead I have an error saying that "Type must be specified" > {code} > jpa-new-field --entity org.model.Test --fieldName lastname > Type must be specified > {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

1
0
0 / 0

[JBoss JIRA] (FORGE-1333) Should command "man" give information about Forge commands ?

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/FORGE-1333?page=com.atlassian.jira.plugin... ] Lincoln Baxter III commented on FORGE-1333: ------------------------------------------- Just got this feature working :) > Should command "man" give information about Forge commands ? > ------------------------------------------------------------ > > Key: FORGE-1333 > URL: https://issues.jboss.org/browse/FORGE-1333 > Project: Forge > Issue Type: Sub-task > Components: UI - Shell > Reporter: Antonio Goncalves > Fix For: 2.x Future > > > This is more a question because I don't know what {{man}} is suppose to do. This is what I get : > {code} > [Test.java]$ man grep > No manual entry for grep > [Test.java]$ man echo > No manual entry for echo > {code} > I would expect to have a manual for each Forge command and also to get completion (e.g. {{man jpa}} TAB and it will give all the JPA commands available in the manual -- 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

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2013