[JBoss JIRA] Created: (JBIDE-596) VPE navigation problems
by Aliaksey Nis (JIRA)
VPE navigation problems
-----------------------
Key: JBIDE-596
URL: http://jira.jboss.com/jira/browse/JBIDE-596
Project: JBoss Tools
Issue Type: Bug
Components: Visual Page Editor
Environment: WindowsXP SP2
rhds-win32-1.0.0.alpha.jar
Red Hat Developer Studio
Version: 1.0.0
Build: build 20070711-nightly
JDK 1.5_08
Reporter: Aliaksey Nis
Import attached test page.
Open it with VPE. Select Visual/Source tab
In Visual part navigate elements using keyboard.
Next possible navigation problems found(navigation started from top):
1. Richtoolbar group (panel with 6 icons) - left-right on icons don't work
2. Datalist element - "up" button from it don't work
3. Add ajax... - "up" button don't work
4. PanelBar - "down" button don't work
5. Canon - "up" and "down" buttons don't work
6. Panel (under the Canon element) - "up" button don't work
7. Tab under DataGrid - "up" button don't work
8. Expences - don't work "left", "right" and partially "up" and "down" buttons
9. Drop down menu - "down" button don't work
10.Slider part - "down" button don't work, when it selected
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBDS-726) Installer should deploy Babel langpacks for Eclipse
by Sean Flanigan (JIRA)
Installer should deploy Babel langpacks for Eclipse
---------------------------------------------------
Key: JBDS-726
URL: https://jira.jboss.org/jira/browse/JBDS-726
Project: Developer Studio
Issue Type: Sub-task
Components: installer
Affects Versions: 2.1.0
Reporter: Sean Flanigan
For Developer Studio to be fully translated, we need to package the Babel langpacks for Galileo [1] in our target languages [2]. These langpacks provide translations for Eclipse and related eclipse.org projects (TPTP, datatools, etc). Translations are always being updated, so we will need to be able to update the langpacks without too much mucking around.
NB: This issue is separate from the question of translating the installer's own English text.
To install the langpacks, we just need to extract them all under jbdevstudio/eclipse/dropins (or perhaps dropins/babel for neatness).
Any guidance on how to approach this? eg, the storage of these langpack downloads, repackage as one big zip (better compression?) or keep the many smaller zips, whether we need a script (sh, Ant?) to download the required langpacks automatically, that sort of thing.
[1] http://download.eclipse.org/technology/babel/babel_language_packs/
[2] de, es, fr, ja, pt_BR, zh
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBIDE-4297) Error while performing background reading of database schema
by Krasimir Goutcev (JIRA)
Error while performing background reading of database schema
------------------------------------------------------------
Key: JBIDE-4297
URL: https://jira.jboss.org/jira/browse/JBIDE-4297
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Environment: JBT nightly build 3.1.0.Alpha1/200905091201
eclipse.buildId=N20090426-1232
java.version=1.5.0_15
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=bg_BG
Command-line arguments: -os win32 -ws win32 -arch x86 -clean
Reporter: Krasimir Goutcev
1.Open some ....hbm.xml file
2.Click on table="|" or <column name="|".../> and try CA
org.hibernate.cfg.JDBCBinderException: Duplicate class name 'AllFileGroups' generated for 'org.hibernate.mapping.Table(SYS._ALL_FILE_GROUPS)'. Same name where generated for 'org.hibernate.mapping.Table(SYS._ALL_FILE_GROUPS)'
at org.hibernate.cfg.JDBCBinder.createPersistentClasses(JDBCBinder.java:172)
at org.hibernate.cfg.JDBCBinder.readFromDatabase(JDBCBinder.java:95)
at org.hibernate.cfg.JDBCMetaDataConfiguration.readFromJDBC(JDBCMetaDataConfiguration.java:42)
at org.hibernate.eclipse.nature.HibernateNature$ReadDatabaseMetaData$1.execute(HibernateNature.java:158)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:64)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:95)
at org.hibernate.eclipse.nature.HibernateNature$ReadDatabaseMetaData.run(HibernateNature.java:156)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month
[JBoss JIRA] Created: (JBIDE-4269) Provide a way to filter out elements which will be generated by exporter.
by Dmitry Geraskov (JIRA)
Provide a way to filter out elements which will be generated by exporter.
-------------------------------------------------------------------------
Key: JBIDE-4269
URL: https://jira.jboss.org/jira/browse/JBIDE-4269
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Hibernate
Affects Versions: 3.1.0.M1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M1
Now exporter uses Configuration object to get for example pojo's for generation.
After this it calls generation for each of them.
We need to add some filter for this.
First place for such injection is ArtifactCollector as developer can easily specify subclass of this class and set it to exporter.
Also TemplateProducer which used for files generating always gets ArtifactCollector object in constructor from exporter and has access to it.
I' going to add methods filter(Map context), setFilter(Filter) to ArtifactCollector class and call it when necessary in template producer.
Method 'filter' by default will not filter out anything. Non default realizations should use context map to get any objects which is passed to template producer.
Second variant is to add Filter field to Generic exporter and call for filtering in GenericExporter.exportPOJO() method(or in each realization of ModelIterator.process()).
I prefer first way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 1 month