[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
[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
[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
[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