[JBoss JIRA] (JBDS-1887) "Create a new Drools Runtime" - creates an empty runtime
by Len DiMaggio (Created) (JIRA)
"Create a new Drools Runtime" - creates an empty runtime
--------------------------------------------------------
Key: JBDS-1887
URL: https://issues.jboss.org/browse/JBDS-1887
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SOA Platform
Affects Versions: 4.1.1.M2, 5.0.0.M3
Environment: Version: 4.1.1.M2
Build id: v20111006-0040-H1061-M2
Build date: 20111006-0040
Reporter: Len DiMaggio
Under
Window->Preferences->Drools->Installed Drools Runtimes
The dialog presented to the user (see attached) screenshot - successfully enables the user to create a runtime by referencing the install directory of a Drools runtime. The user defines a name for the new runtime, specifies the install directory, and presses "OK."
If, however, the user opts to create a new runtime, indicates an empty directory for the new runtime, and presses "Create a new Drools Runtime" - an empty runtime is created - nothing is written to disk.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBDS-1850) Non-fatal warnings written to shell when usage agreement
by Len DiMaggio (JIRA)
Non-fatal warnings written to shell when usage agreement
--------------------------------------------------------
Key: JBDS-1850
URL: https://issues.jboss.org/browse/JBDS-1850
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Usage Reporting
Affects Versions: 5.0.0.M3
Environment: Version: 5.0.0.M3
Build id: v20110915-2216-H26-M3
Build date: 20110915-2216
RHEL6
Reporter: Len DiMaggio
Priority: Minor
Fix For: 5.0.0.M4
The WARNINGs are:
[ldimaggi@ldimaggi studio]$ ./jbdevstudio
LoadPlugin: failed to initialize shared library /home/ldimaggi/.mozilla/plugins/npatgpc.so [/home/ldimaggi/.mozilla/plugins/npatgpc.so: wrong ELF class: ELFCLASS32]
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
(npviewer.bin:29389): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-8427) Really slow deployment while dialog visible
by henk de boer (JIRA)
Really slow deployment while dialog visible
-------------------------------------------
Key: JBIDE-8427
URL: https://issues.jboss.org/browse/JBIDE-8427
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.2.0.CR1
Environment: Mac OS X 10.6.4, Eclipse 3.6.1 (64 bits)
Reporter: henk de boer
When a project is deployed using the Jboss tools WTP adapter with the progress dialog visible the operation is really slow. As soon as the operation is send to the background it's fast again.
It seems the code tries to display every file name on screen, which results in a maximum copy rate of 60 files/second (screen refresh).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months