December 2011 - forge-users - Jboss List Archives

Loading module failed: Failed to add resource root 'fpak.jar' at path 'fpak.jar'

by Jörn Ohmen

Hello, using a snapshot of today and starting forge cause this error: Exception in thread "main" org.jboss.modules.ModuleLoadException: Error loading module from /Users/macuser/Development/forge-1.0.0-SNAPSHOT/modules/org/jboss/forge/main/module.xml at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:249) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:200) at org.jboss.modules.LocalModuleLoader.parseModuleInfoFile(LocalModuleLoader.java:147) at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:124) at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:245) at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:194) at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:97) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:176) at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:172) at org.jboss.modules.Main.main(Main.java:311) Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[26,40] Message: Failed to add resource root 'fpak.jar' at path 'fpak.jar' at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:751) at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:707) at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:575) at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:505) at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:244) Can somebody help please? I use MacOs X 10.6.8 with Java 1.6_29 and JBoss 7.0.2 thanks

12 years, 10 months

2
1
0 / 0

cannot start foge-distribution-1.0.0.Beta5

by olaf.groenemann＠groenemann.de

hi all and merry Xmas, I installed forge-distribution-1.0.0.Beta5 on a ubuntu linux machine and starting forge results in: olaf@olaf-ThinkPad-X100e:~/dev/java/forge-distribution-1.0.0.Beta5$ forge Unable to access jarfile ~/dev/java/forge-distribution-1.0.0.Beta5/jboss-modules.jar here ls -l of the forge dir: olaf@olaf-ThinkPad-X100e:~/dev/java/forge-distribution-1.0.0.Beta5$ ls -l insgesamt 304 drwxr-xr-x 2 olaf olaf 4096 2011-12-21 10:46 bin -rw-r--r-- 1 olaf olaf 45 2011-12-21 10:46 copyright.txt -r--r--r-- 1 olaf olaf 242802 2011-12-21 10:46 jboss-modules.jar drwxr-xr-x 2 olaf olaf 4096 2011-12-21 10:46 lib -rw-r--r-- 1 olaf olaf 8729 2011-12-21 10:46 LICENSE.txt drwxr-xr-x 9 olaf olaf 4096 2011-12-21 10:46 modules -rw-r--r-- 1 olaf olaf 311 2011-12-21 10:46 README.txt Anyone an idea what is going wrong? Note: tried with chmod ugo+x and ugo+w but the same message appeared.

12 years, 10 months

1
0
0 / 0

Re: [forge-users] Plugins can't installed anymore with Beta4!

by Rudy De Busscher

Can we fix it in the beta4 release locally (by adding the missing module.xml in the shell.jar) or do we have to wait for the beta5? Thanks Rudy PS. Apparently I didn't receive any mail from the mailing lists, that is why i have this odd reply. Hi. We are currently looking in to this issue. Sorry for the trouble!https://issues.jboss.org/browse/FORGE-412 ~Lincoln On Tue, Dec 20, 2011 at 9:41 AM, Rudy De Busscher <rdebusscher at gmail.com <https://lists.jboss.org/mailman/listinfo/forge-users>>wrote: >* Hi,*>**>* I just downloaded the new beta4 distribution and it has problems with*>* installing a plugin.*>**>* This is the command sequence what I did:*>**>* * new-project --named rubus--topLevelPackage be.rubus.forge*>* * plugins setup (selected 6 Beta4 version of shell-api)*>* * plugins new-plugin --named rubus*>**>**>* ***INFO*** Installing plugin artifact.*>* Wrote C:\/Users/debusru/.forge/plugins/be*>* Wrote C:\/Users/debusru/.forge/plugins/be/rubus*>* Wrote C:\/Users/debusru/.forge/plugins/be/rubus/forge*>* Wrote C:\/Users/debusru/.forge/plugins/be/rubus/forge/rubus*>* Wrote*>* C:\/Users/debusru/.forge/plugins/be/rubus/forge/rubus/1.0.0-SNAPSHOT-82e9aca8-677d-4fb7-9a00-6252e8904817*>* Wrote*>* C:\/Users/debusru/.forge/plugins/be/rubus/forge/rubus/1.0.0-SNAPSHOT-82e9aca8-677d-4fb7-9a00-6252e8904817/module.xml*>* ***ERROR*** [forge source-plugin] Could not import XML from stream*>**>**>* Problem with the release or something that I miss?*>* --*>* Rudy De Busscher*>* http://www.c4j.be*>**>**>* _______________________________________________*>* forge-users mailing list*>* forge-users at lists.jboss.org <https://lists.jboss.org/mailman/listinfo/forge-users>*>* https://lists.jboss.org/mailman/listinfo/forge-users*>**>** -- Lincoln Baxter, IIIhttp://ocpsoft.comhttp://scrumshark.com "Keep it Simple"

12 years, 10 months

2
2
0 / 0

Plugins can't installed anymore with Beta4!

by Max Schwaab

Hi, got that problem too. Must have anything to do with the path search, because the module.xml is not found by Node module = XMLParser.parse(getClass().getResourceAsStream("/org/jboss/forge/modules/module.xml")); in the ForgePlugin.class A switch back to Beta 3 solves the problem. It's not good to have a step back from Beta 3 to Beta 4 :( I try to develop a plugin and testing is not easy this way.. Best regards Max

