July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22261) Server Adapter: "Show in > Server Log" should open the current running pod log

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22261?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22261: -------------------------------- Sprint: devex #117 July 2016 > Server Adapter: "Show in > Server Log" should open the current running pod log > ------------------------------------------------------------------------------ > > Key: JBIDE-22261 > URL: https://issues.jboss.org/browse/JBIDE-22261 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Fix For: 4.4.x > > > It's currently not practical to open the log for the running server adapter. Users need to open the pod log from the OpenShift Explorer. > Instead, "Show in > Server Log" should open the current running pod log, from the OpenShift 3 Server adapter, in the Servers view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21657: ----------------------------------- Fix Version/s: 4.4.1.AM1 (was: 4.4.x) > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.1.AM1 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-21657: -------------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > set up jobs to handle building from PRs > --------------------------------------- > > Key: JBIDE-21657 > URL: https://issues.jboss.org/browse/JBIDE-21657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.1.AM1 > > > First experimental build: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... > Output: > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > "revision" : { > "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805", > "currentBranch" : "HEAD", > "knownReferences" : [{ > "name" : "origin", > "url" : "git://github.com/jbosstools/jbosstools-build-sites.git", > "ref" : "pr/221/merge" > }] > }, > {code} > http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui... > {code} > #Fri Feb 05 16:42:42 EST 2016 > null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > build log: > {code} > Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1 > originally caused by: > GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts. > ... > Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git > > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/* > Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge) > > git config core.sparsecheckout # timeout=10 > > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805 > {code} > vars: > {code} > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > -DghprbPullId=221 > -Dsha1=origin/pr/221/merge > "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts." > -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22682) "Show In > Web Browser on External Device..." is disabled for OpenShift Servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22682?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-22682. --------------------------------- Fix Version/s: 4.4.1.AM1 Resolution: Done Fixed in master > "Show In > Web Browser on External Device..." is disabled for OpenShift Servers > ------------------------------------------------------------------------------- > > Key: JBIDE-22682 > URL: https://issues.jboss.org/browse/JBIDE-22682 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, openshift > Affects Versions: 4.4.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.1.AM1 > > > Even though BrowserSim is installed, Show In > Web Browser on External Device is disabled for OpenShift Server adapters -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-20180: ---------------------------------- Description: In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. More puzzling cases with {{<}}; these break outline view too: * {{<#if x == '<'></#if><#macro m></#macro>}} * {{<#if x < 1></#if><#macro m></#macro>}} Note: There's an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, gives more detailed syntax highlighting, etc. was: In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. More puzzling cases with {{<}}; these break outline view too: * {{<#if x == '<'></#if><#macro m></#macro>}} * {{<#if x < 1></#if><#macro m></#macro>}} Note: There's in an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, more detailed syntax highlighting, etc. > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Fix For: 4.3.x, 4.4.x > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} > Note: There's an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, gives more detailed syntax highlighting, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Daniel Dekany updated JBIDE-20180: ---------------------------------- Description: In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. More puzzling cases with {{<}}; these break outline view too: * {{<#if x == '<'></#if><#macro m></#macro>}} * {{<#if x < 1></#if><#macro m></#macro>}} Note: There's in an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, more detailed syntax highlighting, etc. was: In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. More puzzling cases with {{<}}; these break outline view too: * {{<#if x == '<'></#if><#macro m></#macro>}} * {{<#if x < 1></#if><#macro m></#macro>}} > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Fix For: 4.3.x, 4.4.x > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} > Note: There's in an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, more detailed syntax highlighting, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Daniel Dekany edited comment on JBIDE-20180 at 7/5/16 2:34 AM: --------------------------------------------------------------- This is being worked on (https://github.com/ddekany/jbosstools-freemarker/tree/JBIDE-20180), but probably won't be practical to rebase on the master until JBIDE-22656 and JBIDE-20386 (and ideally JBIDE-22656) is merged. Also, it has turned into a major overhaul of the main partitioner, the coloring tokenizer and the {{ItemSet}} tokenizer, because these have to agree with each other. was (Author: ddekany): This is being worked on (https://github.com/ddekany/jbosstools-freemarker/tree/JBIDE-20180), but probably won't be practical to rebase on the master until JBIDE-22656 and JBIDE-20386 (and ideally JBIDE-22656) is merged. Also, it has turned into a major overhaul of the main partitioner, the coloring tokenizer and the NodeSet tokenizer, because these have to agree with each other. > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Fix For: 4.3.x, 4.4.x > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Daniel Dekany commented on JBIDE-20180: --------------------------------------- This is being worked on (https://github.com/ddekany/jbosstools-freemarker/tree/JBIDE-20180), but probably won't be practical to rebase on the master until JBIDE-22656 and JBIDE-20386 (and ideally JBIDE-22656) is merged. Also, it has turned into a major overhaul of the main partitioner, the coloring tokenizer and the NodeSet tokenizer, because these has to agree which each other. > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Fix For: 4.3.x, 4.4.x > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Daniel Dekany (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Daniel Dekany edited comment on JBIDE-20180 at 7/5/16 2:33 AM: --------------------------------------------------------------- This is being worked on (https://github.com/ddekany/jbosstools-freemarker/tree/JBIDE-20180), but probably won't be practical to rebase on the master until JBIDE-22656 and JBIDE-20386 (and ideally JBIDE-22656) is merged. Also, it has turned into a major overhaul of the main partitioner, the coloring tokenizer and the NodeSet tokenizer, because these have to agree with each other. was (Author: ddekany): This is being worked on (https://github.com/ddekany/jbosstools-freemarker/tree/JBIDE-20180), but probably won't be practical to rebase on the master until JBIDE-22656 and JBIDE-20386 (and ideally JBIDE-22656) is merged. Also, it has turned into a major overhaul of the main partitioner, the coloring tokenizer and the NodeSet tokenizer, because these has to agree which each other. > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Fix For: 4.3.x, 4.4.x > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21606: -------------------------------- Summary: Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6] (was: Consider using java 8 for EAP 6.4 by default) > Consider using java 8 for EAP 6.4 by default [ resolved making j7 default instead of j6] > ---------------------------------------------------------------------------------------- > > Key: JBIDE-21606 > URL: https://issues.jboss.org/browse/JBIDE-21606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > > Here's the problem that I just hit: > I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime. > Then on the project, I just Run -> Run on Server. > The server started, but deployment failed on Unsupported version: 51.0 > Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6. > So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016