June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22472) Improve UI of per-module zip settings

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22472?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22472: -------------------------------- Story Points: 3 > Improve UI of per-module zip settings > ------------------------------------- > > Key: JBIDE-22472 > URL: https://issues.jboss.org/browse/JBIDE-22472 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > This is a follow up of JBIDE-22157 and JBIDE-20577. > When you were implementing JBIDE-22157, you asked me for feedback which I gave you but there was no further reply from you: > https://github.com/jbosstools/jbosstools-server/pull/412 > {quote} > what happens if I select to zip all? the new column does not apply then? it would be good to make this obvious somehow. > also, could it be a checkbox instead of false/true? > {quote} > 1) Could we have checkboxes instead of true/false? > 2) On a new server adapter, a "false" actually means "see default above" - once you change the default to compress all, each "false" will change to "true". But once you change a module to true and then back to false, changing the default will no longer affect the module settings anymore. This is counter intuitive. > So what would make more sense in my opinion is to have checkboxes for each module and then perhaps a link called "all" at the column header? And get rid of the default settings? What do you think? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20036) As I user I want to be able to add image streams to my project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20036?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20036: ------------------------------------------ [~jcantrill] whats your current take on this? Do you still think that there's limited value in this? Isnt the ability in Docker tooling to push to the Docker registry on OpenShift getting very close to this? > As I user I want to be able to add image streams to my project > -------------------------------------------------------------- > > Key: JBIDE-20036 > URL: https://issues.jboss.org/browse/JBIDE-20036 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.x > > > When creating a new application via templates I am required to have the docker images (base builder image etc.) to be available. Otherwise the build wont succeed. > You can see this in the instrcutions for the eap templates where the steps to create an app via those templates are 2: create the image streams & create the app via the templates: > https://github.com/adietish/application-templates/blob/master/README.md > {code} > $ osc create -n yourproject -f jboss-image-streams.json > $ osc process -n yourproject -f eap/eap6-basic-sti.json -v APPLICATION_NAME=helloworld,APPLICATION_HOSTNAME=helloworld.yourproject.l... | osc create -n yourproject -f - > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-18) Support for Docker Compose [EBZ#479592]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-18?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-18: ----------------------------- Issue Type: Feature Request (was: Task) > Support for Docker Compose [EBZ#479592] > --------------------------------------- > > Key: ERT-18 > URL: https://issues.jboss.org/browse/ERT-18 > Project: Eclipse Release Train > Issue Type: Feature Request > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Oxygen (4.7) > > > Would suggest to support Docker Compose support in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3934) Uninstall process results in odd things

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3934?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3934. ----------------------------- Noone seems to have any objections, therefore closing as rejected. > Uninstall process results in odd things > --------------------------------------- > > Key: JBDS-3934 > URL: https://issues.jboss.org/browse/JBDS-3934 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.0.0.GA > Environment: Fedora 23 > Reporter: Misha Ali > Assignee: Alexey Kazakov > Fix For: 10.0.0.GA > > Attachments: error.log, uninstall.png, uninstalled_but_running.png > > > I've tried to uninstall devstudio 10 GA a few times and got odd results. I'm trying to replicate one of the odd results, so I'll talk about the really odd one I just encountered: > 1. Uninstalling by selecting both the the eclipse test instance and devstudio 10 results in restarting devstudio but without these two components available to uninstall. Surely uninstall should just remove devstudio and then exit devstudio. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22474) jboss.org.schema tasks

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22474?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22474: -------------------------------- Story Points: 10 > jboss.org.schema tasks > ---------------------- > > Key: JBIDE-22474 > URL: https://issues.jboss.org/browse/JBIDE-22474 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, server, upstream > Affects Versions: 4.4.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > > Since workflow is still being figured out, please see http://etherpad.corp.redhat.com/jboss-org-schema for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20051) As a I user I want to be able to automatically install webhooks into my GitHub repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20051?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20051: ------------------------------------- Original Estimate: 4 days Remaining Estimate: 4 days > As a I user I want to be able to automatically install webhooks into my GitHub repository > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20051 > URL: https://issues.jboss.org/browse/JBIDE-20051 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.4.x > > Original Estimate: 4 days > Remaining Estimate: 4 days > > I want to be able to automatically install webhooks into my github repository from Eclipse. > We can detect if a project has a github url. > We can probably detect the user github credentials, or ask the user his credentials before trying to install the webhook. > There must be a GitHub API that allows to then add webhooks automatically. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-148) Add support for custom Dockerfile name to build an image [EBZ#481093]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-148?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-148: ------------------------------ Story Points: 5 > Add support for custom Dockerfile name to build an image [EBZ#481093] > --------------------------------------------------------------------- > > Key: ERT-148 > URL: https://issues.jboss.org/browse/ERT-148 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Neon.1 (4.6) > > > Docker supports custom Dockerfile names to build an image but this feature requires Docker Java client version 3.1.3 or higher (see https://github.com/spotify/docker-client/commit/b3b7371d7e6410e5c8b17cf7d...) > See bug 474196 for support for other options. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ERT-18) Support for Docker Compose [EBZ#479592]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-18?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-18: ----------------------------- Story Points: 40 (was: 20) > Support for Docker Compose [EBZ#479592] > --------------------------------------- > > Key: ERT-18 > URL: https://issues.jboss.org/browse/ERT-18 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Oxygen (4.7) > > > Would suggest to support Docker Compose support in eclipse -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22552) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22552?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22552: ----------------------------------- Sprint: devex #116 June 2017 > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 > ------------------------------------------------ > > Key: JBIDE-22552 > URL: https://issues.jboss.org/browse/JBIDE-22552 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3930 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22283) reveng *.java emitter does not escape java keyword 'return' as variable name

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22283?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22283: -------------------------------- Sprint: (was: devex #115 May 2016) > reveng *.java emitter does not escape java keyword 'return' as variable name > ---------------------------------------------------------------------------- > > Key: JBIDE-22283 > URL: https://issues.jboss.org/browse/JBIDE-22283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.3.x > Environment: Eclipse Mars > Reporter: Darryl Miles > Assignee: Koen Aers > Fix For: 4.4.x > > > reveng *.java emitter does not escape java keyword 'return' as variable name > <table name="oc_return_history"> > <foreign-key constraint-name="FK_oc_return_history__return_id" foreign-table="oc_return"> > <column-ref local-column="return_id" foreign-column="return_id"/> >  > <many-to-one property="return"/> > </foreign-key> > </table> > The expected output would be: > private Return _return; > but actual output is: > private Return return; -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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