October 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-1282) Message "XADisk Error [Native Module] Directory C:\ does not exist" when running in Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1282?page=com.atlassian.jira.plugin... ] George Gastaldi closed FORGE-1282. ---------------------------------- Assignee: George Gastaldi Fix Version/s: 2.0.0.Beta1 Resolution: Done > Message "XADisk Error [Native Module] Directory C:\ does not exist" when running in Windows > ------------------------------------------------------------------------------------------- > > Key: FORGE-1282 > URL: https://issues.jboss.org/browse/FORGE-1282 > Project: Forge > Issue Type: Bug > Components: Resources API, Windows > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 2.0.0.Beta1 > > > Happens when tests are run and also reported in FORGE-1270 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1282) Message "XADisk Error [Native Module] Directory C:\ does not exist" when running in Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1282?page=com.atlassian.jira.plugin... ] George Gastaldi updated FORGE-1282: ----------------------------------- Component/s: Windows > Message "XADisk Error [Native Module] Directory C:\ does not exist" when running in Windows > ------------------------------------------------------------------------------------------- > > Key: FORGE-1282 > URL: https://issues.jboss.org/browse/FORGE-1282 > Project: Forge > Issue Type: Bug > Components: Resources API, Windows > Affects Versions: 2.0.0.Alpha14 > Reporter: George Gastaldi > > Happens when tests are run and also reported in FORGE-1270 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1282) Message "XADisk Error [Native Module] Directory C:\ does not exist" when running in Windows

by George Gastaldi (JIRA)

George Gastaldi created FORGE-1282: -------------------------------------- Summary: Message "XADisk Error [Native Module] Directory C:\ does not exist" when running in Windows Key: FORGE-1282 URL: https://issues.jboss.org/browse/FORGE-1282 Project: Forge Issue Type: Bug Components: Resources API Affects Versions: 2.0.0.Alpha14 Reporter: George Gastaldi Happens when tests are run and also reported in FORGE-1270 -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-146) AngularJS scaffold does not pluralize some entities correctly

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-146?page=com.atlassian.jira.... ] Vineet Reynolds closed FORGEPLUGINS-146. ---------------------------------------- Resolution: Duplicate Issue Valid point. Marking as duplicate though of FORGEPLUGINS-144. > AngularJS scaffold does not pluralize some entities correctly > ------------------------------------------------------------- > > Key: FORGEPLUGINS-146 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-146 > Project: Forge Plugins > Issue Type: Bug > Components: AngularJS Scaffold > Reporter: Oliver Kišš > Assignee: Vineet Reynolds > > AngularJS scaffold creates plurals of entity names by appending 's' to them. A more robust method should be used to correctly pluralize names that cannot be pluralized this way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-144) Use an inflector library to correctly pluralize or singularize names based on context

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-144?page=com.atlassian.jira.... ] Vineet Reynolds updated FORGEPLUGINS-144: ----------------------------------------- Description: Use an inflector to ensure that rules to singularize or pluralize words are used instead of blindly adding a 's' to a word (was: Use an inflector to ensure that rules to singularize or pluralize words are used instead of blindly adding a 's' to a word :)) > Use an inflector library to correctly pluralize or singularize names based on context > ------------------------------------------------------------------------------------- > > Key: FORGEPLUGINS-144 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-144 > Project: Forge Plugins > Issue Type: Feature Request > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Use an inflector to ensure that rules to singularize or pluralize words are used instead of blindly adding a 's' to a word -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-146) AngularJS scaffold does not pluralize some entities correctly

by Oliver Kišš (JIRA)

