December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18980) New Table wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18980?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18980: ----------------------------------- Description: !table.png! > New Table wizard for HTML5 palette > ---------------------------------- > > Key: JBIDE-18980 > URL: https://issues.jboss.org/browse/JBIDE-18980 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: table.png > > > !table.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18980) New Table wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18980?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18980: ----------------------------------- Attachment: table.png > New Table wizard for HTML5 palette > ---------------------------------- > > Key: JBIDE-18980 > URL: https://issues.jboss.org/browse/JBIDE-18980 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: table.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3262: ------------------------------------- It should no be too difficult to remove it. It is basically standalone and noting depends on it except bundles with templates. Would be good if we do it for 9.0.0.Alpha1 and have chunk of binaries out of installer. > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 8.1.0.GA, 9.0.0.Alpha1 > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18914: --------------------------------------------- Same as Fred - i'm fine if we can outline/document how this wont break existing and past still installed releases. > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18869?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18869: --------------------------------------------- +1 to what Gorkem suggests. No using eclipse builds nor should we point to snapshots unless absolutely necessary. btw. I assume this is just for 4.3.0 not 4.2.0 ? (we should set the fix version approriately) And am I blind or is there not a PR for the parent pom that is missing to define the thym repo ? > 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] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3262: ------------------------------------------- #2 depends how soon we have a PR that does it. If it comes late or is super complex with too high risk we might just disable it by default. But all depends on how massive the PR/change is to remove it ? > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 8.1.0.GA, 9.0.0.Alpha1 > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3249: ------------------------------------------- [~nickboldt] as far as I can see all your points are mentioned in the related jiras - I believe we already agreed to go for the "all of JBDS IS installer" approach and if you press Finish very early on you get everything but otherwise the install wizard can let you choose subsets. This is all what the epic is about - container for the issues that relates to making it simpler to install Integration stack - today it requires multiple steps which can be reduced by providing market place entry and installer. I suggest we discuss the specifics of each approach in the specific jiras. > 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)

11 years, 3 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3294: -------------------------------------- Summary: Remove RichFaces tooling from default JBDS installation (was: Remove File->New->RichFaces Project) Alexey - this issue that orginally suggested to remove Richfaces is what Nick correctly deferred, JBIDE-18973 is what we agreed to do instead. Thus i'm renaming this issue back to its original suggestion so the comments/discusssion makes sense and we can track further work for the next versin in JBIDE-18973. > 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: 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)

11 years, 3 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3294?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-3294. ------------------------------------- Resolution: Deferred > 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: 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)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18981) New Text Input wizard for HTML5 palette

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-18981: --------------------------------------------- Summary: New Text Input wizard for HTML5 palette Key: JBIDE-18981 URL: https://issues.jboss.org/browse/JBIDE-18981 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.0.Alpha1 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Alpha1 -- 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