May 2016 - jbosstools-issues - Jboss List Archives

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21657: --------------------------------------------- Trying to read through this - what url pattern are these PR builds going to have ? I didn't see that anywhere. > 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 > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21046) Need to implement "Bower Install" launch shortcut

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21046?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21046. ------------------------------ Verified in 4.4.0.Alpha1. > Need to implement "Bower Install" launch shortcut > ------------------------------------------------- > > Key: JBIDE-21046 > URL: https://issues.jboss.org/browse/JBIDE-21046 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > [Bower Install|http://bower.io/docs/api/#install] - Installs the project dependencies > From the user perspective it will be a launch shortcut just like existing "Bower Update" > *Steps to verify:* > - create JavaScript project > - create *bower.json* in it via *"Bower Init"* wizard; > - add some *dependencies / devDependencies* to it (e.g. grunt / angular / jquery etc.) > - *"Bower Install"* must be available via right-clicking ( bower.json / parent folder / project / editor with opened bower.json ) -> Run As -> Bower install > - After launch all *dependencies / devDependencies* must be available in bower_component folder -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21165. ------------------------------ Verified in 4.4.0.Alpha1. > Need to improve js tools (npm / bower) launch > ---------------------------------------------- > > Key: JBIDE-21165 > URL: https://issues.jboss.org/browse/JBIDE-21165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available: > {quote} > env: node: No such file or directory > {quote} > In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process. > More details can be found here: > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > Basically, this approach kills two birds with one stone: > 1. No mac os Path issue > 2. No need to have preferences for node / npm / bower > Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands > The plan is: > - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future) > - remove irrelevant code with preferences, detectors etc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20931) Build error on: jbosstools-browsersim

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20931?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20931. ------------------------------ Verified in 4.4.0.Alpha1. > Build error on: jbosstools-browsersim > ------------------------------------- > > Key: JBIDE-20931 > URL: https://issues.jboss.org/browse/JBIDE-20931 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.4.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > Steps to recreate: > git clone git@github.com:jbosstools/jbosstools-browsersim.git > cd jbosstools-browsersim/ > mvn clean install > -------------------------------------------------------- > mvn clean install > [INFO] Scanning for projects... > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base (${jbosstools-base-site}): No connector available to access repository jbosstools-base (${jbosstools-base-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [WARNING] Could not transfer metadata org.jboss.tools:parent:4.4.0.Alpha1-SNAPSHOT/maven-metadata.xml from/to jbosstools-jst (${jbosstools-jst-site}): No connector available to access repository jbosstools-jst (${jbosstools-jst-site}) of type p2 using the available factories WagonRepositoryConnectorFactory > [INFO] Computing target platform for MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6... > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bas... > [INFO] Adding repository http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-jst... > [INFO] Resolving dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml > [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.browsersim.ui 3.8.0.qualifier requires 'bundle org.eclipse.jetty.server [9.2.13,9.2.14)' but it could not be found > [ERROR] Cannot satisfy dependency: org.jboss.tools.browsersim.eclipse 3.8.0.qualifier depends on: bundle org.jboss.tools.browsersim.ui 3.7.0 > [ERROR] > [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help. > [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.browsersim.plugins:org.jboss.tools.browsersim.eclipse:3.8.0-SNAPSHOT @ /home/ldimaggi/local/redhat_git/jbosstools-browsersim/plugins/org.jboss.tools.browsersim.eclipse/pom.xml: See log for details -> [Help 1] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20919) Target Platform: add jetty 9.3.2 bundles

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20919?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20919. ------------------------------ 4.4.0.Alpha1 bundles jetty 9.3.5. Closing > Target Platform: add jetty 9.3.2 bundles > ---------------------------------------- > > Key: JBIDE-20919 > URL: https://issues.jboss.org/browse/JBIDE-20919 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha1 > > > *Reason:* Since Eclipse uses some jetty bundles v9.3.2 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > *Project page/sources:* http://www.eclipse.org/jetty/ > *Version:* 9.2.3 > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.2.v20150730/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.3.2.v20... > *Include Sources:* No > *Affected JBoss Tools components:* browsersim, cordovasim, livereload > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21104) Target Platform: update to Jetty 9.3.5 bundles

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21104?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21104. ------------------------------ Verified in 4.4.0.Alpha1. > Target Platform: update to Jetty 9.3.5 bundles > ---------------------------------------------- > > Key: JBIDE-21104 > URL: https://issues.jboss.org/browse/JBIDE-21104 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: browsersim, cordovasim, livereload, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: p2diff.jbdevstudio_jetty.txt > > > Reason: Since Eclipse Neon M3 uses some jetty bundles v9.3.5 in target platform, we need to add all required bundles to make livereload, browsersim and cordovasim works > Project page/sources: http://www.eclipse.org/jetty/ > Version: 9.3.5 > License and owner: Eclipse > Original p2 repo: http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.3.5.v20151012/ > JBoss mirror: > Include Sources: No > Affected JBoss Tools components: browsersim, cordovasim, livereload > Include in JBDS: Yes > Type of dependency: distribution > List of bundles added/removed: See attached PR -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20903) Need to split org.jboss.tools.jst.js to *.node and *.bower

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20903?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20903. ------------------------------ The code has been moved upstream. Closing. > Need to split org.jboss.tools.jst.js to *.node and *.bower > ---------------------------------------------------------- > > Key: JBIDE-20903 > URL: https://issues.jboss.org/browse/JBIDE-20903 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, nodejs > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > After some npm investigation I can claim that npm support covered in the issue description can be implemented pretty easily. However, in order to make the implementation generic I do believe that *org.jboss.tools.jst.js* plugin must be refactored. My proposal is to split it to: > * *org.jboss.tools.jst.js.node* (plugin with generic node tools launch, which will be subclassed for bower, npm etc. Node preferences + some utilities) > * *org.jsboss.tools.jst.js.bower* (bower specific stuff, will have org.jboss.tools.jst.js.node as required bundle ) > it will simplify the implementation of not only npm but also other node dependent tools (grunt, gulp etc.). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20929) "Bower Update" shortcut does nothing when launched from editor with open bower.json

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20929?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20929. ------------------------------ Verified in 4.4.0.Alpha1. > "Bower Update" shortcut does nothing when launched from editor with open bower.json > ----------------------------------------------------------------------------------- > > Key: JBIDE-20929 > URL: https://issues.jboss.org/browse/JBIDE-20929 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Steps to reproduce; > 1) create bower.json via New -> Bower Init wizard > 2) right click on the Editor with newly created bower.json file > 3) Run As -> Bower Update > ERROR: Nothing happens / external process was not launched -- 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21823: ------------------------------------------ The patch forces the default editor for now to avoid the shortcomings in the json editor. > 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] (JBIDE-21823) Unable to re-edit Service config

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21823: ------------------------------------------ Tested the happy path and the case where a user provides invalid json. Works like a charm for me. rebased and merged into master. > 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

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