Oliver Kišš created FORGEPLUGINS-146: ---------------------------------------- Summary: AngularJS scaffold does not pluralize some entities correctly Key: FORGEPLUGINS-146 URL: https://issues.jboss.org/browse/FORGEPLUGINS-146 Project: Forge Plugins Issue Type: Bug Components: AngularJS Scaffold Reporter: Oliver Kišš Assignee: Vineet Reynolds AngularJS scaffold creates plurals of entity names by appending 's' to them. A more robust method should be used to correctly pluralize names that cannot be pluralized this way. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1281) (re)source folders shouldn't be created in multimodule addon project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/FORGE-1281?page=com.atlassian.jira.plugin... ] Fred Bricon moved JBIDE-15781 to FORGE-1281: -------------------------------------------- Project: Forge (was: Tools (JBoss Tools)) Key: FORGE-1281 (was: JBIDE-15781) Affects Version/s: 2.0.0.Alpha14 (was: 4.2.0.Alpha1) Component/s: UI - Eclipse (was: forge) > (re)source folders shouldn't be created in multimodule addon project > -------------------------------------------------------------------- > > Key: FORGE-1281 > URL: https://issues.jboss.org/browse/FORGE-1281 > Project: Forge > Issue Type: Bug > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha14 > Reporter: Fred Bricon > Priority: Minor > > Reporting from memory : > If you create a new forge project of type addon and choose to create all sub modules (api, impl...), src/main/resources and src/main/java folders are created under the parent project of type pom. This is useless since no compilation occurs for pom projects. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1270) Forge 2.0.0.Aplha13 doesn't start on Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-1270?page=com.atlassian.jira.plugin... ] George Gastaldi commented on FORGE-1270: ---------------------------------------- Exception reported by [~fbricon] while booting up Forge 2: http://pastebin.com/rbA4Ka8W > Forge 2.0.0.Aplha13 doesn't start on Windows > -------------------------------------------- > > Key: FORGE-1270 > URL: https://issues.jboss.org/browse/FORGE-1270 > Project: Forge > Issue Type: Bug > Affects Versions: 2.0.0.Alpha13 > Environment: Win 7-64b, JDK 1.7.0_45, forge 2.0.0.Alpha13 > Reporter: Fred Bricon > Priority: Blocker > > * Start forge > * Forge banner is shown > * Prompt never shows up > See threaddump : > {noformat} > 2013-10-20 10:37:12 > Full thread dump Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode): > "Reference Reaper" daemon prio=6 tid=0x000000000c994000 nid=0x259c in Object.wait() [0x000000000d9af000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000007d6c50bc8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x00000007d6c50bc8> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at org.jboss.modules.ref.References$ReaperThread.run(References.java:68) > "Service Thread" daemon prio=6 tid=0x000000000a9c8000 nid=0x1b68 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread1" daemon prio=10 tid=0x000000000a9c6000 nid=0x2380 waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "C2 CompilerThread0" daemon prio=10 tid=0x000000000a9c1000 nid=0x1bdc waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Attach Listener" daemon prio=10 tid=0x000000000a9bf000 nid=0x209c waiting on condition [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Signal Dispatcher" daemon prio=10 tid=0x000000000a9b8000 nid=0x22e0 runnable [0x0000000000000000] > java.lang.Thread.State: RUNNABLE > "Finalizer" daemon prio=8 tid=0x000000000a969800 nid=0x1b58 in Object.wait() [0x000000000bc8f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000007d6605568> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135) > - locked <0x00000007d6605568> (a java.lang.ref.ReferenceQueue$Lock) > at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151) > at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:189) > "Reference Handler" daemon prio=10 tid=0x000000000a95e000 nid=0x1b80 in Object.wait() [0x000000000be2f000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > - waiting on <0x00000007d66050f0> (a java.lang.ref.Reference$Lock) > at java.lang.Object.wait(Object.java:503) > at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133) > - locked <0x00000007d66050f0> (a java.lang.ref.Reference$Lock) > "main" prio=6 tid=0x00000000023af000 nid=0x1124 waiting on condition [0x00000000027df000] > java.lang.Thread.State: TIMED_WAITING (sleeping) > at java.lang.Thread.sleep(Native Method) > at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:177) > at org.jboss.forge.furnace.impl.FurnaceImpl.start(FurnaceImpl.java:122) > at org.jboss.forge.bootstrap.Bootstrap.start(Bootstrap.java:170) > at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:88) > "VM Thread" prio=10 tid=0x000000000a958800 nid=0x24a0 runnable > "GC task thread#0 (ParallelGC)" prio=6 tid=0x000000000229e800 nid=0x1d70 runnable > "GC task thread#1 (ParallelGC)" prio=6 tid=0x00000000022a0800 nid=0x7e8 runnable > "GC task thread#2 (ParallelGC)" prio=6 tid=0x00000000022a2000 nid=0x1694 runnable > "GC task thread#3 (ParallelGC)" prio=6 tid=0x00000000022a3800 nid=0xe70 runnable > "VM Periodic Task Thread" prio=10 tid=0x000000000a9de000 nid=0x1e7c waiting on condition > JNI global references: 134 > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGE-1054) Forge OpenShift plugin hangs when creating a JBoss app in Windows

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/FORGE-1054?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on FORGE-1054: ----------------------------------------- It is very likely that the openshift-java-client used in forge is not using a RH proxy. The operation above targets a dev environment on aws (https://ec2-54-221-0-244.compute-...). DEVENV's are only reachable via RH proxies. Another even more likely cause is that the DEVENV is not propagating the new app DNS record, which is usually the case for me when I'm using an OpenShift live-cd. The workaround is then simple: add the app-name to your local hosts file. If this is true, then this is a non-issue for you guys. Btw. Bill DeCoste left OpenShift, he's now consultant. > Forge OpenShift plugin hangs when creating a JBoss app in Windows > ----------------------------------------------------------------- > > Key: FORGE-1054 > URL: https://issues.jboss.org/browse/FORGE-1054 > Project: Forge > Issue Type: Bug > Affects Versions: 1.3.3.Final > Environment: Window7 > Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64 > Reporter: nan wei > Assignee: William DeCoste > > Description of problem: > When creating a jboss app, app creation process hang there. > Version: > forge-distribution-1.3.3.Final.zip > Window7 > Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64 > How reproducible: > always > Steps to Reproduce: > 1. Ensure that you have already installed a Java 6+ JDK. > 1.1 install jdk-7u25-windows-x64 > 1.2 set JAVA_HOME. > 2. Download Forge 1.3.2.Final and Un-zip Forge into a folder on your hard-disk, this folder will be your FORGE_HOME. > 2.1 Add '$FORGE_HOME/bin' to your windows path. > 2.2 installing Git(Git-1.8.3-preview2013.6.1) > 3. Open a command prompt and run 'forge.bat'. > 4. Install OpenShift plugin for forge. > 5. create a jboss app. > Actual results: > [forge-openshift-demo] forge-openshift-demo $ rhc setup > ***INFO*** Loaded OpenShift configuration from C:\Users\nanwei/.openshift/expres > s.conf > ? Enter the application name [forgeopenshiftd] [forgeopenshiftd] wsy > ***INFO*** Using RHLOGIN:nwei for https://10.4.59.171 > ? Enter your Red Hat Openshift password: ****** > ***INFO*** Found OpenShift User: nwei > Choose a JBoss Cartridge: > > 1 - [Cartridge [name=jbosseap-6.0]]* > 2 - [Cartridge [name=jbossews-2.0]] > 3 - [Cartridge [name=jbossews-1.0]] > > ? Choose an option by typing the number of the selection [*-default] [0] 1 > ***INFO*** Using JBoss Cartridge: jbosseap-6.0 > Initialized empty Git repository in C:/Users/nanwei/Downloads/forge/bin/forge-op > enshift-demo/.git/ > ***INFO*** Waiting for OpenShift to propagate DNS > ***INFO*** Trying to contact http://forge-nweidomain.osetestv2.com/ (attempt 1 of > 500) > Updating openshift > Expected results: > The process will hang there for ever. > Additional info: -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (FORGEPLUGINS-145) AngularJS scaffold is not activated even though it was setup

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-145?page=com.atlassian.jira.... ] Vineet Reynolds resolved FORGEPLUGINS-145. ------------------------------------------ Resolution: Done Pushed: https://github.com/forge/angularjs-scaffoldx-plugin/commit/07eb78d3117161... > AngularJS scaffold is not activated even though it was setup > ------------------------------------------------------------ > > Key: FORGEPLUGINS-145 > URL: https://issues.jboss.org/browse/FORGEPLUGINS-145 > Project: Forge Plugins > Issue Type: Enhancement > Components: AngularJS Scaffold > Reporter: Vineet Reynolds > Assignee: Vineet Reynolds > > Raising this issue to work around the FORGE-1280 limitation. > When running the {{admin_layer.fsh}} script in Forge 1.4.0+ on a fresh clone of TicketMonster, the script responds that the AngularJS scaffold is not installed, despite the {{scaffold setup}} script run in the previous step. > The AngularJS scaffold provider could ensure that the setup command completes only when the Configuration property value is updated, thus bypassing this problem for this 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, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2013