September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15468) Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15468?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-15468: --------------------------------- Attachment: version-ok.png > Ensure versioning errors (eg., maintenance branch at 3.5.1 while master at 3.5.0) are correctly shown in vwatch results table > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15468 > URL: https://issues.jboss.org/browse/JBIDE-15468 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Jiri Peterka > Priority: Blocker > Fix For: 4.1.1.Alpha1 > > Attachments: jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png, version-ok.png > > > This screenshot taken from http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... shows that in some cases the table cell is blank when there's a real problem that should be reported, and that the reported problem in the tool tip doesn't match the information shown. > !jbide15432_missing_table_cell_tooltip_shows_actual_blocker_problem.png! -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2703) JPP 6.1 requirement is not fulfilled after JPP 6.1 runtime is added

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-2703?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-2703. ---------------------------- Verified in JBDS 7.1.0.Alpha1 > JPP 6.1 requirement is not fulfilled after JPP 6.1 runtime is added > ------------------------------------------------------------------- > > Key: JBDS-2703 > URL: https://issues.jboss.org/browse/JBDS-2703 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central > Affects Versions: 7.0.0.GA > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 7.1.0.Alpha1 > > Attachments: portalexamples.png, portal_descriptor.xml > > > With new portal applications descriptor I can see that requirement for JPP 6.1 is never fulfilled even if JPP 6.1 runtime is added. -- 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, 7 months

1
0
0 / 0

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

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14797?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-14797. ------------------------------ Verified in JBDS 7.1.0.Alpha1 > 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: Fred Bricon > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15293) BrowserSim/CordovaSim: add logging callbacks to Eclipse

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15293?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15293: ------------------------------------- Verified with JBT Alpha1-v20130909-0110-B392 > BrowserSim/CordovaSim: add logging callbacks to Eclipse > ------------------------------------------------------- > > Key: JBIDE-15293 > URL: https://issues.jboss.org/browse/JBIDE-15293 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Yahor Radtsevich > Assignee: Yahor Radtsevich > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > Attachments: screenshot.png > > > If something went wrong in BrowserSim/CordovaSim then an error is printed to the console. It would be much better if the error was shown in the Eclipse error log. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15165) CordovaSim does not warn users that it needs Safari to run

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15165?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15165. ------------------------------- Verified with JBT Alpha1-v20130909-0110-B392 > CordovaSim does not warn users that it needs Safari to run > ---------------------------------------------------------- > > Key: JBIDE-15165 > URL: https://issues.jboss.org/browse/JBIDE-15165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.CR1 > Environment: Windows 8 > Reporter: Stefan Bunciak > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Trying to run Hybrid Mobile Application in CordovaSim did nothing, then I tried to open standalone BrowserSim and it turned out that I'm missing Safari. I think the same applies to CordovaSim, so it should warn users of missing Safari installation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-15392 at 9/11/13 5:47 AM: ---------------------------------------------------------------- {quote} "A source lookup container knows only a home directory" - you keep repeating this but why don't we make it so it can use either a home directory (and then just scans for all jars) or a specific server which would then be able to provide much more specific knowledge like this API jboss servers could expose ? Similar could be made for tomcats etc. if this was setup as an extension point where runtime type was mapped to a class that could handle it. {quote} It is possible to make specific containers for different server types. The PR from JBIDE-13851 recognizes a server type and scans jars based on it. However, this jira is created in order to introduce a new API that would provide the Source Lookup plugin not to depend on a server type, i.e., we wouldn't change the Source Lookup plugin when a new server type is introduced. The PR looks fine and can already be used. It would be just good the API to return jars for a default configuration for JBoss AS < 7.0. That isn't obliged, but can be easily added. Creating a specific container for Tomcat, Glassfish... would require introducing new dependencies. In my opinion, they would need to be created in separate plugins. was (Author: snjeza): {quote} "A source lookup container knows only a home directory" - you keep repeating this but why don't we make it so it can use either a home directory (and then just scans for all jars) or a specific server which would then be able to provide much more specific knowledge like this API jboss servers could expose ? Similar could be made for tomcats etc. if this was setup as an extension point where runtime type was mapped to a class that could handle it. {quote} It is possible to make specific containers for different server types. The PR from JBIDE-13851 recognizes a server type and scans jars based on it. However, this jira is created in order to introduce a new API that would provide the Source Lookup plugin not to depend on a server type, i.e., we wouldn't change the Source Lookup plugin when a new sever type is introduced. The PR looks fine and can already be used. It would be just good the API to return jars for a default configuration for JBoss AS < 7.0. That isn't obliged, but can be easily added. Creating a specific container for Tomcat, Glassfish... would require introducing new dependencies. In my opinion, they would need to be created in separate plugins. > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15392: --------------------------------------- {quote} "A source lookup container knows only a home directory" - you keep repeating this but why don't we make it so it can use either a home directory (and then just scans for all jars) or a specific server which would then be able to provide much more specific knowledge like this API jboss servers could expose ? Similar could be made for tomcats etc. if this was setup as an extension point where runtime type was mapped to a class that could handle it. {quote} It is possible to make specific containers for different server types. The PR from JBIDE-13851 recognizes a server type and scans jars based on it. However, this jira is created in order to introduce a new API that would provide the Source Lookup plugin not to depend on a server type, i.e., we wouldn't change the Source Lookup plugin when a new sever type is introduced. The PR looks fine and can already be used. It would be just good the API to return jars for a default configuration for JBoss AS < 7.0. That isn't obliged, but can be easily added. Creating a specific container for Tomcat, Glassfish... would require introducing new dependencies. In my opinion, they would need to be created in separate plugins. > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15296) CordovaSim: Need to update ripple source code to the last version (master 0.9.18) and fix minor bugs after migration

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15296?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15296. ------------------------------- > CordovaSim: Need to update ripple source code to the last version (master 0.9.18) and fix minor bugs after migration > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15296 > URL: https://issues.jboss.org/browse/JBIDE-15296 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Affects Versions: 4.1.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Bump version/changelog to 0.9.18 (tagging master) - https://github.com/apache/incubator-ripple/commit/007fbd5780143f40e1cb726... > Bugs: > - need to fix notification.confirm; > - need to fix vibration.vibrate; > - need to fix "Compass" API. > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2732) Add usage tracking for installs from JBDS central

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2732: ------------------------------- CDW pm_ack: + (was: ?) > Add usage tracking for installs from JBDS central > ------------------------------------------------- > > Key: JBDS-2732 > URL: https://issues.jboss.org/browse/JBDS-2732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Max Rydahl Andersen > > It would be interesting to know which connectors/plugins gets installed from central -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2732) Add usage tracking for installs from JBDS central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2732?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2732: ----------------------------- CDW qa_ack: ? > Add usage tracking for installs from JBDS central > ------------------------------------------------- > > Key: JBDS-2732 > URL: https://issues.jboss.org/browse/JBDS-2732 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: requirements, usage > Reporter: Max Rydahl Andersen > > It would be interesting to know which connectors/plugins gets installed from central -- 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, 7 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 September 2013