December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18669: ---------------------------------- Description: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items It should be possible to limit number of items and edit set of items was: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items 3. Custom set of items (defined by user) It should be possible to limit number of items and edit set of items (for 1 and 2) > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items and edit set of items -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3284: --------------------------------- Fix Version/s: 9.0.0.Alpha1 > Ionic Palette - version selection, detection > -------------------------------------------- > > Key: JBDS-3284 > URL: https://issues.jboss.org/browse/JBDS-3284 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Fix For: 9.0.0.Alpha1 > > > As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3284: ----------------------------------- [~akazakov]I believe it is enough > Ionic Palette - version selection, detection > -------------------------------------------- > > Key: JBDS-3284 > URL: https://issues.jboss.org/browse/JBDS-3284 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Alexey Kazakov > > As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3294) Remove File->New->RichFaces Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3294: ------------------------------------ Assignee: Fred Bricon (was: Nick Boldt) I have changed the title and assigning to [~fbricon] to verify and merge the corresponding PR - https://github.com/jbosstools/jbosstools-central/pull/314 > Remove File->New->RichFaces Project > ----------------------------------- > > Key: JBDS-3294 > URL: https://issues.jboss.org/browse/JBDS-3294 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > Reporter: Burr Sutter > Assignee: Fred Bricon > 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-3294) Remove File->New->RichFaces Project

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3294: --------------------------------- Summary: Remove File->New->RichFaces Project (was: Remove RichFaces tooling from default JBDS installation) > Remove File->New->RichFaces Project > ----------------------------------- > > Key: JBDS-3294 > URL: https://issues.jboss.org/browse/JBDS-3294 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central > 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] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-18869: -------------------------------------- -1 on pointing to Thym snaphots. We can probably use the release repo for Thym once we do the first release soon. I guess we prefer our own mirrors over Eclipse.org infrastructure for builds. In that case Jenkins job to update and with the generic URL seems the best solution to me > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- 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 updated JBDS-3294: --------------------------------- Component/s: (was: build) (was: installer) > 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: central > 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-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 updated JBDS-3294: --------------------------------- Fix Version/s: 9.0.0.Alpha1 > 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-3294) Remove RichFaces tooling from default JBDS installation

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3294: -------------------------------- > 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] (JBIDE-18869) migrate Thym from TP to being an aggregated component

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18869 at 12/19/14 12:09 PM: --------------------------------------------------------------- Merged: https://github.com/jbosstools/jbosstools-build/pull/161 https://github.com/jbosstools/jbosstools-build/pull/163 For review: https://github.com/jbosstools/jbosstools-build-sites/pull/165 https://github.com/jbdevstudio/jbdevstudio-product/pull/253 https://github.com/jbosstools/jbosstools-target-platforms/pull/113 Also, would it make sense to have the parent pom's version of $\{eclipse-thym-site} point to the snapshots site [1] or a specific mirror we've already pulled? And should we have to keep updating the parent pom with each new version of Thym, or would it make sense to just set this in the aggregate site's pom [2] instead? [1] http://download.eclipse.org/thym/snapshots/ [2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... Or, I suppose we could have a Jenkins job that simply creates a mirror of the Thym stuff every time Gorkem decides it's time to pull new bits; then we could just have a generic URL like: {code} <eclipse-thym-site>${jbosstools-site-baseurl}/eclipse-thym_${jbosstools-site-stream}/${jbosstools-site-suffix}</eclipse-thym-site> {code} WDYT [~gercan] [~maxandersen] [~mickael_istria] ? was (Author: nickboldt): Merged: https://github.com/jbosstools/jbosstools-build/pull/161 https://github.com/jbosstools/jbosstools-build/pull/163 For review: https://github.com/jbosstools/jbosstools-build-sites/pull/165 https://github.com/jbdevstudio/jbdevstudio-product/pull/253 https://github.com/jbosstools/jbosstools-target-platforms/pull/113 Also, would it make sense to have the parent pom's version of $\{eclipse-thym-site} point to the snapshots site [1] or a specific mirror we've already pulled? And should we have to keep updating the parent pom with each new version of Thym, or would it make sense to just set this in the aggregate site's pom [2] instead? [1] http://download.eclipse.org/thym/snapshots/ [2] https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... Or, I suppose we could have a Jenkins job that simply creates a mirror of the Thym stuff every time Gorkem decides it's time to pull new bits; then we could just have a generic URL like: {code} <eclipse-thym-site>$\{jbosstools-site-baseurl}/eclipse-thym_$\{jbosstools-site-stream}/$\{jbosstools-site-suffix}</eclipse-thym-site> {code} > migrate Thym from TP to being an aggregated component > ----------------------------------------------------- > > Key: JBIDE-18869 > URL: https://issues.jboss.org/browse/JBIDE-18869 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, build, target-platform, updatesite > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Because Thym changes frequently, and because Gorkem runs the project, we should treat it like a JBT project, not part of the TP. > This would allow it to be incorporated into builds more easily and would avoid TP churn. > This should be fixed in master then backported for 4.2.2 (or 4.2.3). -- 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