February 2016 - jbosstools-issues

[JBoss JIRA] (JBTIS-343) Remove obsolete project examples for ESB (SOA-P 4.3)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-343?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-343: ---------------------------------- [~bfitzpat] - Hey Fitz - could you review and push? This moves ESB to Mars and removes the 4.x quickstart examples. Thkx! https://github.com/jbosstools/jbosstools-esb/pull/70 > Remove obsolete project examples for ESB (SOA-P 4.3) > ---------------------------------------------------- > > Key: JBTIS-343 > URL: https://issues.jboss.org/browse/JBTIS-343 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: ESB > Affects Versions: 8.0.0.GA > Reporter: Tomáš Sedmík > Assignee: Brian Fitzpatrick > Priority: Minor > Attachments: ESB - Project Examples.png > > > In _File --> New --> Example... --> JBoss Tools --> Project Examples_ is obsolete category _ESB for JBoss Enterprise SOA Platform 4.3_ (see attachment). IMHO it should be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21725: ------------------------------- Description: Martin said: {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. What do you think? Makes sense? So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} Nick said: {quote}Makes sense. When stable, add to TP; until stable, just use nightly. Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} was: We would like to add RedDeer 1.0.1 to target platform. Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. Github repo: https://github.com/jboss-reddeer/reddeer Wiki: https://github.com/jboss-reddeer/reddeer/wiki 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) Feature: org.jboss.reddeer.eclipse.feature -- Story points - 5 (fibonacci): * send announcement email re: TP changes, * update TP, * PR to fix integration-tests (simpler repo deps in root pom), * check if anything else depends on Red Deer and submit PR to remove that / depend on TP instead > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Martin said: > {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. > I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. > After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. > What do you think? Makes sense? > So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} > Nick said: > {quote}Makes sense. When stable, add to TP; until stable, just use nightly. > Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21725: ------------------------------- Story Points: 2 (was: 5) > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > Martin said: > {quote}Nick Boldt, ok, I will discuss this with others and then get back to you - I'm not sure if now is the right time to pull a nightly or we should wait. > I think the intention was to have this in the TP so that we know exactly what is used with which version of JBT - just look in the corresponding TP. That's also how it works for server depending on base - it's the same version. But pointing to RedDeer master repo is different. > After discussion with Rastislav Wagner, here's our proposal: What if we stick with RedDeer master repo in our pom for integration tests master? For maintenance branch (4.3.x), it's good that we have a stable version of RedDeer in the TP and we can use that. But for JBT master, we can rely on the RedDeer master repo directly and later when we start testing JBT 4.4.0.Alpha1, we may put some version of RedDeer to the TP and switch to that. > What do you think? Makes sense? > So if you agree, this would mean that for now we won't use RedDeer in TP 4.60.0 - so either you can just leave it there until we replace it with a new version, or you could even remove it.{quote} > Nick said: > {quote}Makes sense. When stable, add to TP; until stable, just use nightly. > Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL.{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21725: ---------------------------------- Summary: Use RedDeer 1.x nightly in master builds Key: JBIDE-21725 URL: https://issues.jboss.org/browse/JBIDE-21725 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Affects Versions: 4.3.1.Beta2 Reporter: Martin Malina Assignee: Nick Boldt Fix For: 4.3.1.CR1 We would like to add RedDeer 1.0.1 to target platform. Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. Github repo: https://github.com/jboss-reddeer/reddeer Wiki: https://github.com/jboss-reddeer/reddeer/wiki 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) Feature: org.jboss.reddeer.eclipse.feature -- Story points - 5 (fibonacci): * send announcement email re: TP changes, * update TP, * PR to fix integration-tests (simpler repo deps in root pom), * check if anything else depends on Red Deer and submit PR to remove that / depend on TP instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21725) Use RedDeer 1.x nightly in master builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21725?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21725: ------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Use RedDeer 1.x nightly in master builds > ---------------------------------------- > > Key: JBIDE-21725 > URL: https://issues.jboss.org/browse/JBIDE-21725 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature > -- > Story points - 5 (fibonacci): > * send announcement email re: TP changes, > * update TP, > * PR to fix integration-tests (simpler repo deps in root pom), > * check if anything else depends on Red Deer and submit PR to remove that / depend on TP instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21405: ------------------------------------ Makes sense. When stable, add to TP; until stable, just use nightly. Re: updating 4.60.0.Alpha1, unless there's a compelling reason to remove it from the TP, I'm good to leave 1.0.1 in there [1]. [1] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... Let me know if you need assistance setting up your pom to depend on Red Deer 1.x nightly URL. > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature > -- > Story points - 5 (fibonacci): > * send announcement email re: TP changes, > * update TP, > * PR to fix integration-tests (simpler repo deps in root pom), > * check if anything else depends on Red Deer and submit PR to remove that / depend on TP instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21405) Add RedDeer 1.0.1 to target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21405?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21405: ------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Add RedDeer 1.0.1 to target platform > ------------------------------------ > > Key: JBIDE-21405 > URL: https://issues.jboss.org/browse/JBIDE-21405 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > We would like to add RedDeer 1.0.1 to target platform. > Note that we don't have 1.0.1 ready yet, it will be released soon (should be in time to make it to Beta2). Currently we have 1.0.0. But I'm creating this JIRA now to find out if anything is needed to be done for this to happen. > Github repo: https://github.com/jboss-reddeer/reddeer > Wiki: https://github.com/jboss-reddeer/reddeer/wiki > 1.0.0 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.0/ > 1.0.1 repo: http://download.jboss.org/jbosstools/updates/stable/mars/core/reddeer/1.0.1/ (not available yet) > Feature: org.jboss.reddeer.eclipse.feature > -- > Story points - 5 (fibonacci): > * send announcement email re: TP changes, > * update TP, > * PR to fix integration-tests (simpler repo deps in root pom), > * check if anything else depends on Red Deer and submit PR to remove that / depend on TP instead -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-21657: ---------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build-sites/pull/223, https://github.com/jbosstools/jbosstools-build-sites/pull/224 (was: https://github.com/jbosstools/jbosstools-build-sites/pull/223) > 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 > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > 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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21066: ---------------------------------------- [~nickboldt] no, we don't want to add any nightly bits to our TP. At least not in this case. It's too minor for that. I'm moving it out of 9.1 scope. [~snjeza] could you please investigate where it's supposed to be fixed? In Neon? What Milstone, etc. Thanks! > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21066: ----------------------------------- Fix Version/s: (was: 4.3.1.CR1) > update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm, tm.term.view.png > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016