December 2014 - jbosstools-issues

[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)

11 years, 3 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)

11 years, 3 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)

11 years, 3 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18928) Create New and Noteworthy for 4.2.1.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18928?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-18928. ------------------------------------ Resolution: Done > Create New and Noteworthy for 4.2.1.Final > ----------------------------------------- > > Key: JBIDE-18928 > URL: https://issues.jboss.org/browse/JBIDE-18928 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.2.1.Final > > > This [query|https://issues.jboss.org/issues/?jql=((project%20in%20(JBDS)%20and%...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 commented on JBDS-3284: -------------------------------------- [~burrsutter] ^ > 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18678: ---------------------------------------- [~kaloyan-raev] thanks for the PR. We will take a look at it. > Make dependencies to org.jboss.tools.usage optional > --------------------------------------------------- > > Key: JBIDE-18678 > URL: https://issues.jboss.org/browse/JBIDE-18678 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim, usage > Affects Versions: 4.2.0.CR1 > Reporter: Kaloyan Raev > Assignee: Alexey Kazakov > Fix For: 4.3.x > > > I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build. > Is it possible to make the dependencies to org.jboss.tools.usage optional? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3259) Markdown Viewer

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3259?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3259: ----------------------------------- I am worried about overloading the 8.1 delivery so 9 is fine > Markdown Viewer > --------------- > > Key: JBDS-3259 > URL: https://issues.jboss.org/browse/JBDS-3259 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: 3rd-party-certification > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.2.GA, 9.0.0.Alpha1 > > Attachments: markdowneditor.gif > > > Most of our quickstarts and example applications come with a Markdown readme.md that provides the end-user with key instructions on how to execute the example. In today's Eclipse/JBDS, this markdown file is normally displayed as pure source/text. Ideally, the file would render just as it does for github, including with "clickable links". > The current poor "wrapping" is problematic for readability > http://www.screencast.com/t/n4Zvwv0W -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3300) include EAP 6.4 in JBDS installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3300?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3300: ---------------------------------- [~burrsutter] [~jpallich] [~maxandersen] [~rob.stryker] How soon do we want to include EAP 6.4 in JBDS 9? > include EAP 6.4 in JBDS installer > --------------------------------- > > Key: JBDS-3300 > URL: https://issues.jboss.org/browse/JBDS-3300 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: installer > Affects Versions: 9.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.GA > > > Include EAP 6.4 (or an early Alpha/Beta/CR?) in JBDS 9 installer, once it's available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3300) include EAP 6.4 in JBDS installer

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3300: -------------------------------- Summary: include EAP 6.4 in JBDS installer Key: JBDS-3300 URL: https://issues.jboss.org/browse/JBDS-3300 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: installer Affects Versions: 9.0.0.GA Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 9.0.0.GA Include EAP 6.4 (or an early Alpha/Beta/CR?) in JBDS 9 installer, once it's available. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 December 2014