October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-2507) Migration to org.eclipse.ui.menus where it is possible

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2507?page=com.atlassian.jira.plugin... ] Daniel Azarov updated JBIDE-2507: --------------------------------- Description: Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: * org.eclipse.ui.ActionSets: * org.eclipse.ui.EditorActions * org.eclipse.ui.popupMenus (including 'objectContributions') * org.eclipse.ui.viewActions Create specific issues as subtask in this issue [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] ||Module|| PR || Status || |[Java EE| https://github.com/jbosstools/jbosstools-base/pull/202 https://github.com/jbosstools/jbosstools-javaee/pull/160 | Merged | |Base| | | |Central| | | |Server| | | |JST| | | |VPE| | | |Hibernate| | | was: Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: * org.eclipse.ui.ActionSets: * org.eclipse.ui.EditorActions * org.eclipse.ui.popupMenus (including 'objectContributions') * org.eclipse.ui.viewActions Create specific issues as subtask in this issue [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] ||Module|| PR || Status || |[Java EE| | Merged | |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| https://github.com/jbosstools/jbosstools-jbpm/pull/16 | | > Migration to org.eclipse.ui.menus where it is possible > ------------------------------------------------------ > > Key: JBIDE-2507 > URL: https://issues.jboss.org/browse/JBIDE-2507 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 3.0.0.alpha > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > > Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: > * org.eclipse.ui.ActionSets: > * org.eclipse.ui.EditorActions > * org.eclipse.ui.popupMenus (including 'objectContributions') > * org.eclipse.ui.viewActions > Create specific issues as subtask in this issue > [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] > ||Module|| PR || Status || > |[Java EE| https://github.com/jbosstools/jbosstools-base/pull/202 > https://github.com/jbosstools/jbosstools-javaee/pull/160 | Merged | > |Base| | | > |Central| | | > |Server| | | > |JST| | | > |VPE| | | > |Hibernate| | | -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2507) Migration to org.eclipse.ui.menus where it is possible

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2507?page=com.atlassian.jira.plugin... ] Daniel Azarov updated JBIDE-2507: --------------------------------- Description: Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: * org.eclipse.ui.ActionSets: * org.eclipse.ui.EditorActions * org.eclipse.ui.popupMenus (including 'objectContributions') * org.eclipse.ui.viewActions Create specific issues as subtask in this issue [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] ||Module|| PR || Status || |[Java EE|https://github.com/jbosstools/jbosstools-javaee]| https://github.com/jbosstools/jbosstools-base/pull/202 https://github.com/jbosstools/jbosstools-javaee/pull/160 | Merged | |Base| | | |Central| | | |Server| | | |JST| | | |VPE| | | |Hibernate| | | was: Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: * org.eclipse.ui.ActionSets: * org.eclipse.ui.EditorActions * org.eclipse.ui.popupMenus (including 'objectContributions') * org.eclipse.ui.viewActions Create specific issues as subtask in this issue [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] ||Module|| PR || Status || |[Java EE| https://github.com/jbosstools/jbosstools-base/pull/202 https://github.com/jbosstools/jbosstools-javaee/pull/160 | Merged | |Base| | | |Central| | | |Server| | | |JST| | | |VPE| | | |Hibernate| | | > Migration to org.eclipse.ui.menus where it is possible > ------------------------------------------------------ > > Key: JBIDE-2507 > URL: https://issues.jboss.org/browse/JBIDE-2507 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 3.0.0.alpha > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > > Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: > * org.eclipse.ui.ActionSets: > * org.eclipse.ui.EditorActions > * org.eclipse.ui.popupMenus (including 'objectContributions') > * org.eclipse.ui.viewActions > Create specific issues as subtask in this issue > [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] > ||Module|| PR || Status || > |[Java EE|https://github.com/jbosstools/jbosstools-javaee]| https://github.com/jbosstools/jbosstools-base/pull/202 > https://github.com/jbosstools/jbosstools-javaee/pull/160 | Merged | > |Base| | | > |Central| | | > |Server| | | > |JST| | | > |VPE| | | > |Hibernate| | | -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-2507) Migration to org.eclipse.ui.menus where it is possible

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-2507?page=com.atlassian.jira.plugin... ] Daniel Azarov updated JBIDE-2507: --------------------------------- Description: Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: * org.eclipse.ui.ActionSets: * org.eclipse.ui.EditorActions * org.eclipse.ui.popupMenus (including 'objectContributions') * org.eclipse.ui.viewActions Create specific issues as subtask in this issue [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] ||Module|| PR || Status || |[Java EE| | Merged | |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| https://github.com/jbosstools/jbosstools-jbpm/pull/16 | | was: Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: * org.eclipse.ui.ActionSets: * org.eclipse.ui.EditorActions * org.eclipse.ui.popupMenus (including 'objectContributions') * org.eclipse.ui.viewActions Create specific issues as subtask in this issue [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] > Migration to org.eclipse.ui.menus where it is possible > ------------------------------------------------------ > > Key: JBIDE-2507 > URL: https://issues.jboss.org/browse/JBIDE-2507 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cleanup > Affects Versions: 3.0.0.alpha > Reporter: Denis Golovin > Assignee: Daniel Azarov > Fix For: 4.2.0.Alpha1 > > > Migrate form extension points listed below to org.eclipse.ui.menus where it is possible: > * org.eclipse.ui.ActionSets: > * org.eclipse.ui.EditorActions > * org.eclipse.ui.popupMenus (including 'objectContributions') > * org.eclipse.ui.viewActions > Create specific issues as subtask in this issue > [Migration Guide|http://pa-blogger.blogspot.com/2008/07/orgeclipseuimenus.html] > ||Module|| PR || Status || > |[Java EE| | Merged | > |[jBPM|https://github.com/jbosstools/jbosstools-jbpm]| https://github.com/jbosstools/jbosstools-jbpm/pull/16 | | -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users

by Luis Garcia (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Luis Garcia commented on JBDS-2797: ----------------------------------- The new installer would be helpful - since it would contain the new updated launcher that doesn't ask for JDK 6 on OS X. Regarding updating the INI file during the upgrade process - the INI file inside the jbdevstudio.app gets updated fine. It is the INI file in the JBoss Developer Studio.app that doesn't get updated to the new launcher. The main issue with OS X is that if you use JDK 7 to install the JAR containing JBDS 7. When you try to launch the application it prompt for a JDK 6 install in order to be able to run. > .ini upgrade issue for 7.0.1 users > ---------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2797) .ini upgrade issue for 7.0.1 users

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2797?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2797: ---------------------------------- {quote}For the discovery site...{quote} https://devstudio.jboss.com/updates/7.0/devstudio-directory.xml -> https://devstudio.jboss.com/updates/7.0/discovery/com.jboss.jbds.central.... -> {code} <connectorDescriptor ... siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0/central/core/}"> ... </connectorDescriptor> {code} So... problem is not in the Central discovery XML or the plugin. Both point at the correct place (the released 7.0 Central site). If the user has changed the value of *-Djboss.discovery.site.url* in their .ini file, or set it via their commandline invocation, then a different XML file might be used which would then point at a different plugin jar. (eg., the 7.0-development/ site instead of the 7.0/ site). Or perhaps the update mechanism is not correctly performing all the p2.inf steps outlined here: https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.1.0.... https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.1.0.... > .ini upgrade issue for 7.0.1 users > ---------------------------------- > > Key: JBDS-2797 > URL: https://issues.jboss.org/browse/JBDS-2797 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer > Affects Versions: 7.0.1.GA > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > > User noticed issues with 7.0.0 to 7.0.1 updates at https://community.jboss.org/message/841477#841477 that needs investigation. > The post is about osx but I don't think this is limited to this OS, just that OSX has a different java behavior. > Worrisome issues are: > development url used in GA update: > -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml > startup/launcher directories are hardcoded in the .ini file: > -startup > ../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar > --launcher.library > ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20130807-1835 > Have these been forgotten/set wrong in the update or is this some specific update path that is failing ? -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15675) [Android] start avd manager when no AVDs are defined

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15675?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15675: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Description: Prompt and start the android avd manager when no avds are detected so that they can be defined. Alternately we can create a temp AVD in case no suitable ones are found. (was: Prompt and start the android avd manager when no avds are detected so that they can be defined) > [Android] start avd manager when no AVDs are defined > ---------------------------------------------------- > > Key: JBIDE-15675 > URL: https://issues.jboss.org/browse/JBIDE-15675 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Priority: Minor > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Prompt and start the android avd manager when no avds are detected so that they can be defined. Alternately we can create a temp AVD in case no suitable ones are found. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15675) [Android] start avd manager when no AVDs are defined

by Gorkem Ercan (JIRA)

Gorkem Ercan created JBIDE-15675: ------------------------------------ Summary: [Android] start avd manager when no AVDs are defined Key: JBIDE-15675 URL: https://issues.jboss.org/browse/JBIDE-15675 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: aerogear-hybrid Reporter: Gorkem Ercan Priority: Minor Fix For: LATER Prompt and start the android avd manager when no avds are detected so that they can be defined -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15674) Better contextual menu

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15674?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on JBIDE-15674: ------------------------------------------- Perspective : JBoss Tools View : Project Explorer In the view Package Explorer it's more contextual but the first elements are all projects. > Better contextual menu > ---------------------- > > Key: JBIDE-15674 > URL: https://issues.jboss.org/browse/JBIDE-15674 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.1.1.Alpha2 > Reporter: Emmanuel Hugonnet > > As a user I want to add a new JAXRS webservice to my Web application > When I right click on my project selecting the "new" entry,the first element is project (which is strange since I have already selected a project), then File, Folder and SQL Files which are not quite relevant in the context of a web application. > I would expect more web related entries in the top most, and less entries as a whole. > If I right click without selecting my current project then the new project entry becomes relevant. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13208) Allow custom 'standalone' mode directory in AS7 server plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13208?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13208: --------------------------------------------- my bad - read it as 4.1.1.Alpha1 - sorry for that. And I don't understand why you find it ok to have "configuration" and "logs" etc. hardcoded as strings since these are obviously possible to change via AS's own API of property settings. nothing to do about others using the api but about what the api need to be flexible to actually support jboss it self. Heck - could even not have this as hardcoded methods but just have a map where those values gets defined so you can add as needed. > Allow custom 'standalone' mode directory in AS7 server plugin > ------------------------------------------------------------- > > Key: JBIDE-13208 > URL: https://issues.jboss.org/browse/JBIDE-13208 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Mac OS-X 10.8.2, Java 6, Java 7, JBoss AS 7.x, JBoss EAP 6, JBDS 5.0.1 > Reporter: Duncan Doyle > Assignee: Rob Stryker > Labels: f2f2012, new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > As with JBoss EAP5.x, I have the habit of working in a copy of a 'profile' directory. With JBoss AS7/EAP6 I therefore work in copies of 'standalone' and 'domain' (depending on the operational mode). When I start AS/EAP, I reference the correct server directory with the 'jboss.server.base.dir' or 'jboss.domain.base.dir' system property. This allows me, among other things, to run multiple AS/EAP instances from a single JBoss AS/EAP installation. > It seems that the JBDS AS7 plugin only allows me to reference the default 'standalone' directory. I'm not able to select a different directory in the 'JBoss Runtime' configuration screen. I would propose to add the possibility to start a JBoss AS7/EAP6 instance from a different directory than 'standalone'. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15674) Better contextual menu

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15674?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15674: --------------------------------------------- Which perspective and view are you right clicking ? the file > new is dependent on those two parameters. > Better contextual menu > ---------------------- > > Key: JBIDE-15674 > URL: https://issues.jboss.org/browse/JBIDE-15674 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.1.1.Alpha2 > Reporter: Emmanuel Hugonnet > > As a user I want to add a new JAXRS webservice to my Web application > When I right click on my project selecting the "new" entry,the first element is project (which is strange since I have already selected a project), then File, Folder and SQL Files which are not quite relevant in the context of a web application. > I would expect more web related entries in the top most, and less entries as a whole. > If I right click without selecting my current project then the new project entry becomes relevant. -- 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, 8 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 October 2013