[JBoss JIRA] (JBIDE-21386) Create and use Neon M5 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21386?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21386:
-------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-discovery/commit/3750aa93b7482d6..., https://github.com/jbosstools/jbosstools-target-platforms/pull/187, https://github.com/jbosstools/jbosstools-discovery/pull/323, https://github.com/jbosstools/jbosstools-target-platforms/pull/190, https://github.com/jbosstools/jbosstools-target-platforms/pull/197, https://github.com/jbosstools/jbosstools-target-platforms/pull/198 (was: https://github.com/jbosstools/jbosstools-discovery/commit/3750aa93b7482d6..., https://github.com/jbosstools/jbosstools-target-platforms/pull/187, https://github.com/jbosstools/jbosstools-discovery/pull/323, https://github.com/jbosstools/jbosstools-target-platforms/pull/190, https://github.com/jbosstools/jbosstools-target-platforms/pull/197)
> Create and use Neon M5 target platform
> --------------------------------------
>
> Key: JBIDE-21386
> URL: https://issues.jboss.org/browse/JBIDE-21386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: jbds-tp-p2diff-460-summary.txt, jbds-tp-p2diff-460.txt, jbt-tp-p2diff-460-summary.txt, jbt-tp-p2diff-460.txt, jbtcentral-p2diff_460.txt, p2diff.JBIDE-21386.summary.txt, p2diff.JBIDE-21386.txt
>
>
> Prepare TP to use Neon M5 bits. Cloned from JBIDE-20976 so I can start a fresh issue.
> https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S...
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build;
> * update install/matrix jobs to use new Eclipse JEE/platform binary;
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21864) Server Adapter: publishing is slow compared to "oc rsync" on the cmd line
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21864?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21864:
---------------------------------------------
our primary goal for this release was to get fast sync support.
if oc now supports exclusions why don't we just add that and main issue is solved according to Andre's comment ?
> Server Adapter: publishing is slow compared to "oc rsync" on the cmd line
> -------------------------------------------------------------------------
>
> Key: JBIDE-21864
> URL: https://issues.jboss.org/browse/JBIDE-21864
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.3.1.CR1
>
>
> Compared with "oc rsync" on the cmd line publishing in the server adapter (which does "oc rsync" behind the scenes) is very slow
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21869:
-----------------------------------
Assignee: Jeff Cantrill
> Encoding issue in when streaming Build Logs to the console
> ----------------------------------------------------------
>
> Key: JBIDE-21869
> URL: https://issues.jboss.org/browse/JBIDE-21869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
>
> Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
> It'll start to spew weird characters eventually :
> {noformat}
> I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
> I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
> I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
> I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
> I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
> ---> Installing application source
> ---> Building your Node application from source
> E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
> E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
> E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
> ...
> E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
> ejs(a)2.4.1 node_modules/ejs
> express(a)4.13.4 node_modules/express
> ��������� escape-html(a)1.0.3
> ��������� array-flatten(a)1.1.1
> ��������� utils-merge(a)1.0.0
> ��������� cookie-signature(a)1.0.6
> ��������� merge-descriptors(a)1.0.1
> ��������� fresh(a)0.3.0
> ��������� methods(a)1.1.2
> ��������� range-parser(a)1.0.3
> ��������� vary(a)1.0.1
> ��������� path-to-regexp(a)0.1.7
> ��������� cookie(a)0.1.5
> ��������� parseurl(a)1.3.1
> ��������� content-type(a)1.0.1
> ��������� etag(a)1.7.0
> ��������� content-disposition(a)0.5.1
> ��������� serve-static(a)1.10.2
> ��������� depd(a)1.1.0
> ��������� qs(a)4.0.0
> ��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
> ��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
> ��������� debug(a)2.2.0 (ms(a)0.7.1)
> ��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
> ��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
> ��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
> ��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
> mongodb(a)2.1.8 node_modules/mongodb
> ��������� es6-promise(a)3.0.2
> ��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
> ��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
> E0315 10:39:27.684535 1 util.go:91] npm info ok
> I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
> I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
> {noformat}
> I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-21869:
-----------------------------------
Summary: Encoding issue in when streaming Build Logs to the console
Key: JBIDE-21869
URL: https://issues.jboss.org/browse/JBIDE-21869
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Fred Bricon
Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu.
It'll start to spew weird characters eventually :
{noformat}
I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ...
I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ...
I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble"
I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run"
I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts"
---> Installing application source
---> Building your Node application from source
E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok
E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13
E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40
...
E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1
ejs(a)2.4.1 node_modules/ejs
express(a)4.13.4 node_modules/express
��������� escape-html(a)1.0.3
��������� array-flatten(a)1.1.1
��������� utils-merge(a)1.0.0
��������� cookie-signature(a)1.0.6
��������� merge-descriptors(a)1.0.1
��������� fresh(a)0.3.0
��������� methods(a)1.1.2
��������� range-parser(a)1.0.3
��������� vary(a)1.0.1
��������� path-to-regexp(a)0.1.7
��������� cookie(a)0.1.5
��������� parseurl(a)1.3.1
��������� content-type(a)1.0.1
��������� etag(a)1.7.0
��������� content-disposition(a)0.5.1
��������� serve-static(a)1.10.2
��������� depd(a)1.1.0
��������� qs(a)4.0.0
��������� finalhandler(a)0.4.1 (unpipe(a)1.0.0)
��������� on-finished(a)2.3.0 (ee-first(a)1.1.1)
��������� debug(a)2.2.0 (ms(a)0.7.1)
��������� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5)
��������� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1)
��������� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10)
��������� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10)
mongodb(a)2.1.8 node_modules/mongodb
��������� es6-promise(a)3.0.2
��������� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0)
��������� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2)
E0315 10:39:27.684535 1 util.go:91] npm info ok
I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image
I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ...
{noformat}
I'm running on OSX
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21840:
------------------------------------------
[~scabanovich] I tested your PR. It doesnt work for me:
The credentials were stored to the secure storage:
!secure-storage.png!
but the editing wizard still isnt checking the checkbox:
!edit-connection-wizard.png!
What am I missing?
> Checkbox to save password in Secure Storage is not checked when password is stored
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21840
> URL: https://issues.jboss.org/browse/JBIDE-21840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: edit-connection-wizard.png, secure-storage.png
>
>
> In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21840) Checkbox to save password in Secure Storage is not checked when password is stored
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21840?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21840:
-------------------------------------
Attachment: edit-connection-wizard.png
secure-storage.png
> Checkbox to save password in Secure Storage is not checked when password is stored
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21840
> URL: https://issues.jboss.org/browse/JBIDE-21840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: edit-connection-wizard.png, secure-storage.png
>
>
> In OpenShift connection wizard there is a checkbox to store password/token in secure storage. If I choose on an existing OpenShift 3 connection with basic authentication to store password in secure storage, technically it is stored and visible on Secure Storage preference page, but in Connection wizard it is not visible. Upon next opening of the Edit Connection wizard, checkbox is unchecked although password is checked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21793) Zero-click import of CDK
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21793?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21793.
-------------------------------
Verified with latest nightly JBDS 9.1.0, installed with the installer built from (2016-03-15) source.
> Zero-click import of CDK
> ------------------------
>
> Key: JBIDE-21793
> URL: https://issues.jboss.org/browse/JBIDE-21793
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Pete Muir
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When the installer with the CDK completes and JBDS opens, the runtime detection dialog shows up asking the user if he wants to create a CDK server.
> We should try to import the CDK with no-clicks, and hide the detection dialog.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years