May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20208) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Arqullian, Birt, Portlet]

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20208?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-20208. ------------------------------------- Thx for the explanation. We can now close this issue. I have verified it with http://download.jboss.org/jbosstools/mars/stable/updates/ and only Portlet and SOA 5.x bundles use the old license (which is ok since there was no change). > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Arqullian, Birt, Portlet] > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20208 > URL: https://issues.jboss.org/browse/JBIDE-20208 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > Attachments: birt-no-license.png > > > For JBIDE 4.3.0.CR1 [Birt]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-493) replace devstudio.jboss.com in all URLs with devstudio.redhat.com; remove links to www.qa.jboss server

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-493?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-493. ----------------------------------- Verified with - https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discove... - https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discov... > replace devstudio.jboss.com in all URLs with devstudio.redhat.com; remove links to www.qa.jboss server > ------------------------------------------------------------------------------------------------------ > > Key: JBTIS-493 > URL: https://issues.jboss.org/browse/JBTIS-493 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2, 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Blocker > Fix For: 9.0.0.GA > > > There should be no references to devstudio.jboss.com anywhere in composite or aggregate update sites. > But today I found this: > {code:title=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha1/compositeContent.xml} > <child location='https://devstudio.jboss.com/9.0/development/updates/'/> > <child location='https://devstudio.redhat.com/9.0/development/updates/core/9.0.0.Beta2/'/> > <child location='https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.0.CR1...'/> > <child location='http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio...'/> > <child location='http://www.qa.jboss.com/binaries/RHDS/mars/development/updates/integratio...'/> > <child location='https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.0.Beta1.jbds...'/> > <child location='https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.0.Beta1.jbds...'/> > {code} > You should also not be linking to www.qa.jboss since that's an internal-facing server and devstudio.redhat.com is external facing. So anyone from outside the VPN will get errors when testing this site. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-696) Update BPEL feature to 1.3.101.Final

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-696?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-696: ----------------------------------------- Hey [~pleacu], [~bbrodt], just to be clear, this has been already fixed in JBTIS-470. All we need to do is to build new version of org.jboss.tools.bpel.feature (1.3.101.Final). > Update BPEL feature to 1.3.101.Final > ------------------------------------ > > Key: JBTIS-696 > URL: https://issues.jboss.org/browse/JBTIS-696 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL, distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > The BPEL editor cannot be updated if a user installs it from JBDS-IS 8.0.2.GA and earlier. For more information please see JBTIS-470. > Note that there is no change in BPEL editor the only problem is that it is not automatically updated from 1.0.4 (JBDS-IS 8.0.2) to 1.0.5 (JBDS-IS 8.0.3+) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3859. ----------------------------- Closing as done. > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3605: -------------------------------------- Sprint: devex #113 April 2016, devex #115 May 2017 (was: devex #113 April 2016) > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Epic > Components: installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: about-jbds10.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-114) JSON Preference page throws exceptions [EBZ#487377]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-114?page=com.atlassian.jira.plugin.sy... ] Max Rydahl Andersen updated ERT-114: ------------------------------------ Sprint: devex #113 April 2016, devex #115 May 2017 (was: devex #113 April 2016) > JSON Preference page throws exceptions [EBZ#487377] > --------------------------------------------------- > > Key: ERT-114 > URL: https://issues.jboss.org/browse/ERT-114 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8_M7, bzira, wst.json > Fix For: Neon (4.6) M7 > > > The following exception is thrown while selecting the "Editor" child node under JSON in the preference wizard. > Testing Neon M5 driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-90) Spike for refactoring and code manipulation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-90?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-90: ----------------------------------- Sprint: devex #113 April 2016, devex #115 May 2017 (was: devex #113 April 2016) > Spike for refactoring and code manipulation > ------------------------------------------- > > Key: ERT-90 > URL: https://issues.jboss.org/browse/ERT-90 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Gorkem Ercan > Assignee: Victor Rubezhny > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out what to do for refactoring and code manipulation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-62: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #113 April 2016, devex #115 May 2017 (was: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #113 April 2016) > Refactor JSDT Code Completion [EBZ#486776] > ------------------------------------------ > > Key: ERT-62 > URL: https://issues.jboss.org/browse/ERT-62 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ian Stewart-Binks > Labels: General, bzira > > The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions. > A proposal base for the code completion engine should include, but is not necessarily limited to: > - Keywords > - Identifiers (declared variables and functions in currently open JS file) > - Recently used methods of functions (currently open JS file as a bare minimum) > All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-93) gulp long-running task (e.g serve) can not be killed from eclipse console [EBZ#489041]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-93?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-93: ----------------------------------- Sprint: devex #4 March 2016, devex #113 April 2016, devex #115 May 2017 (was: devex #4 March 2016, devex #113 April 2016) > gulp long-running task (e.g serve) can not be killed from eclipse console [EBZ#489041] > -------------------------------------------------------------------------------------- > > Key: ERT-93 > URL: https://issues.jboss.org/browse/ERT-93 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: General, bzira > > Long-running task (e.g serve) still locks the port after pressing "Terminate" button on Eclipse console. It looks like sending "exit" command to CLI does not kill the process -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-121) [content assist] Content Assist templates still contain traces of Java [EBZ#489320]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-121?page=com.atlassian.jira.plugin.sy... ] Max Rydahl Andersen updated ERT-121: ------------------------------------ Sprint: devex #113 April 2016, devex #115 May 2017 (was: devex #113 April 2016) > [content assist] Content Assist templates still contain traces of Java [EBZ#489320] > ----------------------------------------------------------------------------------- > > Key: ERT-121 > URL: https://issues.jboss.org/browse/ERT-121 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Each content assist template should be reviewed such that it is applicable to JavaScript developers. > For instance, here's an excerpt from the live JSDT catchblock template: > ${exception_var}.printStackTrace() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016