September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2755) For JBDS 7.1.0.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2755: -------------------------------- Summary: For JBDS 7.1.0.Alpha1: Code Freeze + Branch Key: JBDS-2755 URL: https://issues.jboss.org/browse/JBDS-2755 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Security Level: Public (Everyone can see) Components: installer Reporter: Nick Boldt Priority: Blocker Fix For: 7.1.0.Alpha1 For JBDS 7.1.0.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-15438) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15438: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear] Key: JBIDE-15438 URL: https://issues.jboss.org/browse/JBIDE-15438 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: aerogear-hybrid Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Aerogear] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-15437) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15437: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch Key: JBIDE-15437 URL: https://issues.jboss.org/browse/JBIDE-15437 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Nick Boldt Priority: Blocker Fix For: 4.1.1.Alpha1 For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] See also: JBDS-2755 -- 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-15439) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [JST]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15439: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [JST] Key: JBIDE-15439 URL: https://issues.jboss.org/browse/JBIDE-15439 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: common/jst/core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [JST] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-15440) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [VPE]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15440: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [VPE] Key: JBIDE-15440 URL: https://issues.jboss.org/browse/JBIDE-15440 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: visual-page-editor-core Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [VPE] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-15441) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [XULRunner]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15441: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [XULRunner] Key: JBIDE-15441 URL: https://issues.jboss.org/browse/JBIDE-15441 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: xulrunner Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [XULRunner] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for XULRunner task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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-14530) Support 'Arquillian Cruiser' in standard 'Outline' view

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14530?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-14530. ----------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.x) Resolution: Rejected I have rejected this jira because we can't be changing the Java Outline View without introducing a new editor. Aslak, If you want we to add some feature to the Arquillia Cruiser view, please reopen the jira or create a new one. > Support 'Arquillian Cruiser' in standard 'Outline' view > ------------------------------------------------------- > > Key: JBIDE-14530 > URL: https://issues.jboss.org/browse/JBIDE-14530 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Max Rydahl Andersen > Fix For: 4.2.0.Alpha1 > > > Would it be possible to extend the normal 'Outline' view to specially handle 'Deployment methods' and add the option to continue drilling down into the content of the defined archive? -- 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: --------------------------------------- We can change the required method to public String[] getJarsAndFolders(String configuration) The method would return modules' jars included into the configuration as well as bundles, jboss-modules.jar for AS >=7.0 and common, lib, server, server/{configuration}/lib, server/{configuration}/deploy/lib, server/{configuration}/deployers, server/{configuration}/deploy/jbossweb.sar for AS < 7.0. If you can't add the method to JBossServerType, add it wherever you want. I will try to adapt the PR. However, I think the PR already works good enough. It is only the Search Lookup helping us to find a server type/class using the Java Search lookup and doesn't have any effect on a runtime. > 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-15392) Add api in server needed for source lookup

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15392: ------------------------------------- The class you'll want to look at as your entry point would be RuntimeJarUtility It has a few methods signatures, some requiring IRuntime, and others requiring only a String homeDirectory. However, the one requiring a home directory will probably require you to pass in a Map<String, String> with a full path for the configuration folder (for AS < 7, something like ${jboss_config_dir} -> /home/you/apps/jboss/jboss-6/server/default ) Please see the test case for more use-cases and examples. > 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-14529) Support 'Open Declaration(F3)' on Resource lookup in Deployment methods

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14529?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-14529. ----------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.x) (was: 4.2.x) Resolution: Rejected I have rejected this jira because we can't change the F3 key in the existing Java Editor. Aslak, Please reopen this jira if you want some other (unused) key to open an Arquillian resource. > 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.2.0.Alpha1 > > > 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

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