March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16630) Table of seam runtimes is not updated after seam was added via runtime detection

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16630?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-16630: ------------------------------------- Assignee: Alexey Kazakov (was: Snjezana Peco) > Table of seam runtimes is not updated after seam was added via runtime detection > -------------------------------------------------------------------------------- > > Key: JBIDE-16630 > URL: https://issues.jboss.org/browse/JBIDE-16630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta1 > > > The table Seam Runtime Environment in Preferences is not updated right after the runtime with seam was added via runtime detection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2942) jbdevstudio exits with -1 if _JAVA_OPTIONS set

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2942?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2942: ------------------------------------------- So you started it with too little memory ? Not sure what you expected otherwise? > jbdevstudio exits with -1 if _JAVA_OPTIONS set > ---------------------------------------------- > > Key: JBDS-2942 > URL: https://issues.jboss.org/browse/JBDS-2942 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.GA > Environment: Windows 7, Java 7 > Reporter: Dennis Doubleday > Priority: Minor > > Ran jbdevstudio.bat, using Java 7, and got immediate exit from Java with status -1. > Removed my environment variable setting _JAVA_OPTIONS=-Xmx256m and it started correctly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2924) We want to know which features users are using and where there are issues.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2924?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2924: -------------------------------------- Fix Version/s: 8.0.0.Beta1 > We want to know which features users are using and where there are issues. > -------------------------------------------------------------------------- > > Key: JBDS-2924 > URL: https://issues.jboss.org/browse/JBDS-2924 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: usage > Reporter: Max Rydahl Andersen > Fix For: 8.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2946) The installer should be fast, simple and work on all platforms.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2946?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2946: -------------------------------------- Component/s: installer > The installer should be fast, simple and work on all platforms. > --------------------------------------------------------------- > > Key: JBDS-2946 > URL: https://issues.jboss.org/browse/JBDS-2946 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: installer > Reporter: Max Rydahl Andersen > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2943: -------------------------------------- Component/s: installer maven > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer, maven > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > Priority: Critical > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.1... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2950) Target Platform Requirements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2950?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2950: -------------------------------------- Component/s: installer integration > Target Platform Requirements > ---------------------------- > > Key: JBDS-2950 > URL: https://issues.jboss.org/browse/JBDS-2950 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: installer, integration > Reporter: Max Rydahl Andersen > > Work that defines which java, OS, eclipse dependencies we need/use. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2949) Require Java 7 for the IDE

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2949?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2949: -------------------------------------- Component/s: integration > Require Java 7 for the IDE > -------------------------- > > Key: JBDS-2949 > URL: https://issues.jboss.org/browse/JBDS-2949 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > > Run the IDE with Java 7 (Java 6 no longer supported) (Users applications and servers can still use older and newer JDK’s like Java 1.4,5,6, 8 etc.) P1 > Java 6 is no longer supported by Oracle and by requiring Java 7 we can use better native IO and JavaFX (only on oracle) > Forge already requires Java 7. > Concerns: If we do not run with Java 6 we cannot support Xulrunner based VPE on OSX. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2943: -------------------------------------- Priority: Critical (was: Major) > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > Priority: Critical > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.1... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2948) Improve Performance of small and large projects

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2948?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2948: -------------------------------------- Component/s: integration > Improve Performance of small and large projects > ----------------------------------------------- > > Key: JBDS-2948 > URL: https://issues.jboss.org/browse/JBDS-2948 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > > Users have had noticable issues when importing projects having many schemas, many annotations and dependencies in past. Our and WTP validators seem to be causing issues - some are actual performance issues and others seem to be more perceived than actual issues. > Unfortunately perceived issues for the user feels just as slow as real issues. > Suggestion: > Look in jira for performance issues and add "performance" label to them > Allocate dev to use profiler to spot hotspots and get these findings reported/documented and then triage based on these findings > Work with QE to setup performance measurements for end user common operations related to these issues (example: import project, run validation etc.) for small (quickstarts), medium (ticketmonster) and large (wildfly) projects and publish these numbers over time and keep track if getting better/worse. > Setup goals to reach for these performance measurements. > Don’t add new features that make performance worse. For example don’t introduce one more slow validation feature to the validator which already has performance issues until those issues are solved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2943: ------------------------------------------- First: I think this is critical. Secondly: Does m2eclipse-git actually work ? I couldn't get it to install. Third: How do we handle this in BYOE eclipse? > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Burr Sutter > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.1... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
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 March 2014