February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3593) Consider continuous delivery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3593: ----------------------------- Fix Version/s: 10.0.0.Alpha1 > Consider continuous delivery > ---------------------------- > > Key: JBDS-3593 > URL: https://issues.jboss.org/browse/JBDS-3593 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 10.0.0.Alpha1 > > > A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective). > If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt. > I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3593) Consider continuous delivery

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3593?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3593: ----------------------------- Priority: Blocker (was: Major) > Consider continuous delivery > ---------------------------- > > Key: JBDS-3593 > URL: https://issues.jboss.org/browse/JBDS-3593 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: build > Affects Versions: 10.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > > A continuous delivery build is about setting up the necessary checks to make sure that a "snapshot" is in a good enough state to be released (from a releng perspective). > If we have this, then it means that planning can be changed to whatever strategy; without requiring any specific effort to adapt. > I bootstrapped a CI job to start "hosting" all those quality checks: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21719: ------------------------------- Affects Version/s: 4.3.1.Beta2 > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Fix For: 4.3.x > > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21719 at 2/19/16 9:16 AM: ------------------------------------------------------------- Can't the user just move the view into another location, or enable a different Perspective? Maybe we want to have a Camel/BPMN/Integration Stack perspective that's installed as part of the JBDS IS feature(s) ? was (Author: nickboldt): Can't the user just move the view into another location, or enable a different Perspective? > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Fix For: 4.3.x > > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21719: ------------------------------------ Can't the user just move the view into another location, or enable a different Perspective? > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Fix For: 4.3.x > > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21684) jaxws quickstarts require nonexistant endorsed folder

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21684?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21684: ----------------------------------- Assignee: Rafael Benevides > jaxws quickstarts require nonexistant endorsed folder > ----------------------------------------------------- > > Key: JBIDE-21684 > URL: https://issues.jboss.org/browse/JBIDE-21684 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rafael Benevides > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > The jaxws quickstarts in the 10.x branch have the following errors: > Endorsed directory '/home/rob/code/github/jboss_stuff/quickstart/jaxws-ejb/service/target/endorsed' is missing. You may need to a perform a > Maven command line build in order to create it. > Even after building from the command line, the requested folders are not created. This indicates that either there is something wrong with the build (ie it should be creating the endorsed folder) or this is a legacy detail that is no longer needed (ie the project does not actually require an endorsed directory, so the pom lines requesting it are unnecessary) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21719: ------------------------------- Fix Version/s: 4.3.x > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Fix For: 4.3.x > > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21684) jaxws quickstarts require nonexistant endorsed folder

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21684?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21684: ------------------------------------- [~rafabene] looking at https://github.com/wildfly/quickstart/search?utf8=%E2%9C%93&q=endorsed, it seems to me the jaxws examples can remove the endorsed lib definition > jaxws quickstarts require nonexistant endorsed folder > ----------------------------------------------------- > > Key: JBIDE-21684 > URL: https://issues.jboss.org/browse/JBIDE-21684 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > The jaxws quickstarts in the 10.x branch have the following errors: > Endorsed directory '/home/rob/code/github/jboss_stuff/quickstart/jaxws-ejb/service/target/endorsed' is missing. You may need to a perform a > Maven command line build in order to create it. > Even after building from the command line, the requested folders are not created. This indicates that either there is something wrong with the build (ie it should be creating the endorsed folder) or this is a legacy detail that is no longer needed (ie the project does not actually require an endorsed directory, so the pom lines requesting it are unnecessary) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21715) Unable to deploy image because a deployment (replication controller) does not exist

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21715?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21715: ------------------------------------------ [~fbricon][~jcantrill] sure, deployed the client lib to maven repo. > Unable to deploy image because a deployment (replication controller) does not exist > ----------------------------------------------------------------------------------- > > Key: JBIDE-21715 > URL: https://issues.jboss.org/browse/JBIDE-21715 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > Deploying an image creates a set of resources but trying to manually trigger a deployment throws an exception: http://screencast.com/t/gz8quBbAboGg > This presumably could be a case where we are trying to tigger assuming a deployment exists but one doesnt because: > a) its building and hasnt triggered one yet > b) the built image exists but there is some other reason that prevents the imagechangetrigger > We should still be able to trigger a build using the dc provided OpenShift is able to access the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Andrej Podhradsky updated JBIDE-21719: -------------------------------------- Component/s: build > Move Properties view to its previous position > --------------------------------------------- > > Key: JBIDE-21719 > URL: https://issues.jboss.org/browse/JBIDE-21719 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Environment: JBDS 9.1.0.Beta2 > JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build) > Reporter: Andrej Podhradsky > Priority: Minor > Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png > > > I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png). -- 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