12 years, 10 months

2
1
0 / 0

Plugins can't installed anymore with Beta4!

by Rudy De Busscher

Hi, I just downloaded the new beta4 distribution and it has problems with installing a plugin. This is the command sequence what I did: * new-project --named rubus--topLevelPackage be.rubus.forge * plugins setup (selected 6 Beta4 version of shell-api) * plugins new-plugin --named rubus ***INFO*** Installing plugin artifact. Wrote C:\/Users/debusru/.forge/plugins/be Wrote C:\/Users/debusru/.forge/plugins/be/rubus Wrote C:\/Users/debusru/.forge/plugins/be/rubus/forge Wrote C:\/Users/debusru/.forge/plugins/be/rubus/forge/rubus Wrote C:\/Users/debusru/.forge/plugins/be/rubus/forge/rubus/1.0.0-SNAPSHOT-82e9aca8-677d-4fb7-9a00-6252e8904817 Wrote C:\/Users/debusru/.forge/plugins/be/rubus/forge/rubus/1.0.0-SNAPSHOT-82e9aca8-677d-4fb7-9a00-6252e8904817/module.xml ***ERROR*** [forge source-plugin] Could not import XML from stream Problem with the release or something that I miss? -- Rudy De Busscher http://www.c4j.be

12 years, 10 months

2
1
0 / 0

JBoss Forge 1.0.0.Beta4 Released!

by Lincoln Baxter, III

It's here... with improved scaffolding. Want proof? 1. Download Forge Beta4<https://repository.jboss.org/nexus/service/local/artifact/maven/redirect?...> 2. Install <https://docs.jboss.org/author/display/FORGE/Installation> it. 3. Run it. 4. Copy and execute this command: * * *$** run-url https://raw.github.com/forge/core/master/showcase/posale.fsh * * * 5. Watch the magic ;) View the release notes<https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12311820&versi...>- get excited<http://twitter.com/intent/tweet?source=jbossforge&text=Just%20found%20out...>about it! -- Lincoln Baxter, III http://ocpsoft.com "Keep it Simple"

12 years, 11 months

1
0
0 / 0

JBoss Asylum podcast with Forge

by Max Rydahl Andersen

http://in.relation.to/Bloggers/JBossCommunityAsylum23ForgingForge With Paul Bakker and Lincoln. Hope you like it :) /max http://about.me/maxandersen

12 years, 11 months

1
0
0 / 0

Forge persistence setup not working

by ansar basha

Hi All, I was creating new project in JBoss tools, while issuing persistence setup command i do get ***ERROR*** [persistence setup] null can any one of you know whats wrong with this. I'm using forge-1.0.0.Beta3 on windows 7 with jdk 6 24U thanks ansar

12 years, 11 months

2
1
0 / 0

hibernate-tools plugin

by Max Schwaab

Hey there, I'm new to forge and want to try the database reverse engineering. When I try to use the hibernate-tools plugin, I get log4J errors like: log4j:ERROR A "org.apache.log4j.xml.DOMConfigurator" object is not assignable to a "org.apache.log4j.spi.Configurator" variable. log4j:ERROR The class "org.apache.log4j.spi.Configurator" was loaded by log4j:ERROR [ModuleClassLoader for Module "org.jboss.forge:main" from local modu le loader @510e39 (roots: C:\forge\forge-1.0.0.Beta3\modules,C:\Users\Max\.forge \plugins)] whereas object of type log4j:ERROR "org.apache.log4j.xml.DOMConfigurator" was loaded by [ModuleClassLoa der for Module "org.jboss.hibernate.forge.hibernate-tools-plugin.dependencies:1. 0.0-SNAPSHOT-d4f52737-8c8e-47d5-9113-97edf57516c4" from local module loader @510 e39 (roots: C:\forge\forge-1.0.0.Beta3\modules,C:\Users\Max\.forge\plugins)]. log4j:ERROR Could not instantiate configurator [org.apache.log4j.xml.DOMConfigur ator]. log4j:WARN No appenders could be found for logger (org.jboss.weld.Version). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more in fo. When I try to use the generate-entities command I get errors too. Sometimes a slf4J error like: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further detail s. ***ERROR*** [generate-entities] org/slf4j/impl/StaticLoggerBinder And sometimes a JDBCMetaDataConfguration error like: ***ERROR*** [generate-entities] Could not initialize class org.hibernate.cfg.JDB CMetaDataConfiguration I looked around on the internet and found a remark from Jethro with the same problem. (http://lists.jboss.org/pipermail/forge-users/2011-October/000079.html) I'm using the latest beta3 version of forge and the hibernate-tools-plugin from github (guess its the latest version). Is there some work in progress or did I something wrong with the configuration or something? Would be nice to get this feature working.. Best regards Max

12 years, 11 months

4
5
0 / 0

(no subject)

by Abdullah Shaikh

forge creates html status code files as .xhtml (e.g. 404.xhtml) but creates a .jsf (e.g. /404.jsf) entry in web.xml -Abdullah

12 years, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-users December 2011