July 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-497) Edit Hibernate configuration Wizard

by Krasimir Goutcev (JIRA)

Edit Hibernate configuration Wizard ----------------------------------- Key: JBIDE-497 URL: http://jira.jboss.com/jira/browse/JBIDE-497 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Tools Reporter: Krasimir Goutcev Assigned To: Max Andersen -- 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

18 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-600) Source page should have the "tag statusbar"

by Max Andersen (JIRA)

Source page should have the "tag statusbar" ------------------------------------------- Key: JBIDE-600 URL: http://jira.jboss.com/jira/browse/JBIDE-600 Project: JBoss Tools Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen The "tag" statusbar (the line that shows you the nested main elements - e.g. html, h:form, table, tr, td if you are in a TD inside a tr, inside a table and so on) is only visible when doing visual editing, not when just editing source. this should be available (as an option) when editing source too in my opinion. -- 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

18 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-471) JBoss IDE beta update site installation rejects Eclipse 3.3 Mx (... requires feature "org.eclipse.platform (3.2.0)", or equivalent)

by Arjan van Bentem (JIRA)

JBoss IDE beta update site installation rejects Eclipse 3.3 Mx (... requires feature "org.eclipse.platform (3.2.0)", or equivalent) ----------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-471 URL: http://jira.jboss.com/jira/browse/JBIDE-471 Project: JBoss IDE Issue Type: Bug Components: JBossIDE Core Affects Versions: 2.0.0.Beta2 Environment: Win32, Eclipse 3.3 M6 Reporter: Arjan van Bentem Assigned To: Marshall Culpepper JBoss IDE 2.0.0.Beta2 installs fine when using the update site http://download.jboss.org/jbosside/updates/development/ in Eclipse 3.2.x. However, apparently it has some hardcoded reference to a specific Eclipse version number: when using the same update site URL in Eclipse 3.3 M6 then installation halts with the errors listed at the end of this issue. Maybe somehow relaxing the required Eclipse version will simply enable using the update site in Eclipse 3.3.x as well? ONLY for the sake of the archives: I did not try installing the latest version from CVS. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=102699 notes something about the dependencies in feature.xml. However, note that simply changing match="equivalent" in feature.xml is NOT sufficient. For example, the following will NOT work: - install Web Standard Tools (WST) and J2EE Standard Tools (JST) using Help, Software Updates, Find and Install - download a non-bundle version (such as JBossIDE-2.0.0.Beta2-ALL.zip) and unzip - in the unzipped folder, in each feature.xml file, replace each occurrence match="equivalent" with match="greaterOrEqual" - add a local update site using Help, Software Updates, Find and Install, and make it point to the "eclipse" subfolder of the unzipped archive (note that Eclipse caches the feature details; Eclipse needs to be restarted when changing feature.xml on the fly). Now, all SEEMS to install fine, but it does not run as expected: some plugins are missing, and when in configuration/config.ini the line "eclipse.product=org.eclipse.sdk.ide" is replaced with "eclipse.product=org.jboss.ide.eclipse.product.product" and "jbosside.version=2.0.0.Beta2" then Eclipse does not startup (logs are created though). JST Common Core (1.5.1.v200608082030--0842282_363739) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Server Core (1.5.1.v200608082030--2PD88P8UBJx787) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Web Core (1.5.1.v200608082030--87cMN7NRVeVWXd) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Enterprise Core (1.5.1.v200609051533--2PD88P8YAGDADJ) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JST Enterprise UI (1.5.1.v200608082030-pEBq_haA1H4sJf6) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST Server Core (1.5.1.v200608082030------1G955G5L7D) requires feature "org.eclipse.rcp (3.2.0)", or equivalent. WST XML Core (1.5.1.v200608082030--3YIAAYAjGLENFH) requires feature "org.eclipse.rcp (3.2.0)", or equivalent. WST Web Services Core (1.5.1.v200608082030--4hNDDhDvGTJSLf) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST Web Core (1.5.1.v200608082030--4hNDDhDvKRFXQM) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST Relational Database Core (1.5.1.v200608082030--3YIAAYAeEKFTFU) requires feature "org.eclipse.platform (3.2.0)", or equivalent. WST Relational Database Adapters (1.5.1.v200608082030--Cq0bcpdJw4teC8) requires feature "org.eclipse.platform (3.2.0)", or equivalent. JBossIDE JBossAS Adapter Feature (1.0.0.Beta2) requires plug-in "org.eclipse.ui.workbench.texteditor (3.2.0)", or equivalent. -- 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

18 years, 8 months

3
4
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-390) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: JBIDE-390 URL: http://jira.jboss.com/jira/browse/JBIDE-390 Project: JBoss IDE Issue Type: Feature Request Reporter: Rajesh Rajasekaran Fix For: 1.6.1, 2.0.0.Beta3 Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-627) Bring feature.xml in sync with license/copyright/links etc.

by Max Andersen (JIRA)

Bring feature.xml in sync with license/copyright/links etc. ----------------------------------------------------------- Key: JBIDE-627 URL: http://jira.jboss.com/jira/browse/JBIDE-627 Project: JBoss Tools Issue Type: Task Components: Build/Releng Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Assigned To: Marshall Culpepper Priority: Blocker Most of our feature.xml files still has zero content in the license and copyright area; we need to fix that. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-606) Seam component view should provide "package" mode view

by Max Andersen (JIRA)

