September 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4233) Support for fine grained pages.xml editing

by Max Rydahl Andersen (JIRA)

Support for fine grained pages.xml editing ------------------------------------------ Key: JBIDE-4233 URL: https://jira.jboss.org/jira/browse/JBIDE-4233 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Critical Fix For: 3.1.0.M3 Add support for fine grained page.xml (now we have support for coarse grained pages.xml) in the graphical pages.xml editor. I imagine an additonal tab or a toggle on the current tab that when enabled shows not just the pages that are in the single file, but also includes any info from other *.page.xml files. In the first iteration we can just make this a read only mode for any external files and then double click for editing (maybe that will be too cumbersome for the users ?) -- 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

12 years, 1 month

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-4727) Support distribution defining "New Project" dependencies

by Pete Muir (JIRA)

Support distribution defining "New Project" dependencies -------------------------------------------------------- Key: JBIDE-4727 URL: https://jira.jboss.org/jira/browse/JBIDE-4727 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Pete Muir Summary: Move the responsibility for defining a "New Seam Project"'s dependencies (libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to define the dependencies. Use Maven POM profiles to support different use cases for Seam projects. Reason: Currently JBoss Tools defines the project dependencies which causes issues very time Seam changes either the dependency set of a new seam project, or the layout of libraries in the distribution. Use Maven 2 POM format as it is already a well defined and understood model. Use of Maven POM profiles can further increase the flexibility and support various use cases for Seam (for example, Seam with jBPM or Seam with ICEFaces). Details: JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml, ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite modules of an EAR project. The standard Maven scopes are used: compile to indicate compile/runtime dependencies of the project, test to indicate extra dependencies required in the test project. Maven profiles are used to define additional dependency sets for new seam projects, allowing the user to optionally add extra dependencies to his project. To make this extensible, and not require JBossTools to use a well-known list of profile ids, an xml namespace will be used to add additional metadata to the profile. This allows JBossTools to identify the possible profiles: <profile> <id>drools5</id> <jbt:profile> <jbt:description>Drools 5 support (Tech Preview)</jbt:description> </jbt:profile>  </profile> <profile> <id>ICEFaces</id> <jbt:profile> <jbt:description>ICEFaces</jbt:description> </jbt:profile>  </profile> JBossTools can recognize the jbt:profile element, and use the jbt:description element to as a descriptive element to present to the user: [x] ICEFaces [x] Drools 5 support (Tech Preview) displayed in the New Seam Project Wizard. We should allow for additional information to be placed in the POM and in the future beyond dependency information. For example, additional configuration files to include in the generated project, however this is not a critical feature. We should also consider allowing JBoss Tools to retrieve the POMs from a Maven repository. This would require a user to simply specify the version of Seam they require, and have JBoss Tools download the seam-gen artifact containing all templates and resources. -- 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

12 years, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4791) Properties list in Properties view disappears when the user clicks a tab in CSS Properties view

by Olga Chukhutsina (JIRA)

Properties list in Properties view disappears when the user clicks a tab in CSS Properties view ----------------------------------------------------------------------------------------------- Key: JBIDE-4791 URL: https://jira.jboss.org/jira/browse/JBIDE-4791 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M3 Environment: Ubuntu 8.10, JBossTools revision 17062 Reporter: Olga Chukhutsina Assignee: Sergey Dzmitrovich Properties list disappears from Properties view when the user clicks tabs in CSS Properties view. Steps: Choose some selector in CSS file>Text/Font tab is opened in CSS Properties view by default and the properties list in Properties view is displayed>choose another tab in CSS Properties view(e.g Background )>now properties list in Properties view is not shown any more -- 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

12 years, 1 month

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-6085) Implement Validation of ESB config file

by Viacheslav Kabanovich (JIRA)

Implement Validation of ESB config file --------------------------------------- Key: JBIDE-6085 URL: https://jira.jboss.org/jira/browse/JBIDE-6085 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.1.0.GA Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.2.next We have no validation implemented for consistency of objects, especially of actions that formally may be supplied by any set of properties while each action class requires a specific configuration. We should implement validation similar to that we have for beans in Seam and CDI. Documentation on ESB contains many rules on consistency of ESB objects not covered by simply complying with xml schema. -- 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

