January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10257) Add new set of requirements for usage in SWT Bot tests

by Denis Golovin (Created) (JIRA)

Add new set of requirements for usage in SWT Bot tests ------------------------------------------------------ Key: JBIDE-10257 URL: https://issues.jboss.org/browse/JBIDE-10257 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng, testing Affects Versions: 3.3.0.M5 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 3.3.0.M5 1) riftsaw 2.3.0.final 2) jboss-esb-4.10, 4.9 3) modeshape 2.6.0.Final 4) teiid 7.5, 7.4 -- 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

13 years, 10 months

9
21
0 / 0

[JBoss JIRA] (JBIDE-10692) project example dialog should have the icon used in "central"

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10692: ------------------------------------------- Summary: project example dialog should have the icon used in "central" Key: JBIDE-10692 URL: https://issues.jboss.org/browse/JBIDE-10692 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Reporter: Max Rydahl Andersen Assignee: Fred Bricon Priority: Minor Fix For: 3.3.0.Beta1 the dialog opened with example details does not "inherit" the icon from the actual example. it should. -- 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

13 years, 10 months

4
18
0 / 0

[JBoss JIRA] Created: (JBIDE-9711) AS7 Adapter : Deployment of OSGI projects fails if the temporary folder doesn't exist

by Libor Zoubek (JIRA)

AS7 Adapter : Deployment of OSGI projects fails if the temporary folder doesn't exist ------------------------------------------------------------------------------------- Key: JBIDE-9711 URL: https://issues.jboss.org/browse/JBIDE-9711 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M2 Environment: JBossAS Tools 2.3.0.v20110617-0009-H467-M2 Reporter: Libor Zoubek Assignee: Rob Stryker Fix For: 3.3.0.M3 I noticed that, in the context of JBIDE-9133, for the existing -broken- AS7 server instances the utility projects were not zipped to the deployment area. On the other hand, creating a new server instance fixed the issue. So it seems the temporary folder is only created at the same time as the server instance. It's an issue in the sense that you can not guarantee the temporary folder will exist at deployment time (could have been deleted by the user ...). Solution is to call tempdir.mkdirs() right before the actual deployment occurs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
8
0 / 0

[JBoss JIRA] Created: (JBDS-1673) Installer should align with runtime detection

by Max Rydahl Andersen (JIRA)

Installer should align with runtime detection --------------------------------------------- Key: JBDS-1673 URL: https://issues.jboss.org/browse/JBDS-1673 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: installer Reporter: Max Rydahl Andersen Assignee: Denis Golovin Priority: Blocker Fix For: 5.0.0.M3, 5.0.0.M2 The installer currently has its own form of server detection which generates a file that runtime detection uses to configure specified servers. The detection code is not shared and the workflow/power of them are different. I suggest we either: A) extract the detection code and uses that in both places OR B) change the installer to just ask for directories to scan on every startup which then needs somehow to be read by the runtime detection and then it takes over all this WDYT ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
20
0 / 0

[JBoss JIRA] (JBIDE-10529) test failure in common.verification

by Nick Boldt (Created) (JIRA)

test failure in common.verification ----------------------------------- Key: JBIDE-10529 URL: https://issues.jboss.org/browse/JBIDE-10529 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 After switching to newer target platform (JBIDE-10289), one test is failing: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... {code} [INFO] org.jboss.tools.common.verification.test .......... FAILURE [18.364s] !ENTRY org.eclipse.osgi 2 0 2011-12-18 15:43:22.037 !MESSAGE One or more bundles are not resolved because the following root constraints are not resolved: !SUBENTRY 1 org.eclipse.osgi 2 0 2011-12-18 15:43:22.037 !MESSAGE Bundle initial@reference:file:../../../../../m2-repository/org/eclipse/tycho/org.eclipse.tycho.surefire.junit4/0.13.0/org.eclipse.tycho.surefire.junit4-0.13.0.jar/ was not resolved. !SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037 !MESSAGE Missing imported package org.junit.runner.notification_4.0.0. !SUBENTRY 2 org.eclipse.tycho.surefire.junit4 2 0 2011-12-18 15:43:22.037 !MESSAGE Missing imported package org.junit.runner_4.0.0. {code} Guessing the problem is that the test depends on junit4 but the manifest states only junit (not junit4). -- 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

13 years, 10 months

6
20
0 / 0

[JBoss JIRA] (JBIDE-10390) Support working copy changes in the JAX-RS plugin

by Xavier Coulon (Created) (JIRA)

Support working copy changes in the JAX-RS plugin ------------------------------------------------- Key: JBIDE-10390 URL: https://issues.jboss.org/browse/JBIDE-10390 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 3.3.0.M5 The JAX-RS core plugin should support both changes in the primary copies and in the working copies (ie, the changes done in the Java Editor). As a side effect, the URI Path Templates and other attributes of the JAX-RS endpoints shown in the project explorer should be updated as the user changes his code. -- 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

13 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-9388) Support Seam Servlet module

by Alexey Kazakov (JIRA)

Support Seam Servlet module --------------------------- Key: JBIDE-9388 URL: https://issues.jboss.org/browse/JBIDE-9388 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x http://docs.jboss.org/seam/3/servlet/latest/reference/en-US/html/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9673) Dialog "Show All Generic Beans" should looks like "Open Implementation" in JDT

by Alexey Kazakov (JIRA)

Dialog "Show All Generic Beans" should looks like "Open Implementation" in JDT ------------------------------------------------------------------------------ Key: JBIDE-9673 URL: https://issues.jboss.org/browse/JBIDE-9673 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: CDI extensions Affects Versions: 3.3.0.M3 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.M4 See JBIDE-8692 Now you have to press Ctrl+Click and not to release the button until you click on the needed bean. It's not so convenient. Let's use some dialog like JDT uses in Open Implementation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable

by Martin Malina (JIRA)

Renaming a seam project makes the ds.xml undeployable ----------------------------------------------------- Key: JBIDE-8938 URL: https://issues.jboss.org/browse/JBIDE-8938 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.1.M1 Environment: jbdevstudio-product-eap-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar Mac OS X 10.6 Snow Leopard Reporter: Martin Malina Assignee: Alexey Kazakov If you rename a seam project it fails to deploy again because of failed dependencies: DEPLOYMENTS MISSING DEPENDENCIES: Deployment "persistence.unit:unitName=#SeamWar" is missing the following dependencies: Dependency "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' ** This happens because after the renaming, the ds file becomes undeployable. If you mark it as deployable again, you can then deploy it and also the renamed seam project deploys correctly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
11
0 / 0

[JBoss JIRA] Created: (JBDS-1815) Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline

by Tony Samlal (JIRA)

Context menu misnomer when right clicking on struts-config.xml action-mappings in diagram, tree view or outline --------------------------------------------------------------------------------------------------------------- Key: JBDS-1815 URL: https://issues.jboss.org/browse/JBDS-1815 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: runtime Affects Versions: 4.0.0.GA, 3.0.1.GA, 4.1.0.GA Environment: Windows 7 64 bit w/ Java 1.6.24, Mac OSX 10.6.8 Reporter: Tony Samlal Priority: Minor When right clicking on an existing action mapping to create a local forward or local exception, the only options are global forward and global exception. Using these context menus does indeed create the respective local forward/exception but it is confusing as right clicking on global-exceptions and global-forwards also gives the same options. The local forwards/exceptions should say either "create forward/create exception" as it does in the original Exadel Studio Pro product which Jboss Developer Tools is based on or perhaps just Local Forward/Local Exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
6
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 January 2012