Seam component view should provide "package" mode view ------------------------------------------------------ Key: JBIDE-606 URL: http://jira.jboss.com/jira/browse/JBIDE-606 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Max Andersen Currently the seam component view shows a list of scopes and then the fully qualified variable names for the components. An (in some cases) better alternative would be to have the names listed like in package view. e.g. like a tree org jboss seam EntityManager mail Mailer user or flat tree org.jboss.seam.EntityManager org.jboss.seam.Mailer user and then the icon would indicate the scope. Makes it easier to find the component. -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-502) JBossIDE Packaging Builder: Project --> clean deletes all files of a directory, not only the archive-file

by Perry Rhodan (JIRA)

JBossIDE Packaging Builder: Project --> clean deletes all files of a directory, not only the archive-file --------------------------------------------------------------------------------------------------------- Key: JBIDE-502 URL: http://jira.jboss.com/jira/browse/JBIDE-502 Project: JBoss Tools Issue Type: Bug Components: Build System (Releng) Affects Versions: 2.0.0.Beta3, 2.0.0.GA Environment: Windows-XP, Eclipse 3.3 Europa, JBossTools-200706300254-nightly-ALL-win32.zip Reporter: Perry Rhodan Assigned To: Marshall Culpepper Via the "Project archives" view i configured two archives to be created: --application-ejb.jar --application.ear The application-ejb.jar holds most of the java-classes and will be created into a sub-directory /library. In this directory you wil find additional other application-relevant libraries too. The application.ear will zip the whole contents of /library-directory to an ear-file and save this ear under a directory /release. So far so good, the project has now assigned the JBossIDE Packaging Builder to it's builders. If i now make a Project-->clean from eclipse, then not only the application-ejb.jar will be deletet (as i would expect), but also the wohle other libraries and files and even all "hidden" informations, like .svn-subdirectories in directory /library will be deleted. This is definitely not the correct handling of cleaning the archive-files. The project is after such a clean badly damaged and can only be restored by a fresh checkout. -- 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

18 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-628) table names handled badly in diagram

by Max Andersen (JIRA)

table names handled badly in diagram ------------------------------------ Key: JBIDE-628 URL: http://jira.jboss.com/jira/browse/JBIDE-628 Project: JBoss Tools Issue Type: Bug Components: Hibernate Reporter: Max Andersen Assigned To: Mikle Dryakhlenkov Priority: Critical I noticed that the table names in the diagram was on the form <schemaname>.<tablename>, but this result in default mapping for a customer to show up as e.g. null.Customer Looking throuhg the code I found numerous references to .getSchema() and none of them handled the case of null...we need to fix that (and centralize it instead of having that duplicated 9 times) Also remember that catalog can be part of the "id" of the table names and that catalog and schema both can be null. -- 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

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Resolved: (JBIDE-548) After adding Facet with equal to Attribute name Attribute disappeares from faces-config tree.

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-548?page=all ] Viacheslav Kabanovich resolved JBIDE-548. ----------------------------------------- Resolution: Done org.jboss.tools.jsf.model.impl.FacetObjectImpl > After adding Facet with equal to Attribute name Attribute disappeares from faces-config tree. > --------------------------------------------------------------------------------------------- > > Key: JBIDE-548 > URL: http://jira.jboss.com/jira/browse/JBIDE-548 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: ExadelStudioPro4 > Environment: Windows XP > RedHatDeveloperStudio build-346 > Reporter: Anton Klimkovich > Assigned To: Viacheslav Kabanovich > Priority: Minor > Attachments: faces-config source.png, faces-config tree.png > > > JSF project > 1 Open faces-config.xml on tree tab. > 2 Create new Render Kit (RenderKit)->Renderer -> Attribute (EqualName - name of attribute) > 3 Click on Source tab > 4 Add to source to <render kit > string: <facet><facet-name>EqualName</facet-name></facet> > 5 Click to Tree tab > There is no any error message about equal name of Facet and Attribute. Also after adding facet with equal to attribute name Attribute disappeares from faces-config tree. > It's reprodused not only for Renderers attributes. > ScreenShoots attached. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-595) Close or delete a project and xml editors gives NPE's

by Max Andersen (JIRA)

Close or delete a project and xml editors gives NPE's ----------------------------------------------------- Key: JBIDE-595 URL: http://jira.jboss.com/jira/browse/JBIDE-595 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen Assigned To: Viacheslav Kabanovich Normally editors just states that the file does not exist, but here we are comparing null with some current text... java.lang.NullPointerException at org.jboss.tools.common.model.ui.texteditors.XMLTextEditorComponent.isEqualText(XMLTextEditorComponent.java:223) at org.jboss.tools.common.model.ui.texteditors.TextEditorSupport.update(TextEditorSupport.java:46) at org.jboss.tools.common.model.ui.texteditors.TextEditorSupport.setObject(TextEditorSupport.java:33) at org.jboss.tools.common.model.ui.texteditors.XMLTextEditorComponent.setObject(XMLTextEditorComponent.java:81) at org.jboss.tools.common.editor.ObjectMultiPageEditor.initEditors(ObjectMultiPageEditor.java:457) at org.jboss.tools.jst.web.ui.editors.WebCompoundEditor.doCreatePages(WebCompoundEditor.java:29) at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:220) at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:283) at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:102) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:426) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:592) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:299) -- 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

18 years, 8 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2007