December 2011 - jbosstools-issues

[JBoss JIRA] Created: (TOOLSDOC-220) JBDS50_0405: 64-bit Windows support documentation

by Isaac Rooskov (JIRA)

JBDS50_0405: 64-bit Windows support documentation ------------------------------------------------- Key: TOOLSDOC-220 URL: https://issues.jboss.org/browse/TOOLSDOC-220 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Critical Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0031: 64-bit Windows support Current status: Committed Description: New documentation for 64-bit Windows support -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-205) JBDS50_0070: JBoss perspective documentation

by Isaac Rooskov (JIRA)

JBDS50_0070: JBoss perspective documentation -------------------------------------------- Key: TOOLSDOC-205 URL: https://issues.jboss.org/browse/TOOLSDOC-205 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0070: JBoss perspective Current status: Committed Description: New documentation for the JBoss perspective -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8032) org.jboss.tools.struts.ui.bot.test :: Skipping tests

by Nick Boldt (JIRA)

org.jboss.tools.struts.ui.bot.test :: Skipping tests ---------------------------------------------------- Key: JBIDE-8032 URL: https://issues.jboss.org/browse/JBIDE-8032 Project: Tools (JBoss Tools) Issue Type: Bug Components: struts/shale, testing Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt For some reason, this plugin's tests are not run. http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... [INFO] --- maven-osgi-packaging-plugin:0.10.0:package-plugin (default-package-plugin) @ org.jboss.tools.struts.ui.bot.test --- [INFO] Building jar: /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.jar [INFO] [INFO] --- tycho-p2-plugin:0.10.0:p2-metadata (default-p2-metadata) @ org.jboss.tools.struts.ui.bot.test --- [INFO] [INFO] --- maven-osgi-test-plugin:0.10.0:test (default-test) @ org.jboss.tools.struts.ui.bot.test --- [INFO] Skipping tests [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ org.jboss.tools.struts.ui.bot.test --- [INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.jar to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.jar [INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/pom.xml to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT.pom [INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/p2content.xml to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT-p2metadata.xml [INFO] Installing /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/sources/tests/org.jboss.tools.struts.ui.bot.test/target/p2artifacts.xml to /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.component--struts/m2-repository/org/jboss/tools/struts/tests/org.jboss.tools.struts.ui.bot.test/3.2.0-SNAPSHOT/org.jboss.tools.struts.ui.bot.test-3.2.0-SNAPSHOT-p2artifacts.xml [INFO] [INFO] --- tycho-p2-plugin:0.10.0:update-local-index (default-update-local-index) @ org.jboss.tools.struts.ui.bot.test --- -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-10331) CDI EL Refactoring and Searchers don't look for ELs in dependent project

by Alexey Kazakov (Created) (JIRA)

CDI EL Refactoring and Searchers don't look for ELs in dependent project ------------------------------------------------------------------------ Key: JBIDE-10331 URL: https://issues.jboss.org/browse/JBIDE-10331 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.M5 Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.3.0.Beta1 EXECUTE: Create two CDI projects: Project1 Project2 (depends on Project1) EXECUTE: Create a @Named bean in Project1: @Named("bean1"). EXECUTE: Create a page in Project2 with EL referenced to the bean: #{bean1} EXECUTE: Try Ctrl+G on @Named("bean1"). FAILURE: The EL from Project2 is not found. The same problem with EL refactoring. And I guess it's not working for pure JSF and Seam2 projects either. -- 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

14 years, 2 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10160) Content assist is broken today

by Viacheslav Kabanovich (Created) (JIRA)

Content assist is broken today ------------------------------ Key: JBIDE-10160 URL: https://issues.jboss.org/browse/JBIDE-10160 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI Affects Versions: 3.3.0.Beta1 Reporter: Viacheslav Kabanovich Assignee: Victor Rubezhny Fix For: 3.3.0.Beta1 EXECUTE: Run content assist #{|} and select a been 'foo'. ASSERT: Result is: #{foo} FAILURE: Result is #{foo]}}" Victor, probably you are in the process of fixing another issue, then please link this issue to it, and resolve together. -- 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

14 years, 2 months

7
8
0 / 0

[JBoss JIRA] (JBIDE-10210) EL refactoring for @Named beans doesn't work properly

by Jaroslav Jankovič (Created) (JIRA)

