[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19045:
------------------------------------
Please remember to add TP change JIRAs to the appropriate Epic JIRAs: JBDS-3311 (JBDS 8.1) and JBDS-3299 (JBDS 9.0).
> Update Tern.java (TP) and AngularJS (Central) IDE v.0.7
> -------------------------------------------------------
>
> Key: JBIDE-19045
> URL: https://issues.jboss.org/browse/JBIDE-19045
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central, jsp/jsf/xml/html source editing, target-platform
> Reporter: Alexey Kazakov
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.2.3.Beta1
>
>
> We are going to update Tern to v0.7.0 for 4.2.x.
> Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002)
> p2diff output:
> {code}
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4...
> < tern.eclipse.ide.tools.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.ui [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.jar [0.7.0.201412012159]
> < tern.server.nodejs [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159]
> < tern.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159]
> < tern.eclipse.ide.core [0.7.0.201412012159]
> < tern-server-nodejs-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.ui [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159]
> < tern-jsdt-feature.feature.group [0.7.0.201412012159]
> < tern-feature.feature.jar [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159]
> < tern.eclipse.ide.jsdt [0.7.0.201412012159]
> < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159]
> < tern.eclipse [0.7.0.201412012159]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.core [0.6.0.201409231610]
> > tern-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610]
> > tern.server.nodejs [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610]
> > tern-jsdt-feature.feature.jar [0.6.0.201409231610]
> > tern-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.ui [0.6.0.201409231610]
> > tern-jsdt-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610]
> > tern.eclipse [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610]
> > tern.eclipse.ide.ui [0.6.0.201409231610]
> > tern.core [0.6.0.201409231610]
> > tern-server-nodejs-feature.feature.group [0.6.0.201409231610]
> > tern.eclipse.ide.tools.core [0.6.0.201409231610]
> > tern.eclipse.ide.jsdt [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610]
> > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610]
> === Summary ===
> ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------
that is truly crappy - but I guess that is what is needed if only basic oauth is happening.
How is rhc doing it ?
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------
btw. I assume that token last for awhile and users do not need to go through this manual process everytime they log in ?
> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
> Key: JBIDE-19096
> URL: https://issues.jboss.org/browse/JBIDE-19096
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Alpha1
> Reporter: Andre Dietisheim
> Labels: connection_wizard
> Fix For: 4.3.0.Alpha1
>
> Attachments: fullauthoptions.bmml, fullauthoptions.png, screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> In order to allow us to present v2 and v3 connections we have to change the connection wizard:
> When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
> * v2 connections currently use username/password (and will most likely also allow x509, kerberos)
> * v3 connections will most likely require OAuth settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-19056) A Mojo to validate a version (compared to baseline)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19056?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19056:
---------------------------------------------
the bug is just #1, that it is not looking only on the baseline.
What you see in #2 is just that x.y.z matches but the qualifer is different and assuming it was doing it right in #1 it is expected to tell you that you should have bumped since the latest release already used the version number.
> A Mojo to validate a version (compared to baseline)
> ---------------------------------------------------
>
> Key: JBIDE-19056
> URL: https://issues.jboss.org/browse/JBIDE-19056
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.2.2.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Attachments: build.out
>
>
> We need a mojo that compares a newly-built artifact with other versions of this IU that we have already released.
> Such a mojo would fail is version isn't correct (lower than same one on that stream, equal to another one already released but with different content...)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months