[JBoss JIRA] (FORGE-1261) "rest endpoint-from-entity" fails, ClassNotFoundException: org.apache.log4j.Priority
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1261?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-1261.
----------------------------------
Assignee: George Gastaldi
Fix Version/s: 1.4.2.Final
Resolution: Done
The Hibernate tools plugin already bundles freemarker as a new dependency. Freemarker has a built-in logging facade system that delegates to the underlying logging implementations (much like commons-logging).
When the Hibernate tools plugin is installed, log4j (which is bundled with this plugin as well) kicks in and freemarker chooses the Log4j implementation.
This is not handled correctly in the module.xml, given that declares that it depends on nothing but the javax.api.
Thanks to [~tm2] for detecting this.
> "rest endpoint-from-entity" fails, ClassNotFoundException: org.apache.log4j.Priority
> ------------------------------------------------------------------------------------
>
> Key: FORGE-1261
> URL: https://issues.jboss.org/browse/FORGE-1261
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 1.4.1.Final
> Environment: (Environment-independent, but...) JDK 1.6.0_45, Windows Server 2008 R2
> Reporter: Thomas Maslen
> Assignee: George Gastaldi
> Priority: Minor
> Fix For: 1.4.2.Final
>
>
> Summary: the org.freemarker module should express a dependency on org.apache.log4j but doesn't
> Workaround: edit modules/org/freemarker/main/module.xml and add the dependency
> The long version:
> "rest endpoint-from-entity" works fine in the version of Forge that is bundled in JBoss Tools 4.1 (Forge 1.3.3).
> However, the DTO-based functionality added in FORGE-1060 looked tasty, so I downloaded Forge 1.4.1 and took it for a spin.
> Regardless of whether I run 1.4.1 standalone or within JBoss Tools (Eclipse), "rest endpoint-from-entity" fails with
> java.lang.ClassNotFoundException: org.apache.log4j.Priority from [Module "org.freemarker:main"
> (I have a complete stack trace but it doesn't add anything profound).
> Once I edited modules/org/freemarker/main/module.xml and added a dependency for the "org.apache.log4j" class, "rest endpoint-from-entity" ran happily and generated the expected classes.
--
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
10 years, 8 months
[JBoss JIRA] (FORGE-1261) "rest endpoint-from-entity" fails, ClassNotFoundException: org.apache.log4j.Priority
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-1261?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-1261:
----------------------------------------
Hi Thomas,
That's some very important news. I managed to reproduce this issue by installing the hibernate-tools plugin ({{forge install-plugin hibernate-tools}}) before calling {{rest setup}} .
Thank you very much.
> "rest endpoint-from-entity" fails, ClassNotFoundException: org.apache.log4j.Priority
> ------------------------------------------------------------------------------------
>
> Key: FORGE-1261
> URL: https://issues.jboss.org/browse/FORGE-1261
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 1.4.1.Final
> Environment: (Environment-independent, but...) JDK 1.6.0_45, Windows Server 2008 R2
> Reporter: Thomas Maslen
> Priority: Minor
>
> Summary: the org.freemarker module should express a dependency on org.apache.log4j but doesn't
> Workaround: edit modules/org/freemarker/main/module.xml and add the dependency
> The long version:
> "rest endpoint-from-entity" works fine in the version of Forge that is bundled in JBoss Tools 4.1 (Forge 1.3.3).
> However, the DTO-based functionality added in FORGE-1060 looked tasty, so I downloaded Forge 1.4.1 and took it for a spin.
> Regardless of whether I run 1.4.1 standalone or within JBoss Tools (Eclipse), "rest endpoint-from-entity" fails with
> java.lang.ClassNotFoundException: org.apache.log4j.Priority from [Module "org.freemarker:main"
> (I have a complete stack trace but it doesn't add anything profound).
> Once I edited modules/org/freemarker/main/module.xml and added a dependency for the "org.apache.log4j" class, "rest endpoint-from-entity" ran happily and generated the expected classes.
--
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
10 years, 8 months
[JBoss JIRA] (FORGE-1261) "rest endpoint-from-entity" fails, ClassNotFoundException: org.apache.log4j.Priority
by Thomas Maslen (JIRA)
[ https://issues.jboss.org/browse/FORGE-1261?page=com.atlassian.jira.plugin... ]
Thomas Maslen commented on FORGE-1261:
--------------------------------------
OK, I tried it (a fresh install of Forge 1.4.1) on another machine that had never been touched by Forge before and yes, you're right, in that environment I couldn't reproduce the problem and Forge works fine.
Also, on the original machine, I erased the .forge directory (actually just renamed it to detain it for further questioning) and yes, with that out of the way again Forge works fine.
I looked at the contents of the previous .forge directory. Offhand the .forge/config and .forge/config.xml files look pretty innocent. What _is_ interesting (I'm guessing) is that the plugins directory contains one plugin, hibernate-tools-plugin, and (for whatever it's worth) that plugin includes JAR files for both freemarker (an older version, freemarker-2.3.8.jar) and log4j.
If necessary I can tar up the old .forge directory and attach it (if this system supports attachments -- either I'm not seeing straight or they are well hidden), but my guess is that the plugins/installed.xml file (cut and pasted below) tells the important part of the tale:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<installed>
<plugin api-version="1.0.5.Final" name="org.jboss.hibernate.forge.hibernate-tools-plugin" slot="1.2.0-SNAPSHOT-4f729e5d-125b-46a3-9f07-4ca220ae19c0"/>
</installed>
I can't say for sure how that plugin got there (I can't even swear that it's the guilty party, but it seems like a plausible candidate), but I'm assuming that it's because I was using JBoss Tools 4.1.0 (in Eclipse 4.3.1) and its embedded Forge 1.3.3.
In the new .forge directory there are no plugins (there isn't even a plugins subdirectory yet), even though I have run "new-project", "persistence setup", "entity", "rest setup" and "rest endpoint-from-entity", so I'm guessing that plugin only gets installed if you exercise some of the Forge Eclipse tooling in JBoss Tools? (And perhaps this version of the plugin was installed by Forge 1.3.3, whereas perhaps Forge 1.4.1 might install a newer version that might not trigger this problem?).
> "rest endpoint-from-entity" fails, ClassNotFoundException: org.apache.log4j.Priority
> ------------------------------------------------------------------------------------
>
> Key: FORGE-1261
> URL: https://issues.jboss.org/browse/FORGE-1261
> Project: Forge
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 1.4.1.Final
> Environment: (Environment-independent, but...) JDK 1.6.0_45, Windows Server 2008 R2
> Reporter: Thomas Maslen
> Priority: Minor
>
> Summary: the org.freemarker module should express a dependency on org.apache.log4j but doesn't
> Workaround: edit modules/org/freemarker/main/module.xml and add the dependency
> The long version:
> "rest endpoint-from-entity" works fine in the version of Forge that is bundled in JBoss Tools 4.1 (Forge 1.3.3).
> However, the DTO-based functionality added in FORGE-1060 looked tasty, so I downloaded Forge 1.4.1 and took it for a spin.
> Regardless of whether I run 1.4.1 standalone or within JBoss Tools (Eclipse), "rest endpoint-from-entity" fails with
> java.lang.ClassNotFoundException: org.apache.log4j.Priority from [Module "org.freemarker:main"
> (I have a complete stack trace but it doesn't add anything profound).
> Once I edited modules/org/freemarker/main/module.xml and added a dependency for the "org.apache.log4j" class, "rest endpoint-from-entity" ran happily and generated the expected classes.
--
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
10 years, 8 months
[JBoss JIRA] (FORGE-1265) Forge 2 Shell should not exit on CTRL-C
by Lincoln Baxter III (JIRA)
Lincoln Baxter III created FORGE-1265:
-----------------------------------------
Summary: Forge 2 Shell should not exit on CTRL-C
Key: FORGE-1265
URL: https://issues.jboss.org/browse/FORGE-1265
Project: Forge
Issue Type: Feature Request
Components: UI - Shell
Affects Versions: 2.0.0.Alpha13
Reporter: Lincoln Baxter III
This should instead clear the buffer, kill the current command (if running) and carriage return to the next line. This may need Aesh changes in order to function.
Problems:
1. Buffer cannot be cleared via Console API.
2. Current running command cannot be killed because it executes in the Aesh Console thread.
--
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
10 years, 8 months
[JBoss JIRA] (FORGE-936) UIValidationContext should allow warning messages
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-936?page=com.atlassian.jira.plugin.... ]
George Gastaldi closed FORGE-936.
---------------------------------
Assignee: George Gastaldi
Fix Version/s: 2.0.0.Alpha14
(was: 2.x Future)
Resolution: Done
> UIValidationContext should allow warning messages
> -------------------------------------------------
>
> Key: FORGE-936
> URL: https://issues.jboss.org/browse/FORGE-936
> Project: Forge
> Issue Type: Enhancement
> Components: UI - API
> Affects Versions: 2.0.0.Alpha4
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.0.0.Alpha14
>
>
> There are some messages that would be nice to be displayed to the user given a specific state inside a UICommand (UIWizard and UIWizardStep as well) that do not interfere with the current flow.
> These messages should only be displayed when no errors are visible.
--
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
10 years, 8 months