EL refactoring for @Named beans doesn't work properly ----------------------------------------------------- Key: JBIDE-10210 URL: https://issues.jboss.org/browse/JBIDE-10210 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI, JSF Affects Versions: 3.3.0.M4 Reporter: Jaroslav Jankovič Assignee: Alexey Kazakov Fix For: 3.3.0.Beta1 Sometimes, refactoring @Named annotation doesn't include EL as it should be. Also, another issue, I have found with the steps to reproduce, is disappearing CDI Refactor option in context menu. Workaround exists, it is the same workaround for both issues. -- 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

14 years, 2 months

11
13
0 / 0

[JBoss JIRA] Created: (JBIDE-2735) Error: libapr-1.dll was not found starting JBossAS in JBoss IDE

by hmr_mueller (JIRA)

Error: libapr-1.dll was not found starting JBossAS in JBoss IDE --------------------------------------------------------------- Key: JBIDE-2735 URL: https://jira.jboss.org/jira/browse/JBIDE-2735 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 2.1.2 Environment: Eclipse: 3.3.1.1 OS: Windows JBoss AS 4.2.2GA JBossWeb native Reporter: hmr_mueller When starting the JBossAS 4.2.2GA with JBoss Web native configured from within a JBoss Server configured with the Eclipse IDE (JBoss Tools), I'm getting the error '... libapr-1.dll was not found ..' as a popup. After closing the popup for 3 times the server starts, but does so with errors when starting the Tomcat https connector. When running the run.bat script from the command line everything works fine. Tomcat is configured to used the AprLifecycleListener and a https connector for APR (OpenSSL style configuration). The server launch configuration in eclipse contains the $JBOSS_HOME\bin\native directory in the -Djava.library.path variable The problem seems to be that the libtcnative-1.dll is loading the libapr-1.dll dynamically but since the Path environment variable does not contain the $JBOSS_HOME\bin\native directory the library is not found (setting this is done by the run.bat script). If I put the native directory in the Path variable, the server starts up correctly, so just defining the java.library.path in the launch configuration does not suffice. The problem can be fixed I think, if instead of setting the java.library.path the launch configuration extends the environment (Tab Environment) to contain the native directory in the Path environment variable and changing the class org.jboss.ide.eclipse.as.core.server.internal.launch.AbstractJBossLaunchConfigType to add this to the 'VMRunnerConfiguration' in the 'actualLaunch' method. -- 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

14 years, 2 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-10516) New OpenShift Express application wizard issues

by Jiri Peterka (Created) (JIRA)

New OpenShift Express application wizard issues ----------------------------------------------- Key: JBIDE-10516 URL: https://issues.jboss.org/browse/JBIDE-10516 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: JBDS 5.0.M5a H62, L64 Reporter: Jiri Peterka Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 Steps: Start on New Openshift App wizard on application selection page - Click New - Write app name, click Next, wait... - Then click "Back" Then there are some scenarios that should be tuned: 1. When you click Cancel, you'll get back to table where Application is missing. You have to go back and forward to have it updated. 2. When you click Forward, you'll get message that application is created although wizard wasn't finished (I understand that app was created after "Next" button click" which is strange but so be it) How this can be fixed: 1. Disable Back button when app is created and 2. After cancel, app table list needs to be updated -- 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

14 years, 2 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-10513) management ports in 7.1 as using properties causing automatic detection to fail

by Max Rydahl Andersen (Created) (JIRA)

management ports in 7.1 as using properties causing automatic detection to fail ------------------------------------------------------------------------------- Key: JBIDE-10513 URL: https://issues.jboss.org/browse/JBIDE-10513 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta1 Seems CR1 made the following changes: < <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> < <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> --- > <socket-binding name="management-native" interface="management" port="9999"/> > <socket-binding name="management-http" interface="management" port="9990"/> Two things should happen: 1) we should handle this style 2) we should fallback to default if we can't parse the file instead of creating a "broken" editor. Should add warning about it not being detected, just doing default. -- 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

14 years, 2 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9185) Create preference page for Seam Config validation

by Alexey Kazakov (JIRA)

Create preference page for Seam Config validation ------------------------------------------------- Key: JBIDE-9185 URL: https://issues.jboss.org/browse/JBIDE-9185 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: cdi (jsr-299) Affects Versions: 3.3.0.M2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 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 December 2011