September 2013 - jbosstools-issues

[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 reassigned JBIDE-14529: ------------------------------------- Assignee: Max Rydahl Andersen (was: Snjezana Peco) > 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] (JBTIS-164) Cannot install BPEL from JBDSIS update site

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-164: --------------------------------------- Summary: Cannot install BPEL from JBDSIS update site Key: JBTIS-164 URL: https://issues.jboss.org/browse/JBTIS-164 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: BPEL, distribution Affects Versions: 7.0.0-JBDS, 7.0.1-JBDS Reporter: Andrej Podhradsky Priority: Blocker Cannot install BPEL editor from the update site at http://www.qa.jboss.com/binaries/RHDS/builds/staging/jbdsis-7.0.1-updatesite neither from http://www.qa.jboss.com/binaries/RHDS/builds/staging/jbdsis-7.0.0-updatesite I'm getting the following error: Cannot complete the install because one or more required items could not be found. Software being installed: JBoss BPEL Editor 1.2.1.Final-v20130225-1413-B89 (org.jboss.tools.bpel.feature.feature.group 1.2.1.Final-v20130225-1413-B89) Missing requirement: JBoss BPEL Editor 1.2.1.Final-v20130225-1413-B89 (org.jboss.tools.bpel.feature.feature.group 1.2.1.Final-v20130225-1413-B89) requires 'org.eclipse.bpel.feature.feature.group [1.0.0,2.0.0)' but it could not be 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2740) Support multiple namespaces in OpenShift

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2740?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2740: ----------------------------------- Are we using "namespace" and "domain" interchangeably here? > Support multiple namespaces in OpenShift > ---------------------------------------- > > Key: JBDS-2740 > URL: https://issues.jboss.org/browse/JBDS-2740 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Andy Goldstein > Assignee: Andre Dietisheim > Labels: openshift > > OpenShift will soon add support for a user to have access to multiple namespaces. This includes: > - a user creates and owns multiple namespaces > - a user has permission to work with a domain owned by another user (with differing permission levels) -- 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-13542) Disappearance of validation warning

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13542?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-13542: --------------------------------------- Hello [~jpeterka], Could you please give it another try ? I can't reproduce it here on JBDS 7.0.0.GA on MacOSX. Thanks > Disappearance of validation warning > ----------------------------------- > > Key: JBIDE-13542 > URL: https://issues.jboss.org/browse/JBIDE-13542 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Affects Versions: 4.1.0.Alpha1 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Fix For: 4.1.1.Final > > -- 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-15147) Livereload server shows restart status when it is used by BrowserSim

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15147: --------------------------------------- Hello [~kmarmaliykov], Could you provide me with steps to reproduce the problem ? Thanks > Livereload server shows restart status when it is used by BrowserSim > -------------------------------------------------------------------- > > Key: JBIDE-15147 > URL: https://issues.jboss.org/browse/JBIDE-15147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Environment: Win7 64, Eclipse + JBT > Reporter: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.1.x > > Attachments: livereload_bug.png > > > I was testing browsersim working on CR1a and notice that livereload server shows Started, Restart status. But works fine. -- 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-15155) LiveReload is not working with internal Web Browser

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15155?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15155: --------------------------------------- [~vpakan], can you try with a fresh workspace and without using browsersim once JBDS is started ? BrowserSim uses XULRunner for the internal browser engine and I wonder if it may cause problems. Thanks > LiveReload is not working with internal Web Browser > --------------------------------------------------- > > Key: JBIDE-15155 > URL: https://issues.jboss.org/browse/JBIDE-15155 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Reporter: Vlado Pakan > Fix For: 4.1.x > > > 1. Import HTML5 project from JBoss Central and run it on Server > 2. Click on Show In > Web Browser via LiveReload Server on HTML 5 project within Server View > ASSERT: http://localhost:8080/jboss-as-kitchensink-html5-mobile/ page is opened either in default web browser and internal eclipse browser > 3. Change index.html file of HTML5 project and save changes > ASSERT: Page is reloaded in default web browser > ERROR: Page is not reloaded in internal eclipse browser -- 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: ------------------------------------- Here's a summary of the use cases as Fred and I understand them. Please correct any information that seems wrong so that I can proceed with the patch: There are 3 use cases 1: source lookup / identification : when you enter a java class from the server in debug, we need to access that jar, so we can do some source attachement. Works for *any* jar used by the server 2: java search : in the IDE, user should be able to find any class from the server 'classpath'. IMO, that should be restricted to visible jars only 3: actually adding jars to the classpath of a dynamic web project or other project Items 2 and 3 should return identical jars, while item 1 should return a superset. > 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-15395) testWebKitSetDefaultUserAgent

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15395?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-15395. ------------------------------------------ Assignee: Konstantin Marmalyukov Resolution: Done This issue was created accidentally. Oops:) > testWebKitSetDefaultUserAgent > ----------------------------- > > Key: JBIDE-15395 > URL: https://issues.jboss.org/browse/JBIDE-15395 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > -- 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-15395) testWebKitSetDefaultUserAgent

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-15395: ---------------------------------------------- Summary: testWebKitSetDefaultUserAgent Key: JBIDE-15395 URL: https://issues.jboss.org/browse/JBIDE-15395 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Konstantin Marmalyukov -- 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-15326) openshift-java-client: Push 2.3.0 to maven central

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15326?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15326 at 9/3/13 6:09 AM: ------------------------------------------------------------------ We're now using maven artifact instead of embedded jars. We changed the maven build so that it'll copy maven artifacts to the lib folder when building. In order to have Eclipse still getting the libs I had to add the maven nature to the client plugin. Local maven build works fine: {code} [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] openshift.all ..................................... SUCCESS [0.345s] [INFO] openshift.plugins ................................. SUCCESS [0.009s] [INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.021s] [INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [3.937s] [INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.719s] [INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [4.145s] [INFO] openshift.tests ................................... SUCCESS [0.007s] [INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [24.321s] [INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [31.794s] [INFO] openshift.features ................................ SUCCESS [0.008s] [INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.214s] [INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.161s] [INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.111s] [INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.168s] [INFO] openshift.site .................................... SUCCESS [6.716s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:52.727s [INFO] Finished at: Tue Sep 03 11:05:46 CEST 2013 [INFO] Final Memory: 76M/714M [INFO] ------------------------------------------------------------------------ {code} ...and the jenkins build #432 (https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...) was also successful: {code} [INFO] All tests passed! [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] openshift.tests ................................... SUCCESS [0.410s] [INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [14.237s] [INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [20.835s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:30.896s [INFO] Finished at: Tue Sep 03 05:31:12 EDT 2013 [INFO] Final Memory: 52M/560M [INFO] ------------------------------------------------------------------------ {code} was (Author: adietish): We're now using maven artifact instead of embedded jars. We changed the maven build so that it'll copy maven artifacts to the lib folder when building. In order to have Eclipse still getting the libs I had to add the maven nature to the client plugin. Local maven build works fine: {code} [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] openshift.all ..................................... SUCCESS [0.345s] [INFO] openshift.plugins ................................. SUCCESS [0.009s] [INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.021s] [INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [3.937s] [INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.719s] [INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [4.145s] [INFO] openshift.tests ................................... SUCCESS [0.007s] [INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [24.321s] [INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [31.794s] [INFO] openshift.features ................................ SUCCESS [0.008s] [INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.214s] [INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.161s] [INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.111s] [INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.168s] [INFO] openshift.site .................................... SUCCESS [6.716s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:52.727s [INFO] Finished at: Tue Sep 03 11:05:46 CEST 2013 [INFO] Final Memory: 76M/714M [INFO] ------------------------------------------------------------------------ {code} > openshift-java-client: Push 2.3.0 to maven central > -------------------------------------------------- > > Key: JBIDE-15326 > URL: https://issues.jboss.org/browse/JBIDE-15326 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > In JBT 4.1.0.Final we used openshift-java-client v2.3.0. The code was branched and tagged. Now we need to push the maven artifact to maven 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