April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-732) JBDS-IS 9.0.0 GA Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-732?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-732: ------------------------------- Sprint: 25-Apr >> 08-May 2016-JBDS/JBT (was: 25-Apr >> 08-May 2016-JBDS/J 2) > JBDS-IS 9.0.0 GA Release Notes > ------------------------------ > > Key: TOOLSDOC-732 > URL: https://issues.jboss.org/browse/TOOLSDOC-732 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create Release Notes for GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Rob Stryker (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Rob Stryker (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Rob Stryker (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22209) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [OpenShift]

by Rob Stryker (JIRA)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-16647. ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) Resolution: Rejected Re-closed as Rejected. Not Done. > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22212) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22212?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22212. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [JST] > ----------------------------------------------------------------------------------- > > Key: JBIDE-22212 > URL: https://issues.jboss.org/browse/JBIDE-22212 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Rob Stryker > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [JST]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-jst at https://github.com/jbosstools/jbosstools-jst/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "850b5b" is the last common ancestor of jbosstools-4.3.x and master > 850b5b is 35 commits ago in branch master > 850b5b is 24 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-jst//commit/571f69e92999ec7efb39... > - https://github.com/jbosstools/jbosstools-jst//commit/60e28ed0b405ceca2923... > - https://github.com/jbosstools/jbosstools-jst//commit/090e37f543ea9f3268b7... > - https://github.com/jbosstools/jbosstools-jst//commit/80b09a2bae9520fbe4a7... > - https://github.com/jbosstools/jbosstools-jst//commit/a8fbc1875782258c207b... > - https://github.com/jbosstools/jbosstools-jst//commit/cb4c2a43064b65bf92bc... > - https://github.com/jbosstools/jbosstools-jst//commit/1e6b426c8c203e6b789a... > - https://github.com/jbosstools/jbosstools-jst//commit/3d30634f05154f895ae9... > - https://github.com/jbosstools/jbosstools-jst//commit/e9f70fb64d801715c607... > - https://github.com/jbosstools/jbosstools-jst//commit/40e71e7e78b3bf6ec0c7... > - https://github.com/jbosstools/jbosstools-jst//commit/50d6b9f93516ef3aaa8f... > - https://github.com/jbosstools/jbosstools-jst//commit/795628f2cd9bc72065bc... > - https://github.com/jbosstools/jbosstools-jst//commit/5ece87d8e385e99b76af... > - https://github.com/jbosstools/jbosstools-jst//commit/333c9a71aca9b449b5ba... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for JST task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22217) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Freemarker]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22217?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22217. ---------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Freemarker] > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22217 > URL: https://issues.jboss.org/browse/JBIDE-22217 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Rob Stryker > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Freemarker]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-freemarker at https://github.com/jbosstools/jbosstools-freemarker/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "171cac" is the last common ancestor of jbosstools-4.3.x and master > 171cac is 5 commits ago in branch master > 171cac is 8 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-freemarker//commit/a68fdbc4e1e29... > - https://github.com/jbosstools/jbosstools-freemarker//commit/75774bb9bb6ab... > - https://github.com/jbosstools/jbosstools-freemarker//commit/4d2c09250a53a... > - https://github.com/jbosstools/jbosstools-freemarker//commit/a0dcd63051033... > - https://github.com/jbosstools/jbosstools-freemarker//commit/d33f8812a72b9... > - https://github.com/jbosstools/jbosstools-freemarker//commit/b4c28ff7b02ec... > - https://github.com/jbosstools/jbosstools-freemarker//commit/283825f4e673a... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Freemarker task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21606: ------------------------------------- I tested this in an environment that has j8, j7, and j6 installed. When I use runtime detection, the server that gets created has an execution environment of j6. When I launch the server, it is launched in via the java6 jre as well, so I know there's no error there. When I import the html5 project it has the java6 attached to it with the java6 compiler settings. So... it seems both are taking the minimum allowed runtime environment. So if your workspace has one of each, it seems impossible to get into a situation where the project is compiled with j7 and the runtime targeting j6.... unless you add the j6 jre/jdk sometime after you import the html5 project? Can anyone else confirm what i'm seeing? > Consider using java 8 for EAP 6.4 by default > -------------------------------------------- > > 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.0.Alpha1 > > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22203) For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Aerogear]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22203?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-22203. ---------------------------------- Resolution: Done There are a few false positive commits in the list above. The rest is supposed to be in 4.3.x branch only. Closing the issue. [~gercan] please reopen if I missed anything. > For JBIDE 4.4.0.Alpha1: Find Missing Commits From jbosstools-4.3.x for master [Aerogear] > ---------------------------------------------------------------------------------------- > > Key: JBIDE-22203 > URL: https://issues.jboss.org/browse/JBIDE-22203 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Rob Stryker > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Aerogear]: Ensure all commits pushed to jbosstools-4.3.x have either been made in master, or are intentionally excluded from master. > Below are listed all commits made to jbosstools-4.3.x that have not been found in master. It is possible these commits do exist in master, but the patches are not identical. It is also possible that the commits made in jbosstools-4.3.x are not relevant to master or should not be applied. > If there are no commits listed below, please close (do not resolve) this issue. > Otherwise: > 1) Click on each link below. > 2) Evaluate whether the given commit *should* be in master > 3) If it should be in master, please find out why it is not in master. You may need to browse master's commit log to find a commit that should match. > 4) If you cannot find a matching commit, and it *should* be committed to master, please cherry-pick that commit to master or otherwise merge it in. > 5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in master, whether you have successfully merged it in now, or whether it is not intended to be committed to master or is inappropriate for master. > 6) When all complete, please close (do not resolve) this issue. > > Folder: jbosstools-aerogear at https://github.com/jbosstools/jbosstools-aerogear/ > Searching for commits present in jbosstools-4.3.x and missing from master > Commit hash "fbcaf6" is the last common ancestor of jbosstools-4.3.x and master > fbcaf6 is 10 commits ago in branch master > fbcaf6 is 20 commits ago in branch jbosstools-4.3.x > Commits missing from master that are in jbosstools-4.3.x: > - https://github.com/jbosstools/jbosstools-aerogear//commit/938198c0668e1f5... > - https://github.com/jbosstools/jbosstools-aerogear//commit/c5207dc9e034c51... > - https://github.com/jbosstools/jbosstools-aerogear//commit/b2f26d53504a256... > - https://github.com/jbosstools/jbosstools-aerogear//commit/fd189752b6f5209... > - https://github.com/jbosstools/jbosstools-aerogear//commit/002faaa2701ce0a... > - https://github.com/jbosstools/jbosstools-aerogear//commit/d1776c97ba01bbf... > - https://github.com/jbosstools/jbosstools-aerogear//commit/ec4a1312844e068... > - https://github.com/jbosstools/jbosstools-aerogear//commit/a7686517ded4ef9... > - https://github.com/jbosstools/jbosstools-aerogear//commit/58fbd4aa7342c66... > - https://github.com/jbosstools/jbosstools-aerogear//commit/7c3d92f4e47f85b... > - https://github.com/jbosstools/jbosstools-aerogear//commit/af2dba422b0617a... > - https://github.com/jbosstools/jbosstools-aerogear//commit/b03070aaf0ea89f... > - https://github.com/jbosstools/jbosstools-aerogear//commit/a37e1d0f565e234... > [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...], or [Search for Aerogear task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+an...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 April 2016