September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-14529) Support 'Open Declaration(F3)' on Resource lookup in Deployment methods

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14529?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14529: --------------------------------------------- no, does not make sense to create separate editor for java classes. One way is to use Ctrl+1 (quickfix) to add additional navigation. We do this for bringing JPA queries to the criteria editor in hibernate tools. > Support 'Open Declaration(F3)' on Resource lookup in Deployment methods > ----------------------------------------------------------------------- > > Key: JBIDE-14529 > URL: https://issues.jboss.org/browse/JBIDE-14529 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Max Rydahl Andersen > Fix For: 4.1.x, 4.2.x > > > Given a deployment method with resource references > When pressing 'open declaration(F3)' > Then open the source file for the reference > Not sure if this makes sense in Eclipse lingo, but I personally navigate code via F3 (Open Declaration) a lot. Navigating to JavaArchive.class via F3 but having to do 'Ctrl+Mouse Click' to get to the resource reference seems clumsy. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15392: --------------------------------------------- "We only know a server home directory so we have to recognize directories/jars based on that directory" Why don't the source lookup know which server it is ? How does it find the server dir if not through the related running server ? I know there is an option for just specifying a directory but wouldn't it make sense to be able to know which server thats being used or is that information lost ? > 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 > > 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-15394) Add arquillian.xml GUI editor to jbosstools-arquillian

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15394?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15394: --------------------------------------------- why does the arquillian.xml editor need to modify pom.xml ? what kind of changes is that for ? profile names or ? > Add arquillian.xml GUI editor to jbosstools-arquillian > ------------------------------------------------------ > > Key: JBIDE-15394 > URL: https://issues.jboss.org/browse/JBIDE-15394 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Masao Kunii > Priority: Optional > > The arquillian.xml editor is an editor to edit arquillian.xml easily and visually. This is a feature for jbosstools-arquillian(https://github.com/jbosstools/jbosstools-arquillian) and enables to: > - Edit containers, container groups, extensions, protocols and engines > - Modify pom.xml automatically corresponding settings in arquillian.xml > - Register favorite container/container groups from Eclipse preferences -- 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] (JBTIS-124) Create SY bot test for file gateway

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-124?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-124: ------------------------------------ Fix Version/s: 4.1.2 > Create SY bot test for file gateway > ----------------------------------- > > Key: JBTIS-124 > URL: https://issues.jboss.org/browse/JBTIS-124 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.2 > > > Create a bot test form SY service with file binding -- 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] (JBTIS-124) Create SY bot test for file gateway

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-124?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-124. ----------------------------------- > Create SY bot test for file gateway > ----------------------------------- > > Key: JBTIS-124 > URL: https://issues.jboss.org/browse/JBTIS-124 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.1.2 > > > Create a bot test form SY service with file binding -- 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-2750) cannot log into OpenShift (even though credentials are valid)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2750?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-2750. --------------------------------- Resolution: Duplicate Issue > cannot log into OpenShift (even though credentials are valid) > ------------------------------------------------------------- > > Key: JBDS-2750 > URL: https://issues.jboss.org/browse/JBDS-2750 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 6.0.x > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Attachments: cannot-login.png > > > You cannot log into OpenShift Online using JBDS6 (JBDS7 and OpenShift Enterprise are not affected) any more. -- 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-2734) Forge 2 in JBDS

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2734: --------------------------------------- [~lincolnthree], with [~nickboldt]'s help I got Forge 2 installed alongside JBT in Eclipse. So now I have a better idea of the work that will need doing to document the features that Forge 2 brings to the Forge Tools plug-in. Of course it all depends how much extra gets added to Forge 2 between the 4.1.0 JBT release and the upcoming 7.1.0 JBDS release. So I have: * If Forge 1 and 2 included, explain to users why both necessary and when would use each * If not embedded in JBDS, add/install Forge 2.0 in IDE * Start the Forge 2 console * Create a new project with Forge 2 wizard * Edit Addons (install, remove, build and install) * Add JPA functionality (new entity, new field, JPA setup) * Manage Forge Runtime Servers (potentially setting Forge 1 or 2 as default) * Customize Forge 2 Addon repository location Anything else you can think of at this time? Just using this to estimate the volume of work involved. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > > Is Forge 2 ready to be included 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-358) Check 'install' sections as product name change will affect CSP

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-358?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-358: ------------------------------------------ Live on customer portal: https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... Marking JIRA as DONE. > Check 'install' sections as product name change will affect CSP > --------------------------------------------------------------- > > Key: TOOLSDOC-358 > URL: https://issues.jboss.org/browse/TOOLSDOC-358 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Product name changing to Red Hat JBoss Developer Studio. Changes to CSP should be complete at end of June 2013. Recheck install instructions as these reference the product name labels in the CSP. Install instructions are provided in both Installation Guide and Getting Started Guide. -- 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] (TOOLSDOC-358) Check 'install' sections as product name change will affect CSP

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-358?page=com.atlassian.jira.plug... ] Michelle Murray resolved TOOLSDOC-358. -------------------------------------- Resolution: Done > Check 'install' sections as product name change will affect CSP > --------------------------------------------------------------- > > Key: TOOLSDOC-358 > URL: https://issues.jboss.org/browse/TOOLSDOC-358 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > Product name changing to Red Hat JBoss Developer Studio. Changes to CSP should be complete at end of June 2013. Recheck install instructions as these reference the product name labels in the CSP. Install instructions are provided in both Installation Guide and Getting Started Guide. -- 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] (TOOLSDOC-358) Check 'install' sections as product name change will affect CSP

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-358?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-358: ------------------------------------- Fix Version/s: 4.1.0 (was: 4.1.1) > Check 'install' sections as product name change will affect CSP > --------------------------------------------------------------- > > Key: TOOLSDOC-358 > URL: https://issues.jboss.org/browse/TOOLSDOC-358 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Getting Started Guide, Installation Guide > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.0 > > > Product name changing to Red Hat JBoss Developer Studio. Changes to CSP should be complete at end of June 2013. Recheck install instructions as these reference the product name labels in the CSP. Install instructions are provided in both Installation Guide and Getting Started Guide. -- 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