March 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8549) ProblemBuffer class used not supported API on eclipse 3.7

by Maxim Areshkau (JIRA)

ProblemBuffer class used not supported API on eclipse 3.7 --------------------------------------------------------- Key: JBIDE-8549 URL: https://issues.jboss.org/browse/JBIDE-8549 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.3.0.M1 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Priority: Critical Fix For: 3.3.0.M1 https://svn.jboss.org/repos/jbosstools/trunk/common/plugins/org.jboss.too... used API which not supported in eclipse 3.7 and cause compilation errors. Its only one problem to run VPE on eclipse 3.7 M5. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8236) Refactoring: rename console configuration as refactoring change

by Dmitry Geraskov (JIRA)

Refactoring: rename console configuration as refactoring change --------------------------------------------------------------- Key: JBIDE-8236 URL: https://issues.jboss.org/browse/JBIDE-8236 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.2.x Test case: 1. create jpa project 2. rename it console configuration 3. go to project properties->Hibernate settings OBSERVE: the console configuration name set to <None> EXPECTED: the console configuration name changed -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8270) Create CDI Perspective

by Denis Golovin (JIRA)

Create CDI Perspective ---------------------- Key: JBIDE-8270 URL: https://issues.jboss.org/browse/JBIDE-8270 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Fix For: 3.3.0.M1 It should contain references to CDI related views and New popup menu filled with CDI Artifact new wizards -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-8266) Disable inline editing for "Interfaces" lists in CDI wizards

by Denis Golovin (JIRA)

Disable inline editing for "Interfaces" lists in CDI wizards ------------------------------------------------------------ Key: JBIDE-8266 URL: https://issues.jboss.org/browse/JBIDE-8266 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299), UpStream Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Alexey Kazakov Priority: Optional Fix For: 3.3.0.M1 When user clicks on item in Interfaces list it switches in inline edition mode so interface name can be changed. It looks like New Java Class Wizard Has the same problem. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8499) Provide support for Seam 3 transactions

by Martin Gencur (JIRA)

Provide support for Seam 3 transactions --------------------------------------- Key: JBIDE-8499 URL: https://issues.jboss.org/browse/JBIDE-8499 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Martin Gencur Assignee: Alexey Kazakov Currently, when I import existing maven project with Seam Transactions, the editor complains about incorrect tag in beans.xml file. The transactions implementation is currently in the seam-persistence module (http://sfwk.org/Seam3/PersistenceModule). I imported a project from Remoting module which uses this transaction management (by including the persistence's jars. It's the Validation example (https://github.com/seam/remoting/tree/master/examples/validation). After importing these project into Eclipse it complains about the following lines in the beans.xml: <p:SeSynchronizations> <s:modifies/> </p:SeSynchronizations> The error message is simply something like "Invalid content was found starting with element 'p:SeSynchronizations' ... " The whole beans.xml: <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:p="urn:java:org.jboss.seam.persistence.transaction" xmlns:s="urn:java:ee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/beans_1_0.xsd"> <p:SeSynchronizations> <s:modifies/> </p:SeSynchronizations> <interceptors> <class>org.jboss.seam.persistence.transaction.TransactionInterceptor</class> </interceptors> </beans> Note that there was a discussion about moving the transaction management into another module. Ask module lead about this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8352) Launch instance wizard: cannot launch instance

by Andre Dietisheim (JIRA)

Launch instance wizard: cannot launch instance ---------------------------------------------- Key: JBIDE-8352 URL: https://issues.jboss.org/browse/JBIDE-8352 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBIDE-8615) AS7 server adapter: Start/Stop is confusing

by Andre Dietisheim (JIRA)

AS7 server adapter: Start/Stop is confusing ------------------------------------------- Key: JBIDE-8615 URL: https://issues.jboss.org/browse/JBIDE-8615 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.0.M1 The as7 server adapter offers start and stop. Start and stop are not related to starting/stopping the server. What is their purpose? Are they necessary? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8454) Invalid sites dialog isn't shown when starting New Project Example wizard

by Snjezana Peco (JIRA)

Invalid sites dialog isn't shown when starting New Project Example wizard ------------------------------------------------------------------------- Key: JBIDE-8454 URL: https://issues.jboss.org/browse/JBIDE-8454 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 The issue can be reproduced by creating a user site showing to a non-existing project example xml file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8419) Runtimes aren't visible immediately after adding via JBT Runtime Detection

by Jiri Peterka (JIRA)

Runtimes aren't visible immediately after adding via JBT Runtime Detection -------------------------------------------------------------------------- Key: JBIDE-8419 URL: https://issues.jboss.org/browse/JBIDE-8419 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtimes Affects Versions: 3.2.0.CR2 (tentative) Environment: JBDS 4.0.0.CR4 H173, Linux 64 Reporter: Jiri Peterka Runtimes aren't visible immediately after adding via JBoss Tools Runtime Detection which can be confusing: 0. New workspace 1. Preferences -> JBoss Tools Runtime -> JBoss Tools Runtime Detection 2. Add, select folder with runtimes 3. Have checked all runtimes, OK for adding 4. Click on JBoss AS/Seam/Drools/jBPM Link It's expected that newly added runtimes are visible immediately not after ok and going back to Preferences -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8554) Compilation failure for 3.3.indigo branch :: tests

by Nick Boldt (JIRA)

Compilation failure for 3.3.indigo branch :: tests -------------------------------------------------- Key: JBIDE-8554 URL: https://issues.jboss.org/browse/JBIDE-8554 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.3.0.M1 Reporter: Nick Boldt http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_3.3.indigo.continuou... [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.jboss.tools.ui.bot.ext: Compilation failure: Compilation failure: [ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTBotExt.java (at line 132):[-1,-1] [ERROR] public SWTBotScaleExt scale() { [ERROR] ^^^^^^^^^^^^^^ [ERROR] The return type is incompatible with SWTBot.scale() [ERROR] [ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_3.3.indigo.continuous/sources/tests/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTBotExt.java (at line 136):[-1,-1] [ERROR] public SWTBotScaleExt scale(int index) { [ERROR] ^^^^^^^^^^^^^^ [ERROR] The return type is incompatible with SWTBot.scale(int) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
4
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 March 2011