January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13451) Too many "xmlns:"-proposals when requesting content assist for tag attribute name

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13451?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13451: ---------------------------------------- Try the following: 1. Create a JSF 2 KickStart project. 2. Open inputname.xhtml 3. Ctrl+Space in <ui:composition | 4. FAILURE: There are two xhtml and xhtml* proposals. 5. Select xhtml proposal. 6. xhtml="" inserted and code assist for its value invoked. 7. FAILURE: There is no icon for the proposals in this list of URIs (default red square is used instead). > Too many "xmlns:"-proposals when requesting content assist for tag attribute name > --------------------------------------------------------------------------------- > > Key: JBIDE-13451 > URL: https://issues.jboss.org/browse/JBIDE-13451 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > When requesting the Content Assist for a tag attribute name there are too many "xmlns:" proposals in the proposal list. > Need to hide these proposals for all the tags other that a page root element by showing those namespace proposals only if the entered text matches the "xmlns:" string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13451) Too many "xmlns:"-proposals when requesting content assist for tag attribute name

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13451?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13451: ----------------------------------- Assignee: Victor Rubezhny (was: Alexey Kazakov) > Too many "xmlns:"-proposals when requesting content assist for tag attribute name > --------------------------------------------------------------------------------- > > Key: JBIDE-13451 > URL: https://issues.jboss.org/browse/JBIDE-13451 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha1 > > > When requesting the Content Assist for a tag attribute name there are too many "xmlns:" proposals in the proposal list. > Need to hide these proposals for all the tags other that a page root element by showing those namespace proposals only if the entered text matches the "xmlns:" string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-13439 at 1/30/13 5:13 PM: ---------------------------------------------------------------------- btw. the tests does not need to fail if the tests want to test the examples working. The tests could simply install a project examples into its setup and verify they actually work. Then have a separate test wether the expected examples are actually available when JBDS / JBT "proper" are installed. All depends on what the tests are trying to test: A) does the examples we got for testing/new version work B) are the examples available to users in default install. Right now the tests are testing A and B at the same time. was (Author: maxandersen): btw. the tests does not need to fail if the tests want to test the examples working. The tests could simply install a project examples into its setup and verify they actually work. Then have a separate test wether the expected examples are actually available when JBDS / JBT "proper" are installed. All depends on what the tests are trying to test. > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13439: --------------------------------------------- btw. the tests does not need to fail if the tests want to test the examples working. The tests could simply install a project examples into its setup and verify they actually work. Then have a separate test wether the expected examples are actually available when JBDS / JBT "proper" are installed. All depends on what the tests are trying to test. > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13439: --------------------------------------------- Regarding why things are split between jbds and jbt - its because in JBT we got things that are not yet supported which is not relevant for JBDS and vice versa. Note, it is not necessarily correct that ESB/SOA should install these examples since examples can state that they work best with a specific installed connector id from Central - making it possible to browse ESB examples and then install the missing plugins if relevant. We do the same for GWT and other examples which plugins we don't bundle by default. But it comes back to why we don't have ESB examples listed in JBDS 6 - there are no ESB plugins that will install on these. > ESB Tests are failing locating project examples > ----------------------------------------------- > > Key: JBIDE-13439 > URL: https://issues.jboss.org/browse/JBIDE-13439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > > Problem: > ESB tests stopped being able to find project examples when executing test. Why ? > Nick's original theory, but that does not answer why the content that is still there is not showing up: > Problem: > a) you're missing stuff in http://download.jboss.org/jbosstools/examples/ > b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder > c) yet no one bothered to audit that their content was properly published, aaaand... it's gone. > >> http://memegenerator.net/instance/33999035 << > Solution: > a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... > b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites > d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-8) JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-8?page=com.atlassian.jira.plugin.sy... ] Paul Leacu commented on JBTIS-8: -------------------------------- site.xml and the composite files have been updated: https://github.com/jbosstools/jbosstools-integration-stack/commit/1a43141... --paull > JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-8 > URL: https://issues.jboss.org/browse/JBTIS-8 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-13) JBossTools Integration Stack :: teiid: Verify the component configuration of the initial IS tooling release.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-13?page=com.atlassian.jira.plugin.s... ] Paul Leacu commented on JBTIS-13: --------------------------------- From Barry: FYI, As of 8.0 Teiid Designer, we no longer depend on UML2 UML2 has been removed: https://github.com/jbosstools/jbosstools-integration-stack/commit/1a43141... --paull > JBossTools Integration Stack :: teiid: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-13 > URL: https://issues.jboss.org/browse/JBTIS-13 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: teiid > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Barry LaFond > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13437) bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13437?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13437 at 1/30/13 2:04 PM: ------------------------------------------------------------- Pull request to fix update site (remove org.eclipse.bpel.jboss.riftsaw.runtime.feature, add org.eclipse.bpel.apache.ode.runtime.feature) and upversion everything to 1.2.100 (in master branch) https://github.com/jbosstools/jbosstools-bpel/pull/7 was (Author: nickboldt): Pull request to fix update site (remove org.eclipse.bpel.jboss.riftsaw.runtime.feature, add org.eclipse.bpel.apache.ode.runtime.feature) and upversion everything to 1.2.100 (in master branch) > bpel won't build in 40x branch due to missing org.eclipse.bpel.jboss.riftsaw.runtime.feature > -------------------------------------------------------------------------------------------- > > Key: JBIDE-13437 > URL: https://issues.jboss.org/browse/JBIDE-13437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, updatesite, UpStream > Affects Versions: 4.0.0.Alpha1-SOA > Reporter: Nick Boldt > Assignee: Robert (Bob) Brodt > Fix For: 4.0.0.Alpha1-SOA > > > JBoss BPEL builds are broken in 40x branch due to missing Eclipse.org bpel feature that is trying to be aggregated into the bpel site: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_stable_branch.component--bpel} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT > [ERROR] Missing requirement: bpel.site raw:0.1.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.1.0-SNAPSHOT requires 'org.eclipse.bpel.jboss.riftsaw.runtime.feature.feature.group 0.0.0' but it could not be found > {code} > Solution: remove the feature (and ask upstream why it vanished). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13451) Too many "xmlns:"-proposals when requesting content assist for tag attribute name

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13451?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13451: ----------------------------------- Issue Type: Enhancement (was: Feature Request) > Too many "xmlns:"-proposals when requesting content assist for tag attribute name > --------------------------------------------------------------------------------- > > Key: JBIDE-13451 > URL: https://issues.jboss.org/browse/JBIDE-13451 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > When requesting the Content Assist for a tag attribute name there are too many "xmlns:" proposals in the proposal list. > Need to hide these proposals for all the tags other that a page root element by showing those namespace proposals only if the entered text matches the "xmlns:" string. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-1792) CA: In xhtml files with facelets: no [xmlns:*=""] attribute in content assist .

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-1792?page=com.atlassian.jira.plugin... ] Alexey Kazakov resolved JBIDE-1792. ----------------------------------- Fix Version/s: 4.1.0.Alpha1 (was: LATER) Resolution: Duplicate Issue Yes, you right. Resolved as a duplicate of JBIDE-12175 > CA: In xhtml files with facelets: no [xmlns:*=""] attribute in content assist . > ------------------------------------------------------------------------------- > > Key: JBIDE-1792 > URL: https://issues.jboss.org/browse/JBIDE-1792 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 2.0.1 > Reporter: Andrei Scherbovich > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > CA: In xhtml files with facelets: > 1. no [xmlns:*=""] attribute in content assist > 2. CA when cursor at position [xmlns:*=" | "] not available for not <html> tags. I mean: > a) <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://java.sun.com/jsf/facelets" > xmlns:h="http://java.sun.com/jsf/html" > xmlns:j=" | "> -- HERE CONTENT ASSIST AVAILABLE > b) <h:form id="helloForm" xmlns:j=" | "> -- HERE CONTENT ASSIST NOT AVAILABLE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 January 2013