April 2011 - jbosstools-issues - Jboss List Archives

[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, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8680) Rename Seam UI artifacts to Seam 2.

by Alexey Kazakov (JIRA)

Rename Seam UI artifacts to Seam 2. ----------------------------------- Key: JBIDE-8680 URL: https://issues.jboss.org/browse/JBIDE-8680 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M1 Since Seam 3.0 final has been released and we are working on support of Seam 3 extensions it's time to rename our Seam tools to Seam 2 not to confuse users. We should update UI stuff such as Wizard titles, perspective, views, editors, etc. And BTW the component name in JIRA :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7141) Provide details about selected runtime in the facet configuration dialog

by Lukas Jungmann (JIRA)

Provide details about selected runtime in the facet configuration dialog ------------------------------------------------------------------------ Key: JBIDE-7141 URL: https://jira.jboss.org/browse/JBIDE-7141 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.1.1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick Attachments: screenshot.png It would be nice if we could tell user some details about JBossWS runtime he is going to use. See attached screenshot for how it could look like -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5045) JSF 2: Support annotated manage beans in EL

by Alexey Kazakov (JIRA)

JSF 2: Support annotated manage beans in EL ------------------------------------------- Key: JBIDE-5045 URL: https://jira.jboss.org/jira/browse/JBIDE-5045 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: LATER We have to create JSF builder to load annotated manage beans to provide JSF model which should be used be JSF EL Resolver. -- 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, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8407) Struts Diagram Print Dialog is broken

by Denis Golovin (JIRA)

Struts Diagram Print Dialog is broken ------------------------------------- Key: JBIDE-8407 URL: https://issues.jboss.org/browse/JBIDE-8407 Project: Tools (JBoss Tools) Issue Type: Bug Components: struts/shale Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Denis Golovin Attachments: screenshot109.png Dialog doesn't show preview for diagram and there are no buttons in the bottom. It always says there is only one empty page. !screenshot109.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6953) Disable Usage Reporting in Tests

by Andre Dietisheim (JIRA)

Disable Usage Reporting in Tests -------------------------------- Key: JBIDE-6953 URL: https://jira.jboss.org/browse/JBIDE-6953 Project: Tools (JBoss Tools) Issue Type: Release Environment: CI, Tests Reporter: Andre Dietisheim Assignee: Denis Golovin Priority: Blocker Fix For: 3.2.0.M2 the UI tests we run should not trigger hits in our usage tracking. The plugin has a preferences setting that disables reporting. It looks like we disable reporting for our UI test by having a custom config.ini for our UI tests. The preference settings is: "allowUsageReportPreference" It is in the Configuration Scope (common to all workbenches of a particular eclipse instance). For further lookup @see IUsageReportPreferenceConstants#USAGEREPORT_ENABLED_ID -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6569) Make git repo available for JBoss Tools

by Max Rydahl Andersen (JIRA)

Make git repo available for JBoss Tools --------------------------------------- Key: JBIDE-6569 URL: https://jira.jboss.org/browse/JBIDE-6569 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: LATER I think it would be useful to explore how to make a git-svn repo available for jboss tools trunk. Opening this issue for keeping track of what have been attempted so far. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3191) Cannot run tests when building JMX by itself

by Nick Boldt (JIRA)

Cannot run tests when building JMX by itself -------------------------------------------- Key: JBIDE-3191 URL: https://jira.jboss.org/jira/browse/JBIDE-3191 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Affects Versions: 3.0.0.beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.0.0.cr1 Using /devstudio-trunk/releng/org.jboss.ide.eclipse.releng/hudson/build.sh with the following parameters changed, JMX will build on its own: builders=jmx nightlyBuildSteps=standalone.product,reports,build-results,update-site Turning tests back on, however, the build fails: builders=jmx nightlyBuildSteps=standalone.product,reports,tests,build-results,update-site [java] Java Result: 13 [echo] [echo] The builder <b>tests</b> failed to compile with the following results:<br/><br/> [echo] [echo] <pre> [echo] BUILD FAILED [echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:24: The following error occurred while executing this line: [echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/build.xml:64: The following error occurred while executing this line: [echo] /opt/public/jbt-jbds/nightly-with-tests/org.jboss.ide.eclipse.releng/builders/tests/customTargets.xml:13: The following error occurred while executing this line: [echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/clean-eclipse/eclipse/plugins/org.eclipse.pde.build_3.4.1.R34x_v20080805/scripts/genericTargets.xml:88: Bundle org.jboss.tools.common.kb.test_0.0.0 failed to resolve.: [echo] Missing required plug-in org.jboss.tools.common_0.0.0. [echo] Missing required plug-in org.jboss.tools.common.kb_0.0.0. [echo] Missing required plug-in org.jboss.tools.common.test_0.0.0. [echo] Missing required plug-in org.jboss.tools.common.projecttemplates_0.0.0. [echo] [echo] [echo] Total time: 3 minutes 2 seconds [echo] </pre> [echo] /opt/public/jbt-jbds/nightly-with-tests/jbds-build/3.0.0.CR1/200811132054/tests BUILD FAILED /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/buildNightly.xml:12: The following error occurred while executing this line: /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:56: The following error occurred while executing this line: /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:27: The following error occurred while executing this line: /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/build.xml:37: The following error occurred while executing this line: /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:76: The following error occurred while executing this line: /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:105: The following error occurred while executing this line: /home/nboldt/eclipse/workspace-jboss/devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/product/productBuild.xml:261: Specify at least one source - a file or a resource collection. Total time: 23 minutes 21 seconds I suspect this is a result of the tests being coupled together, such that they depend on the whole build (builders=jmx,examples,drools-ide,archives,richfaces,jbpm-convert,freemarker,hibernate-tools,struts,jbpm,as,seam,esb,ws,birt,portlet,smooks) and its output. Would there be value in incrementally splitting each build's tests out so they can run independently? eg., builders=jmx,jmx-tests nightlyBuildSteps=standalone.product,reports,tests-jmx,build-results,update-site -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8452) JBoss Maven Git integration

by Snjezana Peco (JIRA)

JBoss Maven Git integration --------------------------- Key: JBIDE-8452 URL: https://issues.jboss.org/browse/JBIDE-8452 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco It will enable us to import a maven project from a git repository and create project examples using examples from a git repository directly. As to the seam examples, it will be enough to add an entry to the project examples xml file. This feature will require EGit - http://www.eclipse.org/egit -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
13
0 / 0

[JBoss JIRA] Created: (JBIDE-8651) Revert workaround for wrong implementation of WTP's ElementImpl.getAttribute(String)

by Yahor Radtsevich (JIRA)

Revert workaround for wrong implementation of WTP's ElementImpl.getAttribute(String) ------------------------------------------------------------------------------------ Key: JBIDE-8651 URL: https://issues.jboss.org/browse/JBIDE-8651 Project: Tools (JBoss Tools) Issue Type: Task Components: Visual Page Editor core Affects Versions: 3.3.0.M1 Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 3.3.x Workaround for JBIDE-8649 (https://bugs.eclipse.org/272378 ) should be reverted when this propblen is fixed on WTP. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
3
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 April 2011