May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8526: --------------------------------- Story Points: 1 > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18243) Freemarker syntax highlight requires file reopening

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18243?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18243: ---------------------------------- Story Points: 1 > Freemarker syntax highlight requires file reopening > --------------------------------------------------- > > Key: JBIDE-18243 > URL: https://issues.jboss.org/browse/JBIDE-18243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > When pasting some code into ftl file, syntax highlight is not activated until file is saved closed and reopened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19590: --------------------------------------- See attached screen !hibernate-psf-import.mp4! cast how to use hibernate .psf file (you can skip middle part while it is downloading repos). At first version I included only dependencies in this file (hence the name is dependencies.psf in PR, but we can change it later), then I realized it is easier to import everything, then add remote to personal github.com fork to push branches for pull requests. There are still couple manual steps tough related to preferences configuration: - disable API Baseline - select .target file Would be good to have support for preferences import in .psf files then everything would be done in one step. > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: hibernate-psf-import.mp4 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19590: ---------------------------------- Attachment: hibernate-psf-import.mp4 > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: hibernate-psf-import.mp4 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19780) Confusing <id> placeholder in Batch Diagram editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19780?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19780: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Confusing <id> placeholder in Batch Diagram editor > -------------------------------------------------- > > Key: JBIDE-19780 > URL: https://issues.jboss.org/browse/JBIDE-19780 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > Fix For: 4.3.0.Beta1 > > > Currently, when no id of an element is entered, the "<id>" label is displayed in the node. > This caused issues during usability testing. User for some reason thought the "<>" characters have some meaning and edited the value to "<myId>" and then was confused why he sees "&lt" and "&gt" sequences in the XML. > Note that sapphire does not have placeholders, so this is just a workaround (when id is null, the <id> text is shown). > This approach is has also disadvantage that if user double click the <id> of empty id, presses an arrow and then enter, the whole <id> value originally meant as a placeholder is now the literal value of the property. > I suggest keeping the place for label just empty. User can be still notified by a validation marker and the label inline editor is still accessible by double click. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19780) Confusing <id> placeholder in Batch Diagram editor

by Tomáš Milata (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19780?page=com.atlassian.jira.plugi... ] Tomáš Milata updated JBIDE-19780: --------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/332 > Confusing <id> placeholder in Batch Diagram editor > -------------------------------------------------- > > Key: JBIDE-19780 > URL: https://issues.jboss.org/browse/JBIDE-19780 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Tomáš Milata > Assignee: Tomáš Milata > Priority: Minor > Labels: usability > > Currently, when no id of an element is entered, the "<id>" label is displayed in the node. > This caused issues during usability testing. User for some reason thought the "<>" characters have some meaning and edited the value to "<myId>" and then was confused why he sees "&lt" and "&gt" sequences in the XML. > Note that sapphire does not have placeholders, so this is just a workaround (when id is null, the <id> text is shown). > This approach is has also disadvantage that if user double click the <id> of empty id, presses an arrow and then enter, the whole <id> value originally meant as a placeholder is now the literal value of the property. > I suggest keeping the place for label just empty. User can be still notified by a validation marker and the label inline editor is still accessible by double click. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19780) Confusing <id> placeholder in Batch Diagram editor

by Tomáš Milata (JIRA)

Tomáš Milata created JBIDE-19780: ------------------------------------ Summary: Confusing <id> placeholder in Batch Diagram editor Key: JBIDE-19780 URL: https://issues.jboss.org/browse/JBIDE-19780 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: batch Affects Versions: 4.3.0.Beta1 Reporter: Tomáš Milata Assignee: Tomáš Milata Priority: Minor Currently, when no id of an element is entered, the "<id>" label is displayed in the node. This caused issues during usability testing. User for some reason thought the "<>" characters have some meaning and edited the value to "<myId>" and then was confused why he sees "&lt" and "&gt" sequences in the XML. Note that sapphire does not have placeholders, so this is just a workaround (when id is null, the <id> text is shown). This approach is has also disadvantage that if user double click the <id> of empty id, presses an arrow and then enter, the whole <id> value originally meant as a placeholder is now the literal value of the property. I suggest keeping the place for label just empty. User can be still notified by a validation marker and the label inline editor is still accessible by double click. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19590: --------------------------------------- PR with .psf file attached. > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19590: --------------------------------------- I am trying to create Team Project Set for hibernate and it seems some projects are missing .project files. problem is every project references in .psf file must have .project file ore import fails fish error: {code}Filed to read project description file from location ...{code} First problem is jbosstools-target-platforms/jbosstools/multiple/ maven module missing project description JBIDE-19778. > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19757: --------------------------------------------- have we gotten response/feedback from QE on if they see a time difference ? for now seem to just be Michael tested on his connection ? > Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19757 > URL: https://issues.jboss.org/browse/JBIDE-19757 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml. > Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... ) > In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery. > However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing > {code} > !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088 > !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null". > {code} > because we are lines specifying bundle but no version in the site.xml. > [~nickboldt] What are those site.xml useful for? Could we get rid of them? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 May 2015