[JBoss JIRA] (JBIDE-20054) Connection wizard: Cannot remove secure storage of v3 connection token
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20054?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20054:
---------------------------------------
[~mlabuda] [~adietish] I believe this to only be a UI error. In my tests, if I uncheck save and then check the storage I see there is no token associated with the given server and ID. Additionally, I restarted and check the storage to confirm it wasn't being saved on exit and confirmed the token is not there. The only issue that I believe exists is the 'remember' checkbox is not properly databound to the value in the connection. I will make a fix for that.
> Connection wizard: Cannot remove secure storage of v3 connection token
> ----------------------------------------------------------------------
>
> Key: JBIDE-20054
> URL: https://issues.jboss.org/browse/JBIDE-20054
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> If I create a new v3 connection with OAuth authentization method and choose to store token in secure storage (or I edit the existing one connection with token and check the checkbox to store the token in secure storage), token is stored. But if I decide later to prevent it to being stored by unchecking the checkbox in Edit connection dialog, it does not work. If I uncheck the checbox and hit the Finish button and come back to edit connection dialog, the checkbox is still checked. This is related only to OAuth authentization method (basic authentization method works as expected).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20141) Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20141?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20141:
------------------------------------
So, even though "nightly" is a misnomer (not an accurate description since things are *NOT* built every night), you would rather stick with */updates/nightly/* instead of the new, more accurate and consistent pattern of */snapshots/updates/*.
Am I parsing you correctly?
> Define which vanity URLs to use for publishing JBT/JBDS nightlies & dev sites
> -----------------------------------------------------------------------------
>
> Key: JBIDE-20141
> URL: https://issues.jboss.org/browse/JBIDE-20141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> Today, we produce a lot of artifacts w/ every CI (snapshot), staging, development, & stable build.
> But sometimes, finding these artifacts can be a daunting task.
> Below are some URLs where things can be found.
> *CI builds / SNAPSHOTS / nightlies*
> * http://download.jboss.org/jbosstools/updates/nightly/master/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/updates/nightly/mars -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central, *OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/nightly/updates/ -> ../../mars/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/ (composite of Core + Central)
> * http://download.jboss.org/jbosstools/mars/snapshots/updates/ (individual projects' update sites)
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/master/
> ** http://download.jboss.org/jbosstools/mars/snapshots/updates/webtools/4.3....
> ** ..
> * http://download.jboss.org/jbosstools/mars/snapshots/builds/ (individual timestamped CI builds)
> *Staging Sites*
> * http://download.jboss.org/jbosstools/mars/staging/builds/
> * http://download.jboss.org/jbosstools/mars/staging/updates/
> *Development Milestones*
> * http://download.jboss.org/jbosstools/updates/development/mars/ -> ../../mars/development/updates/ (*OLD URL PATTERN*)
> * http://download.jboss.org/jbosstools/mars/development/updates/ (composites & content that isn't *static*)
> * http://download.jboss.org/jbosstools/static/mars/development/updates/ (actual update sites, moved here for Akamai performance)
> ----
> For JBDS, we follow the same pattern as above but use https://devstudio.redhat.com/9.0/ instead of http://download.jboss.org/jbosstools/mars/ ... but we also have a /builds/installer/ folder because the public JBDS site now includes the standalone installer:
> * https://devstudio.redhat.com/9.0/development/builds/installer/
> Also, for JBDS we don't have to differentiate between /static/ and non-static content, since Akamai set up the entire server to be mirrored to their servers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20156) Connection wizard: can't create new v3 application when launching wizard from Central
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20156?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-20156.
--------------------------------------
Resolution: Duplicate Issue
> Connection wizard: can't create new v3 application when launching wizard from Central
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-20156
> URL: https://issues.jboss.org/browse/JBIDE-20156
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Ma Deshuai
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: login.png
>
>
> OpenShift plug version:
> 3.0.0.Beta2-v20150623-1035-B854
> Steps:
> 1. Open the login dialog from "JBoss Central" -> "OpenShift Application"
> 2. In the login dialog, set server type to "OpenShift v3", set the protocol to "Basic"
> 3. Input userName and Password.
> 4. Click "Next" button
> Expect result:
> Step4 : The "Next" button should enabled.
> Actual result:
> Step4 : The "Next" button is always disabled. so I can't connect to v3.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19757 at 6/29/15 9:52 AM:
-------------------------------------------------------------
{quote}the difference between optimized site and general one is at minimum 20 seconds {quote}
No, you read that wrong. The difference between using the JBT webtools-site for Luna (4.2.3.Final) and the JBT site for Mars (4.3.0.Beta1) is 10 seconds. I don't have data for the 4.3.0.Alpha1 site.
Note that the JBT webtools-site for Mars (4.3.0.Beta1) and the JBT webtools-site for Mars (4.3.0.Alpha2) don't work because of new dependencies from Server to Base which no one communicated to me (dev, releng failure), no one verified worked (dev, releng, QE faiulre). So, for Beta1 we have two choices:
* use the full JBT site for Mars (4.3.0.Beta1), which is 10 seconds longer to use, end-to-end
* rebuild the JBT webtools-site for Mars (4.3.0.Beta1 respin-d)
{quote}But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/{quote}
Yes, it's marginally slower. But at least now it WORKS without having to first install JBT or JBDS to resolve the missing common.jdt dependencies.
was (Author: nickboldt):
{quote}the difference between optimized site and general one is at minimum 20 seconds {quote}
No, you read that wrong. The difference between using the JBT webtools-site for Luna (4.2.3.Final) and the JBT site for Mars (4.3.0.Beta1) is 10 seconds. I don't have data for the 4.3.0.Alpha1 site.
Note that the JBT webtools-site for Mars (4.3.0.Beta1) and the JBT webtools-site for Mars (4.3.0.Alpha2) don't work because of new dependencies from Server to Base which no one communicated to me (dev, releng failure), no one verified worked (dev, releng, QE faiulre). So, for Beta1 we have two choices:
* use the full JBT site for Mars (4.3.0.Beta1), which is 10 seconds longer to use, end-to-end
* rebuild the JBT webtools-site for Mars (4.3.0.Beta1 respin-d)
{quote}But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/{quote}
Yes, it's marginally slower. But at least now it WORKS without having to first install JBT or JBDS.
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Labels: releasework
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19757 at 6/29/15 9:51 AM:
-------------------------------------------------------------
{quote}the difference between optimized site and general one is at minimum 20 seconds {quote}
No, you read that wrong. The difference between using the JBT webtools-site for Luna (4.2.3.Final) and the JBT site for Mars (4.3.0.Beta1) is 10 seconds. I don't have data for the 4.3.0.Alpha1 site.
Note that the JBT webtools-site for Mars (4.3.0.Beta1) and the JBT webtools-site for Mars (4.3.0.Alpha2) don't work because of new dependencies from Server to Base which no one communicated to me (dev, releng failure), no one verified worked (dev, releng, QE faiulre). So, for Beta1 we have two choices:
* use the full JBT site for Mars (4.3.0.Beta1), which is 10 seconds longer to use, end-to-end
* rebuild the JBT webtools-site for Mars (4.3.0.Beta1 respin-d)
{quote}But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/{quote}
Yes, it's marginally slower. But at least now it WORKS without having to first install JBT or JBDS.
was (Author: nickboldt):
{quote}the difference between optimized site and general one is at minimum 20 seconds {quote}
No, you read that wrong. The difference between using the JBT webtools-site for Luna (4.2.3.Final) and the JBT site for Mars (4.3.0.Beta1) is 10 seconds. I don't have data for the 4.3.0.Alpha1 site.
Note that the JBT webtools-site for Mars (4.3.0.Beta1) and the JBT webtools-site for Mars (4.3.0.Alpha2) don't work because of new dependencies from Server to Base which no one communicated to me (dev, releng failure), no one verified worked (dev, releng, QE faiulre). So, for Beta1 we have two choices:
* use the full JBT site for Mars (4.3.0.Beta1), which is 10 seconds longer to use, end-to-end
* rebuild the JBT webtools-site for Mars (4.3.0.Beta1 respin-d)
{quote}But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/{quote}
Yes.
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Labels: releasework
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19757:
------------------------------------
{quote}the difference between optimized site and general one is at minimum 20 seconds {quote}
No, you read that wrong. The difference between using the JBT webtools-site for Luna (4.2.3.Final) and the JBT site for Mars (4.3.0.Beta1) is 10 seconds. I don't have data for the 4.3.0.Alpha1 site.
Note that the JBT webtools-site for Mars (4.3.0.Beta1) and the JBT webtools-site for Mars (4.3.0.Alpha2) don't work because of new dependencies from Server to Base which no one communicated to me (dev, releng failure), no one verified worked (dev, releng, QE faiulre). So, for Beta1 we have two choices:
* use the full JBT site for Mars (4.3.0.Beta1), which is 10 seconds longer to use, end-to-end
* rebuild the JBT webtools-site for Mars (4.3.0.Beta1 respin-d)
{quote}But I read this as this is how we got it setup now for Mars Beta1 ? (slower install times for the wtp server adapter, correct?) Then i'll got try and see what happens and see how it actually feels - but 5s extra to wait for it to popup and then 15s+ for install is not nice ;/{quote}
Yes.
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Minor
> Labels: releasework
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20096) Application wizard: creating eap-simple from templates and show in browser tries to open 'eap.local'
by Paul Weil (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20096?page=com.atlassian.jira.plugi... ]
Paul Weil commented on JBIDE-20096:
-----------------------------------
External DNS for V3 is still the user's responsibility at this point. The way this currently works with routes is:
1. If a user specifies a Host in the route the route will be created with that host used as a key (via http headers or sni) to direct traffic from the router to the backends
2. If the user does not specify a Host in the route a host will be created for them using a configurable post fix (this is configurable in the master.yaml). External DNS is still up to the user, however in future use cases we will be able to register a wildcard DNS entry based on the postfix to direct to the router(s) to provide default DNS services for generated routes.
The sentence in the document pointed out above looks a bit misleading. I will update it.
> Application wizard: creating eap-simple from templates and show in browser tries to open 'eap.local'
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20096
> URL: https://issues.jboss.org/browse/JBIDE-20096
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> not sure what is to "blame" here but creating app from https://github.com/jboss-openshift/application-templates/blob/master/eap/... (v3beta1) results in app getting created but show in browser wants me to go to "eap.local" which pretty sure that is not something that exist from the outside.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months