May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22309) When an Openshift application is created from a builder image, Git reference and context dir are ignored

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22309?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22309: ---------------------------------- Story Points: 2 Sprint: devex #114 May 2017 Assignee: Jeff MAURY > When an Openshift application is created from a builder image, Git reference and context dir are ignored > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22309 > URL: https://issues.jboss.org/browse/JBIDE-22309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.x > > > When you created a new Openshift application from a builder image, the Git reference (branch) and context dir are ignored ie if your modify them then the value from the builder will be taken. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3877: ----------------------------------- Closing the project/package/navigator views during import might also be helpful > can't import bigger maven/git project to jbds > --------------------------------------------- > > Key: JBDS-3877 > URL: https://issues.jboss.org/browse/JBDS-3877 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: maven > Affects Versions: 9.1.0.GA > Reporter: Josef Ludvicek > Assignee: Viacheslav Kabanovich > Fix For: 10.x > > Attachments: jbds-error.png, jbds-import-camel-stuck.png, jbds-import-camel1.png, jbds-thread-tump.tdump, log.log, stdout.txt > > > JBDS can't import sources of Apache Camel (maven project) > https://github.com/apache/camel > Steps to reproduce: > Clone it's git repo > {code} > git clone git@github.com:apache/camel.git > {code} > In jbds File -> Import Existing maven project > Unselect "resolve workspace projects" > Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23) > Wait for error message (~20 minutes) > {code} > An internal error occurred during: "Importing Maven projects". > Java heap space > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22309) When an Openshift application is created from a builder image, Git reference and context dir are ignored

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22309: ---------------------------------- Summary: When an Openshift application is created from a builder image, Git reference and context dir are ignored Key: JBIDE-22309 URL: https://issues.jboss.org/browse/JBIDE-22309 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Jeff MAURY Fix For: 4.4.x When you created a new Openshift application from a builder image, the Git reference (branch) and context dir are ignored ie if your modify them then the value from the builder will be taken. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-696) Update BPEL feature to 1.3.101.Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-696?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-696: -------------------------------- Assignee: Paul Leacu > Update BPEL feature to 1.3.101.Final > ------------------------------------ > > Key: JBTIS-696 > URL: https://issues.jboss.org/browse/JBTIS-696 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPEL, distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > The BPEL editor cannot be updated if a user installs it from JBDS-IS 8.0.2.GA and earlier. For more information please see JBTIS-470. > Note that there is no change in BPEL editor the only problem is that it is not automatically updated from 1.0.4 (JBDS-IS 8.0.2) to 1.0.5 (JBDS-IS 8.0.3+) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-179) StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-179: --------------------------------------- Summary: StructuredTextEditor does not allow for custom IDocumentProvider [EBZ#493145] Key: ERT-179 URL: https://issues.jboss.org/browse/ERT-179 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Priority: Critical I have a custom IDocumentProvider that is used to get events from the text editor framework (document loaded, modified, closed). The StructuredTextEditor does not call all methods on my implementation because it uses its own internal document provider. I think this would be great to support that -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21823: -------------------------------- Component/s: upstream > Unable to re-edit Service config > -------------------------------- > > Key: JBIDE-21823 > URL: https://issues.jboss.org/browse/JBIDE-21823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff MAURY > Fix For: 4.4.0.Alpha2 > > > Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes. > Steps to reproduce: > - select a service in the OpenShift Explorer > - click on the {{Edit...}} command. > - in the JSON editor for the service config, note the resource version. Eg: > {code} > { > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38301", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > }, > ... > {code} > - make some changes and save > - the service config version should have incremented: > {code} > { > "kind" : "Service", > "apiVersion" : "v1", > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38390", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > } > .... > {code} > - close the config editor > - re-open the config editor > *ASSERT: the editor displays the latest config* > *FAIL the editor displays the initial config* > *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version* > {code} > Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource jee-sample: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "jee-sample", > "kind": "services" > }, > "code": 409 > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-697) doTry blocks disappearing in Camel Blueprint.xml

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-697?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBTIS-697: -------------------------------- Assignee: Lars Heinemann > doTry blocks disappearing in Camel Blueprint.xml > ------------------------------------------------ > > Key: JBTIS-697 > URL: https://issues.jboss.org/browse/JBTIS-697 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 9.0.0.GA > Environment: Using JBDS with the integration pack. > Developing camel routes with Blueprint XML. > Reporter: Michael Thirion > Assignee: Lars Heinemann > > During the edition of the Camel's blueprint.xml file, when switching from "design" view to "source" view, the doTry blocks with their content totally disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3844) JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3844?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3844: ----------------------------------- Can you try to build it from command line, with Maven 3.3.9? > JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment. > -------------------------------------------------------------------------------------------------- > > Key: JBDS-3844 > URL: https://issues.jboss.org/browse/JBDS-3844 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.GA > Environment: ALL > Reporter: Chandra Shekhar Pandey > Assignee: Nick Boldt > Attachments: TestProjectin_JBDS9.zip > > > - Testing in a offline environment with Fuse 6.2.1 offline repository from https://access.redhat.com/solutions/1599973. > - A simple Fuse project when built within JBDS 9.0 GA with java8 in offline mode tries to download maven repository with version 2.0.7. Ultimately fails as 2.0.7 is not available in offline repository and internet is not available. > - Same project when built with JBDS 8.1 and java7 in offline mode with offline repository as above, is able to build successfully as 2.0.6 maven dependencies are already available in offline repo, thus no need to download. > - Why JBDS 9.0 is searching for maven dependencies with 2.0.7 version ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-698) JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-698?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-698: ----------------------------- Project: JBoss Tools Integration Stack (was: Red Hat Developer Studio (DevStudio)) Key: JBTIS-698 (was: JBDS-3844) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: Fuse IDE (was: build) Affects Version/s: 9.0.0.GA (was: 9.0.0.GA) > JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment. > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-698 > URL: https://issues.jboss.org/browse/JBTIS-698 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 9.0.0.GA > Environment: ALL > Reporter: Chandra Shekhar Pandey > Assignee: Nick Boldt > Attachments: TestProjectin_JBDS9.zip > > > - Testing in a offline environment with Fuse 6.2.1 offline repository from https://access.redhat.com/solutions/1599973. > - A simple Fuse project when built within JBDS 9.0 GA with java8 in offline mode tries to download maven repository with version 2.0.7. Ultimately fails as 2.0.7 is not available in offline repository and internet is not available. > - Same project when built with JBDS 8.1 and java7 in offline mode with offline repository as above, is able to build successfully as 2.0.6 maven dependencies are already available in offline repo, thus no need to download. > - Why JBDS 9.0 is searching for maven dependencies with 2.0.7 version ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-698) JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-698?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBTIS-698: -------------------------------- Assignee: Lars Heinemann (was: Nick Boldt) > JBDS 9 with java 8 tries to download maven dependencies with version 2.0.7 in offline environment. > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-698 > URL: https://issues.jboss.org/browse/JBTIS-698 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 9.0.0.GA > Environment: ALL > Reporter: Chandra Shekhar Pandey > Assignee: Lars Heinemann > Attachments: TestProjectin_JBDS9.zip > > > - Testing in a offline environment with Fuse 6.2.1 offline repository from https://access.redhat.com/solutions/1599973. > - A simple Fuse project when built within JBDS 9.0 GA with java8 in offline mode tries to download maven repository with version 2.0.7. Ultimately fails as 2.0.7 is not available in offline repository and internet is not available. > - Same project when built with JBDS 8.1 and java7 in offline mode with offline repository as above, is able to build successfully as 2.0.6 maven dependencies are already available in offline repo, thus no need to download. > - Why JBDS 9.0 is searching for maven dependencies with 2.0.7 version ? -- 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 May 2016