July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20388) Renaming an FTL file doesn't update the path of the open editor

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20388?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20388: ---------------------------------- Fix Version/s: 4.3.0.CR1 > Renaming an FTL file doesn't update the path of the open editor > --------------------------------------------------------------- > > Key: JBIDE-20388 > URL: https://issues.jboss.org/browse/JBIDE-20388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.0.CR1 > > > Create a new file with name {{t1.ftl}}. Open it (with the FreeMarker IDE editor). In the Project Explorer's tree rename it to {{t2.ftl}}. Open {{t2.ftl}} too. Now you will have two open editors, both editing the same FTL file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20231) Freemarker New and Noteworthy for 4.3.0.Beta2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20231?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-20231. ----------------------------------- Resolution: Done Updated N&N to match actual feature provided. > Freemarker New and Noteworthy for 4.3.0.Beta2 > --------------------------------------------- > > Key: JBIDE-20231 > URL: https://issues.jboss.org/browse/JBIDE-20231 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20231) Freemarker New and Noteworthy for 4.3.0.Beta2

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20231?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20231: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-website/pull/448 (was: https://github.com/jbosstools/jbosstools-website/pull/445) > Freemarker New and Noteworthy for 4.3.0.Beta2 > --------------------------------------------- > > Key: JBIDE-20231 > URL: https://issues.jboss.org/browse/JBIDE-20231 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Freemarker is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Freemarker by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20245) OpenShift New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20245?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-20245. ------------------------------------ Resolution: Done Resolved but not closed, so, QE can verify and close it. > OpenShift New and Noteworthy for 4.3.0.Beta2 > -------------------------------------------- > > Key: JBIDE-20245 > URL: https://issues.jboss.org/browse/JBIDE-20245 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20245) OpenShift New and Noteworthy for 4.3.0.Beta2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20245?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-20245. ------------------------------- Resolution: Done PR applied in master > OpenShift New and Noteworthy for 4.3.0.Beta2 > -------------------------------------------- > > Key: JBIDE-20245 > URL: https://issues.jboss.org/browse/JBIDE-20245 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20244) server New and Noteworthy for 4.3.0.Beta2

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20244?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20244. --------------------------------- Resolution: Done I do not intend to document JBIDE-20057 since that's really hidden from user in most cases and shouldn't really be public. I do not intend to document JBIDE-17686 because the end-result should be hidden from the user, seen as a seamless migration really. It's kinda hard to document that you now won't see multiple different competing terminals when the user really only saw one before (since the others weren't in our TP). > server New and Noteworthy for 4.3.0.Beta2 > ----------------------------------------- > > Key: JBIDE-20244 > URL: https://issues.jboss.org/browse/JBIDE-20244 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15250. --------------------------------- Resolution: Done > Rob Stryker, how do I control whether the included jar project is exploded or zipped? Or is it either all exploded or all zipped including the ear? You cannot control it. It is based on what the server adapter itself supports. If we find that the server adapter itself supports something other than we implement, than we change the code. I'm sure that's not exactly satisifying to you, since it doesn't exactly provide you an easy way to override and test to see if our impl differs from reality :( > Explode utility jars in EAR/WAR deployments > ------------------------------------------- > > Key: JBIDE-15250 > URL: https://issues.jboss.org/browse/JBIDE-15250 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.0.1.Final > Reporter: Kevin Formsma > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: test-ear.zip > > > For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects. > A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20389: ------------------------------------ Could be lots of things... NFS mount / disk issues, memory issues, network lag/timeout/performance, bad test code (eg., things that don't setup/teardown correctly; sequence/serialization problems), missing OS stuff (like both the 32 and 64-bit libraries for swt or other eclipse stuff that Tycho/Surefire needs) ... > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20389: ------------------------------------- Attachment: openshift-builds.png > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20389: ------------------------------------------ [~nickboldt] any idea what could be wrong here? > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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