June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14584) Runtime Detection needs API for finding runtime detectors by ID.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14584?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14584. --------------------------------- Resolution: Done The proper api would be: IRuntimeDetector rtdet = RuntimeCoreActivator.findRuntimeDetector(String id); IRuntimeDetectorDelegate del = ((RuntimeDetector)rtdet).getDelegate(); This api is not new, we just didn't see it earlier. > Runtime Detection needs API for finding runtime detectors by ID. > ----------------------------------------------------------------- > > Key: JBIDE-14584 > URL: https://issues.jboss.org/browse/JBIDE-14584 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-detection, server > Affects Versions: 4.1.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > Related to: https://issues.jboss.org/browse/JBIDE-14559 > Test case in central is using internal ASTools API. Long-standing practice is that extension point id's are api and cannot be changed, but location can. If an id is api, then a method to search by ID becomes a requirement. > Runtime detection needs apis to find a handler by ID. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14816) API located to find IRuntimeDetectorDelegate

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-14816: ----------------------------------- Summary: API located to find IRuntimeDetectorDelegate Key: JBIDE-14816 URL: https://issues.jboss.org/browse/JBIDE-14816 Project: Tools (JBoss Tools) Issue Type: Task Components: maven Affects Versions: 4.1.0.Beta1 Reporter: Rob Stryker Assignee: Snjezana Peco Fix For: 4.1.0.Beta2 Related to https://issues.jboss.org/browse/JBIDE-14559 Related to https://issues.jboss.org/browse/JBIDE-14584 The proper api would be: IRuntimeDetector rtdet = RuntimeCoreActivator.findRuntimeDetector(String id); IRuntimeDetectorDelegate del = ((RuntimeDetector)rtdet).getDelegate(); This api is not new, we just didn't see it earlier. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14306) CordovaSim: emulation of phonegap's Media API fails on cordova-mega-demo app

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14306?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-14306: ------------------------------------- Actually, there is a way of finding the root folder of the app - http://stackoverflow.com/questions/11175489/ios-phonegap-media-object-how... (second answer). Works on CordovaSim and Android VM. > CordovaSim: emulation of phonegap's Media API fails on cordova-mega-demo app > ----------------------------------------------------------------------------- > > Key: JBIDE-14306 > URL: https://issues.jboss.org/browse/JBIDE-14306 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.1.0.Beta1 > > > Phonegap's Media API ([http://docs.phonegap.com/en/2.6.0/cordova_media_media.md.html#Media]) from cordova-mega-demo app ([https://github.com/jasond/cordova-mega-demo.git]) isn't properly emulated by CordovaSim and ripple. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14810) Rename foundation plugin to foundation.core

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14810?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-14810. --------------------------------- Resolution: Done Committed after building locally all of base and jst. This commit should break central. > Rename foundation plugin to foundation.core > ------------------------------------------- > > Key: JBIDE-14810 > URL: https://issues.jboss.org/browse/JBIDE-14810 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.1.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Beta2 > > > Foundation should be renamed to foundation.core -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14793) install from jboss central "freezes"

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14793?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14793: --------------------------------------- I have tried to reproduce the issue using JBDS 7.0.0.Beta1 and JBT trunk. The Install action works in the background. It uses mylyn's job: PrepareInstallProfileJob_e_3_6. The action takes longer the first time because JBDS/JBT downloads update sites metadata. Every next time, even in a new workspace, the Install action will be very fast. Mylyn uses P2 to install connectors. Periodically, there is feedback about downloading metadata. The UI isn't blocked at any moment, at least when using this action. What version of JBDS/JBT are you using? Do you have a lot of projects in the workspace? > install from jboss central "freezes" > ------------------------------------ > > Key: JBIDE-14793 > URL: https://issues.jboss.org/browse/JBIDE-14793 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > > trying to install everything from jboss central page and clicking Install > Main UI seem freezes for several seconds/minutes with no info/feedback - it is as if the calculations are done in the main thread. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14797) weird question/dialog with missing info when project from archetype/quickstart already exists

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14797?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14797: --------------------------------------- {quote} btw. is the directory actually overwrittten or actually just copied on top ? {quote} If there is a project with the same name and if a user confirms he wants to delete it, the project will be removed with its content and a new project example will be imported. > weird question/dialog with missing info when project from archetype/quickstart already exists > --------------------------------------------------------------------------------------------- > > Key: JBIDE-14797 > URL: https://issues.jboss.org/browse/JBIDE-14797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > > Install a quickstart twice and you get this > http://screencast.com/t/Ptqsqevoe > Title: "Overwrite" > "There is the '<name>' project on the destination path: > Would you like to overwrite it ?" > Should this dialog actually have a Warning icon or similar and be worded a bit more assertive and not have blank fields - like: > Title: "Warning: Directory already exists" > "The project '<name>' already exist at '<actual path>'. > Do you wish to overwrite this directory ? > This cannot be undone" > This is assuming it is actually a project and not a directory. > btw. is the directory actually overwrittten or actually just copied on top ? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14797) weird question/dialog with missing info when project from archetype/quickstart already exists

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14797?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14797: ------------------------------------- Assignee: Snjezana Peco > weird question/dialog with missing info when project from archetype/quickstart already exists > --------------------------------------------------------------------------------------------- > > Key: JBIDE-14797 > URL: https://issues.jboss.org/browse/JBIDE-14797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > > Install a quickstart twice and you get this > http://screencast.com/t/Ptqsqevoe > Title: "Overwrite" > "There is the '<name>' project on the destination path: > Would you like to overwrite it ?" > Should this dialog actually have a Warning icon or similar and be worded a bit more assertive and not have blank fields - like: > Title: "Warning: Directory already exists" > "The project '<name>' already exist at '<actual path>'. > Do you wish to overwrite this directory ? > This cannot be undone" > This is assuming it is actually a project and not a directory. > btw. is the directory actually overwrittten or actually just copied on top ? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14815) Find a way to disambiguate different distributions of the same runtime family

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14815?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14815: -------------------------------- Description: We need to be able to distinguish a gatein runtime from a regular as runtime Use case : a project example needs to check if GateIn 3.6 is installed Use case : a project example requires AS7 or EAP6, we want to propose compatible download runtimes, excluding GateIn Problem : GateIn runtimes have the same wtp runtime id as as7. >From a project example / stacks perspective, we could define wtp ids like org.jboss.ide.eclipse.as.runtime.71#gatein-3.5 was: We need to be able to distinguish a gatein runtime from a regular as runtime Use case : a project example needs to check if GateIn 3.6 is installed Use case : a project example requires AS7 or EAP6, we want to propose compatible download runtimes, excluding GateIn Problem : GateIn runtimes have the same wtp runtime id as as7. > Find a way to disambiguate different distributions of the same runtime family > ----------------------------------------------------------------------------- > > Key: JBIDE-14815 > URL: https://issues.jboss.org/browse/JBIDE-14815 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Fix For: 4.1.0.Beta2 > > > We need to be able to distinguish a gatein runtime from a regular as runtime > Use case : a project example needs to check if GateIn 3.6 is installed > Use case : a project example requires AS7 or EAP6, we want to propose compatible download runtimes, excluding GateIn > Problem : GateIn runtimes have the same wtp runtime id as as7. > From a project example / stacks perspective, we could define wtp ids like org.jboss.ide.eclipse.as.runtime.71#gatein-3.5 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14815) Find a way to disambiguate different distributions of the same runtime family

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14815?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14815: -------------------------------- Description: We need to be able to distinguish a gatein runtime from a regular as runtime Use case : a project example needs to check if GateIn 3.6 is installed Use case : a project example requires AS7 or EAP6, we want to propose compatible download runtimes, excluding GateIn Problem : GateIn runtimes have the same wtp runtime id as as7. was:We need to be able to distinguish a gatein runtime from a regular as runtime > Find a way to disambiguate different distributions of the same runtime family > ----------------------------------------------------------------------------- > > Key: JBIDE-14815 > URL: https://issues.jboss.org/browse/JBIDE-14815 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Fix For: 4.1.0.Beta2 > > > We need to be able to distinguish a gatein runtime from a regular as runtime > Use case : a project example needs to check if GateIn 3.6 is installed > Use case : a project example requires AS7 or EAP6, we want to propose compatible download runtimes, excluding GateIn > Problem : GateIn runtimes have the same wtp runtime id as as7. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2654) Typo in .m2/settings.xml does not result in an error anywhere in the problems section or anywhere else

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2654?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2654: ----------------------------------- I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=410358 upstream > Typo in .m2/settings.xml does not result in an error anywhere in the problems section or anywhere else > ------------------------------------------------------------------------------------------------------ > > Key: JBDS-2654 > URL: https://issues.jboss.org/browse/JBDS-2654 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: maven, Upstream > Affects Versions: 6.0.0.GA > Reporter: Jim Tyrrell > Attachments: settings.xml > > > Made an edit to the maven settings.xml file. Missed a line, and the error reported in the IDE had nothing to do with a typo in the .m2/settings.xml file. Good error reporting and validation needs to be a part of maven in JBDS. -- 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, 10 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 June 2013