December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18974) Latest Ionic app based on tabs template is not shown on HTM5 Preview

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18974?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18974: ---------------------------------- Attachment: screenshot1.png > Latest Ionic app based on tabs template is not shown on HTM5 Preview > -------------------------------------------------------------------- > > Key: JBIDE-18974 > URL: https://issues.jboss.org/browse/JBIDE-18974 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.1.Final > Environment: Fedora 20 Linux x86_64 > OpenJDK 7 > SWT_GTK3=1 > Reporter: Denis Golovin > Attachments: screenshot1.png > > > The app works fine in internal browser, bit not in HTML5 Preview > !screenshot.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18974) Latest Ionic app based on tabs template is not shown on HTM5 Preview

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-18974: ------------------------------------- Summary: Latest Ionic app based on tabs template is not shown on HTM5 Preview Key: JBIDE-18974 URL: https://issues.jboss.org/browse/JBIDE-18974 Project: Tools (JBoss Tools) Issue Type: Bug Components: visual-page-editor-core Affects Versions: 4.2.1.Final Environment: Fedora 20 Linux x86_64 OpenJDK 7 SWT_GTK3=1 Reporter: Denis Golovin The app works fine in internal browser, bit not in HTML5 Preview !screenshot.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-377) Update bpmn2-modeler for IS beta2 TP and aggregate

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-377?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-377: ----------------------------- Description: Pick up new version of bpmn2 modeler. *Reason:* ... *Project page/sources:* ... *Version:* .... *License and owner:* ... *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ *JBoss mirror:* http://downloads.jboss.org/jbosstools/updates/requirements/<projectName> *Include Sources:* Yes|No *Affected projects:* *Include in JBDS:* Yes|No *Type of dependency:* testing|central-only|distribution *List of bundles added/removed:* {code} suggested diff on the .target files {code} was:Pick up new version of bpmn2 modeler. > Update bpmn2-modeler for IS beta2 TP and aggregate > -------------------------------------------------- > > Key: JBTIS-377 > URL: https://issues.jboss.org/browse/JBTIS-377 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution, target-platform > Affects Versions: 4.2.0.Beta2, 4.2.0.Beta2a-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > > Pick up new version of bpmn2 modeler. > *Reason:* ... > *Project page/sources:* ... > *Version:* .... > *License and owner:* ... > *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/ > *JBoss mirror:* http://downloads.jboss.org/jbosstools/updates/requirements/<projectName> > *Include Sources:* Yes|No > *Affected projects:* > *Include in JBDS:* Yes|No > *Type of dependency:* testing|central-only|distribution > *List of bundles added/removed:* > {code} > suggested diff on the .target files > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-377) Update bpmn2-modeler for IS beta2 TP and aggregate

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-377: -------------------------------- Summary: Update bpmn2-modeler for IS beta2 TP and aggregate Key: JBTIS-377 URL: https://issues.jboss.org/browse/JBTIS-377 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: distribution, target-platform Affects Versions: 4.2.0.Beta2, 4.2.0.Beta2a-TP Reporter: Paul Leacu Assignee: Paul Leacu Pick up new version of bpmn2 modeler. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3294) Remove RichFaces tooling from default JBDS installation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3294: -------------------------------------- I created a separate issue for removing File -> New -> RichFaces Project from JBoss Perspective (affects both JBDS & JBT): https://issues.jboss.org/browse/JBIDE-18973 And attached a PR: https://github.com/jbosstools/jbosstools-central/pull/314 This PR removes the wizard shortcut from the File -> New menu but doesn't remove the wizard itself. The wizard is still available via File -> New -> Others -> JBoss Central ->... [~burrsutter] is it enough for JBDS 9.0.0 (JBT 4.3.0) ? > Remove RichFaces tooling from default JBDS installation > ------------------------------------------------------- > > Key: JBDS-3294 > URL: https://issues.jboss.org/browse/JBDS-3294 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, central, installer > Reporter: Burr Sutter > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > With RichFaces going into maintenance mode in 2016, we should remove 'File-New RichFaces Project' and have RichFaces available in the Software/Update tab much like Seam. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3249 at 12/18/14 2:38 PM: ------------------------------------------------------------ Proposal for a single installer for the *4* [1] pieces of JBDS IS, with user input to request WHICH piece(s) may fall into the categories of "unnecessary" and "intermediate" clicks. We can either mimic the old MS Office install path (custom install is an optional screen, allowing users to enable/disable pieces to be installed), or the Marketplace install path (prompt user to confirm they want to install all 4 features, and give them the option to deselect things). Of course both options assume you want the ability to just do, for example, a "JBDS IS Fuse Installer" (to match the proposal in JBDS-3293) rather than "all of JBDS IS installer". If you do not want users to have the option to pick what the installer installs, then we alleviate these extra clicks/confirmations/selection steps, so there are fewer "unnecessary" or "intermediate" steps. [1] Or *5*, if we include a top-level feature group for SOA 5.x support. was (Author: nickboldt): Proposal for a single installer for the *4* [1] pieces of JBDS IS, with user input to request WHICH piece(s) may fall into the categories of "unnecessary" and "intermediate" clicks. We can either mimic the old MS Office install path (custom install is an optional screen, allowing users to enable/disable pieces to be installed), or the Marketplace install path (prompt user to confirm they want to install all 4 features, and give them the option to deselect things). Of course both options assume you want the ability to just do, for example, a "JBDS IS Fuse Installer" (to match the proposal in JBDS-3293) rather than "all of JBDS IS installer". [1] Or *5*, if we include a top-level feature group for SOA 5.x support. > As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps > ------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3249 > URL: https://issues.jboss.org/browse/JBDS-3249 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, integration-platform, updatesite > Reporter: Max Rydahl Andersen > Fix For: 8.0.2.GA, 8.1.0.GA > > > Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find. > Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276) > From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3249: ---------------------------------- Proposal for a single installer for the *4* [1] pieces of JBDS IS, with user input to request WHICH piece(s) may fall into the categories of "unnecessary" and "intermediate" clicks. We can either mimic the old MS Office install path (custom install is an optional screen, allowing users to enable/disable pieces to be installed), or the Marketplace install path (prompt user to confirm they want to install all 4 features, and give them the option to deselect things). Of course both options assume you want the ability to just do, for example, a "JBDS IS Fuse Installer" (to match the proposal in JBDS-3293) rather than "all of JBDS IS installer". [1] Or *5*, if we include a top-level feature group for SOA 5.x support. > As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps > ------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3249 > URL: https://issues.jboss.org/browse/JBDS-3249 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: installer, integration-platform, updatesite > Reporter: Max Rydahl Andersen > Fix For: 8.0.2.GA, 8.1.0.GA > > > Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find. > Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276) > From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18973) Remove RichFaces Project from the File > New menu in JBoss Perspective

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18973?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-18973: -------------------------------------- Assignee: Fred Bricon > Remove RichFaces Project from the File > New menu in JBoss Perspective > ---------------------------------------------------------------------- > > Key: JBIDE-18973 > URL: https://issues.jboss.org/browse/JBIDE-18973 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Affects Versions: 4.2.1.Final > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18973) Remove RichFaces Project from the File > New menu in JBoss Perspective

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-18973: -------------------------------------- Summary: Remove RichFaces Project from the File > New menu in JBoss Perspective Key: JBIDE-18973 URL: https://issues.jboss.org/browse/JBIDE-18973 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Affects Versions: 4.2.1.Final Reporter: Alexey Kazakov Fix For: 4.3.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18766) Test latest Tern available form snaphot update site

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18766?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18766: ---------------------------------- Fix Version/s: 4.3.0.Alpha1 > Test latest Tern available form snaphot update site > --------------------------------------------------- > > Key: JBIDE-18766 > URL: https://issues.jboss.org/browse/JBIDE-18766 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Final > Environment: Linux, Windows, Mac > Reporter: Denis Golovin > Assignee: Victor Rubezhny > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > We need to test latest tern in relation with JBIDE-18740 and see what is better: > * fix it in thym > * fix it by including latest tern -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014