February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18188) HTML5 Palette: filter to show only palette groups for which libraries are defined on the page

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18188?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-18188: --------------------------------------- [~vpakan], do you see Ionic Palette Group without filter button pressed? > HTML5 Palette: filter to show only palette groups for which libraries are defined on the page > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18188 > URL: https://issues.jboss.org/browse/JBIDE-18188 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.x > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: Filter1.png, Filter2.png > > > *Test case 1:* > 1. Open empty html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code} > {code} > ASSERT: > Follow palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Press the button "Show only palette groups for which libraries are defined on the page" > ASSERT: > No Palette groups are visible in HTML 5 Palette > *Test case 2:* > 1. Open follow html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code:html} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.ionicframework.com/1.0.0-beta.13/css/ionic.css" /> > <script src="http://code.ionicframework.com/1.0.0-beta.13/js/ionic.bundle.js"></script> > <meta charset="UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > {code} > ASSERT: > Follow palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Press the button "Show only palette groups for which libraries are defined on the page" > ASSERT: > Follow palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. HTML 5.0 > *Test case 3:* > 1. Open follow html file in Visual Page Editor and make sure button "Show only palette groups for which libraries are defined on the page" is not selected > {code:html} > <!DOCTYPE html> > <html> > <head> > <meta name="viewport" content="width=device-width, initial-scale=1"> > <link rel="stylesheet" href="http://code.jquery.com/mobile/1.4.4/jquery.mobile-1.4.4.min.css" /> > <script src="http://code.jquery.com/jquery-2.0.3.min.js"></script> > <script src="http://code.jquery.com/mobile/1.4.4/jquery.mobile-1.4.4.min.js"></script> > <meta charset="UTF-8"> > <title>Insert title here</title> > </head> > <body> > </body> > </html> > {code} > ASSERT: > Follow palette groups visible on HTML 5 Palette: > 1. Ionic 1.0 > 2. jQuery Mobile 1.4 > 3. HTML 5.0 > 2. Press the button "Show only palette groups for which libraries are defined on the page" > ASSERT: > Follow palette groups visible on HTML 5 Palette: > 1. jQuery Mobile 1.4 > 2. HTML 5.0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3355) Missing zip file for JBDS 8.0.2.GA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3355?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3355: ------------------------------------ Assignee: Max Rydahl Andersen > Missing zip file for JBDS 8.0.2.GA > ---------------------------------- > > Key: JBDS-3355 > URL: https://issues.jboss.org/browse/JBDS-3355 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.2.GA > Reporter: Andrej Podhradsky > Assignee: Max Rydahl Andersen > Priority: Blocker > > I cannot find zip file for JBDS 8.0.2.GA. > At https://www.jboss.org/products/devstudio/download/ and also in CSP there is only zip file for 8.0.0.GA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3355) Missing zip file for JBDS 8.0.2.GA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3355?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3355: -------------------------------------- You can find the zip here - http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html#zips And I'm not sure who controls https://www.jboss.org/products/devstudio/download/ [~maxandersen]? > Missing zip file for JBDS 8.0.2.GA > ---------------------------------- > > Key: JBDS-3355 > URL: https://issues.jboss.org/browse/JBDS-3355 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 8.0.2.GA > Reporter: Andrej Podhradsky > Priority: Blocker > > I cannot find zip file for JBDS 8.0.2.GA. > At https://www.jboss.org/products/devstudio/download/ and also in CSP there is only zip file for 8.0.0.GA. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18597) when using 'server' keyword in New Wizard and "Tern" shows up

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18597?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18597: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > when using 'server' keyword in New Wizard and "Tern" shows up > -------------------------------------------------------------- > > Key: JBIDE-18597 > URL: https://issues.jboss.org/browse/JBIDE-18597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing, upstream > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Fix For: 4.3.0.Alpha2 > > Attachments: image.png, image1.png, image2.png > > > EXECUTE: File > New > EXECUTE: Type "server" in keyword. > ASSERT: things non-related to server should not show up - like Tern. > FAILURE: Tern shows up > > See > https://www.dropbox.com/s/b3ecwm6ok1um0ab/Screenshot%202014-10-13%2015.02... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19333) Ensure all component jobs have access to java 5, 6, 7, and 8 via jre properties

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19333: ----------------------------------- Summary: Ensure all component jobs have access to java 5, 6, 7, and 8 via jre properties Key: JBIDE-19333 URL: https://issues.jboss.org/browse/JBIDE-19333 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Reporter: Rob Stryker Please ensure all jobs in master (and maybe Luna?) have access to the various java installations. This should be done similar to the files in https://github.com/jbdevstudio/jbdevstudio-ci/pull/146 This will mostly involve adding the java17 and java18 variables to all jobs and the sysprops, but may involve cleaning up some jobs who do it incorrectly (such as web services, who puts it in the ${maven_flags} variable) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3354) Seam 2 is still included in JBDS 9 Alpha1 installed from jar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3354?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3354: -------------------------------------- Seam 3 tools supports a lot of Seam3 CDI extensions. For example: - Seam Solder: JBIDE-8195 (@Veto, @Requires, @Exact, @MessageLogger, @MessageBundle, @DefaultBean, @Unwraps, @ServiceHandlerType, @FullyQualified, @Resource, etc.) - sea-beans.xml editor: JBIDE-3120 - Seam Servlet - Seam Persistence - etc. Here you can find a full list of implemented features: - http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M1.html - http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M2.html - http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M3.html - http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M4.html - http://docs.jboss.org/tools/whatsnew/cdi/cdi-news-3.3.0.M5.html We spent a lot of time to make an advance Seam 3 Tools. But I wander if anybody uses Seam 3 (I mean Seam 3 runtime, not our tools for it) at all? > Seam 2 is still included in JBDS 9 Alpha1 installed from jar > ------------------------------------------------------------ > > Key: JBDS-3354 > URL: https://issues.jboss.org/browse/JBDS-3354 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, cdi, seam > Affects Versions: 9.0.0.Alpha1 > Reporter: Martin Malina > Assignee: Fred Bricon > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > It seems to me that we removed the wrong feature. > This is JBDS 8.0.2: > {code} > nattura:features rasp$ ls |grep seam > org.jboss.tools.cdi.seam.feature_1.6.1.Final-v20141209-0505-B79 > org.jboss.tools.maven.seam.feature_1.6.1.Final-v20150109-2320-B116 > org.jboss.tools.runtime.seam.detector.feature_3.6.1.Final-v20141209-0505-B79 > org.jboss.tools.seam.feature_3.6.1.Final-v20141209-0505-B79 > {code} > And this is JBDS 9.0.0.Alpha1 B11: > {code} > nattura:features rasp$ ls |grep seam > org.jboss.tools.seam.feature_3.7.0.Alpha1-v20150213-0551-B3 > {code} > When you look at plugins, it looks as follows: > JBDS 8.0.2: > {code} > nattura:plugins rasp$ ls|grep seam > org.jboss.tools.cdi.seam.config.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.config.ui_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.faces.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.solder.core_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.cdi.seam.text.ext_1.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.jsf.vpe.seam_3.6.1.Final-v20141209-0505-B79 > org.jboss.tools.maven.seam_1.6.1.Final-v20150109-2320-B116.jar > org.jboss.tools.runtime.seam.detector_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.core_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.pages.xml_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.text.ext_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.ui.pages_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.ui_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.xml.ui_3.6.1.Final-v20141209-0505-B79.jar > org.jboss.tools.seam.xml_3.6.1.Final-v20141209-0505-B79.jar > {code} > JBDS 9.0.0.Alpha1 B11: > {code} > nattura:plugins rasp$ ls|grep seam > org.jboss.tools.cdi.seam.solder.core_1.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.jsf.vpe.seam_3.7.0.Alpha1-v20150213-0551-B3 > org.jboss.tools.seam.core_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.pages.xml_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.text.ext_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.ui.pages_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.ui_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.xml.ui_3.7.0.Alpha1-v20150213-0551-B3.jar > org.jboss.tools.seam.xml_3.7.0.Alpha1-v20150213-0551-B3.jar > {code} > For JBoss Tools, both are there (seam and cdi.seam) - I'm not sure if that's intentional. Is there a JIRA for dropping seam? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19321) Unable to close Restore Cordova Plugin Dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19321?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19321: --------------------------------------- Cannot replicate that under Linux. "Restore Cordova Plug-in" dialog needs some progress information to be shown or it just stays completely looked for a while, but that is usability issue. > Unable to close Restore Cordova Plugin Dialog > --------------------------------------------- > > Key: JBIDE-19321 > URL: https://issues.jboss.org/browse/JBIDE-19321 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: MS Windows 7 64 bit JBDS 9.0.0.Alpha1-v20150216-1042-B11 > Reporter: Vlado Pakan > Priority: Critical > > # Import project https://github.com/aerogear/aerogear-push-quickstarts/tree/master/client/... as Hyrid Mobile Project > # Click on Finish button of dialog with title "Restore Cordova Plug-In" > ERROR: Dialog is not closed even when clicking many times > Button Cancel works -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18915) Create Icons for Batch tools

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18915: ---------------------------------- Attachment: (was: plan.png) > Create Icons for Batch tools > ---------------------------- > > Key: JBIDE-18915 > URL: https://issues.jboss.org/browse/JBIDE-18915 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Viacheslav Kabanovich > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha1 > > Attachments: batchlet.png, batch_editor.png, batch_editor_icon.png, batch_icon16.png, batch_node_icon.png, checkpoint-algorithm.png, chunk.png, decision.png, end.png, fail.png, flow.png, listener.png, listeners.png, next.png, partition.png, processor.png, properties.png, property.png, reader.png, split.png, step.png, stop.png, writer.png > > > batch_icon16.png - file batch.xml (initial image is attached, it can be replaced or used) > * *batchlet.png* - 'batchlet' element specifies a task-oriented batch step > * *checkpoint-algorithm.png* - an optional custom checkpoint algorithm that may be used to provide a checkpoint decision based on factors other than only number of items, or amount of time > * *chunk.png* - kind of step that processes multiple items and is periodically checkpointed by the batch runtime according to a configured checkpoint policy > * *decision.png* - decision provides a customized way of determining sequencing among steps, flows, and splits (batch status is set to FAILED) > * *end.png* - end element is used to terminate the job at the current step (batch status is set to COMPLETED) > * *fail.png* - fail element is used to terminate the job at the conclusion of the current step or flow > * *flow.png* - flow defines a sequence of execution elements that execute together as a unit > * *job.png* - root node of file batch.xml, it may be the same as batch_icon16.png > * *listeners.png* - folder for listeners > * *listener.png* - job listener > * *next.png* - transition element that defines condition and target for transition to next step. > * *partition.png* - 'partition' element specifies that a step is a partitioned step > * *processor.png* - 'processor' element specifies the item processor for a chunk step > * *properties.png* - folder for properties > * *property.png* - common 'name'='value' object. > * *reader.png* - 'reader' element specifies the item reader for a chunk step > * *split.png* - split defines a set of flows that execute concurrently > * *step.png* - 'step' element identifies a job step, job may contain any number of steps > * *stop.png* - stop element is used to terminate the job after the current step or flow (batch status is set to STOPPED), optionally defines step at which job can be restarted > * *writer.png* - 'writer' element specifies the item writer for a chunk step -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18915) Create Icons for Batch tools

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18915: ---------------------------------- Attachment: (was: reducer.png) > Create Icons for Batch tools > ---------------------------- > > Key: JBIDE-18915 > URL: https://issues.jboss.org/browse/JBIDE-18915 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Viacheslav Kabanovich > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha1 > > Attachments: batchlet.png, batch_editor.png, batch_editor_icon.png, batch_icon16.png, batch_node_icon.png, checkpoint-algorithm.png, chunk.png, decision.png, end.png, fail.png, flow.png, listener.png, listeners.png, next.png, partition.png, processor.png, properties.png, property.png, reader.png, split.png, step.png, stop.png, writer.png > > > batch_icon16.png - file batch.xml (initial image is attached, it can be replaced or used) > * *batchlet.png* - 'batchlet' element specifies a task-oriented batch step > * *checkpoint-algorithm.png* - an optional custom checkpoint algorithm that may be used to provide a checkpoint decision based on factors other than only number of items, or amount of time > * *chunk.png* - kind of step that processes multiple items and is periodically checkpointed by the batch runtime according to a configured checkpoint policy > * *decision.png* - decision provides a customized way of determining sequencing among steps, flows, and splits (batch status is set to FAILED) > * *end.png* - end element is used to terminate the job at the current step (batch status is set to COMPLETED) > * *fail.png* - fail element is used to terminate the job at the conclusion of the current step or flow > * *flow.png* - flow defines a sequence of execution elements that execute together as a unit > * *job.png* - root node of file batch.xml, it may be the same as batch_icon16.png > * *listeners.png* - folder for listeners > * *listener.png* - job listener > * *next.png* - transition element that defines condition and target for transition to next step. > * *partition.png* - 'partition' element specifies that a step is a partitioned step > * *processor.png* - 'processor' element specifies the item processor for a chunk step > * *properties.png* - folder for properties > * *property.png* - common 'name'='value' object. > * *reader.png* - 'reader' element specifies the item reader for a chunk step > * *split.png* - split defines a set of flows that execute concurrently > * *step.png* - 'step' element identifies a job step, job may contain any number of steps > * *stop.png* - stop element is used to terminate the job after the current step or flow (batch status is set to STOPPED), optionally defines step at which job can be restarted > * *writer.png* - 'writer' element specifies the item writer for a chunk step -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18915) Create Icons for Batch tools

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18915?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18915: ---------------------------------- Attachment: (was: retryable-exception-classes.png) > Create Icons for Batch tools > ---------------------------- > > Key: JBIDE-18915 > URL: https://issues.jboss.org/browse/JBIDE-18915 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Viacheslav Kabanovich > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha1 > > Attachments: batchlet.png, batch_editor.png, batch_editor_icon.png, batch_icon16.png, batch_node_icon.png, checkpoint-algorithm.png, chunk.png, decision.png, end.png, fail.png, flow.png, listener.png, listeners.png, next.png, partition.png, processor.png, properties.png, property.png, reader.png, split.png, step.png, stop.png, writer.png > > > batch_icon16.png - file batch.xml (initial image is attached, it can be replaced or used) > * *batchlet.png* - 'batchlet' element specifies a task-oriented batch step > * *checkpoint-algorithm.png* - an optional custom checkpoint algorithm that may be used to provide a checkpoint decision based on factors other than only number of items, or amount of time > * *chunk.png* - kind of step that processes multiple items and is periodically checkpointed by the batch runtime according to a configured checkpoint policy > * *decision.png* - decision provides a customized way of determining sequencing among steps, flows, and splits (batch status is set to FAILED) > * *end.png* - end element is used to terminate the job at the current step (batch status is set to COMPLETED) > * *fail.png* - fail element is used to terminate the job at the conclusion of the current step or flow > * *flow.png* - flow defines a sequence of execution elements that execute together as a unit > * *job.png* - root node of file batch.xml, it may be the same as batch_icon16.png > * *listeners.png* - folder for listeners > * *listener.png* - job listener > * *next.png* - transition element that defines condition and target for transition to next step. > * *partition.png* - 'partition' element specifies that a step is a partitioned step > * *processor.png* - 'processor' element specifies the item processor for a chunk step > * *properties.png* - folder for properties > * *property.png* - common 'name'='value' object. > * *reader.png* - 'reader' element specifies the item reader for a chunk step > * *split.png* - split defines a set of flows that execute concurrently > * *step.png* - 'step' element identifies a job step, job may contain any number of steps > * *stop.png* - stop element is used to terminate the job after the current step or flow (batch status is set to STOPPED), optionally defines step at which job can be restarted > * *writer.png* - 'writer' element specifies the item writer for a chunk step -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015