12 years, 1 month

4
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4973) OpenOn for <xsi:schemaLocation "|" > in components.xml doesn't open a separate file with schema.

by Anton Klimkovich (JIRA)

OpenOn for <xsi:schemaLocation "|" > in components.xml doesn't open a separate file with schema. ------------------------------------------------------------------------------------------------ Key: JBIDE-4973 URL: https://jira.jboss.org/jira/browse/JBIDE-4973 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, Seam Affects Versions: 3.1.0.M4 Reporter: Anton Klimkovich Assignee: Alexey Kazakov Priority: Minor EXECUTE: Create Seam 2.0 or Seam 2.2 web project EXECUTE: Open components.xml EXECUTE: Make OpenOn on xsi:schemaLocation= "... http://jboss.com/products/seam/core-2.0.xsd for example FAILURE: File with schema isn't found EXECUTE: Make OpenOn on xsi:schemaLocation= "http://jboss.com/products/seam/core " ASSERT: Web Browser with JBoss.com page is opened; XML schema description should exists FAILURE: JBoss.com is opened with 404 - Page Not Found error on the page. -- 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

12 years, 1 month

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4920) New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Habirnate Console Configuration Step after '<Back' is pressed

by Denis Golovin (JIRA)

New Hibernate Console Configuration File (cfg.xml) file doesn't save state for Classpath tab in New Habirnate Console Configuration Step after '<Back' is pressed ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4920 URL: https://jira.jboss.org/jira/browse/JBIDE-4920 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M4 Reporter: Denis Golovin Priority: Trivial 1. EXECUTE: Create Java Project 2. EXECUTE: Select Java Project from step 1 and invoke New Hibernate Configuration file Wizard 3. EXECUTE: Go through all steps to New Hibernate Console Configuration step 4. EXECUTE: Select 'Classpath' tab, remove 'default classpath' entry 5. EXECUTE: Press '<Back' 6. EXECUTE: Press 'Next>' and select 'Classpath' tab 7. ASSERT: State is the same as it was after 4 step 4 above executed Now it restores default values -- 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

12 years, 1 month

5
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4455) Add JUnit tetst for org.hibernate.eclipse.mapper.editors.reveng

by Denis Golovin (JIRA)

Add JUnit tetst for org.hibernate.eclipse.mapper.editors.reveng --------------------------------------------------------------- Key: JBIDE-4455 URL: https://jira.jboss.org/jira/browse/JBIDE-4455 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0.M2 1. Test editor is opened on reveng XML file. 2. Test editor is able to process all kinds of elements in xml file. tests should try to achieve at least 100% classes coverage for org.hibernate.eclipse.mapper.editors.reveng package. -- 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

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3894) Add JUnit test for org.jboss.tools.hibernate.ui.xml.editor

by Denis Golovin (JIRA)

Add JUnit test for org.jboss.tools.hibernate.ui.xml.editor ---------------------------------------------------------- Key: JBIDE-3894 URL: https://jira.jboss.org/jira/browse/JBIDE-3894 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: QA Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 -- 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

12 years, 1 month

3
15
0 / 0

[JBoss JIRA] Created: (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components

by Denis Golovin (JIRA)

Create Stress JUnit Test Suite withch is included all available JUnit tests from all components ----------------------------------------------------------------------------------------------- Key: JBIDE-3937 URL: https://jira.jboss.org/jira/browse/JBIDE-3937 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 Why we need this? The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems. It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite. -- 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

12 years, 1 month

1
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3861) Add JUnit tests for org.jboss.tools.seam.ui.search package

by Denis Golovin (JIRA)

Add JUnit tests for org.jboss.tools.seam.ui.search package ---------------------------------------------------------- Key: JBIDE-3861 URL: https://jira.jboss.org/jira/browse/JBIDE-3861 Project: Tools (JBoss Tools) Issue Type: Task Affects Versions: 3.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.1.0 -- 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

12 years, 1 month

2
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2010