June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16859) JSF tag libraries registred in XML catalog in plugins packed into JARs are not available for KB

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16859?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-16859. ------------------------------------ Resolution: Done Fixed in JBIDE-16096 > JSF tag libraries registred in XML catalog in plugins packed into JARs are not available for KB > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16859 > URL: https://issues.jboss.org/browse/JBIDE-16859 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta3 > > > 1. Create a JSF 2.2 KickStart project with WildFly 8 target server. > 2. Open inputname.xhtml with JBoss XHTML editor. > 3. FAILURE: inputname uses http://java.sun.com/jsf/* namespaces instead of http://xmlns.jcp.org/jsf/* > 4. Replace all http://java.sun.com/jsf/* by http://xmlns.jcp.org/jsf/*: > {code} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:ez="http://xmlns.jcp.org/jsf/composite/demo"> > {code} > 5. FAILURE: Content assist for <h: <f: <ui: <ez: is not working -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16929) Code Assist for <h:link value ""> is missing items "/resources", "/templates", "/pages"

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16929?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-16929. ------------------------------------ Resolution: Done Fixed in JBIDE-16096 > Code Assist for <h:link value ""> is missing items "/resources","/templates","/pages" > -------------------------------------------------------------------------------------- > > Key: JBIDE-16929 > URL: https://issues.jboss.org/browse/JBIDE-16929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1-v20140323-1410-B78, Linux > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta3 > > > 1. Create JSF 2 project > 2. Open inputname.xhtml page > 3. Insert <h:link value=""> tag > 4. Call Code Assist for value attribute > ERROR: Code Assist doesn't contain items: "/resources","/templates","/pages". > Code Assist for <link href=""> href attribute contains these items -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17493) Duplicate certification and category ids not permitted in Core and EA plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17493?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17493: ------------------------------------ [~mickael_istria] PR is good, +1. *However*, the PR only fixes half of the two issues reported here: {code} Duplicate category id 'org.jboss.tools.central.discovery.a.web' {code} is not the same as {code} Duplicate certification id 'com.jboss.jbds.discovery.certification.earlyaccess' {code} So... do we want to have different categories for the EA features vs. Core ones? eg. could have *org.jboss.tools.central.discovery.a.web.ea* ? Should the EA features be filtered above or below the Core ones? I would think below. WDYT? > Duplicate certification and category ids not permitted in Core and EA plugins > ----------------------------------------------------------------------------- > > Key: JBIDE-17493 > URL: https://issues.jboss.org/browse/JBIDE-17493 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-b > Fix For: 4.2.0.Beta2 > > > {code} > Duplicate certification id 'com.jboss.jbds.discovery.certification.earlyaccess': declaring sources: org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_3125701552832129620.jar, org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_7047926761596595680.jar > Duplicate category id 'org.jboss.tools.central.discovery.a.web': declaring sources: org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_3125701552832129620.jar, org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_7047926761596595680.jar > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16129: ---------------------------------- Sprint: Sprint to Beta3 Release > Environment Variables wizard: Refresh should warn that it'll undo all changes > ----------------------------------------------------------------------------- > > Key: JBIDE-16129 > URL: https://issues.jboss.org/browse/JBIDE-16129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: env_var_wizard > Fix For: 4.2.0.Beta3 > > Attachments: RefreshVariables.png > > > In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-16129: ---------------------------------- Fix Version/s: 4.2.0.Beta3 (was: 4.2.x) > Environment Variables wizard: Refresh should warn that it'll undo all changes > ----------------------------------------------------------------------------- > > Key: JBIDE-16129 > URL: https://issues.jboss.org/browse/JBIDE-16129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: env_var_wizard > Fix For: 4.2.0.Beta3 > > Attachments: RefreshVariables.png > > > In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17519) migrate target platform README / scriptlet to an actual bash script

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17519?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17519: ------------------------------------ New instructions: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... Linked-to instructions: https://github.com/jbosstools/jbosstools-target-platforms/blob/4.40.x/REA... https://github.com/jbosstools/jbosstools-target-platforms/blob/master/REA... https://github.com/jbosstools/jbosstools-discovery/blob/master/README.ado... New script, which fails visibly if a step fails (in the past it would fail but keep going- now it blocks subsequent steps): https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/verify... > migrate target platform README / scriptlet to an actual bash script > ------------------------------------------------------------------- > > Key: JBIDE-17519 > URL: https://issues.jboss.org/browse/JBIDE-17519 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Beta2 > > > Currently, there are three versions of this scriplet: > https://github.com/jbosstools/jbosstools-discovery/blob/master/README.bui... > https://github.com/jbosstools/jbosstools-target-platforms/tree/master/#up... > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x/#up... > Instead, we should move this here: > https://github.com/jbosstools/jbosstools-build-ci/tree/master/util/verify... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17519) migrate target platform README / scriptlet to an actual bash script

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17519?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-17519. ------------------------------ Resolution: Done Closing, done. > migrate target platform README / scriptlet to an actual bash script > ------------------------------------------------------------------- > > Key: JBIDE-17519 > URL: https://issues.jboss.org/browse/JBIDE-17519 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Beta2 > > > Currently, there are three versions of this scriplet: > https://github.com/jbosstools/jbosstools-discovery/blob/master/README.bui... > https://github.com/jbosstools/jbosstools-target-platforms/tree/master/#up... > https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x/#up... > Instead, we should move this here: > https://github.com/jbosstools/jbosstools-build-ci/tree/master/util/verify... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-16129: ---------------------------------- Attachment: RefreshVariables.png > Environment Variables wizard: Refresh should warn that it'll undo all changes > ----------------------------------------------------------------------------- > > Key: JBIDE-16129 > URL: https://issues.jboss.org/browse/JBIDE-16129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: env_var_wizard > Fix For: 4.2.x > > Attachments: RefreshVariables.png > > > In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ] Daniel Azarov reassigned JBIDE-16129: ------------------------------------- Assignee: Andre Dietisheim > Environment Variables wizard: Refresh should warn that it'll undo all changes > ----------------------------------------------------------------------------- > > Key: JBIDE-16129 > URL: https://issues.jboss.org/browse/JBIDE-16129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: env_var_wizard > Fix For: 4.2.x > > Attachments: RefreshVariables.png > > > In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16129) Environment Variables wizard: Refresh should warn that it'll undo all changes

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16129?page=com.atlassian.jira.plugi... ] Daniel Azarov commented on JBIDE-16129: --------------------------------------- [~adietish], please review my PR: !RefreshVariables.png! > Environment Variables wizard: Refresh should warn that it'll undo all changes > ----------------------------------------------------------------------------- > > Key: JBIDE-16129 > URL: https://issues.jboss.org/browse/JBIDE-16129 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Marián Labuda > Priority: Minor > Labels: env_var_wizard > Fix For: 4.2.x > > Attachments: RefreshVariables.png > > > In Edit Environment variables shell the Refresh button undo local changes - all changes upon local variables (removed/added/modified) are commited after click on Finish button. So if someone try to modify more environment variables and then "accidentally" click on Refresh button, then all local changes are disposed and variables are refreshed from server. There should be probably some warning before this action to let the user be sure about consequences of his action. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 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 June 2014