July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6174) Folding of exceptions in Console tab

by Ryszard Kozmik (JIRA)

Folding of exceptions in Console tab ------------------------------------ Key: JBIDE-6174 URL: https://jira.jboss.org/jira/browse/JBIDE-6174 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Ryszard Kozmik It would be really helpful to read server logs if exceptions were folded into one line with a plus symbol next to it that would show the whole exception on a click. As we all know sometimes apps are very "talkactive" in case of throwing exceptions and browsing through them to find the exact one that you search for is irritating and folding would greatly help. It can be even a simple folding based on indentation of lines, you can do such set up with GVIM / VIM but it's not so convenient to use and first of all it's not in your favourite IDE ;-) -- 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

15 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBDS-1150) Installer chooses 64-bit VM as the default VM even with 32-bit distribution

by Trustin Lee (JIRA)

Installer chooses 64-bit VM as the default VM even with 32-bit distribution --------------------------------------------------------------------------- Key: JBDS-1150 URL: https://jira.jboss.org/jira/browse/JBDS-1150 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 3.0.0.CR2 Environment: Windows 7 x64 Ultimate Edition Reporter: Trustin Lee At step 4 of 11, the default Java VM path points to C:\Program Files\Java\jre6. However, it is a 64-bit VM which does not work with the 32-bit distribution. If the default system JVM is 64-bit, the installer should ask user to specify the correct VM path or try to guess more paths (e.g. C:\Program Files (x86)\Java\jre6). Otherwise, JBDS will fail on startup even if the installation succeeds. -- 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

15 years, 2 months

6
17
0 / 0

[JBoss JIRA] Created: (JBIDE-6676) Warn if remove method of SFSB is called on non dependent scoped bean

by Pete Muir (JIRA)

Warn if remove method of SFSB is called on non dependent scoped bean -------------------------------------------------------------------- Key: JBIDE-6676 URL: https://jira.jboss.org/browse/JBIDE-6676 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi (jsr-299) Reporter: Pete Muir Assignee: Alexey Kazakov "If a session bean is a stateful session bean, and the scope is not @Dependent, the application may not directly call any EJB remove method of any instance of the session bean. If the application directly calls an EJB remove method of any contextual instance of a session bean that is a stateful session bean and declares any scope other than @Dependent, an UnsupportedOperationException is thrown" JBT should warn or error if a user does this. -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6044) Include BPEL Editor on JBT Build Results Page

by Brian Fitzpatrick (JIRA)

Include BPEL Editor on JBT Build Results Page --------------------------------------------- Key: JBIDE-6044 URL: https://jira.jboss.org/jira/browse/JBIDE-6044 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.2.next Reporter: Brian Fitzpatrick Assignee: Nick Boldt It's come up that some folks would like to have the BPEL Editor plug-ins available as a separate download on the JBT build results page. If we could simply provide a link to the location of the zip that gets sucked into the build, that would be helpful. -- 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

15 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3433) JSF wizard suggestion

by Yura Zhishko (JIRA)

JSF wizard suggestion --------------------- Key: JBIDE-3433 URL: https://jira.jboss.org/jira/browse/JBIDE-3433 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JSF Affects Versions: 3.0.0.cr1 Reporter: Yura Zhishko Assignee: Alexey Kazakov If the user want to create a new JSF project, he/she would be able to know that projects he should to create (with libs or without libs) depending on chosen server. JBossAS doesn't demand libs for starting project, but Tomcat does this. So, for the correct work of project on server we have to alert user which server he/she has to use for project creating using JSF project wizard. -- 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

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6365) BPEL Editor (Tech Preview)

by Brian Fitzpatrick (JIRA)

BPEL Editor (Tech Preview) -------------------------- Key: JBIDE-6365 URL: https://jira.jboss.org/browse/JBIDE-6365 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpm Affects Versions: 3.2.next Reporter: Brian Fitzpatrick Fix For: 3.2.next The BPEL Editor will be included in JBDS as a Tech Preview in this next release. This means it needs to undergo further standalone testing and integration testing where it intersects with other tools. -- 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

15 years, 2 months

6
23
0 / 0

[JBoss JIRA] Created: (JBIDE-2708) Implement webbeans validation rules

by Max Rydahl Andersen (JIRA)

Implement webbeans validation rules ----------------------------------- Key: JBIDE-2708 URL: https://jira.jboss.org/jira/browse/JBIDE-2708 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webbeans Reporter: Max Rydahl Andersen Fix For: LATER See webbeans ref impl for static check* methods. Unittests has tests.broken which we can use as inspiration for tests. -- 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

15 years, 3 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-6575) CDI deployment problems validation.

by Alexey Kazakov (JIRA)

CDI deployment problems validation. ----------------------------------- Key: JBIDE-6575 URL: https://jira.jboss.org/browse/JBIDE-6575 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.x Such as: 5.2.1. Unsatisfied and ambiguous dependencies - If an unsatisfied or unresolvable ambiguous dependency exists, the container automatically detects the problem and treats it as a deployment problem. 5.2.4. Primitive types and null values - if an injection point of primitive type resolves to a bean that may have null values, such as a producer method with a non-primitive return type or a producer field with a non-primitive type, the container automatically detects the problem and treats it as a deployment problem. ... -- 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

15 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-6581) org.jboss.tools.ws.creation.core.test takes more than 15 mins to run - break into smaller pieces?

by Nick Boldt (JIRA)

org.jboss.tools.ws.creation.core.test takes more than 15 mins to run - break into smaller pieces? ------------------------------------------------------------------------------------------------- Key: JBIDE-6581 URL: https://jira.jboss.org/browse/JBIDE-6581 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.9.0:test (default-test) on project org.jboss.tools.ws.creation.core.test: Error while executing platform: Error while executing external command, process killed. Process timeout out after 900 seconds -> [Help 2] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.tycho:maven-osgi-test-plugin:0.9.0:test (default-test) on project org.jboss.tools.ws.creation.core.test: Error while executing platform at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) Does this test need more time? can it be broken into smaller pieces? -- 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

15 years, 3 months

6
33
0 / 0

[JBoss JIRA] Created: (JBIDE-6214) Support project example with no Eclipse metadata, only pom.xml, in zip

by Pete Muir (JIRA)

Support project example with no Eclipse metadata, only pom.xml, in zip ---------------------------------------------------------------------- Key: JBIDE-6214 URL: https://jira.jboss.org/jira/browse/JBIDE-6214 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Pete Muir Assignee: Snjezana Peco If projects want to incorporate producing project examples into their release process, they are likely not to have any valid eclipse metadata available for the example when using Maven. -- 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

15 years, 3 months

7
20
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 July 2010