May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-182) hot swap does not if the Node.js main file is not in the project root [EBZ#493160]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-182: --------------------------------------- Summary: hot swap does not if the Node.js main file is not in the project root [EBZ#493160] Key: ERT-182 URL: https://issues.jboss.org/browse/ERT-182 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Fix For: Neon (4.6) RC1 For now hot swap works only if the Node.js main file located in the root of the project. Debugging app from sub-folders doesn't work due to incorrect source mapping setup -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-182) hot swap does not if the Node.js main file is not in the project root [EBZ#493160]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-182?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-182. ------------------------------------- Resolution: Done > hot swap does not if the Node.js main file is not in the project root [EBZ#493160] > ---------------------------------------------------------------------------------- > > Key: ERT-182 > URL: https://issues.jboss.org/browse/ERT-182 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: 3.8_RC1, Debug, bzira > Fix For: Neon (4.6) RC1 > > > For now hot swap works only if the Node.js main file located in the root of the project. Debugging app from sub-folders doesn't work due to incorrect source mapping setup -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22314) Define Docker registry URL for an OpenShift connection

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22314?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-22314: ------------------------------------------- I created this issue in adb-utils to discuss/track the issue - https://github.com/projectatomic/adb-utils/issues/113 > Define Docker registry URL for an OpenShift connection > ------------------------------------------------------ > > Key: JBIDE-22314 > URL: https://issues.jboss.org/browse/JBIDE-22314 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > When deploying a docker image to openshift, we'll need to know where to push the docker image to. > That docker registry url could be set from the OpenShift Connection wizard, in an advanced section. > For the CDK, that url (hub.openshift.rhel-cdk.10.1.2.2.xip.io) is defined in a docker-registry route in the default project, which only admin can have access to. I don't know of any way to access that URL for a non-admin. Perhaps that url could be/is exposed by the vagrant service manager plugin? [~hardy.ferentschik]? [~rob.stryker]? > In any case, an other url could be defined manually for non-CDK-based openshift instances -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22314) Define Docker registry URL for an OpenShift connection

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22314?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-22314: ------------------------------------------- I guess there are two ways to go about this. # Add the openshift-dev to the cluster:readers (or similar) group. Preferably we make sure that any basic user on the CDK would have the same privileges. This might be helpful for other resources the dev might want to view. # Extend the _vagrant-service-manager_ plugin to expose the registry information as well, eg as part of {{vagrant service-manager env openshift}}. > Define Docker registry URL for an OpenShift connection > ------------------------------------------------------ > > Key: JBIDE-22314 > URL: https://issues.jboss.org/browse/JBIDE-22314 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha2 > > > When deploying a docker image to openshift, we'll need to know where to push the docker image to. > That docker registry url could be set from the OpenShift Connection wizard, in an advanced section. > For the CDK, that url (hub.openshift.rhel-cdk.10.1.2.2.xip.io) is defined in a docker-registry route in the default project, which only admin can have access to. I don't know of any way to access that URL for a non-admin. Perhaps that url could be/is exposed by the vagrant service manager plugin? [~hardy.ferentschik]? [~rob.stryker]? > In any case, an other url could be defined manually for non-CDK-based openshift instances -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-694) Update drools test suite

by Tomas David (JIRA)

[ https://issues.jboss.org/browse/JBTIS-694?page=com.atlassian.jira.plugin.... ] Tomas David updated JBTIS-694: ------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/711 > Update drools test suite > ------------------------ > > Key: JBTIS-694 > URL: https://issues.jboss.org/browse/JBTIS-694 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.3.0.Final > Reporter: Tomas David > Assignee: Tomas David > > This task consists from these subtasks: > * remove brms 5 tests > * remove unused annotations > * remove unused groups > * replace wait method with reddeer AbstractWait > * reorganize test packages > * use drools naming instead of brms -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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: --------------------------------------------- [~mickael_istria] if we don't publish the topic branch updatesite how would QE or others try it out without having to build it ? That said I don't think this should require much more than just a flag to state where things get deployed. So I don't understand the added complexity neither. > 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-21861) Include Docker tooling 2.0.0 in JBT 4.4.x TP

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21861?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21861: --------------------------------------------- I would say the UI is quite different. We don't push the views much, we push the docker explorer since it is much less invasive. In Vagrant tooling there is no Explorer but it has this easy start/stop toolbar button. This is not a bad thing IMO - since the way you work with these techs are different. I'm +1 on adding vagrant in, but we should check it actually works well with the CDK related tooling which currently do not use the vagrant integration from this. > Include Docker tooling 2.0.0 in JBT 4.4.x TP > -------------------------------------------- > > Key: JBIDE-21861 > URL: https://issues.jboss.org/browse/JBIDE-21861 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha2 > > > Include Docker tooling 2.0.0 in Target Platform 4.60.x, targeting JBoss Tools 4.4.x -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22317: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-22317: ----------------------------------- Sprint: devex #114 May 2016 Adding to sprint as it is a blocker. > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22317) Cannot build jbosstools-central locally

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22317?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22317: ---------------------------------------- [~fbricon]: are we missing a reference to a repository? Should this artifact be available remotely? > Cannot build jbosstools-central locally > --------------------------------------- > > Key: JBIDE-22317 > URL: https://issues.jboss.org/browse/JBIDE-22317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central > Affects Versions: 4.4.0.Alpha1 > Reporter: Mickael Istria > Priority: Blocker > > With a clean jbosstools-central, "mvn clean verify" fails locally with > {code} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.7:copy (copy-central-webpage) on project org.jboss.tools.central: Unable to find artifact. Could not find artifact org.jboss.tools.central:jbosstools-central-webpage:zip:2.0.0-SNAPSHOT in jboss-public-repository-group (http://repository.jboss.org/nexus/content/groups/public/) > [ERROR] > {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