March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2944) Should be easier for users to try discover earlyaccess releases and plugins not yet fully supported

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2944?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2944: -------------------------------------- Component/s: central > Should be easier for users to try discover earlyaccess releases and plugins not yet fully supported > --------------------------------------------------------------------------------------------------- > > Key: JBDS-2944 > URL: https://issues.jboss.org/browse/JBDS-2944 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: central > 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-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 updated JBDS-2942: -------------------------------------- Component/s: installer > 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] (JBIDE-16292) Need to restore ability to select specific archetype version per runtime in Central

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16292?page=com.atlassian.jira.plugi... ] Rafael Benevides commented on JBIDE-16292: ------------------------------------------ [~fbricon] That's my understanding too. > Need to restore ability to select specific archetype version per runtime in Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-16292 > URL: https://issues.jboss.org/browse/JBIDE-16292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.1.1.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.2.CR1 > > > The changes done in JBIDE-15645 introduced a regression in the way archetypes are selected. > Basically, we can get different archetype versions depending on the EE version of the runtime (web/full-ee6 vs web/full-ee7) but we lost the ability to pick a different archetype version between 2 different runtimes of the same product and same EE level (eg. EAP 6.1 vs EAP 6.2) > As a consequence, archetype versions designed to run on EAP 6.2 will be selected when EAP 6.1 is selected in the project wizard. > Hopefully EAP 6.2 archetypes will still be able to run on EAP 6.1 so that shouldn't be a problem, but we should fix that for the next minor release. -- 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] (JBIDE-16689) Crash after CTRL + rightclick + find implementation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16689?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16689: --------------------------------------------- [~velteyn] okey - so the repeated error in your logs will go away if you start with a new workspace. its an ufortunate limitation of the windows password provider it does not support mixing 32 and 64 bit encoded passwords. With respect to your actual crash we are still shooting blind here because none of the logs show an actual crash related to java editor or eclipse full crash. Would be great if you can reproduce it and grab more correct log (or upload your log zipped to this jira so it does not get truncated?) > Crash after CTRL + rightclick + find implementation > --------------------------------------------------- > > Key: JBIDE-16689 > URL: https://issues.jboss.org/browse/JBIDE-16689 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Edoardo Barolo > -- 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] (JBIDE-16613) Clone - Project created with Forge 1 not imported to Eclipse on Windows

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16613?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-16613. ------------------------------ Verified in 7.1.1.GA-v20140303-1841-B672 > Clone - Project created with Forge 1 not imported to Eclipse on Windows > ----------------------------------------------------------------------- > > Key: JBIDE-16613 > URL: https://issues.jboss.org/browse/JBIDE-16613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Final > Environment: Windows 7 x86 > JBDS 7.1.0 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.2.CR1 > > > When you create a project in Forge on Windows, it is created alright, but the project is not imported to Eclipse so it does not appear in the project explorer. > Screencast here: http://screencast.com/t/9krBgXxz -- 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] (JBIDE-14310) generate JIRAs when it's time to bump projects' root poms to point at newer parent pom

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14310?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-14310. --------------------------------- Closing. > generate JIRAs when it's time to bump projects' root poms to point at newer parent pom > -------------------------------------------------------------------------------------- > > Key: JBIDE-14310 > URL: https://issues.jboss.org/browse/JBIDE-14310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Final > > > [~maxandersen], please consider spawning a version of this [1] which can be used to JIRA-nag people about the need to update their root poms to the latest parent pom version. > [1] https://github.com/jbosstools/jbosstools-documentation/blob/563b823b98975... -- 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] (JBIDE-16416) Shortcut for Redo action is missing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16416?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16416. --------------------------------- Verified in JBDS 7.1.1.CR1 B672 > Shortcut for Redo action is missing > ----------------------------------- > > Key: JBIDE-16416 > URL: https://issues.jboss.org/browse/JBIDE-16416 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.1.0.Final > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.2.CR1 > > > Shift+Ctrl+Z shortcut (Redo) is not working -- 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] (JBIDE-16415) Shortcut for Redo action is missing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16415?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16415. --------------------------------- Verified in JBT 4.2.0.Beta1 nightly > Shortcut for Redo action is missing > ----------------------------------- > > Key: JBIDE-16415 > URL: https://issues.jboss.org/browse/JBIDE-16415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Victor Rubezhny > Fix For: 4.2.0.Alpha2 > > Attachments: scr.png > > > By default, there is no shortcut for Redo action like in Eclipse (ShiftCtrl+Z). > I think it would be cool if there is a shortcut for redo by default ;-) -- 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] (JBIDE-15937) All seam runtimes are checked after adding/removing

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15937?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-15937: ---------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.1.1.Final) But I would prefer to have this fixed in 4.2.x rather than just 4.1.1 (both would be fine, too, but maybe not necessary). > All seam runtimes are checked after adding/removing > --------------------------------------------------- > > Key: JBIDE-15937 > URL: https://issues.jboss.org/browse/JBIDE-15937 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2 > Affects Versions: 4.1.1.Beta1 > Reporter: Radoslav Rábara > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.2.0.Beta1 > > Attachments: seam runtimes - remaining are checked.jpg, seam runtimes - remove one.jpg > > > All seam runtimes are checked after new seam runtime is added or existing one is removed. -- 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] (JBIDE-16245) Show correct version of integration tests repo web page

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16245?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-16245. --------------------------------- Done and verified. > Show correct version of integration tests repo web page > ------------------------------------------------------- > > Key: JBIDE-16245 > URL: https://issues.jboss.org/browse/JBIDE-16245 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.1.1.Final > > > The integration tests repo is here: > http://download.jboss.org/jbosstools/updates/nightly/integrationtests/trunk/ > At the top it says: > Latest Build: 1.0.0.CR1 > We should display something more meaningful. > If you take core tests for example: > http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/ > They say: > Latest Build: 4.2.0-SNAPSHOT (Alpha1-v20131205-0707-B2751) -- 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